Software measurement

From HandWiki

Software measurement is a quantified attribute (see also: measurement) of a characteristic of a software product or the software process. It is a discipline within software engineering. The process of software measurement is defined and governed by ISO Standard ISO 15939 (software measurement process).

Software metrics

Software size, functional measurement

The primary measurement of software is size, specifically functional size. The generic principles of functional size are described in the ISO/IEC 14143.[1] Software size is principally measured in function points. It can also be measured in lines of code, or specifically, source lines of code (SLOC) which is functional code excluding comments. Whilst measuring SLOC is interesting, it is more an indication of effort than functionality. Two developers could approach a functional challenge using different techniques, and one might need only write a few lines of code, and the other might need to write many times more lines to achieve the same functionality. The most reliable method for measuring software size is code agnostic, from the user's point of view - in function points.

Measuring code

One method of software measurement is metrics that are analyzed against the code itself. These are called software metrics and including simple metrics, such as counting the number of lines in a single file, the number of files in an application, the number of functions in a file, etc. Such measurements have become a common software development practice.[2]

Measuring software complexity, cohesion and coupling

There are also more detailed metrics that help measure things like software complexity, Halstead, cohesion, and coupling.

See also

References

  1. ISO/IEC JTC 1/SC 7 Software and systems engineering (2007-02-01). "ISO/IEC 14143". International Standards Organization. https://www.iso.org/standard/38931.html. Retrieved 2019-02-26. 
  2. Binstock, Andrew. "Integration Watch: Using metrics effectively". SD Times. BZ Media. http://www.sdtimes.com/link/34157. Retrieved April 18, 2017. 

Further reading