Abstract

This paper discusses modularization as a mechanism for improving the flexibility and comprehensibility of a system while allowing the shortening of its development time. The effectiveness of a “modularization ” is dependent upon the criteria used in dividing the system into modules. A system design problem is presented and both a conventional and unconventional decomposition are described. It is shown that the unconventional decompositions have distinct advantages for the goals outlined. The criteria used in arriving at the decompositions are discussed. The unconventional decomposition, if implemented with the conventional assumption that a module consists of one or more subroutines, will be less efficient in most cases. An alternative approach to implementation which does not have this effect is sketched.

Citations

109	A technique for software module specification with examples - Parnas - 1972
79	Information Distribution Aspects of Design Methodology - Parnas
77	The structure of “THE”-multiprogramming system - Dijkstra - 1982
46	Proof of a program: FIND - Hoare - 1971
27	The Structure of the "THE"-Multiprogramming System - Dijkstra - 1968
20	Bliss: A language for systems programming - WULF, RUSSELL, et al. - 1971
17	Another Look at Data - Mealy - 1967
7	Designing Systems Programs - Gouthier, Pont - 1970
6	Dataless programming - Balzer - 1972
3	A View of Programming Languages - Galler, Perlis - 1970
2	Licensing Software Engineers in - Parnas
1	A View of Programming Lu/~grrages, Addison-Wesley - Galler, Perlis - 1970