0% found this document useful (0 votes)
2 views8 pages

05 s Cmp Template

The Software Configuration Management Plan (SCMP) outlines the policies, procedures, and processes for managing software configuration throughout the project lifecycle. It includes sections on SCM environment, objectives, activities, and data, as well as guidelines for configuration identification, change control, and supplier management. This document serves as a template for establishing effective configuration management tailored to the specific project needs.

Uploaded by

Balaji Triplant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views8 pages

05 s Cmp Template

The Software Configuration Management Plan (SCMP) outlines the policies, procedures, and processes for managing software configuration throughout the project lifecycle. It includes sections on SCM environment, objectives, activities, and data, as well as guidelines for configuration identification, change control, and supplier management. This document serves as a template for establishing effective configuration management tailored to the specific project needs.

Uploaded by

Balaji Triplant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Software Configuration Management

Template No. Plan


CEMILAC_SYSGP_SCMP_05
of <LRU/System Name>
for
<Platform Name>

Issue/Rev No: 01/00


Date of Release: 8 Feb 2025
Document No.:
Issue/ Rev No. : <0X>/ <0X> Issue Date : <DD/MM/YYYY>
Copy No. : 01 of N No. of Pages : <Total No .of Pages >

Secret Confidential
Document Classification :
<DESIGNAGENCYLOGO>
Restricted Unrestricted

Title: Project/System :

<System/Project Name>
Software Configuration Management Plan LRU/System Part No.:

of <No.>
Software Criticality Level :
<LRU/SYSTEM Name>for <Platform name>
DO-178C Level <A/ B/ C/ D>

Name & Designation Signature

<Design Rep Name>, < Designation>


Prepared By

<Project Leader Name>, <Designation>

Reviewed By
<AWG/QA HOD Name>, <Designation>

<Project Leader Name>, <Designation>


Approved By <Design Agency>

<Design Agency Name & Address>

Prepared By Checked By Approved By Doc No. <Document number>


Issue Revision Date

Page No: 2 of 8
Disclaimer:

This document is a guidance document. Applicable section / table rows may be


considered. Any additional details may be added. Any not applicable section/
table rows may be deleted. The template is very general and vary with process
to process followed by Development Agency. The document may be fine-tuned
with the TAA for finalization.

Distribution List

Copy No. Designation of the Copy Holder Organisation

01 Head of Design Agency Design Agency Name

02

03

04

Prepared By Checked By Approved By Doc No. <Document number>


Issue Revision Date

Page No: 3 of 8
Amendment History

Issue, Issue, Rev Change Brief Description Affected Changed By Change


Rev. No. Date Request Ref. of Amendment Pages/ Effective
Section Date

01, 00 NA Initial Issue NA NA Initial

Prepared By Checked By Approved By Doc No. <Document number>


Issue Revision Date

Page No: 4 of 8
Contents

1. Introduction .............................................................................................................................. 6

1.1. Purpose and Scope ............................................................................................................ 6

1.2. Applicable documents ....................................................................................................... 6

1.2.1. External documents ....................................................................................................... 6

1.2.2. Internal documents ....................................................................................................... 6

1.3. Part Number and Nomenclature ....................................................................................... 6

2.1. Acronyms and Abbreviations............................................................................................. 6

2. SCM Environment ...................................................................................................................... 6

3. SCM Process Objectives ............................................................................................................. 6

4. SCM Activities ............................................................................................................................ 7

4.1. Configuration Identification ................................................................................................... 7

4.2. Baselines and Traceability ...................................................................................................... 7

4.3. Problem Reporting ................................................................................................................. 7

4.4. Change Control ...................................................................................................................... 7

4.5. Change Review ...................................................................................................................... 7

4.6. Configuration Status Accounting ............................................................................................ 7

4.7. Archive, Retrieval, and Release .............................................................................................. 7

4.8. Software Load Control ........................................................................................................... 8

4.9. Software Life Cycle Environment Controls .............................................................................. 8

4.10. Software Life Cycle Data Controls ....................................................................................... 8

5. Transition Criteria ...................................................................................................................... 8

6. SCM data ................................................................................................................................... 8

7. Supplier Control ......................................................................................................................... 8

Prepared By Checked By Approved By Doc No. <Document number>


Issue Revision Date

Page No: 5 of 8
1. Introduction
The Software Configuration Management Plan establishes the methods to be used to
achieve the objectives of the SCM process throughout the software life cycle.

1.1. Purpose and Scope


The purpose of this Software Configuration Management Plan (SCMP) is to provide
guidance for establishing and implementing configuration management for the <Project
Name>. It will set forth the policies, procedures and processes used to accomplish
system Configuration Management (CM) for this project.

1.2. Applicable documents


Define the list of all applicable documents in following sections:

1.2.1. External documents


Define the list of all applicable documents of external origin, relevant for this
project.

1.2.2. Internal documents


Define the list of all applicable documents of internal origin, relevant for this project.

1.3. Part Number and Nomenclature


2. Define the details of all software components having unique part number and nomenclature to
identify them through the software development life cycle.

2.1. Acronyms and Abbreviations


Define all the abbreviations and acronyms with their expanded names in this section.

2. SCM Environment
Define description of the SCM environment to be used, including procedures, tools,
methods, standards, organizational responsibilities, and interfaces.

3. SCM Process Objectives


Define description of the SCM Process Objectives environment

Prepared By Checked By Approved By Doc No. <Document number>


Issue Revision Date

Page No: 6 of 8
4. SCM Activities
Define description of the SCM process activities in the software life cycle:

4.1. Configuration Identification


Items to be identified, when they will be identified, the identification methods for
software life cycle data (for example, part numbering), and the relationship of software
identification and airborne system or equipment identification.<Define process
Activities as per Sec 7.2.1>
4.2. Baselines and Traceability
The means of establishing baselines, what baselines will be established, when these
baselines will be established, the software library controls, and the configuration item
and baseline traceability.<Define process Activities as per Sec 7.2.2>
4.3. Problem Reporting
The content and identification of problem reports for the software product and
software life cycle processes, when they will be written, the method of closing problem
reports, and the relationship to the change control activity.<Define process Activities as
per Sec 7.2.3>
4.4. Change Control
Configuration items and baselines to be controlled, when they will be controlled, the
problem/change control activities that control them, pre-certification controls, post-
certification controls, and the means of preserving the integrity of baselines and
configuration items.<Define process Activities as per Sec 7.2.4>
4.5. Change Review
The method of handling feedback from and to the software life cycle processes; the
methods of assessing and prioritizing problems, approving changes, and handling their
resolution or change implementation; and the relationship of these methods to the
problem reporting and change control activities.<Define process Activities as per Sec
7.2.5>
4.6. Configuration Status Accounting
The data to be recorded to enable reporting configuration management status,
definition of where that data will be kept, how it will be retrieved for reporting, and
when it will be available.<Define process Activities as per Sec 7.2.6>
4.7. Archive, Retrieval, and Release
The integrity controls, the release method and authority, and data retention. <Define
process Activities as per Sec 7.2.7>.

Prepared By Checked By Approved By Doc No. <Document number>


Issue Revision Date

Page No: 7 of 8
4.8. Software Load Control
A description of the software load control safeguards and records.<Define process
Activities as per Sec 7.4 >
4.9. Software Life Cycle Environment Controls
Define Controls for the tools used to develop, build, verify, and load the software,
addressing sections 11.4.b.1 through 11.4.b.7. This includes control of tools to be
qualified. <Define process Activities as per Sec 7.5>

4.10. Software Life Cycle Data Controls


Description of access and change Controls associated with Control Category 1 and
Control Category 2 data.<Define process Activities as per Sec 7.3>

5. Transition Criteria
Define the transition criteria for entering and the exit from the SCM process.

6. SCM data
A definition of the software life cycle data produced by the SCM process, including SCM
Records, the Software Configuration Index and the Software Life Cycle Environment
Configuration Index.

7. Supplier Control
Define the means of applying SCM process requirements to sub-tier suppliers (if
applicable)

Prepared By Checked By Approved By Doc No. <Document number>


Issue Revision Date

Page No: 8 of 8

You might also like