| 
|
QuoteRef: parnDL12_1972
topics >
all references >
ThesaHelp:
references p-r
ThesaHelp:
ACM references m-z
Topic:
deployable module or assembly
Topic:
interface between program modules
Topic:
separate a module's interface specification from its implementation
Topic:
information hiding
Topic:
program module as encapsulation
Topic:
in-line code
Topic:
identifying program modules
Topic:
the 'uses' hierarchy for organizing systems
Topic:
dependency analysis
Topic:
data types in Thesa
Reference
Parnas, D.L., "On the criteria to be used in decomposing systems into modules", Communications of the ACM, 15, 12, pp. 1053-1058, December 1972. Google
1053 ;;Quote: how to divide a program into modules
1053+;;Quote: a module is a design decision made before programming starts; it is a responsibility assignment and not a subprogram
1056 ;;Quote: design simple, abstract interfaces between modules, otherwise the table structures must be designed carefully; allows independent development
1056 ;;Quote: a module should hide a design decision instead of dividing a program into major steps; information hiding
1056+;;Quote: a module's interface or definition should not reveal its inner workings
1056 ;;Quote: a module hides a data structure with its internal links, accessing procedures, and modifying procedures
1056+;;Quote: a module should hide the sequence for processing an item; also character codes and alphabetic ordering
1057 ;;Quote: information hiding can lead to inefficient switching between modules due to subroutine calls; allow inline expansion of module code
1057 ;;Quote: module decomposition is independent of a hierarchical structure
1057+;;Quote: should organize modules in a hierarchy over the 'uses' or 'depends on' relation; allows independent use of lower levels
1058 ;;Quote: design modules by hiding difficult or likely-to-change design decisions; not flowcharts or processing steps
ThesaHelp: references p-r (245 items)
ThesaHelp: ACM references m-z (280 items)
Topic: deployable module or assembly (10 items)
Topic: interface between program modules (55 items)
Topic: separate a module's interface specification from its implementation (86 items)
Topic: information hiding (50 items)
Topic: program module as encapsulation (28 items)
Topic: in-line code (7 items)
Topic: identifying program modules (26 items)
Topic: the 'uses' hierarchy for organizing systems (18 items)
Topic: dependency analysis (31 items)
Topic: data types in Thesa (92 items)