Software Quality Metrics

by Amira Smale, June 2014

300 words

1 page


1. Identify ideas discussed that were new to you.

A new idea from the article was the use of physical and logical lines of code (LOC) in the calculation of a software product’s defect rate density. This is different from normal calculation procedure of straight LOC counting. Most of the commercial software companies are profit oriented, and do not use the mean time to failure (MTTF) method to determine their software quality (Kan 1).

The use of the function point metric in the calculation of the defect density metric of a software product was new. If the defect per unit in a collection of executable programs is low, then the software program will have better quality. Obtaining consumer satisfaction metrics is a new idea. Its use is significant because it shows a statistical overview survey of how customers are content with the quality of a software product (Kan 1).

2. Identify what was unclear in the paper or anything that you did not understand.

In the article, some of the unclear points were the resultant differences that software developers would probably get in program size between counting instructions statements and physical lines. This is difficult to assess because of uncertainty in determining methods that result in higher numbers. Another unclear point is the correlation of mean times to failure and defect density (Kan 1).

3. Identify ideas presented that you disagree with (and why)

I disagree with the practical notion that the intrinsic product quality metrics is not different on practical purposes application. Diverse commercial companies use different systems, which require software developers to use different approaches. Emergency room surgery systems require high quality programs with extremely low fails or defects (Kan 1).

4. In your opinion, the most important/valuable/useful idea presented in the paper

A significant idea includes the analysis of a software product quality from the perspective of the developers and customers. Critical systems use the mean time to failure approach because they are time sensitive. They appreciate the end user requirements and the simplicity of an application that would make a software program easy to use by a consumer (Kan 1).

Work Cited

Kan, Stephen. Top of Form

Bottom of Form

Top of Form

Kan, Stephen. Metrics and Models in Software Quality Engineering. Boston, [Mass.] ;London: Addison-Wesley, 2002. …

Download will start in 20 seconds


Note that all papers are meant for inspiration and reference purposes only! Do not copy papers in full or in part. Papers are provided by other students, who hold the copyright for the content of those papers. All papers were submitted to TurnItIn and will show up as plagiarism if you try to submit any part of them as your own work. Assignment Lab can not guarantee the quality of the user generated content such as sample papers above.