A NASA provider has submitted a Software Configuration Management Plan in the attached file SCMP_Text_GEND.txt. In assessing the provider plan against your CMMI-DEV v1.3 knowledge base, perform the following two tasks: 1) List and describe the elements of process area Configuration Management that are covered by the provider document, and 2) list and describe the elements of process area Configuration Management that are not covered by the provider document.

 

Assessment of NASA Provider’s Software Configuration Management Plan (SCMP) in Relation to CMMI-DEV v1.3 Configuration Management Process Area

The NASA provider’s Software Configuration Management Plan (SCMP) has been evaluated against the CMMI-DEV v1.3 Configuration Management (CM) process area to determine coverage of its specific practices (SPs) and specific goals (SGs). Below are the findings for each category.

1) Elements of the Configuration Management Process Area Covered by the Provider’s SCMP

• SG 1: Establish Baselines
• SP 1.1 Identify Configuration Items: The SCMP includes a process for identifying software configuration items (CIs), including software components, documents, and test cases. These CIs are managed and tracked in IBM ClearCase, ensuring that each item has a unique identifier​.
• SP 1.2 Establish a Configuration Management System: The plan establishes IBM ClearCase as the configuration management system for version control and baseline management, alongside IBM ClearQuest for tracking changes and integration. These tools ensure systematic tracking, providing clear baselines and versioning across software artifacts​.
• SP 1.3 Create or Release Baselines: The SCMP defines that baselines will be created at major project milestones and will require SCCB approval before changes are implemented. This process ensures that baselines are frozen and released in a controlled manner at various phases, such as requirements and design completion​.
• SG 2: Track and Control Changes
• SP 2.1 Track Change Requests: All changes are initiated through Software Change Control Requests (SCCRs), tracked within ClearQuest. Each SCCR contains relevant details, including change rationale and impact analysis. This ensures transparency in decision-making and tracking throughout the project lifecycle​.
• SP 2.2 Control Configuration Items: Approved SCCRs link directly to affected configuration items in ClearCase, allowing all changes to be documented, versioned, and controlled. The configuration manager and SCCB are responsible for overseeing these changes, ensuring that only authorized adjustments are made​.
• SG 3: Establish Integrity
• SP 3.1 Establish Configuration Management Records: Configuration management records, including SCCRs, status reports, and audit trails, are maintained within ClearQuest, while ClearCase provides a detailed history of configuration item changes. This establishes an audit trail necessary for change tracking​.
• SP 3.2 Perform Configuration Audits: The SCMP states that regular audits will be conducted to verify baseline accuracy and proper implementation of changes. ClearQuest will document audit results, ensuring that all CIs align with the approved baselines​.

2) Elements of the Configuration Management Process Area Not Covered by the Provider’s SCMP

• Explicit Definition of Configuration Management Policies and Standards:
• CMMI-DEV suggests that organizations establish organizational policies for configuration management, including definitions of roles, policies, and practices that are necessary to institutionalize configuration management across projects. The SCMP references the SCCB’s role but lacks details on organizational CM policies that might standardize practices across multiple projects​.
• Integration of Configuration Management with Broader Project Management:
• While the SCMP includes configuration item management within IBM ClearCase and change request tracking via ClearQuest, it could be enhanced by specifying how these configuration management activities are integrated with broader project management practices (e.g., aligning baselines with project planning milestones or adjusting baselines based on project status). CMMI-DEV emphasizes the importance of connecting CM with other process areas such as Project Monitoring and Control, which is not explicitly covered​.
• Documented Configuration Management Training and Resource Requirements:
• The SCMP does not mention training for configuration management personnel or a plan to allocate resources required to perform CM tasks. CMMI-DEV highlights the need for organizations to provide adequate resources and training to ensure effective configuration management. Adding a training section could support personnel in understanding tools like ClearCase and ClearQuest better and aligning with the defined processes​.

Summary

The provider’s SCMP largely aligns with the Configuration Management practices in CMMI-DEV v1.3, covering identification, baseline establishment, change tracking, and configuration audits. However, it could be improved by defining broader CM policies, integrating CM with other project management activities, and documenting training and resource planning. These enhancements would support more comprehensive alignment with CMMI-DEV v1.3 standards for Configuration Management.