CSE143 Summer 2003

Project 1

Game Keeper (I)

Due dates:  Step 1: Thursday, June 26, in quiz section.  Step 2: Electronic parts on Monday evening, June 29 June 30 9:00 PM; printouts and/or remaining non-electronic parts in quiz section June 30 July 1.  (If you are already panicked because you don't know what Step 1 or Step 2 is -- relax.  Read the full instructions word for word, top to bottom and much will become clearer).

Overview.   You are the national record keeper for Poetry Slams held around the country.  People send you the results, by e-mail or phone, which you record.  People also can ask for a list of how all the contestants are doing.  You'll write a program to help you do this.  There are requirements on what the program does (its behavior or functionality) as well as requirements on how the program is written (internal requirements).

Starting Code.  The starting code directory contains two files: the IRecordkeeper interface, and a Test1SimpleGamekeeper class.  Download these files and place then in the same directory where you plan to put the other files that will be part of this project.  Try compiling them.  IRecordkeeper should compile without errors; the other class will have errors since it refers to a class called SimpleRecordkeeper SimpleGamekeeper that you will have to implement.

Step 1 (Written part)  No code is involved. Do two things: 1) "solve" the test case in the Test class.  That is, write down exactly what will be "printed" (displayed on the console) when the test case runs.  2) Write down some of the design for your eventual programming solution, as follows:.  write down the name of each class you expect to implement and turn in, and for each class write down the name of each method you expect to implement.  There is no special format for this, as long as it is clear and legible.  Don't understand?  Ask questions until you do.  Just make your questions more specific than "what am I supposed to do?"

Step 2: (Code part).   Write code (classes) so that the given (starter) Test class will run.  You may not change the Test class.  Your program must compile and run with it.  You can write as many classes as you need, and use whatever names you feel are appropriate -- as long as the original TestSimpleGamekeeper compiles and runs with your stuff.   Also, write a Test class of your own, with a test case of your own that gives the Gamekeeper a good workout.  Call this class Test2SimpleGameClass.  Turn in electronically all the classes to run the program, that is, needed to run the Test class given.  (When the turn-in form is ready, it will answer a lot of questions you might have about the process of submitting your files.  Never heard of the turn-in form?  Don't panic.  Finish reading these instructions first -- then panic!)

Some rules:  Don't change either of the starter files; you won't be able to turn in modified versions.  Your SimpleGamekeeper class must implement the interface IRecordkeeper.  All your classes must compile without error when we compile them (just compiling on your computer isn't enough).  You get no credit if there is a single warning or error message on the compilation.  We will check your program by running tricky test cases which you have never seen before.  All code should be clear and commented, intended to communicate effectively with a human reader..  For now, follow the style example of the starter code and code in the textbook (not lecture or quiz code, which often is compacted to save space).

To get full credit, it is not necessary to go beyond the requirements, and there is no extra credit if you do.  But impressing your TA is always a good thing anyway!

This project is to be done by each student individually.  Review the course and departmental guidelines for use of work not your own.  In particular, any scrap of code you didn't originate yourself (or that isn't CSE143-supplied) must be acknowledged.

Some advice: Before writing a single line of code, read carefully each word of the starter code. Then reread these instructions top to bottom, word for word.  Then study the starter code again.  Then do Step 1.  Don't dream of starting Step 2 until then.   Finish Step 1 24 hours before it is due.  Finish Step 2 48 hours before it is due.  Don't assume the process of turning the homework in electronically will be smooth and trouble-free.

Hints, Tips, and Corrections.   Check here occasionally for major hints or corrections.  Your best source of help is the Message Board, however, or office hours.