Configuration Management Process V2 1 - FingerTec

CONFIGURATION MANAGEMENTPROCESSVersion 2.1FT/CMMI/SUP/MAPPrivate and ConfidentialNo part of this publication may be reproduced or distributed inany form or by any means, or stored in a database or retrievalAmendment Record

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPVersion No22.1Changes / RemarksUpdate ProcessUpdate process to align withISMSVersion2.1Page No2/19Ho Kian PingDaryl ChooReleaseDate18/11/2015Ti Hooi SuanDaryl Choo01/08/2017Prepared ByApproved By

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPVersion2.1Page No3/19TABLE OF CONTENTSPage noCONFIGURATION MANAGEMENT PROCESS . 41.02.03.04.05.06.06.1.6.2.7.08.09.0PURPOSE AND SCOPE .4GLOSSARY .4ROLES AND RESPONSIBILITY .4PROCESS FLOW DIAGRAM.6LIST OF PROCEDURES.11PROCEDURE DESCRIPTION .12Prepare CM Plan .12Setup CM Environment .13MEASUREMENT .18TAILORING OPTIONS .18QUALITY RECORDS.18

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPVersion2.1Page No4/19Configuration Management Process1.0 Purpose and ScopeThe purpose of this Configuration Management (CM) process is to establish andmaintain integrity of work products using configuration identification,configuration control, configuration status accounting, and configurationaudits.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 audits2.0 SQADescriptionConfiguration ControllerChange Control BoardConfiguration ItemConfiguration ManagementChange RequestDecision Analysis & ResolutionProcess Asset LibraryProject DirectorProduct ManagerProject ManagerSystem AnalystSoftware Engineering Process GroupSoftware Quality Assurance3.0 Roles and Responsibility CC Setup repositories to store CIs and non-CIs.Controlling changes to baseline configurationitems.Making changes to version control of CI accordingto the defined procedure.Ensuring backup of CIs and non-CIs.Accounting for status of identified CIs and non-CIs.

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPSA PM CCBHead of CCBSQA Version2.1Page No5/19Publish periodic reports related to CM for the PMEnsure developers support CM processesResponsible for planning, directing, controlling,structuring and motivating the project.Ensure adequate CM resources, including CM tools,are made available.Ensure CM requirements, processes, and practicesare conveyed to all project members.Review all proposed CRs.Assess change impacts.Review modifications to all documentation.Chair the CCB meetingApproved/reject CREnsure quality of the process

Configuration Management ProcessReference NoFT/CMMI/SUP/CMP4.0 Process Flow DiagramSUPPORTPrepared Configuration Management PlanSTARTProject Manager identifies theConfiguration Controller.CC prepares the draft CM planSQA reviews the draft CM plan.PM approves the CM planCC briefs/train the projectteam members on the CMrelated process workflow andrepositories.ENDDraft CM planCM ChecklistBaselined CMplanVersion2.1Page No6/19

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPSUPPORTSetup Configuration Management EnvironmentSTARTCC sets up the CM Environmentas per CM plan.CM environment setup by CCat project level, reviewed byPM, SQA or SA of the project.CC briefs/train the projectteam members on the CMenvironment.ENDCM planVersion2.1Page No7/19

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPSUPPORTAcquire CI and Non-CISTARTProject team member notifiesCC that the CI is ready to bebaselined.CC confirms the submittedwork product is configured asper CM plan.CC checks into the CI/Non-CIinto appropriate repositoryCC update the CI ListENDPALRepositoryCI ListVersion2.1Page No8/19

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPVersion2.1SUPPORTChange Request ProcedureSTARTThe PDM fills the CR Form (PartA)PM allocates the project teammember to perform the impactanalysis and update in CR Form(Part B)CCB reviews and approved/reject the CR based on ImpactAnalysis performed.NoChange RequestForm (Part A)Change RequestForm (Part B)Change RequestForm (Part C)Approved?YesPM will inform project teammember to proceed with thechange implementation.PM updates theimplementation status.ENDChange RequestForm (Part D)Page No9/19

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPVersion2.1SUPPORTRepositories BackupSTARTPM or CC ensure the backup isperformed per policyPALPerform the backup as per CMplanBackupExternal HardDisk / CloudLabel/tag the backup filesaccordinglyENDPage No10/19

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPVersion2.1SUPPORTCM Audits and CM ReportingSTARTIdentify the types of audit toperform in the project (BaselineAudit or CM Audit)Baseline Audit perform by theReviewer. CM Audit perform bySQA.CM ChecklistSQA conducts the Phase EndCM Audit base on CM Checklistand send QA report to PM.END5.0 List of Procedures1.2.3.4.5.6.Prepare CM PlanSetup CM environmentAcquire CI and Non CIChange request procedureRepositories backupCM audits and CM reportingQA ReportPage No11/19

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPVersion2.16.0 Procedure Description6.1. Prepare CM PlanEntry Criteria 1. Project Initiation Note is issued.2.Project Manager is assigned to the project.3.Project members are identified.Inputs1.Project Initiation NoteSteps1.PM identifies CC.In small project, PM can handle role of CC.In medium to large projects, CC role may be distributed tomultiple project team members.2.PM confirms CC has necessary skills to perform the CC role.2.CM Plan templatePM arranges CC-role based training, if required by SEPG.3.CC prepares CM Plan.This involves: Identifying Configuration Items & repositories (refer to CIMaster List) CM related roles & responsibilities Configuration management strategies Backup policy Identifying the composition of CCB. CCB typicallyconsists of Project Manager, Project ConfigurationController, SA, PDM, and other relevant stakeholders. Change management procedure Naming & version numbering convention CM Report CM Audit frequencyGuidelines: CI Master ListCM Templates :CM Plan4.CM Plan is reviewed by SQA using a checklist as per ReviewProcess and will be baselined.Review comments are incorporated and verified as perReview ProcessCM Checklist :Checklist for CM Plan ReviewPage No12/19

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPVersion2.15.CC baselines CM Plan. Subsequent changes to CM Plan arehandled using ‘Control Changes to Configuration Items’procedure of this process.6.CC briefs project team members on: CM related processes & workflowCM repositoriesOutputs1.CM PlanExit Criteria1.CM Plan is baselined after closure of review comments6.2. Setup CM EnvironmentEntry Criteria1. Baselined CM PlanInputsSteps2.File server for CM.1.Baselined CM Plan2.CI Master List1.CC sets up the following CM environment as required toimplement CM Plan: 2.3.Controlled repository structuresSecurity (read/write) accessRelease optionsCM environment set up by CC at project level is reviewedby PM, SQA or SA of the project. Issues raised are trackedto closure.CC briefs project team members on CM environment.Output1.CM environmentExit Criteria1.CM environment is reviewed and ready for usePage No13/19

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPVersion2.16.3. Acquire CI and Non-CI.Entry Criteria1. CI Master List updated with new CI or Non-CIInputs1.Newly submitted CI or Non-CISteps1.Project member notifies CC that the CI is ready to bebaselined.Baseline means a set of specifications or work productsthat: -2.CM Plan Has been formally reviewed and agreed on. Which thereafter serves as the basis for furtherdevelopment Which can be changed only through change controlprocedures2.CC confirms the following: Submitted work product is a configuration item asper CM PlanWork product has a unique identifierWork product has been reviewed or testedWork product follows a defined CI Master ListGuideline : CI Master ListOutputs3.Work product shall be baselined when there is no defectfound.4.CC checks in the CI/Non-CI into appropriate repository(depending on development phase) with the correctname, unique identifier and version number.5.CC updates CI List. CC also conducts configuration statusaccounting on periodic basis.6.CM Template :CI List, CM PlanCC confirms the submitting project member that theCI/Non-CI has been checked in to the repository.1.New CI/Non-CI in the Baselined RepositoryPage No14/19

Configuration Management ProcessReference NoFT/CMMI/SUP/CMPExit CriteriaVersion2.12.CI List1.CI/Non-CI is checked in the Baselined Repository2.Updated CI List6.4. Control Changes to CI / Change Request ProcedureEntry Criteria1. When a Change Request is initiatedInputs1.Change RequestSteps1.CR Part A: InitiationThe PDM fills the CR Form when there is a request that isvaried from the baselined user requirement. A copy of theCR form is sent to CC and CC makes an entry in CRTracking Register.CM Forms :CR FormCM Templates: CR Tracking Register2.CR Part B: Impact AnalysisOnce the CR form is registered into the CR Tracking Registerthe following steps are performed: PM allocates the project team member to performthe impact analysis who will then update the analysiscontent to the CR form (Part B). Impact analysis is performed to analyze the impacton schedules, resources and plans and estimate ismade on the total effort and size required for thechange3.4.When a CR is in progress and another CR comes up and it isinterdependent to the earlier CR then this “Change on aChange” situation will be handled by creating the newchange received as a separate CR and would beexecuted likewise based on priority as per the defined CRprocess.CR Part C: Change Request DispositionCCB reviews and approves/rejects the CR based onImpact Analysis performed. If the CR is approved, the CCBshall determine whether the CR is chargeable or not. DARmay be used to determine the decision making.Page No15/19

Configuration Management ProcessReference NoFT/CMMI/SUP/CMP5.6.7.8.OutputsCC checks in the CI into Baselined Repository with thecorrect name, unique identifier and version number.CC updates CR Tracking Register.CC updates CI ListChargeable or free CR3.CR Form4.Exit CriteriaCR Part D: Implementation Status PM will inform project team member to proceed withthe change implementation. Project team member then makes the necessarychanges. The modified CI together with the CR form will undergoformal review process. Project team member informs CC of completedchange request.1.2.1.2.Version2.1CR Tracking RegisterCI ListCR is closedCR Tracking Register status is set to “Closed” or “Rejected”6.5. Repositories BackupEntry Criteria1. Source code backup daily2. Project related documents backup weeklyInputs1. Project’s repositories2. External Hard DiskSteps1. PM or CC ensure the backup is performed by SystemEngineer2. Frequency and naming convention of backup is as definedin CM Plan.3. The backup external hard disk are labeled with: Type (Source Code, Documents) Date of backupOutputs1. Backup External Hard DiskExit Criteria1. Successful backup carried out and verified by PM.Page No16/19