Week13a

Week13a - Ian Sommerville 2000 Slide 1 Configuration...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Ian Sommerville 2000 Slide 1 Configuration management Managing the products of system change Objectives To explain the importance of software configuration management (CM) To describe key CM activities namely CM planning, change management, version management, and system building Topics covered Configuration management planning Change management Version and release management System building Ian Sommerville 2000 Slide 2 New versions of software systems are created as they change For different machines/OS Offering different functionality Tailored for particular user requirements Configuration management is concerned with managing evolving software systems System change is a team activity CM aims to control the costs and effort involved in making changes to a system Configuration management Why Ian Sommerville 2000 Slide 3 System families Workstation version Unix version DEC version Initial system Mainframe version VM S version PC version Sun version Ian Sommerville 2000 Slide 4 Starts during the early phases of the project All products of the software process may have to be managed Specifications Designs Programs Test data User manuals Thousands of separate documents may be generated for a large software system Configuration management planning Ian Sommerville 2000 Slide 5 Defines the types of documents to be managed and a document naming scheme Defines who takes responsibility for the CM procedures and creation of baselines Defines policies for change control and version management Defines the CM records which must be maintained Describes the tools which should be used to assist the CM process and any limitations on their use The CM plan Ian Sommerville 2000 Slide 6 Large projects typically produce thousands of documents which must be uniquely identified Some of these documents must be maintained for the lifetime of the software Document naming scheme should be defined so that related documents have related names....
View Full Document

Page1 / 24

Week13a - Ian Sommerville 2000 Slide 1 Configuration...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online