Storyboarding
/ Presentation Scenarios
Primary Reference Sources
Androile S (1991) Storyboard Prototyping. QED Information Sciences,
Wellesley, MA.
Summary description
Storyboards are sequences of images which demonstrate the relationship
between individual screens and actions within a system. A typical storyboard
will contain a number of images depicting features such as menus, dialogue
boxes and windows. The formation of these screen representations into a
sequence conveys further information regarding the structure, functionality
and navigation options available within an intended system. The storyboard
can be shown to colleagues in a design team as well as potential users,
which allows others to visualise the composition and scope of an intended
interface and offer critical feedback. This method can be used early in
the design cycle where the use of storyboards supports the exploration
of design possibilities and the early verification of user requirements.
Typical Application Areas
This method is of general relevance, especially to products in which there
a complex structure of information is being developed.
Benefits
Feedback can be gained on system functionality, style and also navigation
options early on in the development cycle where changes can be more easily
implemented.
-
The method promotes communication between designers and users.
-
Storyboards can be created quickly and easily.
-
Only minimal resources and materials are required.
-
The technique can be utilised by those with little or no human factors
expertise.
Storyboards provide a platform for exploring design options via a static
representation which can be shown to both potential users and members of
a design team. This can result in the selection and refinement of particular
design options. This filtering process can be a valuable precursor to prototyping
activities.
Limitations
Storyboards may lack the interactive quality of prototyping methods.
Because of their simplicity, storyboards do not support the evaluation
of fine design detail.
Storyboards do not accurately convey system responsiveness.
Cost of use
The technical resources required to create storyboards are minimal, and
include drawing tools (both computer and non computer-based), paper, card,
pens and adhesives. Furthermore, the time and human resources are low.
Costs of Acquisition
There are no explicit training costs, as with other methods some initial
exposure to the method may be required to acquire the basic principle.
Suitability for requirements engineering in Telematics:
The method appears to be simple and could be readily adopted by consortium
partners and industrial concerns. This method is valuable as a bridging
activity between early data gathering methods such as focus groups and
interviews and the various prototyping methods.
How to get it
This method is well documented in the literature.
Detailed description of method
The general procedure relating to this method follows.
-
Give consideration to the scenarios of use which the storyboard will reflect.
A storyboard may represent several activities such as entering, saving
or printing information. Alternatively a separate storyboard may be created
to represent each distinct theme.
-
Construct the storyboard as a sequence of screen representations. using
separate images to reflect changes in system appearance. Thus the storyboard
indicates the availability and purpose of dialogue windows, menu items,
toolbars and icons.
-
The elements of a storyboard can be annotated with explanatory captions
to aid audience understanding and evaluation.
-
The completed storyboard can be shown to design teams as well as intended
users to solicit evaluative feedback. Several storyboards can be created
and shown to an audience in order to explore different design options.
-
It may be useful to video or audio record the feedback sessions for later
review or to show to other colleagues.
-
Further storyboards can be created and evaluated in light of feedback.