Overview
This tool mentor supports Performing Use-Case Analysis with Rational XDE Developer - Java Platform Edition.
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.
-
The steps in this tool mentor match those in the corresponding task.
-
Links to topics in XDE online Help are marked with .
-
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 Adding Diagrams
.
-
Add a collaboration instance to the diagram. Give it the same name as the use case. See Adding Shapes to Diagrams
.
-
Add a realization relationship to the use case. See Adding Realization Relationships
.
Reference: Collaboration Instances
.
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 Linking External Files to Model Elements
.
-
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 Adding Diagrams
.
-
Add the analysis classes. See Adding Shapes to
Diagrams .
-
Assign analysis class stereotypes as appropriate. See Assigning Stereotypes
.
-
Add a brief description to each class. See Documenting Model Elements
.
-
Optionally associate a document with each class. See Linking External Files to Model Elements
.
Reference: Working with Class Diagrams
.
-
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 Adding Diagrams
.
-
Enter a brief description of the scenario that the sequence diagram depicts. See Documenting Model Elements
.
-
Drag and drop actors and participating classes onto the sequence diagram. See Adding Shapes to Diagrams
.
-
Add messages between the objects. See Adding
Messages or Stimuli
.
-
(optional) Describe the message. See Documenting
Model Elements
.
-
To describe how the object behaves when it receives the message, assign an operation to the message. See Assigning Operations to Messages or Stimuli
. (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.)
Reference:
-
Working with Class Diagrams
-
Working with Interaction (Sequence) Diagrams
-
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 Adding Operations to Classifiers
.
-
Add a description to each operation. See Documenting Model Elements
.
Use the following steps below to describe attributes and associations.
See the Adding Attributes to Classifiers
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 Adding Diagrams
.
-
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 Adding Association Relationships
, Specifying Kinds of Association Relationships
.) Once a
relationship has been added between classes on one diagram, it can be automatically added to another diagram. See
Adding or Removing Related Connectors.
.
-
Specify multiplicity on each association end. See Specifying Multiplicity in Association Ends
.
-
Specify navigability on each association end. See Specifying Navigability in Association Ends
.
Give a name or stereotype the associations to indicate event dependencies. See Naming Relationships
, Assigning Stereotypes
.
Reference: Working with Stereotypes
topic in the
Rational XDE online Help.
Examine the analysis classes and their associations. Identify and resolve inconsistencies, and remove any duplicates.
Reference: Working with Class Diagrams
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 Attaching Notes to
Shapes ).
You may also use an extension to the description of the class (see Documenting Model Elements
) 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 Adding
Diagrams .
-
Drag and drop elements to be traced onto the diagram. See Adding Shapes to Diagrams
.
-
Add the traceability dependencies (abstraction dependencies optionally stereotyped <<trace>>). See Adding Abstraction Relationships
.
There is no Rational XDE specific guidance for this step.
|