Your first deliverable is your planning document.
And your planning document is designed to help you figure
out the appropriate scope for your project and also to
have you really figure out what you're going to build by
having you write the requirements specification for your project.
I have provided a Word template for you to use,
and I've also provided an example of the planning document that I'm using for Wacky Pong.
So let's go take a look at that example planning document.
The first page of your planning document needs to follow this format.
So you need to provide the game title.
In the example that I'm going to use throughout
this course is a game called Wacky Pong which might
remind you of Wacky breakout from
the intermediate object-oriented programming for Unity games course.
But this is, of course,
different because it's Pong not breakout.
You need to include an estimate of how
long you think it will take you to develop the game that you're going to develop,
and this is so that you spend some time thinking about how much time you have available
to you and how much time you think it will take to implement your vision for a game.
This next piece is also to get you thinking
about how long it will take you to do your game and also to let
your peer reviewers estimate how realistic it is based on
this number that you can build this game using this number.
And that's pretty subjective, to be honest,
but if you say it took you 100 hours to build Wacky breakout,
and it's going to take you 30 hours to build crisis,
then you're probably being unrealistic.
So, from the third course in the specialization,
the intermediate object-oriented programming for Unity games course,
how much time did you spend developing Wacky breakout?
Is that estimated or did you actually
keep track of the time that you took to build that game?
And did you follow the detailed instructions or not?
Because you obviously don't have
detailed instructions for the game you're building for this course.
So if you followed those,
then you should probably expand this by some factor,
one and a half, two or whatever because you'll
have to figure everything out all by yourself.
So, this is the format of the first page,
and you need to provide exactly this information on that first page.
The second page of
your planning document is the actual requirement specification for your game.
So you saw this format for the Wacky breakout game in that third course.
I'm giving you this example here for a Wacky Pong again.
I'm also providing to you a requirement specification for a platform that would also be
approximately the correct scope for how many weeks
those courses and how much you know at this point about game programming.
So, you need to either include one of those two requirements specifications or,
of course, a requirement specification for your own game idea,
but make sure it's detailed like this.
You ought to have about a page of
information about the game functionality for the game you plan to implement,
and that's it for
the planning document format and what you
need to include as the information in that document.
To recap, your planning document includes your time estimate for your project.
It includes some Wacky breakout time so that
people can evaluate whether you're hitting an appropriate scope with your project.
It includes your requirements specification where you've
laid out in detail what it is your plan to build.
The planning document deliverable is worth five percent of your overall course grade.