Deadline Date

Overall Goal

Specific Tasks which should be Accomplished

Tuesday, April 14

Have a working model of the game completed: this should include the introduction, tutorial, main game stack, eight completed puzzles incorporated into the game stack, and a conclusion card.

The working model will not at this point include 1) help, 2) sound, 3) the overall theme of the game and items necessary to effect this theme.

• all puzzles should be completely functioning, and be polished for presentation
• The puzzles should be incorporated into the main game stack. This will involved the following modifications:

1. modifying colors so that the puzzles associated with each room match the color of the room
2. implementing a clock which will move on half an hour each time a room is entered
3. Incorporating the names of the students playing the games into the main stack of the game

Tuesday, April 21

By this point, we hope to have a complete "rough draft" of the program available for presentation to our teacher. This draft will include the working puzzle completed the previous week, which will now have sound, theme incorporated, and help sections.

• Decorate the main haunted house room
• Decide on a theme
• Implement the theme; this will include 1) modifying the introduction and possibly tutorial, 2) placing coins in each room which are gathered when the room is arrived, 3) keeping a running total of the money collected, and 4) making a scene in which the ghost is freed using this money
• Decide on format for "Help" sections and write theses
• Decide on placement of sound, and use sound
• Meet with Teacher to obtain her feedback on the program
• This will also be the first time that the program is run on the computers at Blessed Sacrament

Friday, April 25

Adjustments/Student Testing

• Make adjustments to program based on 1) teacher feedback from Tuesday, and 2) computer response of the program (eg does it run on 4Megs and if not, what do we modify)
• Attend Blessed Sacraments to student test the program; this will involve taking eight students at a time, having two work with each team member, having them play the game and observing there responses. We will also have a list of questions to ask them regarding the game

May 5

Documentation/Final Polishing

• preparation of documentation for usage and troubleshooting of the program
• reparations of any problems noted during students testing; modifications of anything which was unclear to the students, etc.
• Documentation of the pedagogical motives behind the program, the results of testing, the success of the program, and future work. This will be done mostly on the web