TAILIEUCHUNG - Lecture Software engineering: Chapter 25 – Configuration Management

This lecture discuss the key concepts related to software process improvement. Triple constraint is the most important concern for project managers and software process infrastructure plays important role in successful project completion. The assessment of existing process based on the defined effective process may help in successful project completion. | Chapter 25 – Configuration Management Chapter 25 Configuration management 1 11/12/2014 Topics covered Version management System building Change management Release management Chapter 25 Configuration management 2 11/12/2014 Configuration management Software systems are constantly changing during development and use. 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. CM is essential for team projects to control changes made by different developers Chapter 25 Configuration management 3 11/12/2014 CM activities 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. 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. Release management Preparing software for external release and keeping track of the system versions that have been released for customer use. Chapter 25 Configuration management 4 11/12/2014 Configuration management activities Chapter 25 Configuration management 5 11/12/2014 Agile development and CM Agile development, where components and systems are changed several times per day, is impossible without using CM tools. The definitive versions of components are held in a shared project repository and developers copy these into their own workspace. They make changes to the code then use system building tools to create a new system on their own computer for testing. Once they are happy with the changes made, they return the modified components to the project .

• Kỹ thuật lập trình
• Software engineering
• Công nghệ phần mềm
• Lecture Software engineering
• Software project management
• Quality management
• Metric for design model
• Object oriented software engineering
• Practical software development
• Object orientation
• Software quality
• Software engineering projects
• Introduction to software engineering
• Lecture Introduction to software engineering
• Software process
• Software engineering ethics
• Professional software development
• Software process activities
• Software engineering diversity
• Introduction Software Engineering
• Software products
• FAQs about software engineering
• Essential attributes of good software
• Importance of software engineering
• Software processes
• Aspect oriented software engineering
• The separation of concerns
• Software engineering with aspects
• Quality concepts
• Detail Design
• Design Software Engineering
• Implementation Software Engineering
• Build Software Engineering
• Buy Software Engineering
• Requirement engineering
• Requirement engineering process
• Software requirements engineering
• Lecture Software requirements engineering
• Requirements engineering
• Software requirements engineering
• Lecture Software requirements engineering
• System engineering
• Software requirements document
• Requirements engineering process tasks