1995Systems and Computers in JapanRequires access

A method for measuring programmer debugging performance from key strokes

Y. Takada, Koji Torii

Open publisher page 2 citations

Abstract

Abstract In software development management, a method is necessary that is capable of measuring programmer performance objectively, and easily. This paper presents a method to measure programmer debugging performance from key strokes. Debugging performance is defined as the efficiency of programmer activities from discovery of software failures to correction of their causes. In this method, programmer activity is first categorized into several classes by monitoring key strokes. Programmer property parameters are then extracted by applying model‐based analysis on monitored programmer activity sequences. The programmer model defined here is based on the assumption that a programmer activity sequence is a Markov process. Finally, several programmer performance values are computed from the extracted parameters. The major value is D, which is the estimated length of time required for debugging one fault. Experiments show that the method is effective enough in practical software development. One of these findings is that D shows strong correlation with a value that represents programmer productivity (the length of program development time for common specifications).

About this research paper

What this paper is about

Abstract In software development management, a method is necessary that is capable of measuring programmer performance objectively, and easily. This paper presents a method to measure programmer debugging performance from key strokes. Debugging performance is defined as the efficiency of programmer activities from discovery of software failures to correction of their causes. In this method, programmer activity is first categorized into several classes by monitoring key strokes. Programmer property parameters are then extracted by applying model‐based analysis on monitored programmer activity sequences. The programmer model defined here is based on the assumption that a programmer activity sequence is a Markov process. Finally, several programmer performance values are computed from the extracted parameters. The major value is D, which is the estimated length of time required for debugging one fault. Experiments show that the method is effective enough in practical software development. One of these findings is that D shows strong correlation with a value that represents programmer productivity (the length of program development time for common specifications).

Why it matters

OpenAlex reports 2 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Abstract In software development management, a method is necessary that is capable of measuring programmer performance objectively, and easily. This paper presents a method to measure programmer debugging performance from key strokes. Debugging performance is defined as the efficiency of programmer activities from discovery of software failures to correction of their causes. In this method, programmer activity is first categorized into several classes by monitoring key strokes. Programmer property parameters are then extracted by applying model‐based analysis on monitored programmer activity sequences. The programmer model defined here is based on the assumption that a programmer activity sequence is a Markov process. Finally, several programmer performance values are computed from the extracted parameters. The major value is D, which is the estimated length of time required for debugging one fault. Experiments show that the method is effective enough in practical software development. One of these findings is that D shows strong correlation with a value that represents programmer productivity (the length of program development time for common specifications).

Key concepts: Programmer, Debugging, Computer science, Algorithmic program debugging, Programming language, Key (lock), Software, Process (computing)

Related papers

Back to paper searchBrowse research topicsOriginal source
A method for measuring programmer debugging performance from key strokes — Research Paper | ScholarLens