1.1.2.2.2 Set Up Software Control Boards

Overview

In this activity, the software configuration management (SCM) manager establishes the control boards for the project. These boards control changes to software products during the project’s software life cycle.

Roles and Responsibilities

The SCM manager is responsible for developing and documenting the control board structures.

The project software manager is responsible for providing input and assistance to the SCM manager as the optimum control board structures are determined.

Controls

See parent activity 1.1.2.2. Determine Project’s Software Configuration Management Activities.

Inputs

The completed Software Configuration Management Needs Form (see Appendix C).

The completed table documenting project roles and their SCM responsibilities.

Procedures

1) Using the information from the completed Software Configuration Management Needs Form and the list or table of roles and responsibilities, the SCM manager determines the most effective and efficient board structure for the project. The SCM manager then defines the board membership and responsibilities. The following paragraphs describe three types of control boards.

A) The Configuration Control Board (CCB) is established at the project level and, thus, is not within the scope of this Guidebook. This board controls system-level products, evaluating and dispositioning all Configuration Change Requests (CCR) (see Appendix C). The CCB works with the authors of proposed changes to resolve outstanding issues. Membership on the CCB may include the project manager or the project system engineer (often serving as chairperson), the project’s software quality assurance (SQA) representative, and representatives from all disciplines (e.g., hardware, software, optics), including the project software manager.

B) The Software Trouble Report Board (STRB) reviews Software Trouble Reports (see Appendix C), verifying that the reported problems are actually software errors and providing the Software Control Board (SCB) with recommendations on when and if corrections should be made. An STRB is needed only on very large projects (see activity 1.1.2.1.1 Perform Software Configuration Management Needs Analysis in this volume and activity 2.2.3.1 Analyze Software Trouble Reports). The STRB is normally chaired by the project software manager or the software engineering manager. Membership also includes (but is not limited to) the authors of any Software Trouble Reports being considered, developers responsible for analyzing the Software Trouble Reports, the SQA representative, and the SCM manager.

C) The SCB reviews and approves or disapproves Software Change Requests (SCR) and Requests for Deviations/Waivers (see Appendix C for both forms) (see activity 2.2.6 Hold Software Control Board Meeting). If a proposed change impacts a system-level product, the SCB forwards it to the CCB with recommendations and impact assessments. Membership on this board may include the authors of SCRs or Requests for Deviations/Waivers being reviewed, the individuals responsible for analyzing the proposed changes, the SCB chairperson (typically the project software manager), the SQA representative, and the SCM manager.

2) The SCM manager, with input from the project software manager, determines the frequency of board meetings based on project needs. Boards should meet regularly; this may be as frequently as weekly, or as infrequently as bi-monthly. The project software manager may call a board meeting at any time.

3) The SCM manager, together with the project software manager, tailors the definitions of the boards to meet project needs and defines their membership. The SCM manager documents the board definitions and the lists of board members in the Configuration Control section of the project’s SCM Plan (SCMP).

Outputs

The project’s control boards and their memberships, which are documented in the Configuration Control section of the SCMP.