CSE 116 Spring 2004
Stage 2 of Major Project (Initial description)
Introduction
You have worked on stage 1, and most of you discovered that
working with other people actually requires some organization. We
will discuss some strategies for managing a team in lecture.
More details to follow
As with the stage 1 description, you should note that this
document is an initial description only. More details will follow
about the tools you will be use (see next section) as well as
information about testing and documentation requirements. I will
also address issues that come up as a result of your analysis of
the problem, so it is in your best interest to ask questions in
the newsgroup (where these questions will be answered).
Tools to be used
You will learn to use the following tools:
You started using Eclipse and CVS in stage 1. In stage 2 you will
begin to use JUnit as well. More details will follow in
recitation.
Stage 2 description
In stage 2, you will develop a graphical user interface for your
game. You will build your stage 2 on one of the code bases to be
provided to you in the next several days (we're aiming to have the
code bases up by Monday PM). We will deal with adjusting team
memberships in approximately the same timeframe. We will make
between five and eight code bases available for you to choose
from. You may build your stage 2 on any of the available code
bases, provided it is not your own. You and your team-mates must
evaluate the available code bases and pick the one which you feel
will be the best starting point for your team. Things to take
into consideration, in no particular order, are (i) commenting,
(ii) design, (iii) correctness of code, (iv) completeness of code
and (v) code readability.
Stage 2 evaluation
Your 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).
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 Stage2. 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
calculator. You must not submit any auto-save files or any
.class files.
Zip the Stage2 directory and submit the resulting zip file,
Stage2.zip using the submit_cse116 command.
This project is due on or before 11:59 PM on April 2, 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 1, 2004 are considered one day early, and
projects submitted on or before 11:59 PM on March 31, 2004 are
considered two days early. Projects submitted after 11:59 PM on
April 2, 2004 are considered late.
Carl G. Alphonce
Last modified: Tue Mar 2 19:59:00 EST 2004