The document discusses change management, software configuration management, and software defects. It provides information on: 1. Elements of a change management process including submitting change requests, reviewing requests, identifying feasibility, approving changes, and implementing changes. 2. The purpose of configuration management to establish and maintain software integrity throughout a project. It lists elements like configuration identification, change control, and status accounting. 3. Software defects are often caused by poor configuration management when the wrong code versions are used. Timely defect discovery and correction can reduce costs.

1. 06-Feb-2012
Session 7
Change
&
Defect/Issue management
CHANGE MANAGEMENT
Why change management is important?
Group work
• Create a simple change management process
1

2. 06-Feb-2012
Change management process elements 1.a. Change request form
1. Submit change request • Change description
2. Review change request • Reasons for change (including business drivers)
3. Identify change feasibility • Benefits of change
4. Approve change request • Costs of change
5. Implement change request • Impacts of change
• Supporting documentation
3.a. Change feasibility report Change register
• Change requirements • The ‘Change Register’ is the log / database within which
• Change options all requests for changes are registered and tracked
• Change costs and benefits through to resolution
Summary Description Approval Implementation
• Change risks and issues ID
Date Raised Assessed
Status Description of Change Description of Impact
Impact Rating Change Approval Approval
Actions Undertaken
Completion Review
Raised By By (L/M/H/C) Approver(s) Status Date Date Date
• Change impact
• Change recommendations & plan
• What is the purpose of the Change register? How can
you use the data collected?
What is SCM?
• The fundamental purpose of Configuration
Management(CM) is to establish and maintain the
integrity and control of software products throughout a
project’s life cycle.
SOFTWARE CONFIGURATION
MANAGEMENT
2

3. 06-Feb-2012
The most frustrating software problems are The elements of the SCM process
often caused by poor configuration
management. • Configuration identification of artifacts/work products
• The latest version of source code cannot be found. used or developed by a project
• A difficult defect that was fixed at great expense suddenly • Change control
reappears. • Status accounting used in the development, release, and
• A developed and tested feature is mysteriously missing. maintenance of a project
• A fully tested program suddenly does not work.
• Project delivery and release management procedures
• The wrong version of the code was tested.
• There is no traceability between the software requirements, • Establishment of a Software Development Library (SDL)
documentation, and code. and maintaining the integrity of the work products
• Programmers are working on the wrong version of the code.
• No one knows which modules comprise the software system
delivered to the customer.
When do we introduce defects?
When do we discover defects?
What is the cost of defect correction?
SOFTWARE DEFECTS
3