Part 1 – Game Design Document (P3, P4, M2, D2pt1)
Task Criteria Y/A
Requirements (audience, purpose & client requirements) P3
Legal & ethical considerations P3
Gameplay design (Description of gameplay & flowboard) P3
Visual design (Description of visual style & asset list) P3
Technical design (Data dictionary & pseudocode/flow chart of processes) P3
Choice of programming language, API and game engine P3
Intended platform for delivery P3
Production schedule (Gantt chart) P3
Hardware & software required P3
Test plan (functionality and requirement tests) P3
Constraints P3
Gather feedback from your client & 2 users on your design documentation P4
(record print screens of the emails sent and received)
Identify & make improvements to your design documentation based on the P4
feedback, providing evidence of changes made
Justify your design decisions made based on the purpose, audience and M2
requirements.
Evaluate (strengths, weaknesses & conclusions) how well your design meets D2pt1
the requirements
Task Criteria Y/A
Requirements (audience, purpose & client requirements) P3
Legal & ethical considerations P3
Gameplay design (Description of gameplay & flowboard) P3
Visual design (Description of visual style & asset list) P3
Technical design (Data dictionary & pseudocode/flow chart of processes) P3
Choice of programming language, API and game engine P3
Intended platform for delivery P3
Production schedule (Gantt chart) P3
Hardware & software required P3
Test plan (functionality and requirement tests) P3
Constraints P3
Gather feedback from your client & 2 users on your design documentation P4
(record print screens of the emails sent and received)
Identify & make improvements to your design documentation based on the P4
feedback, providing evidence of changes made
Justify your design decisions made based on the purpose, audience and M2
requirements.
Evaluate (strengths, weaknesses & conclusions) how well your design meets D2pt1
the requirements
