Software Measurement and Metrics — Purpose and Benefits

What is software measurement?

Software measurement is the process of quantifying attributes of software — the product (size, complexity, defects), the process (effort, time, productivity), and the project (schedule, resources) — using well-defined measures.

A metric is a measurement standard/indicator, e.g.:

• Size metrics: LOC (lines of code), function points (FP), object points.
• Complexity metrics: cyclomatic complexity (McCabe), Halstead metrics, coupling/cohesion measures.
• Quality metrics: defect density, mean time to failure, customer-reported defects.
• Process/project metrics: effort (person-months), schedule (duration), productivity (LOC/PM), schedule slippage, cost variance.

Purpose of measurement

1. Understand and control the software process and product objectively.
2. Predict effort, cost, schedule, and defect levels (estimation models use size/complexity metrics).
3. Compare — across projects, teams, or modules (benchmarking).
4. Identify problem areas early (complex modules → high defect risk).
5. Improve — guide process improvement (e.g., CMM/SPICE) with factual data rather than intuition.

How metrics improve software quality

• Defect density (defects/KLOC) highlights modules needing more testing/refactoring.
• Cyclomatic complexity indicates how many test cases/paths are needed and flags overly complex code that is error-prone.
• Test coverage measures (branch/statement coverage) reveal untested areas.
• Mean time to failure / reliability metrics quantify the product's robustness.

How metrics improve project management

• Estimation: size (FP) and past productivity data drive effort/cost/schedule estimates.
• Tracking/control: effort and schedule variance metrics alert managers to deviations early (earned value analysis).
• Productivity trends guide staffing and process changes.
• Risk management: complexity metrics flag risky modules requiring more review/testing.

Requirements for good metrics (Practical Software Measurement principles)

• Metrics must be objective, measurable, consistent, and useful; data must be collected consistently over time; metrics should be tied to goals (GQM — Goal-Question-Metric) so they drive decisions rather than being collected for their own sake.

Summary: measurement turns software development from an art into a manageable engineering discipline — giving objective data to predict, control, and improve both product quality and project management.