CSSE 371 -- Software Requirements and Specification -- Fall 2004
Homework 4
Due: Thursday, September 16, 2004
Purpose: Practice creating storyboards
1. Keep track of the amount of time you spend on this assignment.
2. Reusing storyboards: On the Web, find a suitable storyboard about an ATM stakeholder. Using this image you find, which you also should turn in, tell your own story about that stakeholder’s interactions with the system. If necessary, replace dialogue shown with your own. For example, if I hadn’t already used I, you might’ve stolen this image from –
http://www.cartoonstudio.co.uk/CartoonStudio/Pages/AbbeyNatATM.html, and made up a story about the second guy stealing the first guy’s secret number, which is not what this is really about. And I probably could think of things for the character at right to say!
3. Making your own storyboards: Drawing them yourself, create a set of 3 “passive” storyboards [1] for the term project, which show a stakeholder performing some key action, in a way which graphically brings home the essence of that action. (This art will not be graded, per se, beyond its needing to be recognizable as telling the story. However, to be fair to any artists, fab artwork will get a bonus!)
4. Documenting the story: After you draw them, describe the story they tell about your stakeholders, using the 3 essential elements we talked about in class.
5. Stretch the story: As you did with the stolen art work, use the storyboard in a different way. This time, show it to someone else (your roommate, say), and ask them to describe what it means without seeing what you wrote about it. Include a synopsis of what they said in the work you turn in.
6. Hand in both sets of art work and their associated descriptions. We are assuming here that you’ll physically hand in this homework, rather than having to scan it in for Angel.
7. Include a note indicating the amount of time you spent on the assignment.
[1] See p. 134 in Leffingwell & Widrig.