1. Configuration Management- Basic Concepts

2. Agenda  Configuration Management process Overview  Process Stages  Planning & Setup  Control  Audit  Case Study

3. Process Overview Definition:- Configuration Management (CM) is the process of identifying, organizing and controlling modifications to the work products in a testing project Why CM? To ensure that.. Software conforms to requirements Software has undergone all reviews and tests Right version of any work product is used at any point of time All components of the delivered software are consistent with each other Right version of software components are shipped to customer site

4. Do you know ………….   Estimated number of bugs due to CM problems 10% to 15%

5. Process Stages -(i)Planning & Setup  Planning involves Identification of work components which needs to be under configuration controlIdentification of work components which needs to be under configuration control Laying down procedures for controlling and implementing changes to the software items within the project’s defined workflow.Laying down procedures for controlling and implementing changes to the software items within the project’s defined workflow. Identification of tools used in the projectIdentification of tools used in the project

6. Planning & Setup contd…. The following should be ensured during planning:- 1. Version control 2. Base-lining procedure 3. Change control procedure 4. Release procedure 5. Status accounting procedure 6. Backup procedure 7. Archival procedure

7. Configurations items : Definition:- “Configuration items are the items that are directly related or involved in creation of work product.”  e.g. requirement specification document, design document, Source Code, Acceptance plan etc. Test Project work Products do not need the formality of configuration management but do need to be placed under some form of Version Control and Change control referred to as “managed and controlled”

8. Some of the items which needs to be managed & controlled  Plans Test plans, test scriptsTest plans, test scripts Project planProject plan CM planCM plan  Data Planning and re- planning data Planning and re- planning data Test data Test data  Records All review recordsAll review records Causal analysis recordsCausal analysis records Program level tracking recordsProgram level tracking records Test recordsTest records Release recordsRelease records Status tracking recordsStatus tracking records  Customer supplied Documentation or manuals Equipment’s or any other items  Others Standards used in project Contract /proposal

9. Participants in planning Test Manager, Configuration Controller/ Configuration Control Board

10. CM Activities  Identify configuration items  Identify items to be managed & controlled  Define the flow of configuration items & identify the baseline points  Define naming and numbering conventions  Identify the storage structure  Define the following procedures for the configuration items: Version ControlVersion Control BaseliningBaselining Change controlChange control ReconciliationReconciliation ReleaseRelease Status accounting Backup Archival  Define the following procedures for the managed & controlled items Version Control Baselining  Identify CM tool  Prepare CM plan  Review CM plan  Identify configuration controller (CC)/CCB  Train the team on projects’ CM plan  Setup configuration environment

11. Process Stages -(ii) Control Configuration control involves controlling/tracking changes to the configuration items in a systematic way. Participants :CC, Test Manager, Testing Team

12. Activities  For configuration items Get authorization for change requestGet authorization for change request Checkout configuration itemsCheckout configuration items Update the status tracker (E.g. Schedule is the simplest form of status tracker)Update the status tracker (E.g. Schedule is the simplest form of status tracker) Update the items & change version number /modlogUpdate the items & change version number /modlog Verify approval/authorization status of modified programs/documentsVerify approval/authorization status of modified programs/documents Check-in configuration items Update the status tracker Backup configuration items Archive configuration items as necessary Maintain a log of change requests processed  For Managed & controlled items Checkout configuration items Update the items & change version number Check-in configuration items

13. Process Stages-(iii) Audit Configuration audits are performed to verify that Configuration management activities are conducted as per plan.Configuration management activities are conducted as per plan. Compliance to the applicable standards is maintainedCompliance to the applicable standards is maintained Integrity of the baseline is maintainedIntegrity of the baseline is maintained Baseline contents are complete & correctBaseline contents are complete & correct Status of each of the configuration items is correctly availableStatus of each of the configuration items is correctly available

14. There are 3 types of CM audits 1. Baseline audit or Physical audit 2. Work product completion audit or Functional audit 3. Release audit

15. Baseline audit or Physical audit  This audit is conducted on a periodic basis.  This audit involves checking If CM activities are planned and available in scheduleIf CM activities are planned and available in schedule Whether workflow is as per the CM planWhether workflow is as per the CM plan Where configuration items are stored and where they are supposed to beWhere configuration items are stored and where they are supposed to be Are changes to the baseline controlled?Are changes to the baseline controlled? Is the status of the configuration item available?Is the status of the configuration item available?  Physical configuration audits are performed as necessary to verify that all items identified as being part of the configuration are present in the respective directory (baseline, release, etc.).

16. Work product completion audit or Functional audit To verify and validate that the configuration item has achieved the performance specified and the documentation is adequate for a move to production, i.e Any work product that is ready should undergo a completion check to confirm that – Performance criteria mentioned in the specifications of the work product are metPerformance criteria mentioned in the specifications of the work product are met All components are availableAll components are available All the planned reviews have been performedAll the planned reviews have been performed All the required tests have been completedAll the required tests have been completed All the defects/ issues raised on the work product are closed.All the defects/ issues raised on the work product are closed. Traceability exists.Traceability exists.

17. Release Audit At the time of release, an audit is done to ensure that – Right version of the work product is shipped to the customerRight version of the work product is shipped to the customer All components of the release are consistent with each otherAll components of the release are consistent with each other All defects are closed before shipping/Unresolved issues/ defects are listed in the release noteAll defects are closed before shipping/Unresolved issues/ defects are listed in the release note

18. Activities  Plan for the audit  Conduct the audit  Generate audit report  Ensure closure of defects

19. Case Study-Argos

20. Thanks!! For more info contact sunilkumar_tm@infosys.com