The project checklist gives a list of deliverables: components that we expect you to include in all your projects. The final project will have some additional deliverables (in particular related to team work and planning), and some of the mini-projects will not require all the standard deliverables.
The list might at first appear intimidating, but it is intended to make things easier for you, by giving you a simple way to check that what you hand in has adequate coverage, and that you have paid attention in your development to all the important issues. You should look at the checklist and make sure you understand it before you start your project work.
We hope that indicating how the different components will be weighted in the grading will make it easier for you to determine how best to invest your effort. In a professional setting, it is common to have documentation standards that dictate deliverables in this way, so learning how to fit your imaginative ideas in the context of a structured document is a useful skill to acquire.
The questions in the right hand column are the ones that the grades will be asking as they evaluate your work, and which you can ask yourself to make sure that you're on track. Don't be misled by the length of the checklist into thinking that making your handin more voluminous will result in a higher grade. On the contrary, if you obscure a simple issue with a lot of irrelevant text, you will receive a lower grade. We expect that in most cases, a miniproject will not require more than 5 pages of documentation in total (in addition to commented code and graphical models), and sometimes less, to receive full credit.
Bonus points will be awarded for particularly good work in any aspect, and these will be used to boost the total grade (although not beyond the grade you would receive for a perfect solution, in order not to create pressure to do extra work).