Analyzing with Rhapsody
This lesson guides you through how to analyze the traceability links in Rhapsody, after the migration.
At this stage, the Rhapsody project has been migrated from a 'Gateway' format to a 'ReqXChanger' format.
The traceability links have been kept, and it is possible to analyze them opening the ReqXChanger traceability tables.
To analyze traceability links, from Rhapsody, select the menu Add Profile to Model...
and select the profile called "ReqXChanger" available in Rhapsody’s Profiles directory "ReqXChanger"
- Select the "Requirements" Package. Right-click and select the menu Add New > ReqXChangerTables > RequirementsDetails.
Set a name to the Requirements Details View created, for example "Requirements Details".
Double-click on the View to open it.
In our example, we can see that the Requirement called "LLR4" is traced by the Architecture Elements "CoffeeBeans" and "Control".
The "Impact Analysis View" and "Requirements Details" Gateway Views are replaced by the ReqXChanger "Requirement Details" Table.
- Select the "Requirements" Package. Right-click and select the menu Add New > ReqXChangerTables > RequirementsHierarchy.
Set a name to the Requirements Hierarchy View created, for example "Requirements Hierarchy".
Double-click on the View to open it.
In our example, we can see that the "LowLevelRequirements" Package is covered at 4.55%, and the "QualityRequirements" Package is covered at 7.69%.
The percentage are kept between Gateway and Rhapsody.
- Select the "Requirements" Package. Right-click and select the menu Add New > ReqXChangerTables > LinksView.
Set a name to the Links View created, for example "Links".
Open the View Specification (Right-Click and then Features...). Change the scope to be "CoffeeMachineTraining" (the name of the Project).
In our example, we can see that the Requirement called "LLR4" is traced by the Architecture Elements "CoffeeBeans" and "Control".