Programming process productivity measurement system for System/370

Authors:
M. J. Flaherty
Affiliations:
IBM Information Systems and Storage Group, Poughkeepsie, New York
Venue:
IBM Systems Journal
Year:
1985

Citing 7
Cited 1

Software Engineering Economics

Software Engineering Economics
Elements of Software Science (Operating and programming systems series)

Elements of Software Science (Operating and programming systems series)
Programming cost estimate: Is it reasonable?

ICSE '84 Proceedings of the 7th international conference on Software engineering
The Cost of Developing Large-Scale Software

IEEE Transactions on Computers
Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation

IEEE Transactions on Software Engineering
A Look at Japan's Development of Software Engineering Technology

Computer
A Software Development Environment for Improving Productivity

Computer

Simple indicators for tracking software process improvement progress

EuroSPI'06 Proceedings of the 13th European conference on Software Process Improvement

Quantified Score

Hi-index	0.00

Visualization

Abstract

Discussed in this paper are the underlying principles of a programmer productivity measuring system. The key measures (or metrics) are people and lines of code. Definitions of these metrics are refined and qualified, according to the conditions under which they are used. Presented also is a data base design for retaining and retrieving these metrics under a wide variety of applications and other circumstances. Depending on definitions, applications, and other circumstances, productivity measurements may differ widely. On the other hand, after suitable productivity metrics have been defined, consistency of application of the same metrics yields comparable results from project to project.