Artifact: Subsystem Supplementary Requirements |
 |
This is essentially the Supplementary Specifications artifact one level down. It has to be a separate artifact because it has a different responsible role (at this level). Otherwise, it has the same purpose and content: it becomes the Supplementary Specifications for the application of RUP to the development of the subsystem. |
Domain:
Systems Engineering
Work Product Kinds:
Specification |
|
Purpose
The following roles and role sets use the Supplementary Specifications:
-
Analysts create and maintain the
Supplementary Specifications, which serve as a communication medium between the analyst, the customer,
and developers.
-
For software development:
-
Developers use the Supplementary
Specifications as a reference when defining responsibilities, operations, and attributes on
classes, and when adjusting classes to the implementation environment.
-
Implementers refer to the
Supplementary Specifications for input when implementing classes.
-
In systems engineering:
-
Managers refer to the Supplementary
Specifications for input when planning iterations.
-
Testers use the Supplementary Specifications
to verify system compliance.
|
Relationships
Roles | Responsible:
| Modified By:
|
Tasks | Input To:
| Output From:
|
Tailoring
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
|
| |
|