1. Essentials of Modeling with IBM Rational Software Architect V7.5
Essentials of Modeling - Instructor Notes
This module will take approximately 60 minutes to complete:
Lecture: 30 minutes
Lab 12: 30 minutes
Essentials of Modeling with IBM Rational Software Architect V7.5
Module 12: Traceability with IBM Rational RequisitePro
Module 12 - Traceability to IBM Rational RequisitePro

2. Essentials of Modeling - Instructor Notes
Module objectives
After completing this module, you will be able to:
Ensure that solutions have traceability to requirements
Create traceability to RequisitePro
This module focuses on the integrations between IBM® WebSphere® Business Modeler, IBM® Rational® RequisitePro®, and Rational Software Architect. These tools can be used together to optimize business transformation and systems development efforts. Additionally, the module shows how to create and maintain links and trace relationships between artifacts in these different development tools.
Finally, it shows how, within Rational Software Architect, you can do traceability analysis using topic and browse diagrams, set up traceability relationships, and create a traceability report.
Module 12 - Traceability to IBM Rational RequisitePro

3. Essentials of Modeling - Instructor Notes
Traceability
Traceability answers key questions in development, such as:
What requirements is this part of the design based on?
Why did this (feature, use-case, subsystem, or class) get implemented in this way?
What are the non-functional requirements for this design?
What is the impact of changing a requirement?
What happens to the solution if the business process is changed?
Software development starts with business modeling, to figure out how to transform a business for competitive advantage through improved business structures, processes, and systems. WebSphere Business Modeler enables you to improve business processes by modeling and analyzing them, and simulating alternatives.
Modeling business processes uncovers opportunities for improvement through automation. Analyzing business processes leads to the discovery of new software requirements. RequisitePro is a market-leading requirements management system for project teams who want to improve the communication of project goals, reduce project risk, and increase the quality of applications before deployment.
In virtually every systems development effort, traceability is required, implicitly if not explicitly. Even if it is not mandated by your stakeholders, traceability is important to ensure that stakeholder requirements are implemented, and to enable impact analysis if requirements change (as they invariably will). As you design your systems, you need to be able to trace design elements back to requirements. In addition , as you implement your systems, you need to be able to trace from the design elements to code, and in a larger context, to hardware itself. ?
Module 12 - Traceability to IBM Rational RequisitePro

4. Traceability from requirements to design
Essentials of Modeling - Instructor Notes
Traceability from requirements to design
Needs
Software
Requirements
Design
User Doc
Features
Solution Space
Problem Space
Traceability
Problem
The system to be built
Test Procedures
Traceability allows us to:
Assess the project impact of a change in a requirement.
Assess the impact of a failure of a test on requirements (that is, if the test fails, the requirement may not be satisfied).
Manage the scope of the project.
Verify that all requirements of the system are fulfilled by the implementation.
Verify that the application does only what it was intended to do.
Manage change.
Managing requirements involves the translation of stakeholder requests into a set of system features. These in turn are detailed into specifications for functional and nonfunctional requirements. Detailed specifications are translated into test procedures, design, and user documentation.
IBM Rational tools provide traceability through the whole development and governance lifecycles. You can model your organizations with Rational Software Architect, and your business processes with Rational Software Architect and WebSphere Business Modeler. You can document policies in RequisitePro, and show how policies are traced to initiatives that allow you to comply with those policies.
Module 12 - Traceability to IBM Rational RequisitePro

5. RequisitePro integration
Essentials of Modeling - Instructor Notes
RequisitePro integration
RequisitePro for requirements management
Track relationships between requirements
Analyze the impact of changes to requirements
The Requirements perspective in Rational Software Architect:
Interface to requirements managed in RequisitePro, including:
Documents
Vision, use-case specifications
Requirements
Requirement Properties
Views
Allows requirements to be traced to model elements
Features and Vision W
Vision Document
FEAT 1
FEAT 3
FEAT 7
The RequisitePro solution is a requirements and use-case management tool for project teams who want to improve the communication of project goals, enhance collaborative development, reduce project risk and increase the quality of applications before deployment.
The RequisitePro integration provides capabilities for associating requirements with domain elements in supported IBM Rational Software Delivery Platform products. You can use the integration to create, manage, and track project requirements.
From within the Eclipse platform, you can view your requirements artifacts, create new requirements, modify requirement properties (attributes), create relationships (traces) between requirements and model elements, and clear suspect links.
Note: The integration capability is only available if the RequisitePro product is installed on the same computer as the IBM Rational Software Delivery Platform product.
All Features
Use Cases
Module 12 - Traceability to IBM Rational RequisitePro

6. Views of the Requirement perspective
Essentials of Modeling - Instructor Notes
Views of the Requirement perspective
Requirements Properties
Requirement Explorer
The Requirement perspective in Rational Software Architect enables all of the capabilities of the integration, including the following views:
Link Clipboard: Used to remember which linkable elements or RequisitePro requirements you saved for linking.
Requirements Trace: Shows requirements (and model elements) that are linked to the requirement selected in the Requirements Explorer.
Requirements Explorer: The RequisitePro package hierarchy that contains requirements documents, requirements, and views. Buttons across the top of this view allow you to open a RequisitePro project and control whether the package structure is shown in the view, and whether the domain object linking views are shown in the Requirement perspective.
Requirement Properties: Provides ready access to selected requirements attributes. From here, you may change attribute values without having to leave your Eclipse environment.
Query Results: Displays the results of a view.
Requirement Link Problems: Displays any link errors between model elements and requirements.
Note: You cannot create views in the Requirement perspective.
Requirements
Trace
Requirement
Link Problems
Link Clipboard
Query Results
Module 12 - Traceability to IBM Rational RequisitePro

7. Essentials of Modeling - Instructor Notes
RequisitePro
Requirements Explorer
Query Results
The RequisitePro interface and the Requirement perspective views are similar in both functionality and look and feel.
The left pane is called the Project Explorer (sometimes called just the Explorer). The right window is where all views are displayed. A view is your window into the project requirements database displayed as matrices.
Documents are opened in Microsoft® Word, which includes the RequisitePro menu option. You can switch between Word and RequisitePro to organize and prioritize your requirements and the trace relationships among them, and track requirement changes.
Module 12 - Traceability to IBM Rational RequisitePro

8. RequisitePro requirements traceability model
Essentials of Modeling - Instructor Notes
RequisitePro requirements traceability model
<<trace to>>
System requirements
FEAT
(Feature)
SUPP (Supplementary Requirement) UC
(Use Case)
Domain element
(other model element)
<<link>>
PROXY requirement
(use case) ?
ReqPro and RSM integration only allows you to drag and drop a requirement onto a model element. Not the other way around. And it creates a default traceability relationship from the model element to the requirement.
Because of the way the integration works, it actually becomes a constraint on how to set up the traceability model in a ReqPro project in order to get full traceability from model elements to high level requirements.
We suggest that for a ReqPro project you use the bottom up traceability model which traces from a low level requirement to a high level requirement or trace from a derived requirement to a source requirement.
When a requirement in RequisitePro is copied or dragged onto a model element, the default relationship created is a traceability relationship from the model element to the requirement. Your projects, then, can follow the traceability model above, which allows you to trace from a model element all the way to your high-level requirement. It is the default traceability model provided with a RequisitePro Use Case template.
This approach allows you to use indirect traces. You can create an indirect association by linking domain elements and requirements through proxy requirements and traceability. An indirect trace is a trace between two requirement types that have another requirement in between. For example, a trace from a Proxy requirement to a SUPP and then to a FEAT will support an indirect trace from the Proxy requirement to the FEAT requirement.
By default, the integration generates a proxy requirement for any associated domain elements other than UML use cases. The proxy requirement represents the domain element within RequisitePro. The integration also creates traceability from the proxy to the requirement that you selected for the association.
Module 12 - Traceability to IBM Rational RequisitePro

9. Associating requirements and model elements
Essentials of Modeling - Instructor Notes
Associating requirements and model elements
Creating a new model element
Drag a requirement to a diagram to create a model element in the model that is linked to the requirement in RequisitePro.
By default, use-case requirements create use cases in the model; all other requirements create classes.
Associating with an existing element
Drag a requirement on to an existing model element to associate that element with the use case in RequisitePro.
You can associate requirements with use cases, classes, diagrams, and relationships (associations, messages, and so on).
If use cases have been written, but model elements to represent them have not been created in Rational Software Architect, you can drag the use case requirements onto a diagram to create a use case model element.
If other requirement types are dragged on to a diagram, a class is created by default.
You may create a mapping between requirement types and model element types by modifying the properties of the RequisitePro project in the Requirements Explorer.
Consider carefully what traces should be established and maintained between model elements and requirements:
Creating traces adds maintenance overhead, but with the right balance, the quality and timeliness of change impact analysis can be greatly improved.
Consider associating architectural and major design elements to those requirements that, if changed, may result in a major impact to the system (and project).
Module 12 - Traceability to IBM Rational RequisitePro

10. Associating requirements and model elements
Essentials of Modeling - Instructor Notes
Associating requirements and model elements
When a requirement is dropped onto a model element, a proxy is created for the model element in RequisitePro.
Use cases are always directly linked
Proxies are RequisitePro requirements
Mapping between model elements and requirement types are managed using the RequisitePro project properties
Additional attributes may be added to the proxy requirement types
Linking requirements and model elements enhances Rational Software Architect. You can extend your requirements and model elements with the following capabilities:
Associate requirements with model elements quickly by dragging artifacts between views
Create associated requirements and model elements quickly by dragging artifacts between views
Navigate to, and view, associated artifacts
Manage your model elements with attributes, such as priority and status, in RequisitePro
Establish traceability to requirements to indicate dependencies, and ensure that your design satisfies your project requirements
Monitor the impact of change within your project
Develop use cases in RequisitePro and model them in Rational Software Architect, showing interaction with actors and other use cases
Change the name and text of a use case in either tool, and synchronize the use-case artifacts based on rules thatyou can configure
Module 12 - Traceability to IBM Rational RequisitePro

11. Trace between elements
Essentials of Modeling - Instructor Notes
Trace between elements
Examine traceability relationships between requirements in the Requirement Trace view
Trace from focus element to requirements
Trace to focus element from requirements
Use the Requirement Trace view to examine traceability relationships between requirements. You can navigate any traceability within the RequisitePro project, including traceability to and from proxy requirements that are created by indirect associations to model elements.
There are several ways to view requirement traceability:
Select a requirement in the Requirement Explorer view and view traceability in the Requirement Trace view
Use the Requirement Query Results view to examine the results of queries that are created in RequisitePro views, including the Traceability Matrix and Traceability Tree views
You can right-click a requirement in any view to perform any of the following actions:
Remember the requirement for linking in the Project Explorer view
Use the Select Requirement In menu items to navigate to the Requirement Explorer view, the Requirement Trace view, RequisitePro, or a RequisitePro document
Remove a link or a trace relationship
Change the focus of the view to the selected requirement to view its trace relationships
Add or remove a suspect condition on a traceability relationship
Module 12 - Traceability to IBM Rational RequisitePro

12. Lab 12: Create Traceability Links
Essentials of Modeling - Instructor Notes
Lab 12: Create Traceability Links
Complete the following tasks:
Explore the Requirement perspective
Link folders and files to requirements
Link UML model elements to requirements
Optional: Link Java classes to requirements
Review requirements
To begin the lab:
In the workbench, click Help > Cheat Sheets to open the Cheat Sheet Selection dialog.
Expand Essentials of Modeling Labs.
Double-click 12 Create Traceability Links.
Follow the directions indicated on the Cheat Sheet.
Complete Lab 19: Create Traceability Links in Rational Software Architect.
Module 12 - Traceability to IBM Rational RequisitePro

13. Essentials of Modeling - Instructor Notes
Review
How is traceability between models useful in model-driven development?
How do you create and manage traceability between UML models and RequisitePro requirements in Rational Software Architect?
What type of relationship is used to show traceability between model elements in Rational Software Architect
Q: How is traceability between models useful in model-driven and business-driven development?
A: Traceability can show what requirements a part of the design is based on; why a feature is implemented a certain way; the impact of changing a requirement; and so on. Ask students how they plan to use traceability to requirements.
Q: How do you create and manage traceability between UML models and RequisitePro requirements in Rational Software Architect?
A: RequisitePro use cases can be used to create use cases in a model. Requirements can be linked to model elements using RequisitePro.
Q: What type of relationship is used to show traceability between model elements in Rational Software Architect?
A: There are many ways to indicate a traceability relationship. The way that transformations show traceability is with a «derive» dependency relationship, so this might be the best way to show traceability in Rational Software Architect.
Module 12 - Traceability to IBM Rational RequisitePro

14. Essentials of Modeling - Instructor Notes
Further information
Web Resources
Articles
Related Courses
Web Resources
IBM. “Rational RequisitePro.” IBM developerWorks.
Articles
Amsden, Jim. "Capturing requirements with Business Motivation Model, IBM Rational RequisitePro, and IBM Rational Software Modeler." IBM developerWorks,
Cowan, Scott. "How to establish traceability by using IBM Rational RequisitePro and IBM Rational Systems Developer." IBM developerWorks,
Hovater, Steven. "UML traceability using IBM Rational RequisitePro, IBM Rational Software Architect, and BIRT, Part 2." IBM developerWorks,
----. "Visualize traceability in your development projects using IBM Rational Software Modeler and IBM Rational RequisitePro." IBM developerWorks,
McEwen, Scott. "Requirements: An introduction." IBM developerWorks,
Miller, Jeff. “Model Rational RequisitePro requirements in Rational Software Architect.” IBM developerWorks,
Mitra, Tilak. “Business-Driven Development.” IBM developerWorks,
Related Courses
REQ370: Essentials of IBM Rational RequisitPro (ILT) or REQ310: Essentials of IBM Rational RequisitPro (WBT)
Module 12 - Traceability to IBM Rational RequisitePro