CompSci 308
Spring 2018
Software Design and Implementation

Game : Project Plan

It's not the plan that is important, it's the planning.Dr. Gramme Edwards

This part is intended to get you thinking about a program without worrying about exactly how it will be implemented. In other words, you should be able to explain a game in enough detail without writing any actual code that you feel comfortable you can finish in about a week (and about 1000 lines of code).

Specification

Create a plain text file (within Eclipse, File -> New -> Untitled Text File), called PLAN.txt, that describes a plan, before beginning to code your Breakout game, of what you intend to build in the next week, including:

This plan is not intended to be completely binding, but the more your deviate from it the worse impact on your project grade. The goal is not to squash your creativity, if you think of something cool to add only later, while you are coding, we want you to add it; however, if you plan to make all your levels have something in common and then you never implement that or change what it is completely, then it is not clear you thought about the project in enough detail to make some basic critical choices.

For each of these points, you can include more than the minimum number asked for because the goal of this plan is partly to get you thinking about what types of variety are possible. However, try to keep the ideas within the realm of feasibility, things you think you might be able to implement in the next week without stressing yourself out too much. In this sense, this plan's other purpose is to give you a chance to try to estimate what you think you can accomplish.

Submission

Use git to commit and push your PLAN.txt file to your game project's repository as your submission of this part of the project. This is how all submissions will be done for this course — only what is in your Gitlab repository will be considered part of your work.