a seminar about Storyboarding in Information Systems Engineering for the Faculty of Information Technology Engineering in Damascus University

1. STORYBOARDING
REQUIREMENTS ENGINEERING
Information Systems Engineering

2. Overview
 Definition.
 Purpose and Benefits of Storyboarding.
 Types of Storyboards.
 Storyboarding Continuum.
 What does Storyboarding do?
 Tools, Tips and Use Cases.
 Agile Software Development.
 Key Points.
STORYBOARDING
2

3. Definition
Purposed
functionality
Story
Series of
steps/discrete
actions
 A graphic organizer that provides the
viewer with a high-level view of a project
 Explains how a product or different parts of
a product, could work
STORYBOARDING
3

4. Definition
STORYBOARDING
4
Storyboards originated in the motion picture
industry to help directors and cinematographers
visual a film's scenes in sequence. Such
storyboards resemble cartoon strips

5. Definition
STORYBOARDING
5
Agile Development
 a storyboard looks less like a cartoon panel
and more like a series of columns filled with
colored squares of paper
 the columns are laid out on large format paper,
a whiteboard or a bulletin board
 Each column represents a status and user
stories are dragged to a new column when the
status of the user story changes

6. Definition
STORYBOARDING
6
Scrum Software Development
Storyboard Task Board

7. Definition
STORYBOARDING
7
 Many storyboards show the user at a screen in
each panel
 Sometimes one picture is enough to illustrate
all the actions and outcomes for a use case
 For more complex use cases, or for playing
out of several use cases or aspects of the
whole product, you need a sequence of
pictures

8. Definition
STORYBOARDING
8

9. Purpose of Storyboarding
STORYBOARDING
9
 Gaining an early reaction from the users on
the concepts proposed for the application
 offer an effective technique for addressing the
"Yes, But" syndrome

10. Why Storyboarding?
STORYBOARDING
10
 Extremely inexpensive
 User friendly, informal, and interactive
 Provides an early review of the system’s
interfaces
 Easy to create and easy to modify
 Anchoring design in end use
 Promotes innovation by capturing the
problems people face in a real world domain

11. Why Storyboarding?
STORYBOARDING
11
 Conveying functionality of a proposed
solution, product or service
 Convince people of the value of a proposed
product in a real-world domain
 Collects requirements and generating
feedback on how the events and
functionalities depicted in the story map to
the intended domain
 Helps people understand how they could
incorporate a new technology in their own
work practice

12. Types of Storyboards
STORYBOARDING
12
Passive
Active
Interactive

13. Types of Storyboards
STORYBOARDING
13
Passive
Storyboards Tell a story to the user
they consist of sketches, pictures,
screen shots, PowerPoint presentations,
or sample application outputs
Walk the user through the storyboard,
with a "When you do this, this happens"
explanation

14. Types of Storyboards
STORYBOARDING
14
Active
Storyboards
Make the user see "a movie that hasn't actually
been produced yet“
They are animated or automated, perhaps by
an automatically sequencing slide presentation,
an animation tool, a recorded computer script or
simulation, or even a homemade movie
Provide an automated description of the way
the system behaves in a typical usage or
operational scenario

15. Types of Storyboards
STORYBOARDING
15
Interactive
Storyboards
Let the user experience the system in a realistic
and practical way
Require participation by the user
They can be simulations or mock-ups or can be
advanced to the point of throwaway code
An advanced, interactive storyboard built out of
throwaway code can be very close to a throwaway
prototype

16. Storyboarding Continuum
STORYBOARDING
16
Continuum
Passive
ActiveInteractive

17. Storyboarding Continuum
STORYBOARDING
17
 The continuum of possibilities ranges from
sample outputs to live interactive demos
 The boundary between advanced storyboards
and early product prototypes is a fuzzy one

18. Storyboarding Continuum
STORYBOARDING
18

19. What does Storyboarding do?
STORYBOARDING
19
 In software, storyboards are used most often
to work through the details of the human-to-
machine interface
 In this area each user is likely to have a
different opinion of how the interface should
work

20. What does Storyboarding do?
STORYBOARDING
20
User-
based
systems
Who
What
How

21. What does Storyboarding do?
STORYBOARDING
21
Users
Other
systems
Devices
Who
Behavior of
users
Behavior of
system
What
Interaction
Events
States
State
transitions
How

22. Tools of Storyboarding
STORYBOARDING
22
Passive Storyboarding

23. Tools of Storyboarding
STORYBOARDING
23
More Advanced
Storyboards

24. Tools of Storyboarding
STORYBOARDING
24
Passive, active, and user-
interactive storyboards

25. Tips for Storyboarding
STORYBOARDING
25
 Don't invest too much in a storyboard.
Customers will be intimidated about making
changes if it looks like a real work product or
they think they might insult you
 Make the storyboard easy to modify
 If you don't change anything, you don't learn
anything
 Don't make the storyboard too functional
 Whenever possible, make the storyboard
interactive

26. Use Cases and Storyboarding
STORYBOARDING
26
If the player is a specific user and the
interaction is between that user and the user
interface, then storyboarding can help us
describe how we are approaching the
interaction

27. Use Cases and Storyboarding
STORYBOARDING
27
convergence on the GUI and the use case at
the same time
Iterative
Incremental

28. Use Cases and Storyboarding
Example
STORYBOARDING
28
Suppose you want to elaborate a section of a
use case that would describe how a user
inserts graphic clip art from an online source
into a document

29. Use Cases and Storyboarding
Example
STORYBOARDING
29
Use Microsoft PowerPoint as your storyboard
presentation tool to build one PowerPoint slide
for each of the steps in the use case to show
the user how you intend the system to work

30. Use Cases and Storyboarding
Example
STORYBOARDING
30

31. Use Cases and Storyboarding
Example
STORYBOARDING
31

32. Use Cases and Storyboarding
Example
STORYBOARDING
32

33. Agile Software Development
STORYBOARDING
33
 A storyboard can help developers quickly get a
sense of what work still needs to be completed
 As long as the team keeps the storyboard up to
date, anyone can see what work has been
completed, who's working on what and what work
is left to do
 This not only provides the product
owner with transparency, it also helps the team to
visualize the sequence and interconnectedness
of user stories
 Storyboards can be physical or digital

34. Key Points
STORYBOARDING
34
 The purpose of storyboarding is to elicit
early "Yes, But" reactions
 Storyboards can be passive, active, or
interactive
 Storyboards identify the players, explain
what happens to them, and describe how
it happens
 Make the storyboard sketchy, easy to
modify, and not shippable
 Storyboard early and often on each
project with new or innovative content

35. STORYBOARDING
35
Presented by:
 Abdul Majeed Al-Kattan
 Rabee Al-Rass
 Rahaf Aamer
 Rimon Koroni
 Sandra Sukarieh

36. STORYBOARDING36
Thank
You.