Business Use-Case Realization		 A business use-case realization describes how a particular business use case is realized within the business object model, in terms of collaborating objects (instances of business workers and business entities).
UML representation: Collaboration, stereotyped as «business use-case realization».
Worker: Business Designer
Optionality: Can be excluded.
Templates: Business Use-Case Realization specification template
Sample Reports: Business Use-Case Realization Report
More information: Guideline: Business Use-Case Realization

Purpose To top of page

The following people use the business use-case realization:

  • People who analyze, design, and implement the system to understand the context of the system to be built.
  • Business designers to describe how processes are performed in the organization.
  • System analysts to derive requirements of the system.
  • Managers to better understand the context, purpose, and importance of the system to be built.

Properties To top of page

Property Name

Brief Description

UML Representation
Workflow Realization A textual description of how the business use case is realized in terms of collaborating objects. Its main purpose is to summarize the diagrams connected to the business use case (see below), and to explain how they are related. Tagged value, of type "formatted text".
Interaction Diagrams The diagrams (sequence and collaboration diagrams) describing how the business 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 business use case. Participants are owned via aggregation "types" and "relationships".
Derived Requirements A textual description that collects all requirements, such as automation requirements, on the business use-case realization that are not considered in the business use-case model, but that need to be taken care of when building the system. Tagged value, of type "short text".
Trace Dependency A trace dependency to the business use case in the business use-case model that is realized. Owned by the system via the aggregation "trace".

Timing To top of page

Business use-case realizations are mainly created during the inception and elaboration phases.

Responsibility To top of page

A business designer is responsible for the integrity of the business use-case realization, ensuring that:

  • The workflow description from the business use case is correctly interpreted.
  • Relationships between business workers and business entities are consistent with and realize the workflow.
  • The diagrams describing the business use-case realization and its relationships are readable and suit their purpose.
 

Display Rational Unified Process using frames

 

© Rational Software Corporation 1998 Rational Unified Process 5.1 (build 43)