Configuration Management Prepared and Presented By: Abhishek Rautela For Internal use only

QMS Overview ~NST

Structure of QMS Quality Manual: Map against ISO9001-2008 and CMMI level 3 concepts Summary of the entire system Policies and Procedures: Quality Policy Antivirus Policy Transport Policy Processes: The QMS of NST consists of 11 processes in compliance with the ISO 9001:2008 standards Guidelines and Checklists: Various Guidelines and checklist are used for complying with the defined processes and assure quality in the delivered product Templates: The QMS of NST has various templates for providing quality in work at various phases of the project’s lifecycle

Configuration Management Software configuration management provides a discipline for identifying items to be managed, controlling changes, maintaining integrity and traceability of the components that are required to develop the final software product, throughout its life cycle. It is an integral part of the software development process and supports the management and control of the project. Reference Process (QMS):-Software Configuration Management Process Key Players\Group:-Project Managers ,Configuration Managers, QA

Objective of CM The main objective of software configuration management is to manage the change process and track changes to ensure that the configuration of the software product is accurately known at any given time

Entry Criteria When Project planning starts. Change Request has been accepted. The changes may be of type: Change request in environment Change request for functionality including enhancements / modifications Change request for database enhancements When a Configuration item is ready for baselining.

Roles and Responsibilities The Configuration Manager has primary responsibility for defining the software configuration management plan for the project. Project team members may be assigned to perform software configuration management on a full-time or part-time basis depending on the size of the project. The Configuration Manager is the central control point for changes in the project. Typically, his / her responsibilities include: Establishing baselines. Ensuring that no unauthorized changes are made to the baseline Ensuring that all baseline changes are recorded in sufficient detail. Configuration status accounting.

Tasks Configuration Management Planning Change control Version Control CI identification in PMP Change control Impact Analysis End to end tracking Version Control Configuration Status Accounting Maintenance of Status accounting sheet Configuration Audit Internal Audit by QA

Outputs • Baselined CIs • Configuration management plan • Updated Configuration Status • Updated Change Request Log

Conclusion Thank You