Professional Documents
Culture Documents
Software Product Quality Metrics
Software Product Quality Metrics
Software Reliability:
The probability that a program will perform its specified function,
for a stated time period, under specified conditions.
Reliability metrics:
Mean Time To Repair (MTTR): average time to restore a system after a failure
Reliability models neglect the time needed to restore the system after a failure.
• company's reputation
• warranty (maintenance) costs
• future business
• contract requirements
• custom satisfaction
3.1.2. Defect rate (density)
Example:
“The latent defect rate for this product, during next four years, is 2.0 defects per KLOC”
Lines Of Code
-Different counting tools
-Defect rate metric has to be completed with the counting method for LOC!
-Not recommended to compare defect rates of two products written in different language
Defect rate for subsequent versions (releases) of a software product:
Example:
field defects – found by the customer (reported problems that required bug fixing)
internal defects – found internally
Reliability:
often used with safety-critical systems such as: airline traffic control systems, avion
(usage profile and scenarios are better defined)
Defect density:
in many commercial systems (systems for commercial use)
• there is no typical user profile
• development organizations use defect rate for maintenance cost and resource
• MTTF is more difficult to implement and may not be representative of all custom
3.2. Customer Oriented Metrics
IBM: CUPRIMDSO
(capability/functionality, usability, performance, reliability, installability, maintainability
documentation /information, service and overall)
Hewlett-Packard: FURPS
(functionality, usability, reliability, performance and service)
Metrics:
– Percent of completely satisfied customers
– Percent of satisfied customers
– Percent of dissatisfied customers
– Percent of no satisfied customers