SE Lecture 7.ppt
- 1. Configuration Management Lecture VII IET-3017 : Software Engineering Asad Javed
- 2. Configuration Management When we develop software, the product (software) undergoes many changes in their maintenance phase; we need to handle these changes effectively. Several individuals (programs) works together to achieve these common goals. 2
- 3. The elements that comprise all information produced as a part of the software process are collectively called a software configuration. A configuration of the product refers not only to the product's constituent but also to a particular version of the component. 3
- 4. Cont… Identify change Monitor and control change Ensure the proper implementation of change made to the item. Auditing and reporting on the change made. Configuration Management (CM) is a technic of identifying, organizing, and controlling modification to software being built by a programming team. 4
- 5. Why configuration Management Multiple people are working on software which is consistently updating. It may be a method where multiple version, branches, authors are involved in a software project, and the team is geographically distributed and works concurrently. It changes in user requirements, and policy, budget, schedules need to be accommodated. 5
- 6. Importance of SCM It is practical in controlling and managing the access. e.g., by preventing the two members of a team for checking out the same component for modification at the same time. 6
- 7. Cont… It provides the tool to ensure that changes are being properly implemented. SCM is used in keeping a system in a consistent state by automatically producing derived version upon modification of the same component 7
- 8. Process involved in SCM Configuration management provides a disciplined environment for smooth control of work products. It involves the following activities: Identification and Establishment Version Control Change Control Configuration Auditing Reporting 8
- 9. Identification and Establishment Identifying the configuration items from products that compose baselines at given points in time (a baseline is a set of mutually consistent Configuration Items, which has been formally reviewed and agreed upon, and serves as the basis of further development). 9
- 10. Version Control Creating versions/specifications of the existing product to build new products from the help of SCM system. A description of version is given below: 10
- 11. Cont… 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. 11
- 12. Change control Controlling changes to Configuration items (CI). A change request (CR) is submitted and evaluated to assess technical merit, potential side effects, overall impact on other configuration objects and system functions, and the projected cost of the change 12
- 13. Cont… The object to be changed is “checked out” of the project database, the change is made, and then the object is tested again. The object is then “checked in” to the database and appropriate version control mechanisms are used to create the next version of the software. 13
- 14. Configuration Auditing A software configuration audit complements the formal technical review of the process and product. It focuses on the technical correctness of the configuration object that has been modified. The audit confirms the completeness, correctness and consistency of items in the SCM system and track action items from the audit to closure. 14
- 15. Reporting Providing accurate status and current configuration data to developers, tester, end users, customers and stakeholders through admin guides, user guides, FAQs, Release notes, Memos, Installation Guide, Configuration guide etc 15
- 16. Advantages of SCM Improved productivity and efficiency by reducing the time and effort required to manage software changes. Reduced risk of errors and defects by ensuring that all changes are properly tested and validated. Improved quality and stability of software systems by ensuring that all changes are properly controlled and managed. 16
- 17. Disadvantages of SCM Increased complexity and overhead, particularly in large software systems. Difficulty in managing dependencies and ensuring that all changes are properly integrated. 17