CSE 116 Spring 2004
Stage 3 of Major Project
Stage 3 description
Group work (software development) - [80%]
In stage 3 you will be given an opportunity to complete any of the
stage 1 and stage 2 functionality not already present in your stage 2
solution. [50%]
You will create a computer player for a two-player (human vs.computer)
version of the game. We will discuss this in lecture on Friday (April
9). [30%]
You may build your stage 3 on any one of the following:
- your stage 2 submission,
- any of the available stage 1 code bases that you could have chosen
as a base for stage 2, or
- your stage 1 submission.
Note that if you choose one of the available stage 1 submissions
rather than your stage 2 submission you will need to adapt your stage
2 GUI to a different stage 1 codebase.
Individual work (writing) [20%]
You must submit (individually, not as a team) a coherent written
report about your 116 project experience. You must report on:
- What and how much you felt that each team member contributed to
the team effort. Incorporate your peer evaluation in this section
(same guidelines apply as for stage 1 and 2 peer evaluations).
- Two major issues you and your teammates faced, how you attempted
to resolve the issues, and whether you were successful.
- What you feel you learned from doing this project.
- What you feel you didn't learn from doing this project, but wish
you had.
- How you would approach a team software development effort in the
future.
- The biggest challenge you faced in doing this project (do not just
repeat what you said in the "two major issues" section above).
Note well that grammar, spelling, clarity of expression, conciseness,
etc. all count.
Stage 3 evaluation
Your code submission will be graded based on its,
- completeness (does it do everything it is supposed to, according
to the requirements outlined in Stage 1 and Stage 2 - e.g. does the
implementation calculate the score, can multiple players play),
- correctness (does everything that has been implemented work as it
should - e.g. is the score calculation correct),
- design (does the implementation demonstrate that the team members
have used design patterns as appropriate),
- code documentation (is the code well-documented),
- user interface design and usability (is the user-interface easy to
use, does it help or hinder gameplay, etc).
- whether the computer player actually plays the game (but not on
how good the computer player is)
Your report submission will be graded based on its,
- grammar
- spelling
- clarity of expression
- conciseness
- content (do you address the points I indicated?)
- thoroughness (do you provide reasonably detailed answers?)
- organization
Due dates and submission procedure
Once you are ready to submit, make sure all the files you intend to
submit are in a directory named Stage3. It is very
important that you only submit .java files, along with a
.dia file (produced by the UML tool, which is at
/projects/CSE115/umltool ) which shows the design of your
game. You must not submit any auto-save files or any
.class files.
Zip the Stage3 directory and submit the resulting zip file,
Stage3.zip using the submit_cse116 command.
The report is submitted by each individual. The report must be in
acrobat PDF format.
This project is due on or before 11:59 PM on April 26, 2004. Recall
the early bonuses and late penalties outlined in the syllabus,
handed out on the first day of classes. Projects submitted on or
before 11:59 PM on April 25, 2004 are considered one day early, and
projects submitted on or before 11:59 PM on April 24, 2004 are
considered two days early. Projects submitted after 11:59 PM on
April 26, 2004 are considered late.
Carl G. Alphonce
Last modified: Mon Apr 5 22:57:36 EDT 2004