Abstract
Software metrics provide a quantitative basis for planning and predicting software development processes. Therefore the quality of software can be controlled and improved easily. Quality in fact aids higher productivity, which has brought software metrics to the forefront. This research paper focuses on different views on software quality. Moreover, many metrics and models have been developed; promoted and utilized resulting in remarkable successes. This paper examines the realm of software engineering to see why software metrics are needed and also reviews their contribution to software quality and reliability. Results can be improved further as we acquire additional experience with variety of software metrics. These experiences can yield tremendous benefits and betterment in quality and reliability.
Highlights
Software metrics are valuable entity in the entire software life cycle
The software product should be seen as an abstract object that begins from an initial statement of requirement to a finished software product, including source and object code and the several forms of documentation exhibited during the various stages of its development
When we examine the patterns of strengths and weaknesses of function point metrics, we observe that for economic studies and for studies that include non-coding work such as specifications, function points are clearly superior to lines of code metrics. [12]
Summary
Software metrics are valuable entity in the entire software life cycle. They provide measurement for the software development, including software requirement documents, designs, programs and tests. The successful execution of the control over software quality requires software metrics. The concepts of software metrics are coherent, understandable and well established, and many metrics related to the product quality have been developed and used. Software metrics provides measurement of the software product and the process of software production. The software product should be seen as an abstract object that begins from an initial statement of requirement to a finished software product, including source and object code and the several forms of documentation exhibited during the various stages of its development. Precisely definable—so that it is clear how the metric can be evaluated; Objective, to the greatest extent possible; obtainable (i.e., at reasonable cost); Valid—the metric should measure what it is intended to measure; and Robust—relatively insensitive to (intuitively) insignificant changes in the process or product
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
