Presentation is loading. Please wait.

Presentation is loading. Please wait.

Team Skill 2 Understanding User and Stakeholder Needs Storyboarding (13)

Similar presentations


Presentation on theme: "Team Skill 2 Understanding User and Stakeholder Needs Storyboarding (13)"— Presentation transcript:

1 Team Skill 2 Understanding User and Stakeholder Needs Storyboarding (13)

2 Storyboarding ▫Comes from movie industry ▫Are inexpensive ▫User friendly and interactive ▫Provide early reviews of the user interface  So we can get users reactions early ▫Used to complement our Use Cases

3 Storyboarding Storyboarding Cont. ▫Flexible ▫Informal ▫Easy to create ▫Easy to Modify

4 Storyboarding 3 Basic Types of Storyboards ▫Passive  Sketches  Pictures  PowerPoint's  Post-it notes ...  Walks user through a scenario  “When this happens do this …”

5 Traditional Storyboard User Validation Main Menu Select Search Criteria Output Report Exit Application

6 Storyboarding Active ▫Animated or automated  More like a movie ▫Shows how the system will act during a typical operational scenario

7 Storyboarding Interactive ▫Lets the user experience typical usage  Realistic simulation  Requires user interaction ▫All the advantages of prototypes ▫Also all the disadvantages of prototypes

8 Storyboarding Some common applications ▫Reporting examples ▫UI Design  Data layout ▫UI flows  Flow from screen to screen ▫Data flow Storyboards model the flow of our use cases

9 Storyboarding What’s the point? ▫Detail human computer interaction Who is involved? ▫Users ▫Interviewers/Monitors How it happens? ▫Actions or script determines the next step  Depending on type of storyboard

10 Storyboarding How/Where do I storyboard: ▫Whiteboard drawings  More Agile methods  Take pictures ▫Post-It notes  Good because you can easily rearrange them and add new ones ▫Create Screen mock-ups  Presentation software (PowerPoint)  Modeling tool (Visio)  Drawing/Animation tool (Photoshop)  Coding tool (flash, eclipse, …)

11 Storyboarding What else can they do for us: ▫Identify/Clarify missed/existing requirements ▫Trace requirements into GUI model ▫Establishes the screen flow and data layout

12 Storyboards Usage guidelines ▫Validate your designs! ▫Don’t let it last to long ▫Don’t let it hold up future cycles Give the users alternatives when a clear solution is not evident ▫Again the iterative process reduces the amount of change


Download ppt "Team Skill 2 Understanding User and Stakeholder Needs Storyboarding (13)"

Similar presentations


Ads by Google