tailieunhanh - Lecture Software engineering (9/e): Chapter 25 - Sommerville

Chapter 25 – Configuration nanagement. The objective of this chapter is to introduce you to configuration management processes and tools. When you have read the chapter, you will: understand the processes and procedures involved in software change management; know the essential functionality that must be provided by a version management system, and the relationships between version management and system building; understand the differences between a system version and a system release, and know the stages in the release management process. | Chapter 25 – Configuration Management Lecture 1 1 Chapter 25 Configuration management Topics covered Change management Version management System building Release management 2 Chapter 25 Configuration management Configuration management Because software changes frequently, systems, can be thought of as a set of versions, each of which has to be maintained and managed. Versions implement proposals for change, corrections of faults, and adaptations for different hardware and operating systems. Configuration management (CM) is concerned with the policies, processes and tools for managing changing software systems. You need CM because it is easy to lose track of what changes and component versions have been incorporated into each system version. 3 Chapter 25 Configuration management CM activities Change management Keeping track of requests for changes to the software from customers and developers, working out the costs and impact of changes, and deciding the changes should be implemented. | Chapter 25 – Configuration Management Lecture 1 1 Chapter 25 Configuration management Topics covered Change management Version management System building Release management 2 Chapter 25 Configuration management Configuration management Because software changes frequently, systems, can be thought of as a set of versions, each of which has to be maintained and managed. Versions implement proposals for change, corrections of faults, and adaptations for different hardware and operating systems. Configuration management (CM) is concerned with the policies, processes and tools for managing changing software systems. You need CM because it is easy to lose track of what changes and component versions have been incorporated into each system version. 3 Chapter 25 Configuration management CM activities Change management Keeping track of requests for changes to the software from customers and developers, working out the costs and impact of changes, and deciding the changes should be implemented. Version management Keeping track of the multiple versions of system components and ensuring that changes made to components by different developers do not interfere with each other. System building The process of assembling program components, data and libraries, then compiling these to create an executable system. Release management Preparing software for external release and keeping track of the system versions that have been released for customer use. 4 Chapter 25 Configuration management Configuration management activities 5 Chapter 25 Configuration management CM terminology Term Explanation Configuration item or software configuration item (SCI) Anything associated with a software project (design, code, test data, document, etc.) that has been placed under configuration control. There are often different versions of a configuration item. Configuration items have a unique name. Configuration control The process of ensuring that versions of systems and components are recorded and .