Tool Mentor: Creating Use-Case Realizations Using Rational Rose

Purpose

This tool mentor describes how to represent use-case realizations in Rational Rose.

Related Rational Unified Process information: Activity: Architectural Analysis.

Overview

The following is a summary of the steps you perform to create the Artifact: Use-Case Realization:

1. Create the Use-Case Realization package in the appropriate model

2. Create a Use-Case Realization
3. Create traceability between a use case and its Use-Case Realization

1. Create the Use-Case Realization package in the appropriate model

Use-Case Realizations may be created in either the Artifact: Analysis Model or the Artifact: Design Model, or both. These artifacts are in turn represented as packages in the "Logical View" of your model. Please refer to Tool Mentor: Capturing the Results of Use-Case Analysis and Tool Mentor: Managing the Design Model for information on creating of these packages. When you create the package, name it "Use-Case Realizations." When you create a new class diagram for the package, name it "Traceabilities."

2. Create a Use-Case Realization

A use-case realization represents the design perspective of a use case. It is an organization model element used to group a number of artifacts related to the use case design. Use cases are separate from use-case realizations so you can manage each individually and so you can change the design of the use case without affecting the baseline use case. For each use case in the use-case model, there is a use-case realization in the design model with a dependency (stereotyped «realize») to the use case.

To create a Use-Case Realization you create and name a new Use Case in the Use Case View package then drag and drop it into the "Use-Case Realizations" package. Using the Use Case Specification, assign the stereotype «use-case realization» to the use case. If a dialog appears indicating the Use Case exists in two name spaces, click OK. In the Use-Case Realizations package you created, create a package to manage the Use-Case Realization, giving it the same name as the use-case realization. See Tool Mentor: Managing the Design Model for information about creating and naming packages. In the browser, drag and drop the use-case realization into this newly created package. The use-case realization now exists in the Design or Analysis model, in a package of its own, organized together with all other use-case realizations. Having a package per use-case realization makes independent management and versioning of the artifact possible.

3. Create traceability between a use case and its Use-Case Realization

To create traceability between a use case and its Use-Case Realization you drag the use case from the "Use Case View" and drop it on to the Traceabilities diagram in the Use-Case Realizations package. From the Use-Case Realizations package, drag the Use-Case Realization onto the Traceabilities diagram putting it close to the Use Case. Then, using the association tool from the diagram toolbar, draw an association between the Use-Case Realization and the Use Case. Open the Association Specification and assign it the stereotype «realize».

Copyright  © 1987 - 2001 Rational Software Corporation

Rational Unified Process