This release adds support for associating certain non-use-case model elements, called traceable model elements, to a new requirement type, model element traceability requirements (prefix DESIGN). You can now assign requirement attributes, particularly traceability attributes, to these model elements. These requirements act as proxies for XDE model elements in your RequisitePro project. You can use these requirements to track the relationships between your model elements and other requirements using RequisitePro requirements management capabilities. Associating model elements with traceability requirements allows you to review and assess the impact of requirements changes on your model elements. For more information about managing requirements in RequisitePro, see the RequisitePro user documentation.
In this release, if you associate a use case to a document, you must also associate that use case to a requirement in that document. When you disassociate that requirement from the use case, the document is likewise disassociated. To associate a use case to an existing document, the existing document must have the same name as the use case.
If you upgrade a project containing documents associated to model elements, restrictions are applied. If the document contains a requirement that is associated to the same model element as the document, that document's association is preserved. If the document does not contain any associated requirements, or if the requirement it contains is associated to a different model element than the document, the document is automatically disassociated from XDE. This disassociation does not affect the associations of any requirements in that document. If a model element in the document is re-associated to a requirement in another document, that document will be automatically associated with the model element.
In earlier versions of Rational RequisitePro, Rational Rose, and Rational XDE, model element names were mapped to the text field of RequisitePro requirements. There was no link between the requirement name and the model element name.
In the current version, XDE model element names are mapped to requirement name fields, and the descriptions of XDE model elements (visible in the element's Model Documentation window in XDE) are mapped to the requirement text. This allows you to edit both the name and the description of the use case from XDE and RequisitePro. When you upgrade an XDE model to the current version, the integration is remapped automatically in the associated RequisitePro database(s) and the affected requirement traceability relationships are marked "suspect." Because the model documentation property for any XDE model element may be blank, associated requirement text may be blank. The requirement text is a required field, so you must enter a common value for the model documentation and requirement text when you navigate from that requirement to its associated model element.
The next time you open a document containing requirements associated to model elements, these requirements display both name and text with separate bookmarks. Each bookmark contains the requirement tag and is formatted as a requirement. You can click the requirement name or text bookmarks for RequisitePro capabilities. Here is an example of how the name and text bookmarks might appear in a document.
The bookmarks are initially inserted side-by-side. You can move the bookmarks apart and format them like any other requirement bookmarks. Disassociating the model element from the requirement removes the requirement name and text bookmarks from the document. Deleting a requirement text bookmark in a document deletes the requirement from the document and the database. Removing a requirement name bookmark deletes the bookmark but does not delete the requirement; as long as the requirement remains associated to a model element, the requirement name bookmark is restored each time you open the document.
Caution Taking a document offline prevents updates from asssociated use-case model elements from updating associated requirement information in documents. When the document is brought back online, changes to the use-case model element may be overwritten by requirement information. We do not recommend making changes to model elements while their associated requirements are in an offline document.
Note If a project is unavailable when you upgrade your model, your associated model elements are not remapped automatically. You can still update requirement text to match the model element’s description on an individual basis by navigating from a requirement to its associated model element. The Resolve Use-Case Name and Description dialog box prompts you to select a common name and text for the requirement and the model element.