To get a clearer sense of the user experience of your planned app.
Your submission for this phase of the project will be another PDF, this time called storyboards.pdf. Only PDFs will be accepted.
Your PDF should consist of a few user stories, illustrated step-by-step with storyboards, of a user interacting with your web application. Your user stories, all together, should demonstrate your application's three or four most important features. Don't try to cram all the features into one user story; if you need a separate story for each feature, then do them that way. You should end up with between two and four distinct stories.
A user story is written in the present tense, and describes not just the user's interaction with your app, but also their intentions and thought process. It begins by introducing the user and the overall goal that they're attempting to achieve by using your application. Plan out the story completely before you make the storyboards.
You and your teammate have been invited to myBalsamiq, an online tool for creating website mockups and other informal technical illustrations. (Email me if you didn't receive an invite or if you have trouble logging in.) Use myBalsamiq to create your storyboards. Each picture should be a rough sketch of your site as the user is interacting with it, sort of like a screenshot. The pictures don't have to be super-detailed, but each one should convey a general idea of the layout of the page and its most important visual elements.
Your PDF may end up being pretty long, because each image should take up about a third of a page. The prose doesn't have to be very extensive; if you've only got a sentence to say between two pictures, that's fine.
Push your PDF (and the source document for it, particularly if you write it using LaTeX) to your team's repository. Tag your commit with phase_2_2. In addition, print it out (double-sided) and bring it to class on Monday.