| 
|
QuoteRef: parnDL8_1971
topics >
all references >
ThesaHelp:
references p-r
Group:
program design
Group:
goals for a programming system
Topic:
data types in Thesa
Topic:
interface between program modules
Topic:
sensitivity of software to change
Topic:
top-down vs. bottom-up design
Topic:
management of large software projects
Topic:
software documentation
Topic:
decomposition of a system into levels
Topic:
programming by sequential implementation
Topic:
information hiding
Topic:
incremental testing
Topic:
localized understanding
Topic:
importance of information hiding for requirement specification
Reference
Parnas, D.L., "Information distribution aspects of design methodology", Information Processing 71, Proceedings of the IFIP Congress 71, Volume 1 -- Foundations and Systems, Ljubljana, Yugoslavia, August 1971, North-Holland Publishing, pp. 339-344. Google
339 ;;Quote: design and development are a series of decisions; effect later decisions
339 ;;Quote: connections between modules are their assumptions about each other; generally more than calling sequences
340 ;;Quote: design from external characteristics first; helps avoid unfortunate consequences
340 ;;Quote: must divide projects into sub-projects before adding staff, but hasty decisions leads to poor usability and a weak internal structure
340 ;;Quote: old changes are difficult to reverse; early decisions should be least likely to change, based on universal truths
341 ;;Quote: programs define algorithms but they are difficult to read; documentation helps answer questions
341+;;Quote: documentation written by groups with unique concepts, terms, and module organization; difficult for outsiders to read
341 ;;Quote: one programs for a virtual machine defined by hardware and other software
341+;;Quote: a good programmer makes use of available information
342 ;;Quote: unnecessary uses of routines and data from other modules increases the connectivity of a structure without improving its performance
342 ;;Quote: information hiding necessary if designers wish to maintain control over a program's structure
344 ;;Quote: designers must specify modules with exactly the information that they want the programmers to have
ThesaHelp: references p-r (245 items)
Group: program design (13 topics, 453 quotes)
Group: goals for a programming system (21 topics, 971 quotes)
Topic: data types in Thesa (92 items)
Topic: interface between program modules (55 items)
Topic: sensitivity of software to change (44 items)
Topic: top-down vs. bottom-up design (30 items)
Topic: management of large software projects (63 items)
Topic: software documentation (64 items)
Topic: decomposition of a system into levels (49 items)
Topic: programming by sequential implementation (26 items)
Topic: information hiding (50 items)
Topic: incremental testing (25 items)
Topic: localized understanding (43 items)
Topic: importance of information hiding for requirement specification (23 items)