About Requirement Proxies

The requirements created in or added from an external requirements management system are displayed as a requirement proxy in Traceable Requirements Management, the Requirements Structure Editor, or the Requirements Specification Editor. The commands to create or add existing requirements from external requirements management systems as a requirement proxy are available from the requirement context menu in the Requirements Structure Editor and the Requirements Specification Editor. You cannot import, export, create, remove, or add existing requirements from external requirements management systems as a requirement proxy in Traceable Requirements Management.

Any sub requirements or downstream requirements of the requirement proxy are not displayed in Traceable Requirements Management, the Requirements Structure Editor, or the Requirements Specification Editor. Requirement proxies are treated as leaf objects as sub requirements or downstream requirements, so you cannot add any other requirements objects beneath the requirement proxy in the requirement specification. You can reorder a requirement proxy within the requirement specification, but it must always remain a leaf object.

A requirement proxy's properties are ready-only. Any properties not provided to the requirement proxy from the external requirements management system may either have no values or have the default values for the requirement object type in Traceable Requirements Management. You cannot create or revise requirement proxies; instead, you must create or revise the requirement associated with a requirement proxy in the external requirements management system. The lifecycle state of requirement proxies is always Undefined, so you cannot promote or demote them like other objects in a requirement specification. Because requirement proxy objects cannot be copied, they are only referenced when importing one requirement specification's structure into another. If you export a requirement specification to a Microsoft Word document, the requirement proxies are not included in the exported structure. You cannot import requirements from an external requirements management system, thus adding a requirement proxy, using Requirements Capture. You cannot lock a requirement proxy for exclusive editing or transfer its ownership to another user. You cannot delete requirement proxies in Traceable Requirements Management, the Requirements Structure Editor, or the Requirements Specification Editor. You can delete the associated requirement in the external requirements management system, then manually remove the relationship to the requirement proxy from the requirement specification in Traceable Requirements Management, the Requirements Structure Editor, or the Requirements Specification Editor. Requirement proxies do not appear in search results.