| 
|
QuoteRef: jackD10_2002
topics >
all references >
Topic:
dependency analysis
Topic:
interface between program modules
Topic:
separate a module's interface specification from its implementation
Topic:
program proof via assertions
Topic:
design pattern
Topic:
shared information for collaborative work
Reference
Jackson, D., "Module dependencies in software design", in Wirsing, M., Knapp, A., Balsamo, S. (ed.), Radical innovations of software and systems engineering in the future. 9th International Workshop, RISSEF 2002, Venice, Italy, October 2002, Springer, LNCS 2941, pp. 198-203. Google
199 ;;Quote: a dependency between modules is an assumption about a module's specification in an environment; a module may have multiple specifications, one per dependency
200 ;;Quote: dependency specification better than dependency graph; no transitivity problem, allows polymorphism, supports pre- and post-conditions, enables substitutivity
200 ;;Quote: design patterns are motivated by dependence considerations; e.g., the Observer pattern uses a generic observer specification, allowing reuse by other observer classes
201 ;;Quote: a design pattern may complicate the code; dependency specifications simplify a pattern
202 ;;Quote: dependency models do not capture shared information; e.g., a format shared between modules
Topic: dependency analysis (34 items)
Topic: interface between program modules (55 items)
Topic: separate a module's interface specification from its implementation (86 items)
Topic: program proof via assertions (61 items)
Topic: design pattern (17 items)
Topic: shared information for collaborative work (36 items)