Tool Mentor: Detailing a Use Case Using Rational XDE Developer - .NET Edition
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 XDE online Help are marked with .
Overview
This tool mentor assumes that a Use-Case Model has been created in accordance
with the XDE Model Structure Guidelines.
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
XDE.
The following steps are performed in this tool mentor:
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
.
- 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
.
- You can also associate use cases with requirement and documents using the
Rational RequisitePro-XDE Integration. To associate a use case to a RequisitePro
requirement or document, refer to the RequisitePro-XDE integration help. This
is accessed from the top menu bar by clicking Tools > Rational RequisitePro
> Integration Help. More information about the RequisitePro-XDE integration
is provided below.
Rational RequisitePro-XDE Integration
Using the Rational RequisitePro-XDE 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 attributes, such as 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.
To use the integration, RequisitePro must be installed, and the RequisitePro
profile must be applied to the XDE model. The RequisitePro profile is automatically
applied to a model created with the Use Case model template. For existing models,
you must apply this profile manually. See
.
- 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
.
- (optional) Add swimlanes. See
.
- Add initial state, final state, and activities. See
.
- Annotate each activity with a brief description. See
.
- Connect activity states with transitions. See
.
- Create synchronization bars (as needed). See
.
- Specify guard conditions on transitions (as needed). See
.
For more information,
refer to
in the Rational XDE 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 XDE. Relationships with other use cases are
described in Tool Mentor: Structuring the Use-Case Model
Using Rational XDE.
For more information, refer to
in the Rational XDE 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. Rational
XDE 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
.
|