Map
Index
Random
Help
Topics
th

QuoteRef: berrDM10_2002

topics > all references > ThesaHelp: references a-b



Topic:
specification is infeasible
Topic:
change
Topic:
software documentation
Topic:
ease of use
Group:
software engineering
Topic:
information hiding
Topic:
stepwise refinement
Group:
requirement specification
Topic:
software change management
Topic:
extreme programming
Group:
software maintenance
Topic:
software management
Topic:
formal methods and languages
Topic:
local vs. global
Topic:
software review

Reference

Berry, D.M., "The inevitable pain of software development: Why there is no silver bullet", in Wirsing, M., Knapp, A., Balsamo, S. (ed.), Radical innovations of software and systems engineering in the future. 9th International Workshop, RISSEF 2002, Venice, Italy, October 2002, Springer, LNCS 2941, pp. 50-74. Google

Notes

http://se.uwaterloo.ca/~dberry/FTP_SITE/tech_reports/painpaper.pdf

Quotations
52 ;;Quote: in programming, discoveries and requirements grow faster than code; can not be systematic or keep up with documention
Quote:
berrDM10.02 ;;
QuoteRef:
Brooks
brooRA_1986 ;;17 "The hardest single part of building a software system is deciding precisely what to build ... No other part of the work so cripples the resulting system if it is done wrong. No other part is more difficult to rectify later."
54 ;;Quote: while programming methods help with accidental difficulties, they are only slightly better for essence-borne difficulties; some part of the method becomes painful, distasteful, and difficult
56 ;;Quote: requirement changes often cross-cut information hiding boundaries; should restructure the code, but restructuring is expensive without observable change
58 ;;Quote: while stepwise refinement works well for new development, it requires rewrite for changed requirements
60 ;;Quote: discourage change if want comprehensive requirements before coding starts
60+;;Quote: a change review board discourages change through bureaucracy
62 ;;Quote: refactoring takes time and may require throwing out perfectly good code; used for new requirements under extreme programming
62 ;;Quote: under schedule pressure, extreme programmers drop test cases, refactoring, testing, GUI standards, and documentation; the painful parts of XP
65 ;;Quote: dealing with changed requirements is particularly painful for formal program development
65 ;;Quote: requirements and proofs are inherently global; a changed requirement may require redoing most of the proofs; verification gets dropped
65 ;;Quote: software inspection is a double pain; requires documentation beforehand and inspection itself is painful; easily dropped


Related Topics up

Topic: specification is infeasible (46 items)
Topic: change (28 items)
Topic: software documentation (64 items)
Topic: ease of use (47 items)
Group: software engineering   (18 topics, 470 quotes)
Topic: information hiding (50 items)
Topic: stepwise refinement (25 items)
Group: requirement specification   (11 topics, 307 quotes)
Topic: software change management (48 items)
Topic: extreme programming (6 items)
Group: software maintenance   (14 topics, 368 quotes)
Topic: software management (28 items)
Topic: formal methods and languages (53 items)
Topic: local vs. global (29 items)
Topic: software review (80 items)

Collected barberCB 10/04
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.