CS 121 -- Fall 2012


Phase 4 - Version 1.0

1. Overview

In the final phase of the project you will 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
Final report 100


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 by me when you build and demostrate the grame.

  1. Quality as a game (10 pts.)
    This will be evaluated by the following rubric.
  2. Installation Documentation (10 pts.)
    This will be evaluated by the following installation documentation rubric.

3.3 Project Presentation

One team make a final presentation that will be evaluated for content using Project Rubric and the presentation rubric.

3.4 Final report

You are to create a 8-10 page document that summarizes the overall project. You have created numerous reports along the way. The final report may have links to some of the same material, but I am looking for something different as far as content. I would like you to review the whole project, discussing what happened in each phase, rather than the final result of each phase. For example, you might look at the requirements process that you went through and discuss the lack of specifics provided by your consumer; and/or you might discuss the issues related to group dynamics; and/or you might discuss the applicability of the various testing methodologies to your project; and/or you might discuss the usefulness of Domain Diagrams; and/ or etc. One way to organize the report is to look at each of the four phases and discuss specifics about the issues with each phase. This report will be viewed using the Deliverables from each Phase, i.e., I am interested in what you can say about each Phase, and the deliverables required in that Phase.

4. Submissions

Deliverables are due as indicated on the Calendar (usually Sunday midnight). You should link deliverables to your wiki where specified in the template.

Each team is entitled to two late days that can be applied to any phase 4 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 will be penalized

5. Grading

I am not going to rehash grading here. Check out: grading.