Software Configuration Management
- 1. Laxmi Institute of Technology, Sarigam Approved by AICTE, New Delhi; Affiliated to Gujarat Technological University, Ahmedabad Department of IT Engineering Presentation on Software Configuration Management Prepared by: Guided By: 160860116002 Faiyaz Ansari Hardik Soneria 160860116019 Keya Pandya 160860116039 Murtuza Rangwala 160860116046 Pratik Tandel
- 2. Outline • Software Configuration Management • SCM process – Identification – Version Control – Change Control – Configuration Audit – Reporting • Participant of SCM Process
- 3. Software Configuration Management • Configuration Management helps organizations to systematically manage, organize, and control the changes in the documents, codes, and other entities during the Software Development Life Cycle. • It aims to control cost and work effort involved in making changes to the software system. The primary goal is to increase productivity with minimal mistakes.
- 4. Why do we need Configuration management? • There are multiple people working on software which is continually updating. • It may be a case where multiple version, branches, authors are involved in a software project, and the team is geographically distributed and works concurrently. SCM Cont…
- 5. Why do we need Configuration management? • Changes in user requirement, policy, budget, schedule need to be accommodated. • Software should able to run on various machines and Operating Systems • Helps to develop coordination among stakeholders SCM Cont…
- 6. SCM Cont…
- 7. SCM Process Configuration management provides a disciplined environment for smooth control of work products. It involves the following activities: • Identification • Version Control • Change Control • Configuration Audit • Reporting
- 9. • Configuration Identification is a method of determining the scope of the software system. • It is a process of labeling software and hardware configuration items with unique identifiers. • With the help of this step, you can manage or control something even if you don't know what it is. Configuration Identification
- 10. Configuration Identification Cont… The purpose of configuration identification is to maintain control of an evolving system by: • Uniquely identifying the system, revisions of the system and the component parts of each revision • Understanding the status of configuration items as they progress through the development process.
- 11. We achieve this by: • Breaking a system down into a number of known and manageable parts (configuration items) • Uniquely identifying each of these parts • Keeping detailed and accurate records in a CONFIGURATION ITEM REGISTER. Configuration Identification Cont…
- 13. • Creating versions/specifications of the existing product to build new products from the help of SCM system. • SCM uses archiving method or saves every change made to file. • With the help of archiving or save feature, it is possible to roll back to the previous version in case of issues. Version Control
- 15. • Suppose after some changes, the version of configuration object changes from 1.0 to 1.1. • Minor corrections and changes result in versions 1.1.1 and 1.1.2, which is followed by a major update that is object 1.2. Version Control Cont…
- 16. • The development of object 1.0 continues through 1.3 and 1.4. • But finally, a noteworthy change to the object results in a new evolutionary path, version 2.0. • Both versions are currently supported. Version Control Cont…
- 17. • Change control is a procedural method which ensures quality and consistency when changes are made in the configuration object. • In this step, the change request is submitted to software configuration manager. • Controlling changes to Configuration items (CI) Change Control
- 19. • Software Configuration audits verify that all the software product satisfies the baseline needs. • A baseline is a formally accepted version of a software configuration item. • A software configuration audit complements the formal technical review of the process and product. Configuration Audit
- 20. Activities during this process: • Configuration auditing is conducted by auditors by checking that defined processes are being followed and ensuring that the SCM goals are satisfied. • The audit confirms the completeness, correctness and consistency of items in the SCM system Configuration Audit Cont…
- 21. • Providing accurate status and current configuration data to developers, tester, end users, customers and stakeholders through admin guides, user guides, FAQs, Release notes, Installation Guide, Configuration guide etc . Reporting
- 22. Participant of SCM Process
- 23. Participant of SCM Process Cont… 1. Configuration Manager • Configuration Manager is the head who is Responsible for identifying configuration items. 2. Developer • The developer needs to change the code as per standard development activities or change requests.
- 24. Participant of SCM Process Cont… 3. Auditor • The auditor is responsible for SCM audits and reviews. 4. Project Manager: • Monitors the progress of development. 5. User • Uses the Product.