J-STD-0 1 6-1 995

Page 204

Annex 0
Candidate management indicators

(informative)

0.1 Scope

This annex identifies a set of management indicators that might be used on a software
development project. It is informative only, provided to aid in using this standard.

0.2 Candidate indicators

Given below is a set of candidate management indicators that might be used on a software
development project. There is no intent t o impose these indicators or t o preclude others.

Requirements volatility: total number of requirements and requirement changes over

time.
Software size: planned and actual number of units, lines of code, or other size
measurement over time.
Software staffing: planned and actual staffing levels over time.
Software complexity: complexity of each software unit.
Software progress: planned and actual number of software units designed,
implemented, unit tested, and integrated over time.
Problemlchange report status: total number, number closed, number opened in the
current reporting period, age, priority.
Build release content: planned and actual number of software units released in each
build.
Computer hardware resource utilization: planned and actual use of computer hardware
resources (such as processor capacity, memory capacity, input/output device capacity,
auxiliary storage device capacity, and communications/network equipment capacity)
over time.
Milestone performance: planned and actual dates of key project milestones.
Scraphework: amount of resources expended t o replace or revise software products
after they are placed under project-level or higher configuration control.
Effect of reuse: a breakout of each of the indicators above for reused versus new
software products.