60 likes | 279 Views
Metrics. PART TWO Managing Software Projects. Chapter 4 Metrics. Measure 1 Measure 2 …… …… …… Measure n. indicators. PART TWO – Managing - Metrics. Size-Oriented Metrics. The normalization value: lines of code ( LOC ). Errors per KLOC. Errors per person-month.
E N D
Metrics PART TWOManaging Software Projects Chapter 4 Metrics Measure 1 Measure 2 …… …… …… Measure n indicators
PART TWO – Managing - Metrics Size-Oriented Metrics The normalization value: lines of code (LOC) Errors per KLOC Errors per person-month Defects per KLOC LOC per person-month $ per LOC $ per Page of documentation Page of documentation per KLOC Programming language dependent Penalize well-designed but shorter programs
PART TWO – Managing - Metrics weighting factor count simple avg. complex measurement parameter number of user inputs X 3 4 6 = number of user outputs X 4 5 7 = number of user inquiries X 3 4 6 = number of files X 7 10 15 = number of ext.interfaces X 5 7 10 = count-total LOC/FP Table on p.94 Function-Oriented Metrics The normalization value: function point (FP) Complexity adjustment values p.91
PART TWO – Managing - Metrics Product Revision Product Transition Product Operation Correctness Robustness Efficiency Integrity Usability Risk Metrics for Software Quality McCall & Cavano (1978) Understandability Maintainability Flexibility Testability Portability Reusability Interoperability
PART TWO – Managing - Metrics Correctness: defects / KLOC Maintainability: Mean-Time-To-Change (MTTC) Integrity: Threat – the probability that an attack of a specific type will occur within a given time; Security– the probability that the attack of a specific type will be repelled. Usability: user-friendliness (Ch.15) Defect Removal Efficiency (DRE) := E / (E+D) Errors found before delivery Errors found after delivery
PART TWO – Managing - Metrics Unstable data Mean value Unstable projects Statistical Process Control: -- Control Chart [Walter Shewart 1920s] 1. Moving Range Control Chart 2. Individual Control Chart Stable