The Elements of Programming Style
The Elements of Programming Style
The effects of symbology and spatial arrangement on the comprehension of software specifications
ICSE '81 Proceedings of the 5th international conference on Software engineering
Methods for improving controlled experimentation in software engineering
ICSE '81 Proceedings of the 5th international conference on Software engineering
Third time charm: Stronger prediction of programmer performance by software complexity metrics
ICSE '79 Proceedings of the 4th international conference on Software engineering
Using a behavioral theory of program comprehension in software engineering
ICSE '78 Proceedings of the 3rd international conference on Software engineering
Program evolution and its impact on software engineering
ICSE '76 Proceedings of the 2nd international conference on Software engineering
A complexity measure based on nesting level
ACM SIGPLAN Notices
Error free code: is it attainable?
ACM SIGPLAN Notices
On the Quality of Examples in Introductory Java Textbooks
ACM Transactions on Computing Education (TOCE)
| Hi-index | 0.00 |
Small programs are those which are written and understood by one. person. Large software systems usually consist of many small programs. The complexity of a small program is a prediction of how difficult it would be for someone to understand the program. This complexity depends of three factors: (1) the size and interelationships of the program itself; (2) the size and interelationships of the internal model of the program's purpose held by the person trying to understand the program; and (3) the complexity of the mapping between the model and the program. A theory of small program complexity based on these three factors is presented. The theory leads to several testable predictions. Experiments are described which test these predictions and whose results could verify or destroy the theory.