courses.pgbovine.net

Project Milestone 2

DUE: Wednesday, April 18 at noon

For all remaining milestones, even though TAs will be grading and giving you feedback during different in-class sessions, everyone's write-up is still due at the same time. You may continue to update your project's code after the due date, but make sure to turn in the write-up by each due date.

For this milestone, you will need to turn in storyboards and “paper” prototypes for your initial project idea to get feedback on them. It is similar to the storyboarding/prototyping milestone in COGS120/CSE170. For a review of storyboards and paper prototypes, see these lecture slides.

  • Create 2 different storyboards showing setting + sequence + satisfaction for how different kinds of users might find your app to be helpful. If your app is meant for only one type of user, think about 2 different settings or user scenarios where they might find it helpful.
  • Create 2 different a “paper” prototypes showing all of the main webpages/screens of your proposed app. Your two prototypes should show two different alternative user interface ideas. You are not bound by any particular UI design, so it's perfectly OK if you brainstorm ones that are unusual or inefficient. That's the beauty of paper prototyping! It's easy to iterate.

(You can work on the storyboards and paper prototypes independently; this means that you don't necessarily need to match up 1 storyboard with 1 prototype. Feel free to make 2 prototypes that correspond to 1 storyboard, or even make your prototypes different from your storyboard ideas.)

In COGS120/CSE170, we were strict about having you hand-draw storyboards and paper prototypes with thick markers, but here we will not be as strict. You can use whatever tools you want to make these drawings, either on paper or digital. If you like using mockup sketching tools such as Balsamiq, InVision, or even PowerPoint, go for it! Or if you prefer to draw on paper and take pictures to upload for your milestone, that's fine too. Just make sure it's clearly readable.

What to turn in

By the due date, you should have created a milestone2.md file in your project's GitHub repository. Remember to push to GitHub so that you can see the file on the public GitHub website. (If you simply commit but don't push, then your changes are not visible.)

Your milestone2.md file should contain images of your 2 storyboards and 2 paper prototypes embedded in the file itself. Label each one with a heading and brief description of it.

You can use as many images as you need in order to convey the necessary info to your TA; for instance, each prototype should probably have a separate image for every webpage/screen in your app.

Store your images in your GitHub repository and then embed those images into milestone2.md. That way, when your TA opens milestone2.md in their web browser, they should see all of your content in one place without having to look around for different files.

Finally, fill out a teammate assessment form to reflect on the work that your team has been doing so far.

Your TA will grade your milestone in class during your assigned grading day, so plan to come to class then to present your prototypes. If you do not come to class that day, then your milestone will not be graded.

Grading rubric (8 points)

  1. milestone2.md is present in your project's GitHub repository and contains images of 2 storyboards and 2 paper prototypes embedded inside of it (not linked as external files), with each one clearly labeled as Storyboard 1, Storyboard 2, etc.
  2. You have made an honest effort to make your 2 storyboards and 2 paper prototypes different from one another.
  3. Storyboard 1's setting begins with a clear user need, and ends with a satisfaction addressing it.
  4. Storyboard 2's setting begins with a clear user need, and ends with a satisfaction addressing it.
  5. Paper prototype 1 presents an interface (at a sketch level) that accomplishes the design's major functionality.
  6. Paper prototype 1 has enough detail that the user can see all of the interactions, understand how they work, and a programmer could use the prototype to create a functional application with a defined flow.
  7. Paper prototype 2 presents an interface (at a sketch level) that accomplishes the design's major functionality.
  8. Paper prototype 2 has enough detail that the user can see all of the interactions, understand how they work, and a programmer could use the prototype to create a functional application with a defined flow.

Frequently Asked Questions

First please check the project FAQ.