Milestone #3: 60% complete

6.7.0.1

Milestone #3: 60% complete

1 Description

Milestone #2 described the iterative design process and led you through one iteration. To complete your project you should continually be looping over the four stages of iterative design: Prototyping, Testing, Evaluation and Refinement. In this Milestone, you will demonstrate a prototype of your project that is 60% complete, gather feedback from others inside and outside the class, and write a 2-3 page single-spaced 12-pt paper providing a brief analysis of your project and feedback.

1.1 Testing

Once you have a working prototype, you are going to test it. You should try and find as many people as you can to try your product; between five and ten people, with at least half coming from outside the class.

1.2 Evaluation

You should have some way of capturing the feedback from those that tested your product. You can have a questionnaire that they complete after trying it, or perhaps you could interview them. Try and determine if they understood the way it worked. Did they like the feedback they got from the program? What didn’t they like about the product? Would they use it again? Why or why not?

Also, you should observe testers using your prototype and note when you feel they were having trouble understanding the product, or were unhappy with the way it worked.

1.3 Refinement

Finally, look at the feedback you got from the testers. Do you see some commonalities in their complaints or praise? What changes could you make to your program to address their concerns? Prioritize the improvements you could make to your product, based on the testers’ feedback, and start working on incorporating those changes into your next prototype.

2 Write-up

You are going to submit a 3-page paper describing your iteration through the design process. Your paper should use 12pt font, have 1in margins, and be single-spaced. Here are the major sections (label them clearly) you need in your paper along with a brief description of each:

Description Briefly describe the idea behind your product, the look of the program, and its basic controls.
Prototype Describe what features and rules you have implemented in your prototype.
Testing Describe the process the users went through in testing your program. How did you find your testers? How much time did you spend explaining how it worked? How long did they use it? How did you gather information from them? What questions did you ask them?
Analysis Analyze the data. Start by summarizing the measurements you made. Then: do you see clear common elements in your responses? Are there any patterns that you see?
Refinement Given this feedback, what should you change about your program? You should include the prioritized list of improvements discussed above.

}

3 Deliverables

In lab on Wednesday of Week 10, your team must be prepared to demonstrate a 60% complete version of your project.
Before 11:00 PM on that night, your team must submit a .zip file containing your writeup along with all files required to run your project, using Polylearn. If you have more than one file in your project, include a README text file that lists the files in your project and what each one’s role is.

4 Assessment

You will be graded using the following rubric:

Handing something in: 5 pts
Project running as is (all code included, etc.): 5 pts
Clear and correct Data Definition: 5 points
Clear and correct code: 5 points
Writeup: Testing (3pts)
Writeup: Analysis (3pts)
Writeup: Refinement (3pts)
Writeup: Overall Quality (5pts)
In-lab Demo: (8 pts)