Standish Chaos Report
- 71% of IT projects underperform or fail outright
- 4 of the top 5 reasons for failure have to do with requirments
- lack of user input
- incomplete requirements
- unclear objectives
- changing requirements
Seilevel
- Structured hiring process
- Resumes
- Complex problem solving
- Practical
- Formal assessment
- model based methodology
- identify project type
- capture business objectives
- complete models
- derive requirements
- map to objectives
- transition to dev/test
- validate ROI (did app meet requirements & business objectives)
- Process tools
- Team collaboration
- Issue tracking
- Requirements management
- requiements collection
- document management
SHALL is a good way to capture information but not a good way to work with requirements.
Models help us categorize, group, and organize requirements.
Models
- People (who)
- org chart
- use cases
- decision trees
- systems (interaction between systems
**