Configuration Management Principles and Practice

Figure I-1 Generic Development Model

Figure 1-1 Overview of Configuration Management Activities

Figure 1-2 Configuration Item Class and Instantiations

Figure 1-3 The Life of a Configuration Item Class

Figure 1-4 Identification in Context

Figure 1-5 Document Front Page

Figure 1-6 Test Cases

Figure 1-7 Storage in Context

Figure 1-8 Example Library Structure

Figure 1-9 Change Control in Context

Figure 1-10 Change Control Process Diagram

Figure 1-11 Status Reporting in Context

Figure 2-1 CMM Version 1.1 Maturity Levels

Figure 2-2 SPICE Process Area Model

Figure 2-3 SPICE Maturity Levels

Figure 5-1 Configuration Management Cost for One Item

Figure 5-2 Configuration Management Total Cost

Figure 6-1 Configuration Item Class Hierarchy

Figure 6-2 Requirement Specification Delivery

Figure 6-3 Hardware-Related Delivery

Figure 7-1 Overview of Metadata

Figure 7-2 Metadata for Unique Identification

Figure 7-3 Metadata for Authorization

Figure 7-4 Metadata for Relations to Other Configuration Items

Figure 7-5 Example of Tracing

Figure 7-6 Metadata for Distribution

Figure 8-1 Item Approval in Context

Figure 8-2 Mail Message Used as Approval Registration

Figure 8-3 Unit Approval FormHigh Degree of Formalism

Figure 8-4 Release Request in Context

Figure 8-5 Mail Message Used as Release Registration

Figure 8-6 Release Request FormHigh Degree of Formalism

Figure 8-7 Excel Workbook Used for Event RegistrationsLow Degree of Formalism

Figure 8-8 Full Event Life Cycle Registration FormHigh Degree of Formalism

Figure 8-9 Change Requests Derived from an Event Registration

Figure 8-10 Excel Workbook Used for Change Request Registrations

Figure 8-11 Change Request Life Cycle Registration FormHigh Degree of Formalism

Figure 9-1 Release Note Example 1

Figure 9-2 Release Note Example 2

Figure 9-3 Item Status List

Figure 9-4 Item History List

Figure 9-5 Item Composition List

Figure 9-6 Trace Report, Part a

Figure 9-7 Trace Report, Part b

Figure 11-1 Multiple Configuration Control Boards

Figure 14-1 Customer, Contractor, and Subcontractor

Figure IV-1 Configuration Management Complexity for One Item

Figure 15-1 Document Delivery

Figure 16-1 Single Requirement

Figure 16-2 Test-Related Tracings

Figure 17-1 Release Note for Full Delivery (Excerpt)

Figure 18-1 Initial Build Success, All Subsystems

Figure 18-2 Promotion of Code

Figure 18-3 Configurator Subsystem Beta Release August 24, 2001: 75% Successful

Figure 18-4 Salespoint Subsystem Beta Release August 17, 2001: 95% Successful

Figure 18-5 Stages in Iterative Development

Figure 18-6 Pure Waterfall Development Model

Figure 18-7 W-Model

Figure 19-1 Composite SystemExample

Figure 19-2 Web Usage

Figure 20-1 Multisite DevelopmentSharing Items

Figure 20-2 Synchronization of Multisites

Figure 20-3 Synchronization

Figure 20-4 Multisite Build

Figure 20-5 Parallel Development and Merge

Figure 20-6 Naming Conventions in Parallel Development

Figure 21-1 Usage Matrix

Figure 21-2 Use of Reuse Components in Projects

Figure 21-3 Event Registration Involving a Component

Figure V-1 CMMI Capability Levels

Figure 23-1 RASIC Chart Example

Figure 24-1 Simple Identification Process

Figure 24-2 Flowchart Conventions

Figure 25-1 Process Deployment and Improvement

Figure 25-2 Average and Range Control Chart

Figure 26-1 Configuration Management Tool Classes