Page 81 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Unit 4: Introduction to Validation, Metrics

Notes
Table 4.2: Measures and Metrics
Measure Metrics
1. Customer Number of system enhancement requests per year Number of
satisfaction index maintenance fix requests per year User friendliness: call volume
to customer service hotline User friendliness: training time per
new user Number of product recalls or fix releases (software
vendors) Number of production re-runs (in-house information
systems groups)
2. Delivered defect Normalized per function point (or per LOC) At product delivery
quantities (first 3 months or first year of operation) Ongoing (per year
of operation) By level of severity By category or cause, e.g.:
requirements defect, design defect, code defect, documentation/
on-line help defect, defect introduced by fixes, etc.
3. Responsiveness Turnaround time for defect fixes, by level of severity Time for
(turnaround time) minor vs. major enhancements; actual vs. planned elapsed time
to users (by customers) in the first year after product delivery
4. Complexity of McCabe’s cyclomatic complexity counts across the system
delivered product Halstead’s measure Card’s design complexity measures
Predicted defects and maintenance costs, based on complexity
measures
5. Cost of defects Business losses per defect that occurs during operation Business
interruption costs; costs of work-arounds Lost sales and
lost goodwill Litigation costs resulting from defects Annual
maintenance cost (per function point) Annual operating cost
(per function point) Measurable damage to your boss’s career
6. Costs of quality Costs of reviews, inspections and preventive measures Costs
activities of test planning and preparation Costs of test execution, defect
tracking, version and change control Costs of diagnostics,
debugging and fixing Costs of tools and tool support Costs of
tools and tool support Costs of test case library maintenance
Costs of testing & QA education associated with the product
Costs of monitoring and oversight by the QA organization (if
separate from the development and test organizations)
7. Re-work Re-work effort (hours, as a percentage of the original coding
hours) Re-worked LOC (source lines of code, as a percentage
of the total delivered LOC) Re-worked software components
(as a percentage of the total delivered components)
8. Reliability Availability (percentage of time a system is available, versus the
time the system is needed to be available) Mean time between
failure (MTBF) Mean time to repair (MTTR) Reliability ratio
(MTBF / MTTR) Number of product recalls or fix releases
Number of production re-runs as a ratio of production runs
9. Test coverage Breadth of functional coverage Percentage of paths, branches
or conditions that were actually tested Percentage by criticality
level: perceived level of risk of paths The ratio of the number
of detected faults to the number of predicted faults.

LOVELY PROFESSIONAL UNIVERSITY 75