View
213
Download
0
Tags:
Embed Size (px)
Citation preview
1
Team Skill 2 -Understanding User and Stakeholder Needs(Chapters 8-13 of the requirements text)
CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute of TechnologySeptember 13, 2005Thanks to Mark Ardis and Steve Chenoweth for some of the slides included.
2
Outline
BackgroundBarriers to ElicitationFeatures
Techniques InterviewingRequirements Workshops and BrainstormingStoryboarding
4
Three Common Barriers
Each described in the text as a syndrome
“Yes, But…” Syndrome Undiscovered Ruins Syndrome User and Developer Syndrome
6
Needs vs. Features
Each stakeholder will have needs that will hopefully be addressed by the new system Example: “I want to be able to advise my students more
effectively.”
A feature is a service that the system provides to fulfill one or more stakeholder needs. Example: “This tool will allow the advisor to see the critical path
in an advisee’s coursework.”
Look for needs that suggest features
8
Where Should You Hold an Interview? Non-threatening environment
Customer's turfRoom large enough for group
Free from distractions
9
Interview Preparation
Do some research Prepare questions Prepare agenda Select roles:
LeaderNote takerQuestioners
10
Interview Phases
1. Establish user profile
2. Assess the problem
3. Understand the environment
4. Recap for understanding
5. Analyst's inputs
6. Assess solution
7. Assess opportunity
8. Assess reliability, performance
9. Other requirements
10. Wrap-up
11
Why Not A Questionnaire Instead?...
…After all, they can be done so much more efficiently!
Advantages of interviews:Personal Contact Interaction/Follow-ups
13
Benefits of Requirements Workshop
All stakeholders get their say May expose political issues Helps form effective team (developers
and stakeholders)
14
Workshop Facilitator
Establish proper tone Introduce goals and agenda Keep team on track Facilitate decision making Make sure all voices are heard
15
Sample One-Day Agenda
Introduction 0.5 hours Context 1.5 hours Brainstorming 2.0 hours Lunch 1.0 hours Brainstorming 1.0 hours Feature definition 1.0 hours Idea reduction 1.0 hours Wrap-up 1.0 hours
16
Brainstorming Benefits
Encourages participation by allAllows participants to build on one another's
ideasHigh bandwidth: many ideas in short period of
timeEncourages out-of-the-box thinking
17
One Brainstorming Method
Write down ideas on post-it notes, put on wall
Read ideas out loud No criticizing!
18
A Similar Method
Use an easel or whiteboard Ask for ideas and write them down as
they are said aloud Once again - no criticizing!
19
Idea Reduction
Classify the ideas into groups Vote on the ideas (i.e. rank them) Choose what ideas will go forward post-
workshop Prioritize the ideas
21
Key Points
Purpose – Elicit “Yes, But” reactions
Passive, active, & interactive Identify players, explain what
happens & how Storyboards should be
sketchy A place to add innovative
content
Above, right – “At the forefront of innovative content, interactivity is valuable only if it is user-friendly.”From www.rthk.org.hk/ mediadigest/md0001/04.html
22
Get the idea from some Storyboard Examples
More movies --This one’s from Blade Runner
In the movie industry, storyboarders don’t think they get enough credit – See www.tipjar.com/dan/colomba.htm
23
Another Storyboard Example
More movies – Ace Ventura: When Nature Calls
Storyboard from Storyboarding 101, by James O. Fraioli. Michael Weise Productions, 2000, ISBN 0-941188-25-6.
24
Another Storyboard Example
From software & web development. This one’s “Understanding your automobile,” at http://www.mcli.dist.maricopa.edu/authoring/studio/guidebook/storyboard_example.html
You can check out their website for more about their methodology…
25
Ideas onhow to do these
From a book on visual language –
Storyboards are an example of using the visual for multiple purposes: Audience focus Designer focus And breadth in both
From Designing Visual Language, by Charles Bostelnick and David D. Roberts.Allyn and Bacon, 1998, ISBN 0-205-20022-2, p. 42.