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