Tool Mentor: Detailing a
Use Case Using Rational Software Architect
Purpose
This section provides links to additional information related to this tool mentor.
The steps in this tool mentor match those in the activity. Links to topics
in the Rational Software Architect online Help are marked with .
Overview
This tool mentor assumes that a Use-Case Model has been created in accordance
with the Model Structure Guidelines for Rational Software Architect.
It further assumes that a use case has been created by following the steps outlined
in Tool Mentor: Finding Actors and Use Cases Using Rational
Software Architect.
The following steps are performed in this tool mentor:
Additional Tool Information
Before detailing a use case, you need to decide how these details will be captured.
Some options are:
- Using the Model Documentation window, you can document any selected model
element. See
Documenting Model Elements.
- A separate use-case specification document can be created using the RUP-provided
template (see Artifact: Use Case
for templates). The document can then be associated with the use-case model
element. See
Linking External Files to Model Elements.
- You can also associate use cases with requirement and documents using the
Rational RequisitePro-RSA Integration. To associate a use case to a RequisitePro
requirement or document, refer to the RequisitePro-RSA integration help.
More information about the RequisitePro-RSA
integration is provided below.
Rational RequisitePro-RSA Integration
Using the Rational RequisitePro-RSA Integration, you can edit use-case model
elements from their associated requirements in RequisitePro databases and documents.
You can associate use cases with requirements documents in RequisitePro, which
allows you to develop a textual definition of the use case in a RequisitePro
Microsoft Word document. In RequisitePro use-case documents, you can elaborate
the use case with descriptions, flows of events, special requirements, and conditions.
The integration also allows you to assign requirement traceability to model elements.
You can use associated requirements to track the relationships
between your model elements and other requirements using RequisitePro requirements
traceability capabilities. Associating model elements with requirements allows
you to review and assess the impact of requirement changes on your model elements.
For more information, see the
Managing Use Cases Using Rational Software Architect and Rational RequisitePro guidelines.
- Open the Use-Case Model.
- Navigate to the use case to be detailed.
- Enter a detailed flow of events into the documentation associated with the
model element.
You can illustrate the structure of the flow of events with an activity diagram.
To do this, follow these steps:
- Right-click the use case in the Model Explorer, and add an activity diagram.
See
Adding Diagrams to Models.
- (optional) Add swimlanes. See
Adding Shapes.
- Add initial state, final state, and activities. See
Adding Shapes.
- Annotate each activity with a brief description. See
Documenting Model Elements.
- Connect activity states with transitions.
Relationships.
- Create synchronization bars (as needed). See
Adding Shapes.
- Specify guard conditions on transitions (as needed).
For more information, refer to
Modifying Model Elements in Activity Diagrams
in the RSA online Help.
This is an optional step that is performed only to clarify the relationships
between the use case and its associated actors and use cases. Adding relationships
with actors is described in Tool Mentor: Finding Actors
and Use Cases Using Rational Software Architect. Relationships with other use cases are
described in Tool Mentor: Structuring the Use-Case Model
Using Rational Software Architect.
For more information, refer to
Modeling the Behavior of a System with Use-Case Diagrams
in the RSA online Help.
Enter this information into the documentation associated with the use case.
Note that there is a specific section for this information in the Use-Case Specification
template.
Enter this information into the documentation associated with the use case.
Note that there is a specific section for this information in the Use-Case Specification
template.
Enter this information into the documentation associated with the use case.
Note that there is a specific section for this information in the Use-Case Specification
template.
Enter this information into the documentation associated with the use case.
Note that there is a specific section for this information in the Use-Case Specification
template.
Enter this information into the documentation associated with the use case.
Note that there is a specific section for this information in the Use-Case Specification
template.
Each detailed use-case description should be reviewed with stakeholders. RSA
reports and published Use-Case Model diagrams (use case and activity) can
aid in the review of the detailed use-case description.
For more information, refer to
ReferenceHelpTopic("Publishing Models for Review Outside the Modeling Tool","cr","cr_o_rptg_rsa"); and to the following tutorials:
Generating Standard Model Reports
Generating Custom Model Reports
Publishing Models to Web
Tutorials:
Requirements: Create Activity Diagram
Samples:
Annotated Activity Diagram
|