Configuration Management Process v2 2

CONFIGURATION MANAGEMENT PROCESS

Version 2.2

TT/CMMI/SUP/CMP

Private and Confidential

No part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval

Configuration Management Process

Reference No Version Page No

TT/CMMI/SUP/CMP 2.2 2/20

Amendment Record

Version No Changes / Remarks Prepared By Approved By Releas

e

Date

2 Update Process Ho Kian Ping Daryl Choo 18/11/2015

2.1 Update process to align with ISMS

Ti Hooi Suan Daryl Choo 01/08/2017

2.2 Added definition of work product, CI

Ti Hooi Suan Daryl Choo 25/01/2018




TABLE OF CONTENTS

Page no

CONFIGURATION MANAGEMENT PROCESS ........................................................................................ 4

1.0 PURPOSE AND SCOPE ........................................................................................................................................... 4

2.0 GLOSSARY.............................................................................................................................................................. 4

3.0 ROLES AND RESPONSIBILITY................................................................................................................................... 5

4.0 PROCESS FLOW DIAGRAM ................................................................................................................................... 7

5.0 LIST OF PROCEDURES ........................................................................................................................................... 12

6.0 PROCEDURE DESCRIPTION ................................................................................................................................. 13

6.1. Prepare CM Plan ....................................................................................................... 13

6.2. Setup CM Environment ............................................................................................. 14

7.0 MEASUREMENT ..................................................................................................................................................... 19

8.0 TAILORING OPTIONS ........................................................................................................................................... 20

9.0 QUALITY RECORDS .............................................................................................................................................. 20





1.0 Purpose and Scope

The purpose of this Configuration Management (CM) process is to

establish and maintain integrity of work products using configuration

identification, configuration control, configuration status accounting,

and configuration audits.

CM activities include:

• Preparing CM Plan

• Placing identified configuration items (CI) into repositories

• Tracking and controlling changes of CI(s)

• Maintaining configuration records

• Performing configuration audits

2.0 Glossary

Abbreviation Description

CC Configuration Controller

CCB Change Control Board

CI Configuration Item

CM Configuration Management

CR Change Request

DAR Decision Analysis & Resolution

PAL Process Asset Library

PD Project Director

PDM Product Manager

PM Project Manager

SA System Analyst

SEPG Software Engineering Process Group

SQA Software Quality Assurance




Terms Definition

Configuration

audit

An audit conducted to verify that a configuration

item or a collection of configuration items that make

up a baseline conforms to a specified standard or

requirement.

Configuration

baseline

The configuration information formally designated at a

specific time during a product’s or product

component’s

life.

Configuration

control

An element of configuration management consisting

of the evaluation, coordination, approval or

disapproval, and implementation of changes to

configuration items after

formal establishment of their configuration

identification.

Configuration

item

An aggregation of work products that is designated for

configuration management and treated as a single

entity in the configuration management process.

Configuration

identification


of selecting the configuration items for a product,

assigning unique identifiers to them, and recording their

functional and physical characteristics in technical

documentation.

Configuration

management

A discipline applying technical and administrative

direction and surveillance to (1) identify and

document the functional and physical characteristics

of a configuration item, (2) control changes to those

characteristics, (3) record and report change

processing and implementation status, and (4) verify

compliance with specified requirements.

Configuration

status

accounting


of the recording and reporting of information needed

to manage a configuration effectively.

Work product A useful result of a process. This result can include files,

documents, products, parts of a product, services,

process descriptions, specifications, and invoices. A key

distinction between a work product and a product

component is that

a work product is not necessarily part of the end

product.




3.0 Roles and Responsibility

CC

• Setup repositories to store CIs and non-CIs.

• Controlling changes to baseline

configuration items.

• Making changes to version control of CI

according to the defined procedure.

• Ensuring backup of CIs and non-CIs.

• Accounting for status of identified CIs and non-

CIs. • Publish periodic reports related to CM for the PM

SA • Ensure developers support CM processes

PM

• Responsible for planning, directing,

controlling, structuring and motivating the

project.

• Ensure adequate CM resources, including CM

tools, are made available.

• Ensure CM requirements, processes, and

practices

• are conveyed to all project members.

CCB • Review all proposed CRs.

• Assess change impacts.

• Review modifications to all documentation.

Head of CCB • Chair the CCB meeting

• Approved/reject CR

SQA • Ensure quality of the process




4.0 Process Flow Diagram

Prepared Configuration Management Plan

SUPPORT

CC briefs/train the project

SQA reviews the draft CM plan.

Project Manager identifies the Configuration Controller.




Setup Configuration Management Environment

SUPPORT

CC briefs/train the project team members on the CM

CM environment setup by CC

PM, SQA or SA of the project.




PAL Repository

SUPPORT

into appropriate repository

CC confirms the submitted work product is configured as

per CM plan.

Project team member notifies



FT/CMMI/SUP/CMP 2.2 10/20

SUPPORT

Change Request Procedure

START

The initiator fills the CR Form (Part A)

PM allocates the project team

member to perform the impact

analysis and update in CR Form

(Part B)

Management reviews and

approved/reject the CR based

on Impact Analysis performed.

END

PM will inform project team

member to precede the

change implementation.

Change Request

Form (Part A)

Change Request

Form (Part B)

Change Request

Form (Part C)

Approved?

Yes

No

PM update the implementation

status.

Change Request

Form (Part D)




PAL

Backup External Hard

Repositories Backup

SUPPORT

Label/tag the backup files

performed per policy




5.0 List of Procedures

1. Prepare CM Plan

2. Setup CM environment

3. Acquire CI and Non CI

4. Change request procedure

5. Repositories backup

6. CM audits and CM reporting

CM Checklist

SUPPORT

Baseline Audit perform by the

Identify the types of audit to




6.0 Procedure Description

6.1. Prepare CM Plan

Entry Criteria 1. Project Initiation Note is issued.

2. Project Manager is assigned to the project.

3. Project members are identified.

Inputs 1. Project Initiation Note

2. CM Plan template

Steps 1. PM identifies CC.

In small project, PM can handle role of CC.

In medium to large projects, CC role may be distributed to

multiple project team members.

2. PM confirms CC has necessary skills to perform the CC role.

PM arranges CC-role based training, if required by SEPG.

3. CC prepares CM Plan.

This involves:

■ Identifying Configuration Items & repositories (refer to CI

Master List)

■ CM related roles & responsibilities

■ Configuration management strategies

■ Backup policy

■ Identifying the composition of CCB. CCB typically

consists of Project Manager, Project Configuration

Controller, SA, PDM, and other relevant stakeholders.

■ Change management procedure

■ Naming & version numbering convention

■ CM Report

■ CM Audit frequency

Guidelines: CI Master List

CM Templates :CM Plan

4. CM Plan is reviewed by SQA using a checklist as per Review

Process and will be baselined.

Review comments are incorporated and verified as per

Review Process

CM Checklist :Checklist for CM Plan Review




5. CC baselines CM Plan. Subsequent changes to CM Plan

are handled using ‘Control Changes to Configuration

Items’ procedure of this process.

6. CC briefs project team members on:

• CM related processes & workflow

• CM repositories

Outputs 1. CM Plan

Exit Criteria 1. CM Plan is baselined after closure of review comments

6.2. Setup CM Environment

Entry Criteria 1. Baselined CM Plan

2. File server for CM.

Inputs 1. Baselined CM Plan

2. CI Master List

Steps 1. CC sets up the following CM environment as required to

implement CM Plan:

• Controlled repository structures

• Security (read/write) access

• Release options

2. CM environment set up by CC at project level is reviewed

by PM, SQA or SA of the project. Issues raised are tracked

to closure.

3. CC briefs project team members on CM environment.

Output 1. CM environment

Exit Criteria 1. CM environment is reviewed and ready for use




6.3. Acquire CI and Non-CI.

*ISMS ISO 27001:2013 Clause 7.5 Documented Information is applicable here.

Entry Criteria 1. CI Master List/ISMS Document Master List updated with

new

CI or Non-CI

Inputs 1. Newly submitted CI or Non-CI

2. CM Plan

Steps 1. Project member notifies CC that the CI is ready to be

baselined.

Baseline means a set of specifications or work

products that: -

■ Has been formally reviewed and agreed on.

■ Which thereafter serves as the basis for

further development

■ Which can be changed only through change

control procedures

2. CC confirms the following:

• Submitted work product is a configuration

item as per CM Plan

• Work product has a unique identifier

• Work product has been reviewed or tested

• Work product follows a defined CI Master List

Guideline : CI Master List, ISMS Document Master List

3. Work product shall be baselined when there is no

defect found.

4. CC checks in the CI/Non-CI into appropriate

repository (depending on development phase)

with the correct name, unique identifier and

version number.

5. CC updates CI List. CC also conducts configuration

status accounting on periodic basis.

CM Template :CI List, CM Plan




6. CC confirms the submitting project member

that the CI/Non-CI has been checked in to the

repository.

Outputs 1. New CI/Non-CI in the Baselined Repository

2. CI List

Exit Criteria 1. CI/Non-CI is checked in the Baselined Repository

2. Updated CI List / ISMS Document Master List

6.4. Control Changes to CI / Change Request Procedure

Entry Criteria 1. When a Change Request is initiated

Inputs 1. Change Request

Steps 1. CR Part A: Initiation The PDM fills the CR Form when there is a request that is

varied from the baselined user requirement. A copy of the

CR form is sent to CC and CC makes an entry in CR

Tracking Register.

CM Forms :CR Form

CM Templates: CR Tracking Register

2. CR Part B: Impact Analysis Once the CR form is registered into the CR Tracking Register

the following steps are performed:

• PM allocates the project team member to perform

the impact analysis who will then update the analysis

content to the CR form (Part B).

• Impact analysis is performed to analyze the impact on

schedules, resources and plans and estimate is made

on the total effort and size required for the change

3. When a CR is in progress and another CR comes up and it is

interdependent to the earlier CR then this “Change on a

Change” situation will be handled by creating the new

change received as a separate CR and would be executed

likewise based on priority as per the defined CR process.




4. CR Part C: Change Request Disposition CCB reviews and approves/rejects the CR based on Impact Analysis performed. If the CR is approved, the CCB shall determine whether the CR is chargeable or not. DAR may be used to determine the decision making.

5. CR Part D: Implementation Status • PM will inform project team member to proceed

with

the change implementation.

• Project team member then makes the necessary

changes.

• The modified CI together with the CR form will

undergo formal review process.

• Project team member informs CC of

completed change request.

6. CC checks in the CI into Baselined Repository with the

correct name, unique identifier and version number.

7. CC updates CR Tracking Register.

8. CC updates CI List

Outputs 1. Chargeable or free CR

2. CR Tracking Register

3. CR Form

4. CI List

Exit Criteria 1. CR is closed

2. CR Tracking Register status is set to “Closed” or “Rejected”

6.5. Repositories Backup

Entry Criteria 1. Source code backup daily

2. Project related documents backup weekly

Inputs 1. Project’s repositories

2. External Hard Disk

Steps 1. PM or CC ensure the backup is performed by System

Engineer

2. Frequency and naming convention of backup is as

defined in CM Plan.

3. The backup external hard disk are labeled with:

■ Type (Source Code, Documents)




■ Date of backup

Outputs 1. Backup External Hard Disk

Exit Criteria 1. Successful backup carried out and verified by PM.

6.6. CM Audits and CM Reporting

Entry Criteria 1 Successful review of CM Plan

2 Project is in execution phase

Inputs 1 CM Plan

2 CI List

Steps 1 CC identifies types of audit to perform in the project.

Audits

performed are:

• Baseline audit which focuses on the product and

work product and is done before an item is base

lined

• Configuration management audit which is

typically performed and focuses on conformance

to the configuration management process and

conforms to the physical characteristics

expected in terms of location, etc.

2 CC determines frequency of each audit to be

performed and documents the frequency in the

Configuration Management plan.

CC also determines the stakeholder responsible to

perform the audits.

• Baseline audit is performed by reviewer

• Configuration management audit is performed by

SQA




3 CC assists SQA in performing audits. Audits are

performed using a defined checklist. Audit results are

documented in QA Audit Report as per Process and

Product Quality Assurance Process.

SQA reports any non-conformances to the Project

Manager.

CC closes any non-conformances found during audit.

Checklist: CM Checklist

Forms: QA Report

Forms: Non-compliance Form

4 CC maintains the latest CM Plan and all

configuration management related records such

as CI List and CR Tracking Register

5 System Engineer performs backup activities.

PM or CC perform random retrieval to check integrity of

the backups.

6 Brief new members of the project on configuration

management and CM tool.

7 SQA conducts Phase End CM audit and sends QA

Audit Report to PM.

Forms: CI List

Forms: QA Audit Report

Output 1 CI List

2 QA Audit Report

Exit Criteria 1 Project is complete

7.0 Measurement

None identified




8.0 Tailoring Options

Refer to the Process Tailoring Document

9.0 Quality Records

Output / Record Retention Responsibility

CM Plan, CR Form, CR Tracking

Register, CI List, ISMS Document

Master List

Retained by CC until project completion

Retained by PAL for 7 years thereafter

Defect Tracking Logs of CM Plan Retained by CC until project completion

NAS / Cloud storage Retained by CC until project completion

Retained by PAL for 7 years thereafter

~ End of Document ~