Skip to content

Commit a72c580

Browse files
committed
Add technical report on SLOC counting
1 parent 3fd54ca commit a72c580

1 file changed

Lines changed: 11 additions & 1 deletion

File tree

docs/references/bib.bib

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1695,10 +1695,20 @@ @inproceedings{abdalkareem:2017a
16951695

16961696
@techreport{park:1992a,
16971697
abstract = {This report presents guidelines for defining, recording, and reporting two frequently used measures of software size—physical source lines and logical source statements. We propose a general framework for constructing size definitions and use it to derive operational methods for reducing misunderstandings in measurement results. We show how the methods can be applied to address the information needs of different users while maintaining a common definition of software size.},
1698-
author = {Robert E Park},
1698+
author = {Robert E. Park},
16991699
institution = {Software Engineering Institute, Carnegie Mellon University},
17001700
keywords = {static analysis, software development, cocomo, sloc, lloc},
17011701
title = {{Software Size Measurement: A Framework for Counting Source Statements}},
17021702
url = {https://resources.sei.cmu.edu/asset_files/TechnicalReport/1992_005_001_16082.pdf},
17031703
year = {1992},
17041704
}
1705+
1706+
@techreport{nguyen:2007a,
1707+
abstract = {Source Lines of Code (SLOC or LOC) is one of the most widely used sizing metrics in industry and literature. It is the key input for most of major cost estimation models such as COCOMO, SLIM, and SEER-SEM. Although the SEI and the IEEE have established SLOC definitions and guidelines to standardize counting practice, inconsistency in SLOC measurements still exists in industry and research. This problem causes the incomparability of SLOC metric among organizations and the inaccuracy of cost estimation. This report presents a set of counting standards that defines what and how to count SLOC. Our experience with the development and use of the USC CodeCount™ toolset, a popular utility that automates the SLOC counting process, suggests that this problem can be alleviated by the use of a reasonable and unambiguous counting standard guide and with the support of a configurable counting tool. },
1708+
author = {Vu Nguyen and Sophia Deeds-Rubin and Thomas Tan and Barry W. Boehm},
1709+
institution = {Center for Systems and Software Engineering, University of Southern California},
1710+
keywords = {static analysis, software development, cocomo, sloc, lloc},
1711+
title = {{A SLOC Counting Standard}},
1712+
url = {http://csse.usc.edu/TECHRPTS/2007/usc-csse-2007-737/usc-csse-2007-737.pdf},
1713+
year = {2007},
1714+
}

0 commit comments

Comments
 (0)