1.2 Change Mgmt
- Software systems are subject to continual change requests
- From users
- From developers
- From market forces
- Change management is concerned with keeping managing of these changes
and ensuring that they are implemented in the most cost-effective
way
1.2.0.0 The change management process
fill out change request form;
analyze change request;
if (change is valid) then
assess how change might be implemented
assess code of change
submit request to change control board
if (change is accepted) then
repeat
make changes to software;
submit changed software for quality approval;
until quality is adequate;
create new system version;
else
reject change request;
else
reject change request
|
1.2.0.0 Change request form
- Designed during CM planning process
- Records change required, suggestor of change, reason why change was
suggested and urgency of change
- Records change evaluation, impact analysis, change cost and
recommendations
- from the system maintenance staff
1.2.0.0 Change tracking tools
- A major problem in change management is tracking change status
- Change tracking tools keep track the status of each change request and
automatically ensure that change requests are sent to the right people
at the right time.
- Integrated with E-mail systems allowing electronic change request
distribution
1.2.0.0 Change control board
- Changes should be reviewed by an external group who decide whether
or not they are cost-effective from a strategic and organizational
viewpoint rather than a technical viewpoint
- Should be independent of project responsible for system.
- May include representatives from client and contractor staff
1.2.0.0 Derivation history
- Record of changes applied to a document or code component
- Should record, in outline, the change made, the rationale for the change,
who made the change and when it was implemented
- May be included as a comment in code. If a standard prologue style is
used for the derivation history, tools can process this automatically