1.) Based on the size of the software project data is measured, including cost and effort, pages, defects etc.
2.)Mainly uses the LOC as the normalization value.
3.)Advantage of size oriented metric is it can be easily counted, large body of literature and data based on LOC.
4.)It is language dependent, Programmer dependent.
5.)It is useful for projects with similar environment.
6.)Therefore, size-oriented metrics are not universally accepted as the best way to measure the software process.
7.) Example:
i.) Productivity = Size / Effort
= kLOC / person-month
ii.) Quality = Errors / Size
= Errors / kLOC
iii.) Cost = $ / kLOC
iv.) Documentation= pages / kLOC
8.) It is derived by normalizing the quality and/or productivity measures by considering the size of the software produced
9.)There are thousand lines of code (KLOC) which are often chosen as the normalization value
10.)Metrics include
Errors per KLOC - Errors per person-month
Defects per KLOC - KLOC per person-month
Dollars per KLOC - Dollars per page of documentation
Pages of documentation per KLOC
11.) Attempt to quantify software projects by using the size of the project to normalize other quality measures
• Possible data to collect:
• number of lines of code
• number of person-months to complete
• cost of the project
• number of pages of documentation
• number of errors corrected before release
• number of bugs found post release
12.) - The opponents are the one that argue with KLOC measurements
i.)Are dependent on the programming language
ii.)Penalize well-designed but short programs
iii.) Cannot easily accommodate non-procedural languages
iv.) Require a level of detail that may be difficult to achieve
13.) Proponent of line of code measure claims that LOC is an “artefact” of all software development projects that can be easily counted, that many existing software estimation
14.)Models use LOC or KLOC as a key input, and that a large body of literature and data predicated on LOC is already exists.
and 5 others joined a min ago.
teamques10
★ 68k