ThesaHelp: references i-l
Topic: design documentation
Topic: reusable programming
Topic: program module as encapsulation
Group: object-oriented programming
Topic: user-centered design
Topic: data-driven design
Topic: top-down vs. bottom-up design
Topic: general vs. specific purpose systems
Topic: collecting statistics on a UserInterface
Topic: software review
Topic: visual programming
Topic: flow diagrams and flow charts
Topic: problem of classifying information
Group: relationship information
Topic: entity-relationship database model
| |
Reference
Jones, T.C.,
"An overview of programming architectures and design languages",
IBM Design '79 Symposium, April 1979, draft January, 1979.
Google
Quotations
5 ;;Quote: the design for a million line system would take a year to read; too bulky for practical use
| 10 ;;Quote: a functionally strong module performs only one generic function, like square root; highly reusable
| 11 ;;Quote: module communication by data coupling allows the definition of reusable black boxes; pass actual data or its location
| 14 ;;Quote: outside-in design means starting with its effect on users; e.g., write tutorials and user guides first
| 15 ;;Quote: data-driven design starts with the input data; avoids the unlimited wish list of functional design
| 15 ;;Quote: if design from inside out, i.e., internals first, get a 'queen bee' system; one that requires a support team of systems programmers
| 15 ;;Quote: a functional design leads to a virtually unlimited wish list of features
| 16 ;;Quote: Jackson's goal is a design methodology so simple that ordinary people can use it successfully
| 18? ;;Quote: data-driven design from output to input often works better then working from front to back
| 19 ;;Quote: design a survey by first agreeing on what the result tabulations should look like
| 22 ;;Quote: typeset drafts appear to get more thorough reviews then rough drafts
| 29 ;;Quote: in a hybrid graphics language, the graphics provide the overview and context for textual details; e.g., flow charting
| 34 ;;Quote: to describe data, need to account for an entity's membership in innumerable sets
| 34+;;Quote: to describe data, must represent multiple relationships between objects
|
Related Topics
ThesaHelp: references i-l (342 items)
Topic: design documentation (43 items)
Topic: reusable programming (77 items)
Topic: program module as encapsulation (28 items)
Group: object-oriented programming (26 topics, 814 quotes)
Topic: user-centered design (65 items)
Topic: data-driven design (41 items)
Topic: top-down vs. bottom-up design (30 items)
Topic: general vs. specific purpose systems (11 items)
Topic: collecting statistics on a UserInterface (12 items)
Topic: software review (80 items)
Topic: visual programming (31 items)
Topic: flow diagrams and flow charts (21 items)
Topic: problem of classifying information (41 items)
Group: relationship information (5 topics, 69 quotes)
Topic: entity-relationship database model (21 items)
|