Software Configuration Management
Authors: Keyes J.
 Published year: 2006
 Pages: 183-184/235
Buy this book on amazon.com >>

1.8 SCMP Updates

This document will be periodically reviewed to ensure that all SCM functions are accurately described. Audit and review reports or changes to available resources may require this document to be updated. All changes will be incorporated in either change pages or a document revision. Updates to this document are recorded on the Record of Changes and List of Effective Pages sheets located at the front of this document.



SECTION 2: ORGANIZATION

This section describes the SCM organization in relation to the program and project organization structure.

2.1 Organizational Structure

Figure T3 is a graphic representation of the program and project organizational structure with respect to the SCM organization. Although SCM takes direction from the Project Manager, it operates within the policies and procedures established by [ name of the organization establishing policies]. Listed below are the responsibilities of each of the organizations as related to [system title] development.

click to expand
Figure T3: Structure Organization

SCM interfaces with the functions listed below to control software configuration and release activities.

  • <Depending on the size of the organization, the functional groups defined below may be combined (e.g., the Software Systems Engineering Group and the Software Design and Development Group may be one group known as software development). You will need to define the group interfacing with the SCM organization.>

  • Program Management (Code Number) ” Responsible for and has the authority to ensure complete fulfillment of all program requirements. The Program Manager has the overall responsibility for acquisition, funding, and transitioning of the project.

  • Project Management (Code Number) ” Responsible for the technical aspects of the project. The Project Manager has the responsibility for local funding, allocations , scheduling, tasking, and reporting to program management.

  • Software Systems Engineering (Code Number) ” Responsible for systems design (and associated documentation) overview and guidance; detailed design and coding; test plans, procedures, and reports ; software unit testing; and preliminary CSCI testing.

  • Software Design and Development (Code Number) ” Responsible for software design (and associated documentation) overview and guidance; detailed design and coding; test plans, procedures, and reports; software unit testing; and preliminary CSCI testing.

  • Software Test (Code Number) ” Responsible for the conduct of software testing, including preparation of test plan, description, procedures, and reports. The Software Test Group ensures that the correct configuration is undergoing test and incorporates approved changes into released test documentation based on change request baselining data from SCM. The Software Test Group confirms verification of change request corrective measures prior to change request closure. SCM identifies all change requests included in an Engineering Master (EM) that is to be tested . Test personnel then provide SCM a copy of the test report.

  • Software Quality Assurance (SQA) (Code Number) ” Responsible for auditing the software development activities and products (FCA and PCA) and certifying of SCM compliance with this plan and DTPs.

  • System Test (Code Number) ” Responsible for administering the verification and validation (V&V) testing prior to release of the software. The System Test Group is a separate organization from the Software Development Group (i.e., the Software Systems Engineering Group and the Software Design and Development Group).

  • Logistics (Code Number) ” Responsible for ensuring that changes made to a system are supportable. SCM provides CSCI and associated technical data for logistics evaluation.

  • Data Management (DM) (Code Number) ” Responsible for the receipt, distribution, and tracking of technical data associated with the project. DM also ensures compliance with contract requirements as defined in the Contract Data Requirements List (CDRL).

    <If the list of organizations exceeds the list above, it may be appropriate to create numbered paragraph headings for each organization.>

2.1.1 SCM Responsibilities

SCM is responsible for maintaining configuration control over software Developmental Configurations and Baselines and for processing changes to the software configuration. SCM functions include Software Development Library (SDL) operation, software product release coordination, and change request processing and tracking.

The responsibilities of each SCM function are listed in the paragraphs below.

  • <Tailor these responsibilities to be project specific.>

2.1.1.1 Configuration Identification

  1. Establish methods and procedures for unique identification of CSCIs.

  2. Establish and maintain Functional, Allocated, and Product Baselines and the Developmental Configuration (identify, document, archive, and track changes to system releases).

  3. Establish and follow release procedures to obtain Product Baselines for new version releases.

  4. Coordinate assignment of identifying numbers for CSCIs and documents.

  5. Provide documentation that reflects the release software package.

  6. Coordinate release of software and associated documentation to release organizations.

  7. Maintain records and prepare reports on release coordination activities.

2.1.1.2 Configuration Control

  1. Serve as a member of the Software Configuration Control Board (SCCB). SCM is responsible for preparing and distributing the meeting agenda and minutes and for recording action items and their resolution.

  2. Establish and document configuration change control procedures.

  3. Establish and follow configuration controls for software and documentation.

  4. Place contents of baseline and Developmental Configurations under configuration control in the SDL.

  5. Generate executable load modules from controlled source code.

  6. Ensure that the contents of the SDL are changed by SCM personnel and only upon receipt of the appropriate paperwork signed by the SCM Manager.

  7. Prepare and maintain master(s) of the currently active version of each CI until superseded by a new version. Retain superseded versions of the master(s) in the SDL archive files.

  8. Maintain records and prepare reports on SDL activities and software products.

  9. Perform nontechnical check of software documentation.

  10. Interface with the Software Change Review Board (SCRB) Chairperson to schedule SCRB meetings, prepare SCRB agendas , and record SCRB meeting minutes.

2.1.1.3 Configuration Status Accounting (CSA)

  1. Provide CSA recording and reporting.

  2. Maintain accounting of software changes by tracking change requests, ensuring traceability to a formal change proposal (i.e., ECP) from initiation through resolution and disposition.

  3. Prepare status reports on change requests, formal change proposals (i.e., ECPs), and changes.

2.1.1.4 Configuration Audits

  1. Support requests for audit and certification of software systems by SQA or the independent auditor .

  2. Perform reviews of SCM activities and products.

  3. Review and update SCM documentation as required to ensure that current applicability is maintained .

2.1.1.5 Training

  • <Tailor this section to list specifics of project organization training.>

The SCM Manager is responsible for identifying, establishing, coordinating, and revising training as required to ensure effective performance of SCM activity by the SCM organization and software-related groups.

2.2 Boards

  • <Identify the configuration control boards (CCBs) established for the project and program organization (e.g., CCB, SCCB, SCRB). Reference any charters , Memorandum of Understanding, or any program directives that establish CCBs.>

The paragraphs below provide an overview of the functions, responsibilities, and authority of the CCBs.

2.2.1 Software Change Review Board (SCRB)

The SCRB functions in a technical advisory capacity to the Program Manager. The SCRB considers the recommendations of the project's SCCB for final approval or disapproval of proposed engineering changes to a CSCI's current approved configuration and its documentation. The board also approves or disapproves proposed waivers and deviations.

SCM provides status accounting reports to the program's SCRB and updates the status accounting database to reflect SCRB decisions. [SCM or designate ] serves as secretariat to the board.

2.2.2 Software Configuration Control Board (SCCB)

The SCCB supports the Project Manager and is composed of technical and administrative representatives who recommend approval or disapproval of proposed engineering changes to a CSCI's current approved configuration and its documentation. The board also recommends approval or disapproval of proposed waivers and deviations from a CSCI's current approved configuration and its documentation.

Issues that the project's SCCB is unable to resolve or that involve a change in scheduling or fiscal costs are initially addressed by the SCCB and forwarded to the program's SCRB for final approval or disapproval and recommendations.

SCM provides status accounting reports to the project's SCCB and updates the status accounting database to reflect SCCB decisions. SCM or designate serves as secretariat to the board.


Software Configuration Management
Authors: Keyes J.
 Published year: 2006
 Pages: 183-184/235
Buy this book on amazon.com >>

Similar books on Amazon

Software Configuration Management Patterns: Effective Teamwork, Practical Integration

Software Configuration Management Patterns: Effective Teamwork, Practical Integration

Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation (Addison-Wesley Signature Series (Fowler))

Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation (Addison-Wesley Signature Series (Fowler))

Configuration Management Best Practices: Practical Methods that Work in the Real World

Configuration Management Best Practices: Practical Methods that Work in the Real World

Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing

Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing

Software Configuration Management Handbook, Second Edition

Software Configuration Management Handbook, Second Edition

Similar books