Tool Mentor: Performing Use-Case
Analysis 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 Rational XDE online Help are marked with .
Overview
This tool mentor assumes that a Design Model and Use-Case Model have been created
in accordance with the XDE Model Structure
Guidelines. It also assumes that the Use-Case Model has been populated with
actors and use cases by following Tool Mentor: Finding
Actors and Use Cases Using Rational XDE.
In this tool mentor, the following steps are performed for each use case in
the current iteration:
The following steps are performed once per iteration:
Create the Use-Case Realization
For each use case to be analyzed:
- Navigate to the Design-Model package in which the use-case realizations
are to be created. See Rational XDE
Model Structure Guidelines.
- Create a use-case diagram to capture the use-case realizations (unless one
already exists). See
.
- Add a collaboration instance to the diagram. Give it the same name as the
use case. See
.
- Add a realization relationship to the use case. See
.
For more information, refer to the
topic in the Rational XDE online Help.
If the use-case description needs to be supplemented with additional internal
behavioral descriptions, this can be done by adding to an existing use-case
description created by following the steps outlined in Tool
Mentor: Detailing a Use Case with Rational XDE. If the internal behavior
of the system bears little resemblance to its external behavior, a completely
separate description may be warranted. In this case, attach a separate use-case
specification document (see Artifact:
Use Case for the template) to the collaboration instance in the model.
See
.
- Navigate to the package in the Design Model that will contain the analysis
classes. See Rational XDE Model Structure
Guidelines.
- Create one or more class diagrams to capture the analysis classes. See
.
- Add the analysis classes. See
.
- Assign analysis class stereotypes as appropriate. See
.
- Add a brief description to each class. See
.
- Optionally associate a document with each class. See
.
For more information, refer to the
topic in the Rational XDE online Help.
-
Navigate to each use-case realization (collaboration instance) to be analyzed.
- For each independent sub-flow (scenario), create one or more interaction
instances. (In the Model Explorer, right-click the collaboration instance,
and then click Add UML > Interaction Instance.)
-
Create a sequence diagram for this interaction instance. See
.
- Enter a brief description of the scenario that the sequence diagram depicts. See
.
- Drag and drop actors and participating classes onto the sequence diagram.
See .
- Add messages between the objects. See
.
- (optional) Describe the message. See
.
- To describe how the object behaves when it receives the message, assign an operation to the message. See
.
(If the operation does not exist, add one to the class as described under
Describe Responsibilities below,
and then assign the operation to the message.)
For more information, refer to the following topics in the Rational XDE online
Help:
- Describe responsibilities of the class by adding operations. When you enter
the operation name, precede it with two forward slashes (//). The use of these
special characters indicates that the operation is being employed to describe
the responsibilities of the analysis class. See
.
- Add a description to each operation. See
.
Use the following steps below to describe attributes and associations.
See the
topic in the Rational XDE online Help.
- (optional) Navigate to each use-case realization, and add a class diagram
to show the participants in the use-case realization. See
.
- Add association relationships (either to the "participants" diagram
for a use-case realization or to the class diagram in which the class was
first introduced, or to both). (See
and
.)
Once a relationship has been added between classes on one diagram, it can
be automatically added to another diagram. See
.
- Specify multiplicity on each association end. See
.
- Specify navigability on each association end. See
.
Give a name or stereotype the associations to indicate event dependencies. See
and
.
For more information, refer to the
topic in the Rational XDE online Help.
Examine the analysis classes and their associations. Identify and resolve
inconsistencies, and remove any duplicates.
For more information, refer to the
topic in the Rational XDE online Help.
The analysis mechanisms used by a class and their associated characteristic
do not need to be captured in a formal way. A note attached to a diagram (see
)
or an extension to the description of the class (see
)
is sufficient to convey the information.
Add traceability dependencies between the Analysis/Design-Model elements and
other models, as specified in project guidelines. For example, there may be
a separate business model, conceptual data model, or model of user interface
screens that you wish to trace analysis classes to. To do this:
- Create a diagram for Traceability. See
.
- Drag and drop elements to be traced onto the diagram. See
.
- Add the traceability dependencies (abstraction dependencies optionally stereotyped «trace»). See
.
It may be helpful to publish any models to html format. Also note that diagrams
can be copied from Rational XDE to Microsoft Word and other programs.
For more information, refer to
.
|