Design Rationales
Readings:
Homework due this week:
Scenario: Create a set of task scenarios that demonstrate the sequence of actions the user(s) will have to go through
in order to achieve their practical goals. You will use these scenarios both to guide your designs and to assess your designs
throughout the rest of the project. You should end up with 3 to 5 primary scenarios;
more than this will make it difficult to focus. You will also have to make a judgement call about how detailed to make
the task descriptions but they should be at least as detailed as the examples
in the Carroll reading.http://testingeducation.org/BBST/testdesign/CarrollScenarios.pdf
in order to achieve their practical goals. You will use these scenarios both to guide your designs and to assess your designs
throughout the rest of the project. You should end up with 3 to 5 primary scenarios;
more than this will make it difficult to focus. You will also have to make a judgement call about how detailed to make
the task descriptions but they should be at least as detailed as the examples
in the Carroll reading.http://testingeducation.org/BBST/testdesign/CarrollScenarios.pdf
STORYBOARD
Storyboard: Design a storyboard that shows how a user or users will interact with your design.
The storyboard should highlight important aspects of how your design will be used along with transitional
frames that show how a user will navigate through the system.
Submit at least 1 storyboard with 5 frames (or 2 storyboards with 3-5 frames).
The scenario is the story or script of how a user will use your system and the storyboard is a graphic depiction
for how the story will play out in the system. A storyboard is an early version of paper prototypes of the screens
in your system.
The storyboard should highlight important aspects of how your design will be used along with transitional
frames that show how a user will navigate through the system.
Submit at least 1 storyboard with 5 frames (or 2 storyboards with 3-5 frames).
The scenario is the story or script of how a user will use your system and the storyboard is a graphic depiction
for how the story will play out in the system. A storyboard is an early version of paper prototypes of the screens
in your system.
A note: to make storyboards useful, try to think about what you can learn from drawing your solution out,
over what you can get from just a narrative scenario. In other words, a storyboard should be a little more than just
a drawn scenario. Try to represent physical environment or other type of context (e.g., location of other people)
which might help you think through how your system needs to work.
over what you can get from just a narrative scenario. In other words, a storyboard should be a little more than just
a drawn scenario. Try to represent physical environment or other type of context (e.g., location of other people)
which might help you think through how your system needs to work.
No comments:
Post a Comment