Assignment 7: Ready for testing

Brief

Crunch time! Your interactive prototypes have to be ready for user testing by the end of this week.

Assignment

By the end of this week your interactive prototypes should be fully functional. Use the JSON and handlebars techniques that you learned in lab (or equivalent technology) to populate the data for your application. Remember, we are not at the "making it pretty" phase yet, so don't procrastinate by playing with Photoshop. If you planned it out right and you have been doing your work, you should be in good shape. If not, it's time to step it up. You will get much less out of user testing if you are still struggling with bugs and a half finished interface.

Keep updating your development plan. You'll submit it again this week. (If you'd like to give yourself the option of "late days", set an early deadline so your schedule has some flexibility.)

Student Examples

Here is an example of a pretty good development plan (except that it's missing time estimates).

GradeSource++: This example project from last year abstracts GradeSource for you and works with the data to show you where you are in a class.

Balancr: This app helps people balance their time between work and play. They have done a wonderful job making the app functional-- you can create a sign-up, add activities, and see it reflected on the pie chart.

Submit

  • The URL of the prototype version that you want us to see. Note: the URL must work at least until your assignment is graded. If it doesn't work, you'll receive no credit.
  • The PDF of your development plan that you submitted last week.
  • The PDF of your updated development plan. (We recommend making a Google spreadsheet and saving it as a pdf; this gives you a snapshot for comparison.)
  • The shared github repo for your project.

Note: since we may grade your assignment up to a few days after submission, per the honor code, we expect that the prototype URL show the state of your prototype at the time of submission. You will very likely be updating your prototype after submission, but please do so on another version.

Submit

Evaluation criteria & Grading rubric

Category Nope Weak Proficient Mastery
Functionality
3 points		 0: No pages are connected and interactive. 1: Prototype lacks a lot of features or has many bugs. 2: Prototype is mostly complete but may still lack one or two features. 3: Prototype is completely functional and ready for user testing. While not completely polished, the overall look and feel is reflective of the final prototype.
Data/Templates
2 points		 0: No data customization. 1: Data customization (e.g., JSON/Handlebars) in key places. 2: Pervasive data customization and templating. All major functionality is templated rather than copied & pasted.
Mobile Design
3 points		 0: Prototype is not designed for a mobile form factor. 1: Minimal attempt to design the prototype for a mobile form factor. 2: Prototype is somewhat designed for a mobile form factor. 3: The prototype's information architecture is well-tuned for a mobile form factor.
Goals
3 points		 0: No goals were met. 1: Only a few goals were met. 2: Most, but not all, of the goals were met. 3: All goals were met.
Updated Development Plan
3 points		 0: No updates to plan. 1: Plan reflects some minor changes. 2: Plan is mostly updated, but is lacking some detail or deadlines seem unreasonable. 3: Plan is detailed and reflects progress, new tasks, and any changes to previous tasks.

Github Repo
1 point.		 Github Repo URL present.

Outside the Box
1 point. Up to 5% of submissions.		 Your prototype is amazing and the TAs are extremely impressed with how complete it is. Not only is everything working, you have either solved an incredibly difficult engineering problem or you have introduced an extremely unique design. Your prototype shows thought and care. You should turn your app into a start-up or at least bring it to market.