Skip to main content.

Final Project: Preparation Analysis

Objective: Prepare for the final project by reviewing the given code and planning what has to be done for the project.

Due: Before class, Nov 18

Review Specifications

Review the specifications for the final project.

Discussion Questions

Create a PREPARATION text file. (Can be a PDF; definitely not a .doc, .docx, .odt, or .rtf file.) Answer the following questions in that file. Clearly label which question you're addressing.

  1. What are the main parts/steps/components that need to be completed to complete the project? Try to be as specific and precise as possible. How much work does each part require? (Approximate in terms of time or relative to the other steps.) How many people should work on each part?
  2. How will your program handle the following use case: "The user starts the program, types 'fd 50' in the command window, and sees the turtle move in the display window leaving a trail." It should be clear from your description which objects are responsible for completing each part of the task. Some of the classes are given to you; others need to be added.
  3. What 3 extensions would you like to have in your final application?
  4. Bring the above answers together into a plan for how you would tackle implementing the project with your team. What parts can be completed independently of the other parts? What parts need to be completed before other parts?
  5. The parts of the project you're most interested in working on, in ranked order.
  6. Any questions about the given code. (Ask these in class as well.)

Submission

In your turnin directory, create a final directory. Copy your PREPARATION file into that directory.

Alternatively, you can create a final directory in your cs209 directory and run submitAssignment.sh final to submit the assignment.

You can create/save the files using Eclipse remotely and run the submitAssignment.sh script, adapting the directions from assignment 6.

Grading

Clear descriptions, articulation of answers to above questions. Evidence that you thought about the questions and reviewed the code.