Short Note on Size-Oriented Metrics

Size Oriented Metrics derived by normalizing quality and productivity Point Metrics measures by considering size of the software that has been produced. The organization builds a simple record of size measure for the software projects. It is built on past experiences of organizations. It is a direct measure of software.

This metrics is one of simplest and earliest metrics that is used for computer program to measure size. Size Oriented Metrics are also used for measuring and comparing productivity of programmers. It is a direct measure of a Software. The size measurement is based on lines of code computation. The lines of code are defined as one line of text in a source file.

While counting lines of code, simplest standard is:

  • Don’t count blank lines
  • Don’t count comments
  • Count everything else
  • The size-oriented measure is not a universally accepted method.

Simple set of size measure that can be developed is as given below:

Size = Kilo Lines of Code (KLOC) 
Effort = Person / month
Productivity = KLOC / person-month
Quality = Number of faults / KLOC
Cost = $ / KLOC
Documentation = Pages of documentation / KLOC 

Advantages :

  • Using these metrics, it is very simple to measure size.
  • Artifact of Software development which is easily counted.
  • LOC is used by many methods that are already existing as a key input.
  • A large body of literature and data based on LOC already exists.

Disadvantages :

  • This measure is dependent upon programming language.
  • This method is well designed upon programming language.
  • It does not accommodate non-procedural languages.
  • Sometimes, it is very difficult to estimate LOC in early stage of development.
  • Though it is simple to measure but it is very hard to understand it for users.
  • It cannot measure size of specification as it is defined on code.

Example –
For a size oriented metrics, software organization maintains records in tabular form. The typical table entries are: Project Name, LOC, Efforts, Pages of documents, Errors, Defects, Total number of people working on it.

Project Name LOC Effort Cost ($) Doc. (pages) Errors Defects People
ABC 10, 000 20 170 400 100 12 4
PQR 20, 000 60 300 1000 129 32 6
XYZ 35, 000 65 522 1290 280 87 7

Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.

My Personal Notes arrow_drop_up

Check out this Author's contributed articles.

If you like GeeksforGeeks and would like to contribute, you can also write an article using or mail your article to See your article appearing on the GeeksforGeeks main page and help other Geeks.

Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.

Article Tags :


Please write to us at to report any issue with the above content.