Javatpoint Logo
Javatpoint Logo

Size Oriented Metrics

LOC Metrics

It is one of the earliest and simpler metrics for calculating the size of the computer program. It is generally used in calculating and comparing the productivity of programmers. These metrics are derived by normalizing the quality and productivity measures by considering the size of the product as a metric.

Following are the points regarding LOC measures:

  1. In size-oriented metrics, LOC is considered to be the normalization value.
  2. It is an older method that was developed when FORTRAN and COBOL programming were very popular.
  3. Productivity is defined as KLOC / EFFORT, where effort is measured in person-months.
  4. Size-oriented metrics depend on the programming language used.
  5. As productivity depends on KLOC, so assembly language code will have more productivity.
  6. LOC measure requires a level of detail which may not be practically achievable.
  7. The more expressive is the programming language, the lower is the productivity.
  8. LOC method of measurement does not apply to projects that deal with visual (GUI-based) programming. As already explained, Graphical User Interfaces (GUIs) use forms basically. LOC metric is not applicable here.
  9. It requires that all organizations must use the same method for counting LOC. This is so because some organizations use only executable statements, some useful comments, and some do not. Thus, the standard needs to be established.
  10. These metrics are not universally accepted.

Based on the LOC/KLOC count of software, many other metrics can be computed:

  1. Errors/KLOC.
  2. $/ KLOC.
  3. Defects/KLOC.
  4. Pages of documentation/KLOC.
  5. Errors/PM.
  6. Productivity = KLOC/PM (effort is measured in person-months).
  7. $/ Page of documentation.

Advantages of LOC

  1. Simple to measure

Disadvantage of LOC

  1. It is defined on the code. For example, it cannot measure the size of the specification.
  2. It characterizes only one specific view of size, namely length, it takes no account of functionality or complexity
  3. Bad software design may cause an excessive line of code
  4. It is language dependent
  5. Users cannot easily understand it

Youtube For Videos Join Our Youtube Channel: Join Now


Help Others, Please Share

facebook twitter pinterest

Learn Latest Tutorials


Trending Technologies

B.Tech / MCA