Individual and Group Evaluations
The first step in this Object-Oriented Game Architecture suite of programs you'll write is to specify the model of a game. Eventually the game will be one of several implemented using a Model-View-Controller architecture as an applet and an application.
In the final suite of games, you'll have stand-alone, solitaire games; networked-based solitaire games; and multi-player games against the computer or other human players.
For the purposes of designing the Model class/interface you should restrict yourself to games that do not involve continuous motion. There might be some animation that's part of the games, but the animation isn't essential to the purpose of playing the game, it's a bell-and-whistle.. Here are links to some sample games. The Yahoo Games site has many others (and other sites do as well).
Of course these are all grid games. You should consider card games and other game genres as well.
The game plan should include the names of each game you plan to implement. This should include both guarantees and projections. Failure to meet a guarantee engenders dire consequences. Failure to meet projections incurs no penalty. Implementing a game that's not in your game plan will be admired, but it won't earn many points.
Thus, it's important to do careful forecasting.
submit_cps108 oogasubmit1 ....You don't need to submit if all your code/documentation is linked to your group webpages. In that case, email ola@cs.duke.edu the URL for your pages.
Please leave your original group/game plan intact. Supply a new game plan based on the past week. This plan should be a revised version of your original plan. Your web pages should make both plans completely explicit --- it should be clear which was your April 5 game plan and which is the version 0.9 plan.
The revised plan should be updated to reflect the experience of the last week of coding/planning. Please include new guarantees and projections, modifying the previous ones to reflect your experiences.
Each group should submit one zipped/compressed/tar file of all code and a README indicating where the group website is located.
submit_cps108 ooga-v.9 .....Every individual should submit a README indicating their own/self effort, indicating how many hours (approximately) you've put into OOGA, what your responsibilities are, and what your impressions of the group's achievements are to-date. This self-assessment and evaluation will be worth 1% of your OOGA grade, the final self assessment will be worth 4% of your OOGA grade.
The self assessment should be as long as necessary to spell out your individual accomplishments and the efforts of the group. You do not need to evaluate other group members at this time, you will need to do that for the version 1.0 submission.
submit_cps108 ooga-self.9 ....
To submit use the assignment name oogafinal. You can do this via Eclipse, but you probably won't be able to submit all your materials since the Eclipse and default submission mechanism put a 300K limit on the total size of the submission. Instead, create a zip/.tgz or similar compressed archive of your submission. You can submit this from the command-line on acpub using the command shown below.
submit_cps108final oogafinal ooga.tgz
You may need the full path to the submit executable, see below.
/afs/acpub/project/cps/bin/submit_cps108final oogafinal ooga.zip
You should submit
Please deliver to Prof. Astrachan's office, D241 LSRC, sometime before Monday at noon a group notebook. In that notebook you should have the following sections clearly marked.
The 20-minute presentation is a tight limit, so you might want to practice. I suggest bringing a laptop configured with everything ready to go: presentation, program, demo, etc.