Configuration management Configuration management Configuration - PDF document

Configuration management Configuration management Configuration management Configuration management Configuration management � Field of management that focuses on establishing and maintaining consistency of a system’s attributes (functional and physical) and performance with its requirements, design, and operational information throughout its life. 1

Outline � Motivation � Versioning � Configuration items, configurations, baselines � Change control � Build � Configuration management plan � Configuration management tools Motivation 2

Main Phases Development Development Development Development deployment deployment deployment deployment Operation Operation Operation Operation retirement retirement retirement retirement Maintenance Maintenance Maintenance Maintenance t Development Req. inspection Req. inspection Req. inspection Req. inspection Requirements Requirements Requirements Requirements definition definition definition definition Des. inspection Des. inspection Des. inspection Des. inspection Requirement Requirement Requirement Requirement document document document document Code inspection + test Code inspection + test Code inspection + test Code inspection + test Design Design Design Design Design Design Design Design Implemen Implemen Implemen Implemen document document document document Code Code Code Code tation tation tation tation Project management Project management Project management Project management Configuration management Configuration management Configuration management Configuration management t 3

Development Requirements Requirement Requirement VV requirements document document engineering Design VV Design Design . design document document Implement VV unit unit Unit Unit Implement Unit Unit VV unit unit Integrate System VV system System units Project management Configuration management Quality management Time and space dimensions � Space � System made of many parts (documents, code) � System (and parts) adapted for many situations � Time � Parts, and system, change over time 4

Software - space � Made of many parts – Documents – Programs � With different instantiations � Customers, platforms � Thousands of separate documents are generated for a large software system Time - Change is inevitable � A software system changes � Different instantiations of software for different customers � Same software changes over time “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.” [Bersoff et al., 1980] 5

Issues � What is history of document? � versioning � What is the correct set of documents for a specific need? � configuration � Who can access and change what? � change control � How the system is obtained? � build Goals of CM � Identify and manage parts of software � Control access and changes to parts � Allow to rebuild previous version of software 6