Page 253 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Unit 12: Monitoring & Control

12.4.2 Usage of Metadata Notes

When performing the change process, metadata is used for analytical purposes. This may be in
the form of reports or a direct search in the database or the databases where metadata is
maintained. Trace information is often used—for instance, to determine in which configuration
item changes are required due to an event. Also information about variants or branches belonging
to a configuration item is used to determine if a change has effects in several places.
Finally metadata may be used to determine if a configuration item has other outstanding event
registrations, such as whether other changes are in the process of being implemented or are
awaiting a decision about implementation.
Consequence Analysis

When analyzing an event, you must consider the cost of implementing changes. This is not always
a simple matter. The following checklists, adapted from a list by Karl Wiegers, may help in analyzing
the effects of a proposed change. The lists are not exhaustive and are meant only as inspiration.

Identify

 All requirements affected by or in conflict with the proposed change.
 The consequences of not introducing the proposed change.
 Possible adverse effects and other risks connected with implementation.
 How much of what has already been invested in the product will be lost if the proposed
change is implemented—or if it is not.
Check if the proposed change

 Has an effect on nonfunctional requirements, such as performance requirements (ISO
9126, a standard for quality characteristics, defines six characteristics: functional,
performance, availability, usability, maintainability, and portability. The latter five are
typically referred to as nonfunctional.)
 May be introduced with known technology and available resources.
 Will cause unacceptable resource requirements in development or test.
 Will entail a higher unit price.
 Will affect marketing, production, services, or support.

Follow-on effects may be additions, changes, or removals in

 user interfaces or reports, internal or external interfaces, or data storage,
 designed objects, source code, build scripts, include files,
 test plans and test specifications,
 help texts, user manuals, training material, or other user documentation,
 project plan, quality plan, configuration management plan, and other plans,
 other systems, applications, libraries, or hardware components,

Roles

The configuration (or change) control board (CCB) is responsible for change control. A
configuration control board may consist of a single person, such as the author or developer

LOVELY PROFESSIONAL UNIVERSITY 247