Software configuration management
- 2. Group # 1: Fiza Mustanser (1330310) Hira Qadir (1330288) Maryam Tariq (1330352) Misbah Shafiq (1330290) Ramza Khalid (1330358) Tanzeela Afzal (1330349)
- 3. Software configuration management output of software process is information. Information is divided into these parts. Computer Program Work Product Data or Content
- 4. DEFINITION: The items that comprise all information produced as a part of software process is called software configuration.
- 5. First Law of System Engineering “No matter where you are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle.”
- 6. changes New business or market conditions. New stakeholder needs demand modification of data produced by information systems. Reorganization or business growth/downsizing. Budgetary or scheduling constraints cause a redefinition of the system or product.
- 7. Software configuration management Software configuration management is a set of activities that have been developed to manage change throughout the life cycle of computer software. Software quality assurance activity
- 8. Involving factors Configuration manager programmer CM Operational Scenario UserProject manager
- 9. He is in charge of a software group. He is in charge of the CM procedures and policies software engineers who are responsible for developing and maintaining the software product He uses the product
- 10. Ensure that the product is developed within a certain time frame. Monitors the progress of development and recognizes and reacts to problems. Done by generating and analyzing reports about the status of the software system and by performing reviews on the system.
- 11. Ensure that procedures and policies for creating, changing, and testing of code are followed. Introduces mechanisms for making official requests for changes. Creates and disseminates task lists for the engineers and basically creates the project context. Collects statistics about components in the software system, such as information determining which components in the system are problematic.
- 12. The goal is to work effectively. They communicate and coordinate by notifying one another about tasks required and tasks completed. Engineers use tools that help build a consistent software product. The engineers have their own workspace for creating, changing, testing, and integrating code. At a certain point, the code is made into a baseline from which further development.
- 13. The customer uses the product. Since the product is under CM control, the customer follows formal procedures for requesting changes and for indicating bugs in the product.
- 14. Elements of CMS Configuration management system Process element Construction element Component element Human element
- 15. Details of Elements Component element A set of tools coupled within a file management system (e.g., a database) that enables access to and management of each software configuration item. Process element A collection of actions and tasks that define an effective approach to change management (and related activities) for all constituencies involved in the management, engineering, and use of computer software. Construction element A set of tools that automate the construction of software by ensuring that the proper set of validated components (i.e., the correct version) have been assembled Human element A set of tools and process features (encompassing other CM elements) used by the software team to implement effective SCM.
- 16. Baselines A baseline is a software configuration management concept that helps you to control change without seriously impeding justifiable change. The IEEE defines a baseline as: A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures.
- 18. Software configuration items SCIs are organized to form configuration objects that may be cataloged in the project database with a single name. A configuration object has a name, attributes, and is “connected” to other objects by relationships. The configuration objects, Design Specification, Data Model, Component N, Source Code, and Test Specification are each defined separately.
- 20. Software configuration items However, each of the objects is related to the others as shown by the arrows. A curved arrow indicates a compositional relation. That is, Data Model and Component N are part of the object Design Specification. A double-headed straight arrow indicates an interrelationship. If a change were made to the Source Code object, the interrelationships enable you to determine what other objects (and SCIs) might be affected.
- 21. Summary The changes can be done any where in the life cycle of software development. These changes can be implemented for many causes. A system is running for the validity of these changes which is called software configuration management system. Four factors are involve in this system. Every one is responsible for his own specific job.
- 22. Summary When a design model is designed, reviewed, corrected and approved it becomes a baseline software Baseline software can be use for the further development but can be use as a base for new software. SCIs are important for SCM and for the modification in software design.
- 23. THANK YOU