Introduction to Software Maintenance & Configuration Management (SCM) PDF

TMA4093 Software Maintenance & Configuration Management (SCM) Introduction to SCM  What is Software Configuration Management? Definition SEE FOR The process of identifying, YOURSELF! organizing, and contr...

TMA4093 Software Maintenance & Configuration Management (SCM) Introduction to SCM  What is Software Configuration Management? Definition SEE FOR The process of identifying, YOURSELF! organizing, and controlling modifications to the software being built by a programming team. The goal is to maximize productivity by minimizing mistakes caused by confusion in managing multiple versions of a product. - Roger S. Pressman It is a set of activities designed to manage change by identifying the work products that are likely to change, establishing relationships among them, defining mechanisms for managing different versions of these work products, controlling the changes imposed, and auditing and reporting on the changes made. - also called as change management.  SCM and the Software Lifecycle “No matter where you are in the system life cycle, the system will change, and the desire toSEE FOR change it willYOURSELF! persist throughout the life cycle” - Edward H. Bersoff SCM is an umbrella activity that is applied throughout the software process. Because change can occur at any time and at any stage of the SDLC.  What Are the Core Activities in SCM? Identification of Configuration Items (CI) Identifying and organizing all the items in a software project, such as code files, documents, and resources. This process allows teams to track what needs to be managed effectively. Version Control Combines procedures and tools to manage different versions of configuration items created during the software development process. This includes monitoring, approval, and documentation of changes. Change Control Keeps track of all changes, detailing what has been altered, when, and by whom. This transparency is crucial for maintaining the integrity of the project. Configuration Status Accounting Provides updates on the current state of configuration items, changes made, and overall project health. This helps stakeholders stay informed about progress and any issues that arise. Configuration Audits Conducts audits to verify whether the software and its changes meet required standards and align with project goals, ensuring consistency and quality.  Who is Involved in SCM? Developers Quality Assurance (QA)SEE FOR Engineers YOURSELF! Project Managers Release Managers Operations and DevOps Teams System Administrators Configuration Managers Stakeholders/Clients  Why is Configuration Management Important? Version Control Enables tracking of changes and management of multiple code versions, providing a clear history of modifications. Consistency and Stability Ensures software integrity across different environments, minimizing errors and enhancing reliability during deployment. Change Management Systematically manages and documents changes, allowing teams to evaluate the impact and minimize risks associated with modifications. Collaboration Centralizes code sharing and facilitates teamwork, enabling multiple contributors to work efficiently on projects simultaneously. Disaster Recovery Provides backups and ensures that configurations and codebases can be quickly restored, protecting against data loss and system failures.  Benefits of Configuration Management Improved Quality Assurance Ensures consistency and adherence to quality standards, reducing the likelihood of defects in the final product. SEE FOR YOURSELF! Effective Change Management Provides a systematic approach to managing changes, minimizing risks and maintaining system stability. Enhanced Collaboration and Communication Facilitates better teamwork by providing a centralized system for managing configuration items, allowing team members to share information, track changes, and coordinate efforts more effectively. Traceability and Accountability Offers a clear record of changes, enhancing accountability and facilitating audits. Faster Recovery from Failures Enables quick restoration of systems and configurations, minimizing downtime and service disruption. Cost Efficiency Reduces overall costs by streamlining processes, minimizing errors, and avoiding costly downtime associated with misconfigurations or inadequate change management.  Disadvantages of SCM Complexity Implementing and maintaining SCM can be complex, especially for large projects with numerous configuration items, potentially leading to confusion and inefficiencies. Initial Setup Costs Establishing SCM processes and tools may require significant upfront investments in software, hardware, and training, which can be a barrier for some organizations. Resistance to Change Team members may be resistant to adopting new SCM practices and tools, particularly if they are accustomed to different workflows, hindering successful implementation. Management Overhead SCM processes can introduce additional administrative overhead, diverting time and resources away from actual development work. Tool Limitations Some SCM tools may lack essential features or be challenging to integrate with existing systems, leading to inefficiencies or frustration among users. Requires Discipline and Training Effective SCM necessitates disciplined practices and proper training, and without this, teams may struggle to implement SCM processes effectively. Thank You