Browse Prior Art Database

Automatic Estimator for Source Code Modifications

IP.com Disclosure Number: IPCOM000038943D
Original Publication Date: 1987-Mar-01
Included in the Prior Art Database: 2005-Feb-01
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Bartek, BA: AUTHOR

Abstract

A method is described which provides a quick and accurate way for a programmer to report the work effort involved in making changes to source code. It can be run at any point in or after a development cycle with accurate results. It is independent of a particular programmer's knowledge of a file's history. The number of lines of code that were added, modified or deleted during the development of a software product, is sometimes of interest to the product developers. These numbers are used in resource planning for future products. The two existing methods for counting up the lines of codes changed are not satisfactory. In the first method, a programmer manually compares a previous version of the source code to the new version. This method is very tedious and time consuming, especially if the change is large.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 63% of the total text.

Page 1 of 1

Automatic Estimator for Source Code Modifications

A method is described which provides a quick and accurate way for a programmer to report the work effort involved in making changes to source code. It can be run at any point in or after a development cycle with accurate results. It is independent of a particular programmer's knowledge of a file's history. The number of lines of code that were added, modified or deleted during the development of a software product, is sometimes of interest to the product developers. These numbers are used in resource planning for future products. The two existing methods for counting up the lines of codes changed are not satisfactory. In the first method, a programmer manually compares a previous version of the source code to the new version. This method is very tedious and time consuming, especially if the change is large. Manually counting the changes can be accurate only if ample time is allowed. The second method uses a utility called LOC to determine the changed lines of code. LOC is a program which counts the lines of code in a source file. A programmer runs LOC on both the previous and new version of the source code. The difference between the two line of code counts is used for the number of lines of code changed. The problem with this method is that it is comparing magnitudes only. It does not distinguish between lines of code that were added, modified or deleted. Also, the results can be inaccurate. A file can be changed...