This Guidebook is written in the style of a formal process model. The activities in this Guidebook adhere to the following layout template:
Each activity described in this Guidebook has a number and name corresponding to an activity on an IDEF0 diagram.
Each overview section describes the activity's overall purpose. The first sentence of the overview is a concise description summarizing what will be done in the activity (i.e., the purpose of the activity). The remaining text expands on this information.
This section identifies the roles and responsibilities of the individuals performing the activity. The primary roles are described in Section 3 of this Introduction. Specific personnel designated by position titles are not assigned until the project is defined. The roles identified as performing the activity also are depicted as mechanisms in the accompanying IDEF0 diagrams.
This section lists external factors, data, or products that may influence how the activity is performed or that may be required to produce correct output. Data or products listed here also may be transformed into activity outputs.
This section lists all data or products that are not controls, but that are directly transformed by the activity into outputs.
This section describes the subactivities or steps to complete and document the activity. External material containing guidelines and instructions may be referenced in this section. The sequence of subactivities or steps is explained. Any subactivities or steps that may be performed in parallel are identified. The steps state how the activity will be accomplished, and specify that the artifacts are placed under CM, if appropriate. The Guidebook uses shaded text for examples to distinguish them from procedure steps. User-entered directions and commands are italicized in the examples.
This section lists all software products or data produced by the activity and their destinations. Outputs include all artifacts, data stores, or documents that are created, added to, or modified by the activity.