Software errors and complexity: an empirical investigation0
Communications of the ACM
Module size: a standard or heuristic?
Journal of Systems and Software - Special issue on the fifth Minnowbrook workshop on software performance evaluation
On the criteria to be used in decomposing systems into modules
Communications of the ACM
Composite Structure Design
The Elements of Programming Style
The Elements of Programming Style
A discriminant metric for module cohesion
ICSE '84 Proceedings of the 7th international conference on Software engineering
ICSE '79 Proceedings of the 4th international conference on Software engineering
Recent advances in software measurement (abstract and references for talk)
ICSE '90 Proceedings of the 12th international conference on Software engineering
Methodology for Validating Software Metrics
IEEE Transactions on Software Engineering
An annotated bibliography on software maintenance
ACM SIGSOFT Software Engineering Notes
A measure for composite module cohesion
ICSE '92 Proceedings of the 14th international conference on Software engineering
Software complexity and maintenance costs
Communications of the ACM
A Unified Framework for Cohesion Measurement in Object-OrientedSystems
Empirical Software Engineering
COMPSAC '04 Proceedings of the 28th Annual International Computer Software and Applications Conference - Volume 01
Improving Cohesion Metrics for Classes by Considering Dependent Instance Variables
IEEE Transactions on Software Engineering
Enabling Reuse-Based Software Development of Large-Scale Systems
IEEE Transactions on Software Engineering
Software faults: a quantifiable definition
Advances in Engineering Software
A design perspective on modularity
Proceedings of the tenth international conference on Aspect-oriented software development
Hi-index | 0.02 |
A central issue in programming practice involves determining the appropriate size and information content of a software module. This study attempted to determine the effectiveness of two widely used criteria for software modularization, strength and size, in reducing fault rate and development cost. Data from 453 FORTRAN modules developed by professional programmers were analyzed. The results indicated that module strength is a good criterion with respect to fault rate, whereas arbitrary module size limitations inhibit programmer productivity. This analysis is a first step toward defining empirically based standards for software modularization.