75 ;;Quote: in practice, requirements engineering produces one large document that is seldom followed, and if followed, often unsuccessful; what is wrong?

75 ;;Quote: a requirements specification must treat the system as a block box

75+;;Quote: a requirements specification includes functional requirements that show external behavior in terms of input and output

75+;;Quote: a requirements specification includes nonfunctional requirements such as performance, portability, and reliability

75 ;;Quote: a requirements specification is consistent, correct, understandable, complete, and a foundation for design and test

75 ;;Quote: poor practice for requirements engineering due to changing, hard-to-uncover requirements, CASE, poor training and communication, insufficient time

76 ;;Quote: structured analysis leads to premature design; hard to visualize overall behavior

76 ;;Quote: object-oriented analysis has not been effective for specifying a system's black box behavior