View in EDS PDF Full Text

Beware of Counting LOC.

Saved in:
Bibliographic Details
Title: Beware of Counting LOC.
Authors: Armour, Philip G.1 armour@corvusintl.com
Source: Communications of the ACM. Mar2004, Vol. 47 Issue 3, p21-24. 4p.
Subjects: Software productivity measurement, Source code, Function point analysis, International Function Point Users Group (Organization), Information retrieval, Computer science
Abstract: The most common software sizing metric is source Lines of Code (LOC). Counting LOC implies trying to size a system, by counting the number of compiled source codes and lines that have been created. The need to count and measure LOC is to evaluate the power of the computer system, many times to determine the size of the system that is being built. The situation offers a dilemma, as LOC cannot be reckoned before the system is built, and once the system has been built, estimation of LOC does not remain necessary. This institutes the necessity to seek other ways to measure the power of computer system, and Function Points is one such way. This approach, adopted by the International Function Point Users Group involves counting and weighting input, output and data storage elements. Such counts are more helpful; as they can be reckoned at the time estimates are required in the project. However, this system is not free from drawbacks either. Function Point analysis may not always count transform behavior, state behavior, platform interaction, design dependence and a number of other attributes that legitimately affect the size of the system.
Database: Engineering Source
FullText Links:
  – Type: pdflink
Text:
  Availability: 0
Header DbId: egs
DbLabel: Engineering Source
An: 12456343
AccessLevel: 6
PubType: Periodical
PubTypeId: serialPeriodical
PreciseRelevancyScore: 0
IllustrationInfo
Items – Name: Title
  Label: Title
  Group: Ti
  Data: Beware of Counting LOC.
– Name: Author
  Label: Authors
  Group: Au
  Data: <searchLink fieldCode="AR" term="%22Armour%2C+Philip+G%2E%22">Armour, Philip G.</searchLink><relatesTo>1</relatesTo><i> armour@corvusintl.com</i>
– Name: TitleSource
  Label: Source
  Group: Src
  Data: <searchLink fieldCode="JN" term="%22Communications+of+the+ACM%22">Communications of the ACM</searchLink>. Mar2004, Vol. 47 Issue 3, p21-24. 4p.
– Name: Subject
  Label: Subjects
  Group: Su
  Data: <searchLink fieldCode="DE" term="%22Software+productivity+measurement%22">Software productivity measurement</searchLink><br /><searchLink fieldCode="DE" term="%22Source+code%22">Source code</searchLink><br /><searchLink fieldCode="DE" term="%22Function+point+analysis%22">Function point analysis</searchLink><br /><searchLink fieldCode="DE" term="%22International+Function+Point+Users+Group+%28Organization%29%22">International Function Point Users Group (Organization)</searchLink><br /><searchLink fieldCode="DE" term="%22Information+retrieval%22">Information retrieval</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+science%22">Computer science</searchLink>
– Name: Abstract
  Label: Abstract
  Group: Ab
  Data: The most common software sizing metric is source Lines of Code (LOC). Counting LOC implies trying to size a system, by counting the number of compiled source codes and lines that have been created. The need to count and measure LOC is to evaluate the power of the computer system, many times to determine the size of the system that is being built. The situation offers a dilemma, as LOC cannot be reckoned before the system is built, and once the system has been built, estimation of LOC does not remain necessary. This institutes the necessity to seek other ways to measure the power of computer system, and Function Points is one such way. This approach, adopted by the International Function Point Users Group involves counting and weighting input, output and data storage elements. Such counts are more helpful; as they can be reckoned at the time estimates are required in the project. However, this system is not free from drawbacks either. Function Point analysis may not always count transform behavior, state behavior, platform interaction, design dependence and a number of other attributes that legitimately affect the size of the system.
PLink https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=12456343
RecordInfo BibRecord:
  BibEntity:
    Identifiers:
      – Type: doi
        Value: 10.1145/971617.971635
    Languages:
      – Code: eng
        Text: English
    PhysicalDescription:
      Pagination:
        PageCount: 4
        StartPage: 21
    Subjects:
      – SubjectFull: Software productivity measurement
        Type: general
      – SubjectFull: Source code
        Type: general
      – SubjectFull: Function point analysis
        Type: general
      – SubjectFull: International Function Point Users Group (Organization)
        Type: general
      – SubjectFull: Information retrieval
        Type: general
      – SubjectFull: Computer science
        Type: general
    Titles:
      – TitleFull: Beware of Counting LOC.
        Type: main
  BibRelationships:
    HasContributorRelationships:
      – PersonEntity:
          Name:
            NameFull: Armour, Philip G.
    IsPartOfRelationships:
      – BibEntity:
          Dates:
            – D: 01
              M: 03
              Text: Mar2004
              Type: published
              Y: 2004
          Identifiers:
            – Type: issn-print
              Value: 00010782
          Numbering:
            – Type: volume
              Value: 47
            – Type: issue
              Value: 3
          Titles:
            – TitleFull: Communications of the ACM
              Type: main
ResultId 1