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
- 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.
- 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.
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|
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.
- Short Note on Function-Oriented Metrics
- Short note on Behavioral Model
- Short note on Data Dictionary
- Short note on Risk Assessment and Risk Mitigation
- Short Note on Activity and Swimlane Diagram
- Short note on Project Scheduling
- Short Note on Data Visualization
- Short Note on Work Breakdown Structure (WBS)
- Short Note on Barrier Analysis
- Short note on Reactive and Proactive RCA
- Software Engineering | Halstead’s Software Metrics
- Software Engineering | Identifying Software Development Metrics
- Software Measurement and Metrics
- Extended Function Point (EFP) Metrics
- Product Metrics in Software Engineering
- Measuring Software Quality using Quality Metrics
- Metrics for the Design Model of the Product
- Core Metrics to Manage Modern Process
- Inspection Metrics in Software Engineering
- Note on Checkpoints of the Process
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. 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.