Final Project | Scored 100%

Final Project

Mazes and Links and Queues, oh my! Redux. Grading: You will NOT be demonstrating your final project! This means you must spend more time on the reflections, design and test documents. The grader will not be able to ask you questions. If he has a question that is not answered in your supplied
documentation then you will likely lose points.

(15 pts) Polyas steps 1, 2, and 4 do not directly deal with you C++ code itself, but rather, the steps you took to write a correct program that solves the given problem statement. With this said, make yourself familiar with the three sections below, and make sure you can provide documentation and talk intelligently about what you did to arrive at the solution you did. You will have to explain how you went through these steps to your TA, as part of your assignment grade. On some assignments you will be required to submit your class hierarchy and be able to explain it.
Understanding the problem. (Recognizing what is asked.)
Devising a plan. (Responding to what is asked.)
Carrying out the plan. (Developing the result of the response.)
Looking back. (Checking. What does the result tell me? )

(75 points) Program Requirements
The graders were unanimous about the common problem with assignment 3. Too many students did not design their program!! This caused two significant problems. First, the programs were not well-written and were confusing. This aggravated the second problem, which was that the TAs in many cases, couldnt understand what was intended. That meant they couldnt provide constructive feedback. The
graders made a request and I am honoring it. If you do not have an actual design document they will
not grade your final project!! This does not mean you show them a piece of paper you say is a design.
If they do not see your design in the document then it is NOT a design document.
I strongly encourage you to talk to a TA. Ask for specific feedback. They will help you as much as they
can. Do that this week! The better your design document is going into the final project the better your
final project will be.
Assignment 4 corrections (15 points) You may need to make corrections for this assignment to make it
possible to move on to the final project. You can get some credit for that here. If you had assignment 4
done correctly and the grader at your demo said it was good, you still get these points.
The following are the changes you will make to add different behavior to the assignment.
Ghost (15 points) The ghost will move in any 4 directions randomly. It will ignore walls. If it moves
within 5 spaces of the player it will change its movement to head in the direction of the players current
position. The ghost should move first every turn. Distance is measure by Manhattan Geometry.
Remember you can only move up, down, left and right. So you must count the spaces along the shortest
path to measure distance.

There is no change to the ghost catching the player. If the ghost moves within 1 space of the player she is
returned to the starting space. There is no change to the effect of cherries. If the player moves into a C
space she gets 20 spaces of invincibility where the ghost cannot send the player back.
Movement (15 points) Most movement remains the same, with one major change. The current floor is
not shown to the player. The player can only see an area around his current position up to a distance of 5
spaces. As the player moves, the revealed spaces remain that way. They are not made blank again. This
will require some change so document it in your design! You may need to change the array that holds
the floor to indicate if each space is revealed. You may want to have 2 arrays for each floor. The master
copy read from the file and a copy that indicates which part has been revealed. There are other ways;
these are just 2 options to get you thinking about it.
You may also need to modify the move function for the ghost. The ghost will need to measure the
distance to the player before it moves. Again, there are many possible ways to do this.
Design (15 points) If you did a design for assignment 3, modify it to add these requirements to your
program. If you didnt do the design, or the grader says you didnt do it well, then create the design now.
These are points for the grader to give you feedback. Remember that if you do NOT have a design
document the final will NOT be graded!
Testing (15 points) Please describe how you tested your program. Identify logic paths through your
program (what decisions your program makes). How did you ensure that the correct action was taken?
What did you do to try and break your program? Did you have someone else try your program?
These design and test documents are in addition to your reflections.

(10 points) Programming Documentation and Style
Review the programming style guide for the class. You are expected to write your code in compliance
with this guideline. I do not expect exact adherence but you should be consistent in what you do. If the
grader cant understand your code then you are doing something wrong.