| 
|
QuoteRef: roycWW8_1970
topics >
all references >
Topic:
management of large software projects
Group:
software engineering
Topic:
software lifecycle
Topic:
performance testing
Group:
requirement specification
Topic:
team programming
Topic:
top-down vs. bottom-up design
Topic:
good requirement specifications
Topic:
design documentation
Group:
software maintenance
Topic:
incremental development
Group:
program design
Group:
testing
Topic:
bugs
Topic:
software review
Topic:
quality assurance
Topic:
user-centered design
Reference
Royce, W.W., "Managing the development of large software systems", Proceedings, IEEE WESCON, August 1970, pp. 1-9. Google
Other Reference
p. 328-338 in Proceedings of the Ninth International Conference on Software Engineering, ACM, 1989.
328 ;;Quote: programming consists of analysis and coding; these steps are not enough for large software systems
328 ;;Quote: program large systems by systems requirements, software requirements, program analysis, design, coding, and testing
329 ;;Quote: discover timing, storage, and I/O problems at the end of the development cycle; may require a major redesign and a 100-percent overrun
331 ;;Quote: the program designer must impose performance constraints on the analyst; requires a preliminary design before analysis begins
331 ;;Quote: designers should design the data processing modes, data base, execution time allocations, interfaces, processing modes, input/output processing, and operating procedures
331+;;Quote: designers should produce an overview document that is understandable, informative, current
332 ;;Quote: management of software requires a lot of documentation; need a 1500 page software specifications vs. a 30 page hardware specification
332 ;;Quote: write down interface and management decisions; otherwise designers may be "90% complete" for months
332 ;;Quote: until coding begins documentation, specification, and design are the same; if the documentation is bad the design is bad
332 ;;Quote: software maintenance requires good documentation
334 ;;Quote: always build a preliminary program before delivering to a customer; study timing, storage, and critical design/operation areas
334+;;Quote: human judgment in computer program design is invariably and seriously optimistic
335 ;;Quote: testing is the most expensive phase of software development
335+;;Quote: testing has the greatest risk in cost and schedule; testing occurs last when backup alternatives are least available
335 ;;Quote: visually inspect every bit of analysis and code; most errors are obvious
335 ;;Quote: test every logical path in a program at least once; uncovers most coding errors; customers should require a certified test
335 ;;Quote: software design is subject to wide interpretation; involve the customer in a formal way before final delivery
Topic: management of large software projects (63 items)
Group: software engineering (18 topics, 470 quotes)
Topic: software lifecycle (13 items)
Topic: performance testing (8 items)
Group: requirement specification (11 topics, 307 quotes)
Topic: team programming (7 items)
Topic: top-down vs. bottom-up design (30 items)
Topic: good requirement specifications (36 items)
Topic: design documentation (43 items)
Group: software maintenance (14 topics, 368 quotes)
Topic: incremental development (74 items)
Group: program design (13 topics, 454 quotes)
Group: testing (18 topics, 557 quotes)
Topic: bugs (66 items)
Topic: software review (80 items)
Topic: quality assurance (22 items)
Topic: user-centered design (65 items)