1
Configuration Management
Lecture # 4
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Configuration Management: Minimizing Confusion in Software Development, Slides of Software Project Management
An in-depth overview of software configuration management (scm), a crucial practice in software engineering. It covers the sources and importance of change, the role of scm in minimizing confusion, the key scm functions (identification, version control, change control, configuration audit, and status accounting/reporting), and the comprehensive change control process. The document emphasizes the need for management commitment to scm and how it serves as an umbrella activity throughout the software development lifecycle. It draws insights from industry-leading references on software engineering and quality assurance, making it a valuable resource for students and professionals alike.
Typology: Slides
2022/2023
1 / 50
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Configuration Management: Minimizing Confusion in Software Development and more Slides Software Project Management in PDF only on Docsity!
Configuration Management
Lecture # 4
Agenda
- Change
- Software configuration management
- SCM Functions
Sources of Change - 1
- New business or market conditions dictate changes in product requirements or business rules
- New customer needs demand modification of data produced by information systems, functionality delivered by products, or services delivered by computer-based system
Sources of Change - 2
- Reorganization or business growth / downsizing causes changes in project priorities or software engineering team structure
- Budgetary or scheduling constraints cause a redefinition of the system or product
Confusion
- Confusion arises when changes are not
- Analyzed before they are made
- Recorded before they are implemented
- Reported to those who need to know
- Controlled in a manner that will improve quality and reduce errors
- We need to minimize this confusion, or else our projects will get out of control
Configuration Management
- The art of coordinating software development to minimize confusion is called configuration management
- The goal is to maximize productivity by minimizing mistakes
Purpose of SCM Activities
- Identify change
- Control change
- Ensure that the change is being properly implemented
- Report changes to others who may be interested
SCM provides Cover against
- Lack of visibility
- Lack of control
- Lack of traceability
- Lack of monitoring
- Uncontrolled change
Baseline every Software
Configuration Item
How to Manage Change?
- A baseline is a software configuration management concept that helps us to control change without seriously impeding justifiable change
Baseline
- A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures - IEEE Std. No. 610.12- 1990
Baseline
- Before a software configuration item becomes a baseline, changes may be made quickly and informally
- However, once a baseline is established, changes can be made, but a specific, formal procedure must be applied to evaluate and verify each change request
Baseline
- Typical, work products that are base-lined are - System specification - Software requirements - Design specification - Source code - Test plans/procedures/data - Operational system