Workflow Detail: Change and Deliver Configuration Items
| The purpose of this workflow detail is to manage project artifacts and the work involved from their initial creation as private artifacts through to their delivery and general availability to the project team and other stakeholders. | |
| Topics - Description - Related Information - Timing - Optionality - How to Staff - Work Guidelines |
Description
This workflow detail is focused on:
- The creation of workspaces, accessing project artifacts, making changes to those artifacts, delivering the changes for inclusion in the overall product, by any role in the project team.
- The building of the product, creation of baselines and promotion of the baselines for availability to the rest of the development team.
Related Information
This section provides links to additional information related to this workflow detail.
Timing
Typically this work starts in Inception and continues throughout the lifecycle.
Optionality
This work is not considered optional.
How to Staff
“Any Role” is used to represent any one of the roles defined in this configuration of the Rational Unified Process (RUP), where someone playing the role may want to make changes to a RUP Artifact (Configuration Item).
The Integrator (as described in other Workflow Details) needs to be sure that artifacts delivered from the developer workspaces are sufficiently tested such that they can be incorporated into a testable build. The Integrator needs to be familiar with Project CM Policies and Test Practices.
Work Guidelines
See the Related Information section for additional guidance that will help you in performing this work.