Final Project Progress Report

Show your progress by submitting your project code and documentation as well as creating a video that describes what you have learned as you implement your proposed game.

Specifications

Documentation

Make a README.txt file:

• acknowledgments for any online or human resources used
• acknowledgments for any resource files (images, sounds, etc.) used, all of which must be royalty free and not "stolen" off of the web
• how to interact with the game, how to win or lose the game, and how the levels increase the challenge of the game

Iteration Journal

Use this template to show your current status of your game's development and your implementation plan for the next part you will work on.

Feedback

Letting others play your game early and often, while changes can be easily made, is a vital part of the iterative process. Authentic feedback can be ambiguous or even contradictory, so deciding how to respond may require significant really thinking about what will improve the game. Summarize the feedback as follows in your README.txt file:

• Positive feedback. Note the top good things about your game that others commented critically about, and you feel are important to keep. Ideally, these would be similar comments made by multiple playtesters.
• What could be improved. Note the top things about your game that others commented critically about, regardless of whether or not you agree with the users or if they seem to contradictory. If any of these comments are made by multiple playtesters, make sure to note that as well.
• Response. Note the changes you feel need to be made based on playtester feedback.

Video

Record a 5-10 minute video showing your current progress and describing what you have completed to this point:

• Play your game showing both winning and losing (if those are implemented yet)
• Describe what code you have written to make implementing your game mechanics easier or more readable (i.e., classes outside the main Game class or methods outside those from Arcade you have overridden)
• Describe the following things encountered during the process of creating a game:
  • Describe your problem solving process for a new feature in your game
  • Describe a bug you have dealt with: how did you find it, figure out its cause, and fixed it
  • In what ways do you see programming as part of your identity or what is it like to express yourself creatively with code?
  • In what ways will your knowledge of programming be helpful in non-CompSci courses you are taking or plan to take?
• Evaluate your progress:
  • Are you on track or behind according to your timeline?
  • What parts of are on time and what parts are delayed and why?
  • What are you planning to work on next?
  • Has the scope of your project changed? If so, how and why?