Assignment 03 - Rapid Prototyping
- Marks: 11
- Weighting: 11%
- Due: 5:00 pm, Friday 26th January, 2018
To investigate the unknown aspects of your project, and use the information gained to refine and develop both your project plan and game design.
This is a team assignment.
Last week your team worked on a Game Design Document, and as a part of this exercise you were supposed to come up with a prototyping plan. This week you are creating a number of prototypes. Document each prototype you construct. For each, describe:
- What you are trying to achieve?
- Who worked on the prototype?
- How long the prototype took to complete.
- What decisions did you make based on the prototype? What worked, what didn’t?
- What new questions / prototypes arose from this one?
Finally, present a summary briefly describing how the results of your prototyping have altered / confirmed your project plan. What aspects of the project are still unknowns?
- If there’s nothing else you do, make sure there is a playable (in some minimal form) version of your core game mechanic. If you can’t demonstrate this in a week, you’re in trouble.
- As always, making this document interesting to read (without sacrificing clarity) will put me in a better mood when marking.
- Handing in something that vaguely describes your prototyping week is worth half marks. A well written report with prototypes I can look at / play with will be worth 3/4 marks. Impress me with the depth of your investigation and clear thought put into prototyping for full marks.
- Have a look at pg. 92 (1st ed)/pg. 108 (2nd ed) in the Art of Game Design for a good starting point for your reports.
- Any code/unity projects should be checked-in into your team's GitLab repository. A good option for code prototypes is to use a common Unity project, but have different scenes for different prototypes. This way the assets can be easily shared, but different members of the team can work independently on different prototypes. In your reports describe where the corresponding prototype resides.
- I will not be judging the code’s quality, but I do want to be able to run the code-based prototypes.
- For non-code prototypes, submit the relevant bits and pieces in a readily accessible form. For example, if you are using tools other than those available in the lab, export a copy that I can read. For example, export Adobe Illustrator files as .png or .pdf files.
- Paper prototypes should be included in electronic form: take a photo or scan them (there's a scanner available in Lab A).
- Any questions for stranger types of prototypes, contact me.
Submissions must be made by 5:00 pm, Friday 26th January, 2018. Late submissions will not be marked.
To submit your assignment:
All the documentation should go into the same wiki on GitLab where your Game Design Document resides. You don't have to wikify your prototype reports - you can create links on the wiki to pdf documents if it's more convenient. Each prototype should be described by a separate document. You will be submitting the assignment with link to the wiki as you did for the previous assignment.
Only one team member needs:
- To submit the assignment send an e-mail to email@example.com with the Subject: "COSC360 <team name> Assignment 3 submission", and the link to the wiki pasted in the body. This e-mail constitutes your submission and it must be sent before 5pm, Friday 26th January, 2018. Late submissions will not be marked.