3. Understanding Stakeholder Needs - Overview Problem Solution Space Problem Space Needs Features Software Requirements I need … Test Procedures Design User Docs The Product To Be Built Traceability
4. What Are Sources for Our Requirements? Customer Users Problem Domain Domain Experts Industry Analysts Site Visits Competitive info. Bug Reports Change Requests Requirement Specs Business Plans Personal Goals Business Models Analyst Partners
5.
6.
7. What Does This Process Look Like? Customer Development Requirements Spec Approved ! Rejected Reworked Spec Rejected Reworked again Ad hoc requirements
8.
9.
10.
11. Workshops: Tricks of the Trade Problem Solution breaks “ Late From Break” ticket, Kitchen timer, Charitable contribution box ($1 after ticket used) Pointed criticism - petty biases, turf wars, politics and cheap shots “ 1 Free Cheap Shot” ticket, “That’s a Great Idea!!” ticket Grandstanding, domineering positions, uneven input from participants Trained facilitator, “Five Minute Position Statement” Flagging energy after lunch Light lunches, breaks, coffee, soda, candies, cookies, rearrange room, change temperature Hard to get restarted after
12. Workshop Tickets That’s a Great Idea!! Five Minute Position Statement 1 Free Cheap Shot Late From Break Five Minute Position Statement That’s a Great Idea!!
13.
14.
15.
16.
17.
18. What Is a Use Case? Key Words and Phrases Describes functions of the system To avoid too detailed use cases To avoid too complex use cases A use case defines a sequence of actions performed by a system that yields an observable result of value to an actor