06-Feb-2012

1

Session 7

Change

&

Defect/Issue management CHANGE MANAGEMENT

Why change management is important?

Group work

• Create a simple change management process

06-Feb-2012

2

Change management process elements

1. Submit change request2. Review change request3. Identify change feasibility4. Approve change request5. Implement change request

1.a. Change request form

• Change description• Reasons for change (including business drivers)• Benefits of change• Costs of change• Impacts of change• Supporting documentation

3.a. Change feasibility report

• Change requirements• Change options• Change costs and benefits• Change risks and issues• Change impact• Change recommendations & plan

Change register

• The ‘Change Register’ is the log / database within which all requests for changes are registered and tracked through to resolution

• What is the purpose of the Change register? How can you use the data collected?

Summary Description Approval Implementation

IDDate

RaisedRaised

ByAssessed

ByStatus Description of Change Description of Impact Impact Rating

(L/M/H/C)Change

Approver(s)Approval

StatusApproval

DateActions Undertaken

Completion Date

Review Date

SOFTWARE CONFIGURATION MANAGEMENT

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.

06-Feb-2012

3

The most frustrating software problems are often caused by poor configuration management.• The latest version of source code cannot be found.• A difficult defect that was fixed at great expense suddenly

reappears.• A developed and tested feature is mysteriously missing.• A fully tested program suddenly does not work.

• The wrong version of the code was tested.• There is no traceability between the software requirements,

documentation, and code.• Programmers are working on the wrong version of the code.

• No one knows which modules comprise the software system delivered to the customer.

The elements of the SCM process

• Configuration identification of artifacts/work products used or developed by a project

• Change control• Status accounting used in the development, release, and

maintenance of a project• Project delivery and release management procedures• Establishment of a Software Development Library (SDL)

and maintaining the integrity of the work products

SOFTWARE DEFECTS

When do we introduce defects?When do we discover defects?What is the cost of defect correction?