Chapter 5 Evolutionary requirements Expect change! Learn as you go Validate as you build Why – 25% requirements change on an average software project
The case against waterfall On average 25% of requirements change during a project Inflexible Fig 5.1 in text - 45 % of requirements actually not used! A word of caution - waterfall is sometime still the best way! (why?)
Finding The text emphasizes finding requirements This requires skill!
FRUPS + Functional Usability Reliability Performance Supportability
+ Implementation Interface Operations Packaging Legal
UP defines: Use-Case Model Supplementary specs – non-functional Glossary Vision Business rules
Resources Text offers several suggestions Also, refer to any text on UP or software engineering as well