Guidelines: Managing
Use Cases Using Rational Software Architect and Rational RequisitePro
Purpose
These guidelines describe how to manage use cases in Rational Software Architect
using the RSA RequisitePro Integration.
Overview
Implementers, testing professionals, and project managers manage use cases
as they are developed and refined throughout the inception, elaboration, construction,
and transition phases of a project. Effective use-case management requires integrated
documentation to record the current status of the use case and to provide detailed
descriptions of the use case. RSA RequisitePro Integration allows you to manage
use cases using attributes-such as Priority, Risk, Status, and Iteration-by
associating use cases in RSA with RequisitePro requirements.
The main capabilities of the RSA RequisitePro Integration are:
- Open and browse multiple RequisitePro projects allowing access at
different levels of detail or perspectives: requirements, packages, views
- Associate requirements with model elements - create direct and indirect
associations using drag and drop or menu items
- Create model elements from requirements - drag use-case requirements
onto model packages
- Customizable synchronization policies for name and text - none, model
wins, requirement wins, bi-directional
Although many developers may prefer to initially develop use cases in RSA,
most analysts prefer to begin developing use-case requirements in RequisitePro.
RSA RequisitePro Integration allows you to begin in either tool and then create
associated use cases or use-case requirements.
The RSA RequisitePro Integration provides two types of associations: direct
and indirect, which both could be used to implement traceability. The direct
associations should be used when the requirement and the associated model element
are conceptually the same item. For example, you may have a use case requirement
and a use case model element that are conceptually the same use case-just
two different ways to view it. The direct association is the best one to use
in such cases. For example, the use-case requirement / use-case model type association
drives the following tool behavior:
- Dragging one onto the other creates a direct association
- Dragging a use case requirement onto a model package creates use case model elements
- Dragging a use case requirement onto other model elements creates traces
An indirect association is realized through a design requirement acting as
a proxy for the model element. In this case, a requirement is created in the
RequisitePro project to represent the model element. The standard RequisitePro
traceability mechanisms can then be used to trace requirements to that model
element, perhaps to indicate that the model element contributes to the satisfaction
of those requirements. For example, dragging a FEAT requirement onto a class
to create RequisitePro traceability has the following consequences:
- Proxy CLASS requirement is created if it doesn't already exist
- Proxy CLASS requirement is associated directly with the class model element
if it didn't already exist
- Trace is created from CLASS requirement to FEAT requirement
- FEAT requirement is thus indirectly associated with class model element
Topics:
- Opening a RequisitePro
project in RSA
- Associate a Requirement
with a Model Element
- Create Associated Model Elements and Requirements
- Browsing Requirements Traceability
Additional Tool Information
- Open the Rational RSA model.
- Choose Window > Show View > Other > RequisitePro Integration >
Requirement Explorer or open the Requirement perspective
- Click the Open Project button on the view toolbar
- Browse to a RequisitePro project (.RQS)
- Project, packages, requirements, and views are displayed
Refer to Opening Requirements Projects in the online Help.
- Select one or more requirements in the Requirement Explorer
- Drag and drop the selection onto the target model element in the Model Explorer
- As a result, the requirements are associated with the model element
Refer to Associate Existing Requirements and Model Elements
in the online Help.
Refer to
Creating Model Elements from Requirements
and Creating Requirements from Model Elements in the online Help.
- Right-click a requirement in the Requirement Explorer, choose "Open Requirement Associations"
- The requirement is shown in the Requirement Associations view
- The view shows items tracing out of the requirement
- A button can toggle to show items tracing into the requirement
Refer to Traceability in the online Help.
Tutorials:
Requirements: Create a Use-Case Diagram
Samples:
Annotated Use Case Diagram
Cheat Sheets:
Working
with Requirements and Use Cases
|