Artifact: Use-Case Realization

Use-Case Realization	A use-case realization describes how a particular use case is realized within the design model, in terms of collaborating objects.
UML representation:	Collaboration, stereotyped as ½use-case realization╗.
Worker:	Designer
Templates:	Microsoft Word Template HTML Template
Reports:	Use-Case-Realization Report
More information:	Guidelines: Use-Case Realization Checkpoints: Use-Case Realization
Purpose Properties Brief Outline Timing Responsibility Tailoring Annotated Outline (hyperlinks into HTML template in a new window)

Input to Activities:

Class Design

Database Design

Design Test

Plan Subsystem Integration

Plan System Integration

Plan Test

Subsystem Design

Use-Case Analysis

Use-Case Design

Output from Activities:

Architectural Analysis

Subsystem Design

Use-Case Analysis

Use-Case Design

Purpose

The purpose of the use-case realization is to separate the concerns of the specifiers of the system (as represented by the use-case model and the requirements of the system) from the concerns of the designers of the system. The use-case realization provides a construct in the design model which organizes artifacts related to the use case but which belong to the design model. These related artifacts consist typically of the collaboration and sequence diagrams which express the behavior of the use case in terms of collaborating objects.

Properties

Property Name	Brief Description	UML Representation
Flow of Events Design	A textual description of how the use case is realized in terms of collaborating objects. Its main purpose is to summarize the diagrams connected to the use case (see below), and to explain how they are related. Optional - created only if there is additional information needed for analysis or design which is not appropriate in the use cases itself; this is very rare.	Tagged value, of type "formatted text".
Interaction Diagrams	The diagrams (sequence and collaboration diagrams) describing how the use case is realized in terms of collaborating objects.	Participants are owned via aggregation "behaviors".
Class Diagrams	The diagrams describing the classes and relationships that participate in the realization of the use case.	Participants are owned via aggregation "types" and "relationships".
Derived Requirements	A textual description that collects all requirements, such as non-functional requirements, on the use-case realization that are not considered in the design model, but that need to be taken care of during implementation.	Tagged value, of type "short text".
Realization Association	A stereotyped dependency to the use case in the use-case model that is realized.	dependency

Brief Outline

A template is provided for a use-case realization specification, which contains the textual properties of the use-case realization. This document is used with a requirements management tool, such as Rational RequisitePro, for specifying and marking the requirements within the use-case realization properties.

The diagrams of the use- case realization can be developed in a visual modeling tool, such as Rational Rose. A use-case realization report (with all properties) may be generated with Rational SoDA.

1. Introduction

1.1 Purpose

1.2 Scope

1.3 Definitions, Acronyms and Abbreviations

1.4 References

1.5 Overview

2. Flow of Events û Design

3. Derived Requirements

Timing

Use-case realizations are created in the Elaboration Phase for architecturally significant use cases. Use-case realizations for the remaining Use cases are created in the Construction Phase.

Responsibility

A use-case designer is responsible for the integrity of the use-case realization, and ensures that:

The use-case designer is not responsible for the classes and relationships employed in the use-case realization; instead, these are under the corresponding designer's responsibilities.

Tailoring

Use-case realizations express the behavior of a set of model elements performing some or all of a Artifact: Use Case. As a result, there should be a use-case realization for each use case which needs to be expressed in the design model. Similarly, if use cases are not used, then use-case realizations will also be omitted.