Software Configuration Management Tasks

This section consists of the following:

• Identification of Configuration Items
• Configuration Items
• Baseline Identification
• Repository Identification
• Configuration Item Identifier
3.1 Identification of Configuration Items

The terms Configuration Identification and Configuration Item are defined in Section 1.1 of this document.

In this SCM Plan, work products are considered for configuration management based on the following criteria. A work product is any tangible item that results from a project function, activity or task.

• May be used by one or more work groups
• Are expected to change over time either because of errors or change of requirements
• Are dependent on each other in that a change in one mandates a change in another/others
• Are critical to the project

Items in the following categories are selected to be placed under configuration management:

• Project Management documentation, including Project Plan and Project Charter
• SEM documentation, including all deliverables, Structured Walkthroughs (SWT), Stage Exit Position Response form
• Models
• Interfaces
• Process descriptions
• Product/Application data such as lookup tables, system files
• Source code and executable code
• Test scripts
• Test data
• Metrics, status reports, quality review reports, etc.
• Support tools, including compilers, editors, testing tools
• Touch Point documentation including EA solution documents, Infrastructure Services Request (DTMB-0184), and Security Plan and Assessment (DTMB-0170)
3.2 Configuration Items (CIs)

The following table contains CIs that are included in this SCM Plan.

Configuration Items Description/SUITE Form Responsible for placing item under control When item is put under control
Project Charter PMM-0002 Project Manager Initiation & Planning Stage Exit
Project Plan PMM-0003 Project Manager Initiation & Planning Stage Exit
Security Plan DTMB-0170 OES Liaison Initiation & Planning Stage Exit
Software Configuration Management Plan SEM-0302 CM Manager Initiation & Planning Stage Exit
Maintenance Plan SEM-0301 DTMB Analyst/CM Manager Initiation & Planning Stage Exit
Requirements Specification SEM-0402 Business Owner Requirements Stage Exit
Requirements Traceability Matrix SEM-0401 Project Manager/DTMB Analyst Requirements Stage Exit
EA Solutions Assessment SEM Touch Point Project Manager/DTMB Analyst Requirements Stage Exit
Infrastructure Services Request (ISR) SEM Touch Point, DTMB-0184 Project Manager/DTMB Analyst Requirements Stage Exit
Hosting Solution SEM Touch Point Project Manager/DTMB Analyst Requirements Stage Exit
Functional Design SEM-0501 Business Owner/Project Manager/DTMB Analyst Functional Design Stage Exit
Conversion Plan SEM-0601 Project Manager/DTMB Analyst System Design Stage Exit
Test Plan SEM-0602 Business Owner/Test Manager System Design Stage Exit
Test Type Approach and Report (multiple) SEM-0603 Business Owner/Test Manager System Design Stage Exit
System Design SEM-0604 Project Manager/DTMB Analyst System Design Stage Exit
System Design Checklist SEM-0605 Project Manager/DTMB Analyst System Design Stage Exit
Test Case (multiple) SEM-0606 Project Manager/DTMB Analyst System Design Stage Exit
Transition Plan SEM-0701 Project Manager/DTMB Analyst Construction Stage Exit
Installation Plan SEM-0702 Project Manager/DTMB Analyst Construction Stage Exit
Training Plan SEM-0703 Business Owner Construction Stage Exit
Training Plan checklist SEM-0704 Business Owner Construction Stage Exit
Release Notes Word/Excel Project Manager/DTMB Analyst Implementation Stage Exit
Post Implementation Evaluation Report PMM-0016 Business Owner/Project Manager/DTMB Analyst Implementation Stage Exit
Request for Change (RFC) SEM Touchpoint, SMC website Project Manager/DTMB Analyst Construction Stage Exit
Structured Walkthrough Meeting Record SEM-0187 Business Owner/Project Manager/DTMB Analyst All Stages
Defect Tracking Log (or equivalent) SEM-0186 (or equivalent) Project Manager/DTMB Analyst All Stages
Stage Exit Approvals SEM-0189 Business Owner/Project Manager/DTMB Analyst All Stages
Project Charter PMM-0002 EXP Project Manager Initiation, Requirements & Design Stage Exit
Project Plan PMM-0003 EXP Project Manager Initiation, Requirements & Design Stage Exit
Initiation, Requirements and Design Plan SEM-0001 EXP Business Owner/Project Manager/DTMB Analyst Construction & Testing Stage Exit
Construction and Testing Plan SEM-0002 EXP Business Owner/Project Manager/DTMB Analyst Construction & Testing Stage Exit
Post Implementation Evaluation Report PMM-0016 EXP Business Owner/Project Manager/DTMB Analyst Implementation Stage Exit
C/JAVA Code (Example) Application Source Code Developer Initial unit test
Database Stored Procedures Database Source Code DBA Initial unit test
Cobol Compiler (Example)
File Editor (Example) Support Tools Infrastructure After received from vendor
Graphics/Images User Interface Elements Graphic Designer Initial unit test
3.3 Baseline Identification

In this SCM Plan, a software baseline is created by the identification and labeling of CIs at a specific point in time. A baseline represents the current approved configuration.
3.4 Repository Identification
3.5 Configuration Item Identifier

Configuration Item Identifiers are used to label all of the CIs that make up a particular grouping such as an application release, a project development phase or documentation changes.

This identification scheme preserves all of the files that are used to create each release and exactly which versions of those files were used. This scheme works for the application installations and then for subsequent upgrades.

Identifiers are used to label the documentation deliverables in a project. For instance, at the end of the system design stage, all of the approved deliverables will be labeled and preserved for future reference. After the completion of the project, many of the deliverables will need to be updated to reflect changes to the application. Those deliverables are assigned identification labels so that their current state can be identified and preserved for future reference.

The following tables show how identifiers are assigned to files and baselines.

Examples 1 and 2 show sample baseline release configuration identification labeling schemes using these abbreviations for baseline (BL), major (mm), minor (nn), and revision (rr).

Example 1
Environment Identification Scheme
Development N/A
Unit Test SFSweb.TST.BL.mm.nn.rr
User Acceptance Testing (UAT) SFSweb.UAT.BL.mm.nn.rr
Production SFSweb.PRD.BL.mm.nn.rr

Example 2
Environment Identification Scheme
Development DEV.BL.00001 through DEV.BL.99999
Test region TST.BL.00001 through TST.BL.99999
UAT UAT.BL.00001 through UAT.BL.99999
Production PRD.BL.00001 through PRD.BL.99999

Table 1 shows three different schemes for identifying documents. The software change request number, document identifies (see Table 2 below), and a status indicator (Initial (I), Final (F)) are used in combination to form an item scheme.

Table 1
Document Name Document description
S123.PP.I.doc Change Request S123 Project Plan Initial
PP.F.S123.doc Project Plan Final Change Request S123
F.PP.S123.doc Final Project Plan Change Request S123

Table 2
Document Identifiers Document CI description
PP Project Plan
PMC Project Management Charter
SEC Security Plan
SCM Software Configuration Management Plan
MAIN Maintenance Plan
REQ Requirements Specification
REQT Requirements Traceability Matrix
INFRA EA Solutions Assessment
INFRAR Infrastructure Request
DESN Functional Design
HOST Hosting Solution
CONV Conversion Plan
TESTP Test Plan
TTAR Test Type Approach and Report
SYSD System Design Document
SYSCH System Design Checklist
TRAN Transition Planning
INSTP Installation Plan
TRAIN Training Plan
TRAINCH Training Plan Checklist
IRDEXP Initiation, Requirements and Design for Express
CTEXP Construction and Testing for Express
RELEASE Release Notes
RFC Request for Change Document
PIER Post Implementation Evaluation Report