In this release, UML stereotypes can affect how you create requirements from UML elements, and how you create UML elements from requirements. However, you cannot customize this functionality in the IDE. The following procedure explains how to create mappings between requirement types and UML metatypes with stereotypes.
[Rational Software Architect]
- Open the RequisitePro project file (.RQS) in an editor.
- Locate the section with the settings for the Eclipse/RequisitePro integration. Sections start with a line that has an identifier enclosed in square brackets. The Eclipse/RequisitePro integration section begins with a line such as this:
In this section, each line is a key value pair. You typically add two lines for each mapping. Below is an example mapping followed by an explanation of what it means:
CreateElementFromReqUTILCLASSuml=UTILCLASS,CLASS,uml,true,Basic__Utility
CreateReqFromElementCLASSumlBasic__Utility=UTILCLASS,CLASS,uml,true,Basic__Utility
The above two lines map UTILCLASS requirements to <<utility>> class model elements. The first line says UTILCLASS requirements should create <<utility>> class elements and the second line says <<utility>> class elements should create UTILCLASS requirements. Each line decribes mapping in one direction, which means that you can support 1-way mappings by only adding one of the lines.
In the following description, the same two lines of code are repeated. However, the second line of code includes spaces, which indicate each piece of information. The words in bold indicate the breaks:
CreateElementFromReqUTILCLASSuml=UTILCLASS,CLASS,uml,true,Basic__Utility
CreateElementFromReq UTILCLASS uml = UTILCLASS , CLASS , uml , true , Basic__Utility
Key (three strings are directly concatated):
Item Description CreateElementFromReq Indicates a mapping for creating elements from requirements of some requirement type UTILCLASS The requirement type tag uml The domain ID (uml is the only value that makes sense because it is the only domain with stereotypes)
= separates the key and value parts
Value (five comma-separated strings):
Item Description UTILCLASS The requirement type tag (MUST match the value in the key) CLASS The LinkableKind ID, which is the UML metaclass in all capital letters (for example, CLASS, INTERFACE, USECASE, and so on) uml The domain ID (again "uml" is the only value that makes sense) true Link after create (true or false) - typically true Basic__Utility Fully qualified stereotype name with two colons (::) replaced by two underscores (__). In this case, the actual stereotype qualified name was Basic::Utility. The second line is divided as follows:
CreateReqFromElementCLASSumlBasic__Utility=UTILCLASS,CLASS,uml,true,Basic__Utility
CreateReqFromElement CLASS uml Basic__Utility = UTILCLASS , CLASS , uml , true , Basic__Utility
Key (four strings are directly concatated):
Item Description CreateReqFromElement Indicates a mapping for creating requirements from elements of a given type or stereotype CLASS The LinkableKind ID, which is the UML metaclass in all capital letters (for example, CLASS, INTERFACE, USECASE, and so on) uml The domain ID (again "uml" is the only value that makes sense here) Basic__Utility Fully qualified stereotype name with two colons (::) replaced by two underscores (__).
= separates the key and value parts
Value - The value is interpreted as the value above
This format extends the format that describes the mappings for non-stereotyped elements. The new format differs from the old format in the following ways:
- A final item in the value part indicates the stereotype name. However, existing entries without the stereotype part continue to work as before.
- The CreateReqFromElement items now have stereotypes in the key. Existing CreateReqFromElement items do not have stereotypes in their keys, and continue to work as they are.
The Requirement perspective changed in version 6.0.1. When you upgrade from version 6.0, your Requirement perspective does not reflect these changes unless you manually reset the Requirement perspective.
To manually reset the Requirement perspective:
- Switch to the Requirement perspective:
- Click Window > Open Perspective > Requirement. If Requirement is not in the list, click Other and select the Show all check box.
- Click Window > Reset Perspective.
The most visible change to the Requirement perspective for 6.0.1 is the addition of a new view called the Link Clipboard. If you have difficulty finding or showing the Link Clipboard view after you upgrade to 6.0.1, reset the Requirement perspective as described above.
Return to the main readme file
©Copyright IBM Corporation 2004, 2005. All Rights Reserved.