Roles and Artifacts

In the Rational Unified Process, how is all this translated concretely in terms of roles, artifacts, activities, and workflows? Figure 7-2 shows the major role in the project management discipline, the Project Manager, and the artifacts of the discipline. Not shown in the figure is the Project Reviewer, who is responsible for evaluating project planning artifacts and project assessment artifacts at major review points in the project lifecycle.

Figure 7-2. Role and artifacts in the project management discipline

The key artifacts of the project management discipline are as follows :

• The software development plan (SDP), which contains several artifacts:

  - Product acceptance plan

  - Risk management plan (and risk list)

  - Problem resolution plan

  - Measurement plan

• The business case

• The iteration plans (one per iteration)

• The iteration assessment

• The (periodic) status assessment

• The work order

• The project measurements database

Other plans are part of the SDP, but they are developed by other roles. Here are two examples:

1. Configuration management plan, developed by the Role: Configuration Manager (see Chapter 13)

2. Development case (the process used for the project), developed by the Role: Process Engineer (see Chapters 14 and 17)