Roles and Artifacts

In the Rational Unified Process, how is all this translated in terms of roles, artifacts, activities, and workflows? Figure 11-1 shows the roles and artifacts involved in the implementation discipline.

Figure 11-1. Roles and artifacts in implementation

The main roles involved in the implementation discipline are as follows :

• The Implementer, who develops the components and related artifacts and performs unit testing

• The System Integrator, who constructs a build

Other roles include:

• The Software Architect, who defines the structure of the implementation model (layering and subsystems)

• The Code Reviewer, who inspects the code for quality and conformance to the project standard

The key artifacts of implementation are as follows:

• Implementation Subsystem

  A collection of implementation elements and other implementation subsystems, it is used to structure the implementation model by dividing it into smaller parts .

• Implementation Elements

  A piece of software code (source, binary, or executable) or a file containing information (for example, a start-up file or a readme file), an implementation element can also be an aggregate of other elements ”for example, an application consisting of several executables.

• Integration Build Plan

  This document defines the order in which the elements and subsystems should be implemented and specifies the builds to be created when the system is integrated.