Design:
Make available to me any other files that you want me to consider.
You are required to submit your source code, however, you should also turn in
any project files
that help establish that you've been working hard on your project.
This can include source code, .git logs, meeting notes, blue-prints,
sketches, tables (e.g. comparing parts to help decide which is best),
algorithms, e-mails, invoices/receipts, pictures, even a scan of the
back of a stained coffee-shop napkin where you first drew a concept
of what your project would do.
"Design" is a catch-all term. Add any assets that you use.
Be sure to include an updated version of the milestones.
Also, include a short document (like a README.txt file). This should make
it clear where things came from. It's partly to give credit where credit is
due, and to let us know exactly what you have done. Any assets that are
not clearly sourced will not help you. Make sure the author's name/source
is included in any program files, even for the ones you wrote.
As with other assignments, do not use a proprietary format for the
README document.
Crediting people in the README file is not enough; the README file will only
be seen by a couple of people. Be sure to credit people appropriately
in the final video, too.
Here is an example of the information that should be included.
Asset
File name: myimage1.png, myimage2.png, enemysprite.png
What is it: a spritesheet for the main character, and enemy character
Where it comes from: downloaded from https://freepixels.com
Who created it: John Smith
(This should be repeated for all of the files. Note that you can group
these together as shown in the above example. If the files do not
go together logically, such as a character sprite sheet and a code file,
then create another entry.)
Turn in your final project code, design, and other files
on the same date (as the video).
Submit this through iCollege unless otherwise directed.