ThesaHelp: references t-z
Group: philosophy of science
Topic: understanding systems
Topic: meaning by language as a whole
Topic: marketing technical products and innovations
Topic: education
Group: requirement specification
Topic: user-centered design
Topic: programming style
Topic: software documentation
Topic: design documentation
Topic: specification is infeasible
Group: program design
Topic: prototyping
Topic: architecture
Topic: software management
| |
Reference
Weinberg, G.M.,
"Rethinking systems analysis and design", Boston, Massachusetts, Little, Brown and Company, 1982.
Google
Quotations
27 ;;Quote: understanding an event means fitting it into a preconceived scheme of thought; could be science or a private delusion
| 38 ;;Quote: while others had movable type, Gutenberg figured out how to print works that looked sufficiently like hand-lettering to sell
| 53 ;;Quote: learning is the process by which inputs of information in the past lead to images of the future in the present
| 65 ;;Quote: test question: write an appropriate question and then answer it
| 69 ;;Quote: an analyst shouldn't ask very precise questions with yes/no answers since the 'noise' contains much useful information
| 102 ;;Quote: a true test of self-documenting design is whether its maintainability is maintained
| 157 ;;Quote: there's no sense being precise about something when you don't even know what you're talking about
| 157 ;;Quote: in design fields such as architecture, the rough sketch is heavily used; detailed drawings seldom occur before the creative work is finished
| 165 ;;Quote: ninety percent of aggravation in programming projects comes at the end; the unimportant, last 10%, could be dropped
|
Related Topics
ThesaHelp: references t-z (309 items)
Group: philosophy of science (10 topics, 377 quotes)
Topic: understanding systems (48 items)
Topic: meaning by language as a whole (26 items)
Topic: marketing technical products and innovations (17 items)
Topic: education (35 items)
Group: requirement specification (11 topics, 306 quotes)
Topic: user-centered design (65 items)
Topic: programming style (47 items)
Topic: software documentation (64 items)
Topic: design documentation (43 items)
Topic: specification is infeasible (46 items)
Group: program design (13 topics, 453 quotes)
Topic: prototyping (18 items)
Topic: architecture (14 items)
Topic: software management (27 items)
|