Your report should have the following sections:
* Introduction/Overview
* Inspirations/Background
* Design
* Implementation
* Iteration/Evaluation
* Lessons Learned
* Conclusion
Grading will be based on:
* 30% Writing & presentation quality (organization, grammar, flow)
* 30% Technical scope
* 20% Creativity
* 20% Evaluation/Process
Again, the weighing may be changed.
Your report should have the following sections:
* Introduction/Overview
- what did you do?
* Inspirations/Background
- What led to what you did?
- inspiring games, articles, daydreams, whatever
- cite inspirations
* Design
- high-level description of what you built
* Implementation
- details, how it exists in Godot
- ideally explain object hierarchies & scenes, code structure
- enough detail that someone who looks at your code will have a basic
idea of what is going on, how to find bits they are interested in
- if chunks of your implementation came from outside sources, just
give a high level summary of it and cite the source
* Iteration/Evaluation
- organize what you wrote in your journal, what was the process?
- how close did you get to what you wanted to do?
- what are the major issues remaining?
- report on any playtesting or other testing you did
- cite resources that helped you along the way
* Lessons Learned
- what do you know now that you didn't know at the start of the term?
* Conclusion
Grading will be based on:
* 30% Writing & presentation quality (organization, grammar, flow)
* 30% Technical scope
* 20% Creativity
* 20% Evaluation/Process
Again, the weighing may be changed.
Progress report
---------------
- how are you doing compared to what you planned to do (in the proposal)?
- give drafts of whatever you can for the final report
- progress on design
- progress on implementation
- progress on process (bring together recent journals, maybe expand)
Remember, progress is ultimately about the report, not what you are building
- I grade the written artifacts