Based on these specific goals and practices of configuration management, provide a Software Configuration Management Plan applies Software Change Control Requests, a Software Change Control Board, and tools IBM Clear Quest and Clear Case

To create a Software Configuration Management (SCM) Plan that integrates Software Change Control Requests (SCCRs), a Software Change Control Board (SCCB), and tools such as IBM ClearQuest and ClearCase, we need to address the goals and practices of the Configuration Management process area as defined in CMMI-DEV V1.3. The following is a structure for this plan:

Software Configuration Management Plan

1. Introduction

This Software Configuration Management Plan (SCMP) defines the procedures and tools used to control and manage software configuration items (CIs) throughout the project lifecycle. It ensures compliance with the CMMI-DEV, Version 1.3 Configuration Management (CM) process area, using IBM ClearQuest and ClearCase to support configuration management activities.

2. Purpose

The purpose of this SCM plan is to establish configuration baselines, track and control changes, and maintain the integrity of the project’s software products by utilizing a structured change management process. This plan will implement software change control requests (SCCRs) and a Software Change Control Board (SCCB) for decision-making and oversight.

3. Scope

This plan applies to all software configuration items (CIs) produced, modified, or procured as part of the software development lifecycle for the project.

4. Configuration Management Organization

• Software Change Control Board (SCCB):
  The SCCB is responsible for reviewing, evaluating, and approving or rejecting all SCCRs. It ensures that changes to configuration items are controlled, with impacts on cost, schedule, and technical performance taken into account. Members of the SCCB include the project manager, configuration manager, software architects, and key stakeholders.
• Configuration Manager:
  The configuration manager is responsible for the overall implementation of configuration management procedures, using ClearQuest for change request tracking and ClearCase for version control and baseline management.

5. Configuration Identification

• SP 1.1 Identify Configuration Items:
  The project’s software components, documents, test cases, and other artifacts will be designated as configuration items (CIs). These items will be tracked in IBM ClearCase, and unique identifiers will be assigned for each item.
• SP 1.2 Establish a Configuration Management System:
  IBM ClearCase will be used for version control and establishing baselines for all CIs. IBM ClearQuest will handle SCCRs and provide integration with ClearCase for change tracking and impact analysis.
• SP 1.3 Create or Release Baselines:
  Baselines will be established at major project milestones, such as the completion of requirements, design, and development phases. IBM ClearCase will be used to freeze baselines and ensure that any changes are approved by the SCCB before they are implemented.

6. Configuration Change Control

• SP 2.1 Track Change Requests:
  All proposed changes to configuration items will be initiated through SCCRs in IBM ClearQuest. SCCRs will document the rationale for the change, impact analysis, and any related work products affected. The SCCB will review each SCCR.
• SP 2.2 Control Configuration Items:
  Once an SCCR is approved by the SCCB, IBM ClearQuest will link it to the corresponding configuration item in IBM ClearCase. Changes will be made to the configuration item, and new versions will be tracked. The configuration manager will ensure that only approved changes are implemented, and the SCCB will review the status of open SCCRs regularly.

7. Configuration Audits and Reporting

• SP 3.1 Establish Configuration Management Records:
  IBM ClearQuest will maintain records of all configuration management activities, including SCCRs, status reports, and audit trails. ClearCase will maintain a detailed history of changes to all configuration items, including versioning, file history, and baseline snapshots.
• SP 3.2 Perform Configuration Audits:
  Regular audits will be conducted to ensure that the baselines reflect the latest approved configurations. The SCCB and configuration manager will ensure that changes have been implemented correctly and that all configuration items are properly tracked. Audit results will be documented in ClearQuest.

8. Tools and Procedures

• IBM ClearCase:
  ClearCase will manage the version control of all CIs. It will store different versions of software code, design documents, and other artifacts, allowing developers to branch, merge, and compare versions.
• IBM ClearQuest:
  ClearQuest will handle the creation, tracking, and approval of SCCRs. It will integrate with ClearCase to ensure that all changes to CIs are tracked from the initiation of a change request through implementation and audit.

9. Conclusion

This SCM Plan ensures structured control over software configuration items and the changes made to them, leveraging IBM ClearQuest and ClearCase. The SCCB, along with the automated tools, guarantees that all changes are properly vetted, tracked, and controlled to maintain software integrity and meet project objectives.

This plan integrates the CMMI-DEV specific goals of establishing baselines, tracking and controlling changes, and maintaining integrity using software tools and structured oversight.