ThesaHelp: references a-b
Topic: team programming
Topic: information as knowledge
Topic: automated tests of specifications and designs
Topic: software portability
Group: user interface
Topic: software management
Topic: programming environment
Topic: programming system
Topic: user maintenance
Topic: specific purpose computer systems
| |
Reference
Boehm, B.W.,
"Software engineering--as it is",
Proceedings International Conference on Software Engineering, IEEE, pp. 11-21, 1979.
Google
Quotations
11 ;;Quote: should have lean staffing during design phase
| 14 ;;Quote: a paper is good for technology transfer if its technique was implemented and evaluated
| 15 ;;Quote: formatted specifications use a standardized syntax to help with basic consistency and completeness checks, e.g., ISDOS, CADSAT, SREM
| 15 ;;Quote: users tend to compensate for deficiencies in software; these habits are difficult to change once established
| 15 ;;Quote: software engineering should include resource engineering and human relations
| 16 ;;Quote: several organizations are building all-encompassing software design systems; these may collapse under their own weight
| 16+;;Quote: a library of simple, limited-purpose design aids is better than an all-encompassing design system
| 18 ;;Quote: in 1976, the most pressing problems were in all phases of application software development; by technicians and cost-driven
|
Related Topics
ThesaHelp: references a-b (396 items)
Topic: team programming (7 items)
Topic: information as knowledge (17 items)
Topic: automated tests of specifications and designs (12 items)
Topic: software portability (43 items)
Group: user interface (75 topics, 1633 quotes)
Topic: software management (27 items)
Topic: programming environment (46 items)
Topic: programming system (9 items)
Topic: user maintenance (13 items)
Topic: specific purpose computer systems (9 items)
|