We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byKenia Coppage
Modified about 1 year ago
Configuration Management Main issues: manage items during software life cycle usually supported by powerful tools
SE, Configuration Management, Hans van Vliet, © Configuration management tasks identification and definition of configuration items, such as source code modules, test cases, requirements specification managing changes and making configuration items available during the software life cycle, usually through a Configuration Control Board (CCB) keeping track of the status of all items (including the change requests) crucial for large projects
SE, Configuration Management, Hans van Vliet, © Configuration Control Board ensures that every change to the baseline (change request - CR) is properly authorized and executed CCB needs certain information for every CR, such as who submits it, how much it will cost, urgency, etc CCB assesses the CR. If it is approved, it results in a work package which has to be scheduled. so, configuration management is not only about keeping track of changes, but also about workflow management
SE, Configuration Management, Hans van Vliet, © Workflow of a change request change request (CR) investigate schedule work implement change approve reject defer notify owner request info
SE, Configuration Management, Hans van Vliet, © Tool support for configuration management if an item has to be changed, one person gets a copy thereof, and meanwhile it is locked to all others new items can only be added to the baseline after thorough testing changes in the status of an item (e.g. code finished) trigger further activities (e.g. start unit testing) old versions of a component are kept as well, resulting in versions, like X.1, X.2, … we may even create different branches of revisions: X.2.1, X.2.2, … and X.3.1, X.3.2,...
SE, Configuration Management, Hans van Vliet, © Functionalities of SCM tools Components (storing, retrieving, accessing, …) Structure (representation of system structure) Construction (build an executable) Auditing (follow trails, e.g. of changes) Accounting (gather statistics) Controlling (trace defects, impact analysis) Process (assign tasks) Team (support for collaboration)
SE, Configuration Management, Hans van Vliet, © Models of configurations version-oriented: physical change results in a new version, so versions are characterized by their difference, i.e. delta change-oriented: basic unit in configuration management is a logical change identification of configuration becomes different: “baseline X plus fix table bug” instead of “X Y2.7 + Z3.5 + …”
SE, Configuration Management, Hans van Vliet, © Evolution of SCM tools Early tools: emphasis on product-oriented tasks Nowadays: support for other functionalities too. They have become a (THE) major tool in large, multi-site projects Agile projects: emphasis on running system: daily builds
SE, Configuration Management, Hans van Vliet, © Configuration Management Plan Management section: organization, responsibilities, standards to use, etc Activities: identification of items, keeping status, handling CRs
SE, Configuration Management, Hans van Vliet, © Summary CM is about managing al kinds of artifacts during software development Crucial for large projects Supported by powerful tools
Configuration Management Main issues: manage items during software life cycle usually supported by powerful tools ©2008 John Wiley & Sons Ltd.
CS 5521 Configuration Management the problem Not a simple task! –Different versions of software usually is in the field during the life cycle –Different.
CS Software Configuration Management (SCM) Frank Tsui, Orland Karam, and Barbara Bernal, Essential of Software Engineering, 3rd edition, Jones &
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
“Change is Inevitable” 1. The art of coordinating software development to minimize confusion is called configuration management. Configuration management.
Software Configuration Management (SCM) Source: Pressman, R., Software Engineering: A Practitioner ’ s Approach. Boston: McGraw Hill, Inc., 2005; Ghezzi,
Configuration Management. Why Is Software Difficult to Build? Lack of control Lack of control Lack of monitoring Lack of monitoring Lack of traceability.
Software Configuration Management “The art of progress is to preserve order amid change and to preserve change amid order.” --Alfred North Whitehead “I.
Configuration Management Managing Change. Points to Ponder Which is more important? stability progress Why is change potentially dangerous?
CSSE 375 Software Construction and Evolution: Configuration Management Shawn and Steve “You don’t know what version the customer is running?” -- Your instructors.
SG Software Configuration Management And CVS scmGalaxy Author: Rajesh Kumar
Configuration Management CIS 376 Bruce R. Maxim UM-Dearborn.
Chapter 25 – Configuration Management 1Chapter 25 Configuration management.
Software Configuration Management. The process of identifying, organizing, and controlling changes to the software during development and maintenance.
Configuration Management (managing change). Starter Questions... Which is more important? stability progress Why is change potentially dangerous?
Project management Topic 8 Configuration Management.
SE 555 Software Requirements & Specification Requirements Management.
Page 1 October 31, 2000 An Introduction to Large-Scale Software Development Steve Varnau Core HP-UX Operation October 31, 2000.
Ch-10 Configuration Management. Introduction A software project produces a number of items during its execution including various documents, manuals,
Requirements and Estimation Process From a CMM Level 5 Organization Alan Prosser.
Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Software Configuration Management (SCM) an umbrella activity that is applied throughout the software process. Because changes can occur at any time,
Michael Solomon Tugboat Software Managing the Software Development Process.
Software Configuration Management. The “First Law” No matter where you are in the system life cycle, the system will change, and the desire to change.
1 Software Configuration Management CIS 375 Bruce R. Maxim UM-Dearborn.
1 Ivan Marsic Rutgers University LECTURE 2: Software Configuration Management.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Managing Change 1. Why Do Requirements Change? External Factors – those change agents over which the project team has little or no control. Internal.
Software Quality Assurance By Adnan Khan. The process of identifying, organizing, and controlling changes to the software during development and maintenance.
Software Project Management Lecture # 14. Outline Software Configuration Management (SCM) What is SCM What is software configuration Sources of.
Software Configuration Management (SCM) ä Overview ä What is SCM? ä What are the processes of SCM? ä How does each process do? ä Summary.
Nov. 6, 2003CS WPI1 CS 509 Design of Software Systems Lecture #10 Thursday, Nov. 6, 2003.
Software Configuration Management Speaker: Jerry Gao Ph.D. San Jose State University URL:
Management of Software Project CSM Software Configuration Management (SCM)
Software Engineering Lecture 9: Configuration Management.
Chapter 27 Change Management - Introduction - SCM repository - The SCM process (Source: Pressman, R. Software Engineering: A Practitioner’s Approach. McGraw-Hill,
More RUP and Configuration Management CS3300 Fall 2015.
1 / 16 CS 425/625 Software Engineering Software Configuration Management Guest Speaker Jim Hunt November 17, 2008.
Configuration Management Matti Kuikka CONFIGURATION MANAGEMENT by Matti Kuikka, Unit Manager, Ericsson, Turku, Telecom R&D, Wireless Charging.
© Mahindra Satyam 2009 Configuration Management QMS Training.
Software Configuration Management (SCM). Product Developer Disciplines One view of the world is that there are three types of activities are required.
Software Configuration Management (SCM) By, Muhammad Imran Hashim SQA Engineer VisualSoft (Pvt) Ltd.
Configuration & Build Management. Why Software Configuration Management ? The problem: Multiple people have to work on software that is changing More.
Software Configuration Management (SCM). Product Integrity As software becomes more and more complex we need to ensure that software developed has the.
1 Software Configuration Management METU Computer Engineering CEng 492 Spring'2004.
Component-level testing – Equivalence partitioning, boundary value analysis, path testing Navigation testing – Testing navigation syntax and semantics.
© 2017 SlidePlayer.com Inc. All rights reserved.