Artifact: System Use-Case Realization |
 |
In the systems engineering context, this is the equivalent to the Work Product: Use-Case Realization . A System Use-Case Realization describes how a particular system use-case is realized within the System Design Model, in terms of collaborating subsystems (and possibly processes, represented as active classes/objects). |
Work Product Kinds:
Model Element |
|
Purpose
The purpose of the System Use-Case Realization is to derive, from the concerns of those specifying
the system (as represented by the Use-Case Model and the requirements of the system), a form which
addresses system design issues. The System Use-Case Realization provides a construct in the Design Model
that is traceable to a system use case. These related artifacts consist typically of the collaboration and
sequence diagrams which express the behavior of the system use case in terms of collaborating subsystems,
and possibly active objects (representing process decisions at the System level (see Task: System Architectural Analysis - Determine the
System-Level Processes).
|
Relationships
Container Artifact |
System Design Model
|
Roles | Responsible:
| Modified By:
|
Tasks | Input To:
| Output From:
|
Tailoring
Representation Options | UML Representation:
Collaboration, stereotyped as "use-case realization.". This artifact is contained within the System Design Model.
This artifact is mandatory in the systems engineering context; there is some flexibility in representation
(for example, the System Designer might decide that producing the context property adds little value to the
interaction diagrams), and the depiction of processes (or not) depends on system design choices.
|
More Information
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
|
| |
|