Computer Science 121 - Project Phase IV

Beta design and implementation

1. Overview

In the final phase of the project you'll produce your v.1 release.

  1. Summary of phase IV deliverables
  2. Description of phase IV deliverables
  3. Submission
  4. Grading

2. Summary of phase IV deliverables

Major Deliverables Points
Management update 5
V1 20
Code review package 10
Code review 5
Final report 20


3. Description of phase IV deliverables

3.1 Management

You'll have one final management update. (See management update format for details.)

3.2 V1

Your V1 will be evaluated for

  1. Quality as a game (10 pts.)
    This will be evaluated by your peers using the following rubric.
  2. Code & documentation quality (10 pts.)
    This will be evaluated by a reviewing team using the following code rubric.

3.2 Code review package

You will prepare a code review package for review by another team. Your code and code review package will be evaluated by this code rubric.

3.3 Code review

You and your team will review another team's code. Each team member will be assigned responsibility for some aspect of the code. You should come to the design review with an understanding of your portion, its strengths and weaknesses, be prepared to describe it at a high level to the other reviewers, and to lead a discussions about it. Through these discussion, the review team will agree on an assessment of the code and code package, completing the code rubric and issuing a set of recommendations. The recommendations will be organized into lists of "must do," "should do," and "should consider."

Individual members of the review team will be evaluated on her/his preparation, contributions to the discussion, and role in assessing the code. The team will aso be evaluated on the quality of its recommendations. For more details, see the code reviewer rubric.

3.4 Final report

This 8-10 page document should summarize your project. It will be evaluated according to this rubric.

4. Submissions

Deliverables are due at the start of class time on Tuesday unless otherwise specified. You should link deliverables to your wiki where specified in the template. You should also specify the percentage contribution of each team member to the deliverable.

Each team is entitled to two late days that can be applied to any phase 1 deadline except those involving in-class scheduled events (e.g. Customer Elicitation) or work products that are subject to customer/user review (e.g. game treatment). If there is any question about whether a deliverable can be turned in late, be sure to ask ahead of time. A late submission that is not redeemed with late days loses ten percent of its value for each day missed.

5. Grading

Your team will be assigned a letter grade for each work product; these grades will be normalized based on the point value of each work project in order to compute a team grade for Phase 1. In addition, individual grades will be determined for each phase based on the team grade, the contribution percentages for the deliverables, your work logs, and peer evaluations. Note that in the case of unevenly sized teams, a team of size 5 is expected to produce a project with larger scope than a team of size 4! It is your job to choose an appropriate scope to your project.