1. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Configuration Management

2. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 2 Slide 2 Definition According to Wiki: Configuration management is the management of features and assurances through control of changes made to hardware, software, firmware, documentation, test, test fixtures and test documentation of an system, throughout the development and operational life of a system. hardwaresoftwarefirmwaredocumentation Source Code Management or revision control is part of this.revision control

3. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 3 Slide 3 Definition According to Dennis: Configuration and change management is the tracking of the state of the artifacts (hardware, software, firmware, documentation, test, test fixtures and test documentation of an system) throughout the development of a system.hardwaresoftwarefirmware documentation

4. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 4 Slide 4 Configuration Management Defined Configuration management is defined as the management and control of all any changes made to any and all features of the software development activity. This includes hardware, software, documentation, and firmware. Configuration management can be done with a tool. These tools range in price from 0 to 400,000 dollars. It depends on how many features you wish to manage and how well you want to manage them.

5. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 5 Slide 5 Definition Why do we care. Remember Apollo 13. If a change needs to be made to ANY artifact then when you put them all together again you had better make it right. Suppose you have a programming error and need to change it, recompile and use that software. What version of the hardware did you use for the original, what version of the OS, DB, compiler what version of the file management software. All that should be the same to recompile. So we must manage.

6. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 6 Slide 6 Definition Why do we care. Suppose we change requirements and get a new use case diagram– do other things have to change. Will we have more actors, attributes, screens. So even if the documentation of the system changes as it evolves, we must track it.

7. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 7 Slide 7 Definition What are the artifacts? Hardware – ANY hardware that is used by the system. Software – system software (OS, DB, Compiler, etc), supporting software (sorters, mergers, utilities), application software (you wrote or you use). Firmware – ANY firmware used by the system. Documentation – deliverables for development, documentation maintained for the operation of the system, etc.

8. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 8 Slide 8 Configuration Management Defined Configuration Management includes Change management -management of changes to the specifications of a potential software system. Documentation Management – management of all documentation incouding defects, specification, testing, purchasing, emails, memos, agendas…every single documentation detail Hardware/Firmware Configuration Management - management of all the hardware and firmware.

9. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 9 Slide 9 Configuration Management Defined Configuration Management includes (cont) Source code management – management of changes to the source code including the application code, operating system, compilers, utilities, database management system, communication system, middleware, etc.

10. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 10 Slide 10 Configuration Management Defined Configuration Management Standards exist such as IEEE Std. 828-1998 IEEE Standard for Software Configuration Management Plans ANSI/EIA-649-1998 National Consensus Standard for Configuration Management MIL-STD-973 Military Standard for Configuration Management[1] (cancelled, but still good reference)[1] GEIA Standard 836-2002 Configuration Management Data Exchange and Interoperability

11. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 11 Slide 11 Source Code Management One of the important parts of configuration manatement is the Source Code Management For our system you will need to have a plan for Source Code Management.

12. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 12 Slide 12 Source Code Management If you use an IDE such as VB Studio or Eclipse then you can simple set the tool to keep versions of the software for you. However, if you are not using an IDE you will want to use CVS for your version control. l You may want to use THE CVS software. But, at a minimum, you will want to understand it as during your career you may have a need for such a free system.

13. ©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 13 Slide 13 Source Code Management l CVS is a version control system for code, It records the history of source files, and documents those revisions. l CVS servers run on most unix variants, and clients for Windows NT/95, OS/2 and VMS are also available. l Learn More: http://www.nongnu.org/cvs/#TOCintroduction