Games Design and Development
GATEWAY QUALIFICATIONS LIMITED
vocational
Games design and development involves understanding game types, platforms, and the design process. Learners generate ideas, plan, develop a prototype, and review their work.
6
Learning Outcomes
20
Assessment Guidance
20
Key Skills
6
Key Terms
23
Assessment Criteria
Assessment criteria
Gateway Qualifications Level 1 Award in Games Design and Development
Gateway Qualifications Level 2 Diploma in Digital and IT Skills
Gateway Qualifications Level 2 Certificate in Digital and IT Skills
Gateway Qualifications Level 2 Extended Certificate in Digital and IT Skills
Gateway Qualifications Level 2 Award in Games Design and Development
Gateway Qualifications Level 2 Award in Digital and IT Skills
Topic Overview
The Gateway Qualifications Level 1 Award in Games Design and Development introduces you to the fundamental principles of creating digital games. You will explore the entire game development process, from initial concept and design to prototyping and testing. This qualification covers key areas such as game mechanics, narrative design, visual assets, and user experience, providing a solid foundation for further study or entry-level roles in the creative digital sector.
Understanding games design and development is crucial in today's digital world, as the gaming industry continues to grow rapidly. This course not only teaches you technical skills like using game engines and scripting but also develops your problem-solving, creativity, and teamwork abilities. By the end of the award, you will have created your own playable game prototype, demonstrating your understanding of the design cycle and the importance of iteration based on user feedback.
This qualification fits within the broader context of computer science and digital media by combining artistic creativity with logical thinking. You will learn how to balance fun gameplay with technical constraints, a skill applicable to software development, interactive media, and even simulation training. The hands-on projects prepare you for further qualifications such as the Level 2 Certificate in Games Development or GCSE Computer Science.
Key Concepts
Core ideas you must understand for this topic
- →Game Design Document (GDD): A comprehensive blueprint outlining the game's concept, mechanics, story, characters, and technical requirements. It serves as a reference throughout development.
- →Game Mechanics: The rules and systems that define how the game operates, including player actions, scoring, levels, and win/lose conditions. Examples include jumping, collecting items, and enemy AI.
- →Prototyping and Iteration: Creating a basic, playable version of the game to test core mechanics. Iteration involves refining the prototype based on testing and feedback to improve gameplay.
- →User Interface (UI) and User Experience (UX): UI includes on-screen elements like menus, health bars, and buttons. UX focuses on how the player interacts with the game, ensuring it is intuitive and enjoyable.
- →Asset Creation: Designing visual and audio elements such as characters, backgrounds, sound effects, and music. Assets must be optimised for the target platform.
Learning Objectives
What you need to know and understand
- 1. Know about the purpose, types and platforms for computer games. 2. Be able to generate ideas and plan a game design.3. Be able to develop and present a game prototype. 4. Review the computer game design and prototype.
- 1. Know about the purpose, types and platforms for computer games. 2. Be able to generate ideas and plan a game design.3. Be able to develop and present a game prototype. 4. Review the computer game design and prototype.
- 1. Know about the purpose, types and platforms for computer games. 2. Be able to generate ideas and plan a game design.3. Be able to develop and present a game prototype. 4. Review the computer game design and prototype.
- 1. Know about the purpose, types and platforms for computer games. 2. Be able to generate ideas and plan a game design.3. Be able to develop and present a game prototype. 4. Review the computer game design and prototype.
- 1. Be able to understand different types of computer games. 2. Be able to design a computer game in response to a client brief. 3. Be able to develop and test a computer game. 4. Be able to review a computer game.
- 1. Be able to understand different types of computer games. 2. Be able to design a computer game in response to a client brief. 3. Be able to develop and test a computer game. 4. Be able to review a computer game.
Assessment Criteria
Key criteria assessors look for in your portfolio
- Identify different game genres and platforms.
- Generate original game ideas and create a design document.
- Develop a playable prototype using appropriate tools.
- Evaluate the final game against initial objectives.
- Describe different game types and platforms.
- Generate and document game ideas with a clear concept.
- Plan a game design including mechanics, story, and assets.
- Develop a playable prototype and review it against the plan.
- Award credit for clearly identifying and explaining at least two distinct game types (e.g., simulation, strategy) and their suitable platforms, with reference to target audience and purpose.
- Credit the production of a detailed game design document that includes narrative, rules, character sketches, level layouts, and asset lists, demonstrating thorough planning.
- Expect the prototype to be functional, showcasing core gameplay mechanics, and be accompanied by a presentation that effectively communicates design choices and received feedback.
- Describe different game types and platforms.
- Generate and plan a game design concept.
- Develop and present a working prototype.
- Identifies different game genres and platforms.
- Designs a game that meets the client brief.
- Develops a functional game prototype.
- Tests the game and fixes bugs.
- Reviews the game against objectives.
- Award credit for demonstrating clear understanding of game genres, platforms, and mechanics, with specific examples linked to the client brief.
- Award credit for a detailed design document that includes game flowcharts, wireframes, asset lists, and a clear narrative or gameplay mechanic aligned with the brief.
- Award credit for evidence of iterative development and functional testing, including documented bug reports, fixes, and version control that show a methodical approach to quality assurance.
- Award credit for a thorough review that evaluates the game against the original brief, identifies strengths and weaknesses, and suggests realistic improvements based on tester feedback and self-reflection.
Assessment Guidance
Guidance for achieving higher grades
- 💡Keep a log of design decisions.
- 💡Test your prototype early and often.
- 💡Be prepared to justify design choices.
- 💡Start with a simple core mechanic and build on it.
- 💡Use flowcharts to plan game logic.
- 💡Get feedback from peers during development.
- 💡Always ensure your game design document links directly to the initial idea generation; assessors look for clear progression from concept to plan.
- 💡When developing the prototype, prioritize creating a minimum viable product (MVP) that showcases the core mechanic rather than attempting excessive features.
- 💡In your review, use a structured evaluation framework (e.g., SWOT analysis) comparing the prototype against the design aims, and propose specific improvements.
- 💡Research existing games for inspiration.
- 💡Keep the prototype simple and functional.
- 💡Document the development process.
- 💡Use flowcharts or storyboards for design.
- 💡Prioritise core gameplay over extra features.
- 💡Include user feedback in review.
- 💡Read the client brief multiple times and highlight key requirements—ensure every element of your design and development is mapped back to these.
- 💡Use a structured design template (e.g., game design document) that covers storyboarding, mechanics, and assets to present your planning clearly and professionally.
- 💡Keep a development log with screenshots, code snippets, and notes on challenges and solutions—this serves as vital evidence for marking.
- 💡Test early and often; create a test plan that covers functionality, usability, and edge cases, and record test results as proof.
- 💡In your review, use the brief as a checklist, directly compare the final game against each requirement, and support your evaluation with feedback from playtesters.
- 💡Tip 1: Always start with a clear Game Design Document. Examiners look for evidence of planning and consideration of all game elements. A well-structured GDD shows you understand the design process.
- 💡Tip 2: Focus on playtesting and iteration. Document how you tested your game and what changes you made based on feedback. This demonstrates reflective practice and a user-centred approach.
- 💡Tip 3: Keep your prototype simple but polished. A small, fully functional game with good UI/UX scores higher than a complex, buggy one. Ensure controls are responsive and instructions are clear.
Common Mistakes
Common errors to avoid in your coursework
- Overcomplicating the prototype scope.
- Neglecting player feedback during review.
- Poor documentation of design ideas.
- Creating a prototype that is too complex for the time available.
- Ignoring target platform constraints.
- Not testing the prototype thoroughly.
- Students often confuse game genre with game platform, failing to match the technical requirements of the platform with the design.
- A common error is producing a prototype that deviates significantly from the original design document without justification, weakening the iterative design evidence.
- Many learners neglect to include user feedback in the review stage or provide superficial evaluation, missing the opportunity to demonstrate critical reflection.
- Choosing a platform without considering its limitations.
- Overambitious scope for the prototype.
- Not testing the prototype thoroughly.
- Designs without considering target audience.
- Spends too little time on testing.
- Fails to document the development process.
- Misinterpreting the client brief by focusing on personal preferences rather than the specified requirements, leading to a game that misses key objectives.
- Neglecting to document the design process adequately, making it difficult for assessors to trace decisions and for the learner to manage development efficiently.
- Over-relying on pre-made assets without customisation, which can limit originality and prevent demonstration of development skills.
- Testing only for obvious errors rather than systematically checking all interactions, resulting in an unstable final product.
- Providing a superficial review that merely describes what was done without critical evaluation against the brief or user feedback.
- Misconception: Games design is just about programming. Correction: While coding is important, games design also involves storytelling, art, sound, and psychology. Many roles focus on design without heavy programming.
- Misconception: A good game idea is enough to succeed. Correction: Execution matters more than the idea. A well-designed prototype with polished mechanics and feedback is crucial; many great ideas fail due to poor implementation.
- Misconception: Testing is only for finding bugs. Correction: Testing also evaluates fun, balance, and usability. Player feedback helps refine mechanics and improve the overall experience.
Frequently Asked Questions
Common questions students ask about this topic
Pass / Merit / Distinction Evidence Checklist
How your portfolio evidence is graded for GATEWAY QUALIFICATIONS LIMITED Games Design and Development
Pass (P)
Demonstrate baseline knowledge, accurate terminology, and core practical application.
Merit (M)
Provide detailed analysis, structured explanations, and clear workplace reasoning.
Distinction (D)
Deliver thorough evaluation, original problem solving, and fully justified recommendations.
Before You Start
Prior knowledge that will help with this topic
- •Basic digital literacy, including file management and using software applications.
- •Some familiarity with creative tools like image editors or sound software is helpful but not essential.
- •An interest in games and how they work, including analysing what makes a game enjoyable.
Coursework AI Review
Self-check your coursework evidence against P/M/D criteria
Key Terminology
Essential terms to know
- 1. Know about the purpose, types and platforms for computer games. 2. Be able to generate ideas and plan a game design.3. Be able to develop and present a game prototype. 4. Review the computer game design and prototype.
- 1. Know about the purpose, types and platforms for computer games. 2. Be able to generate ideas and plan a game design.3. Be able to develop and present a game prototype. 4. Review the computer game design and prototype.
- 1. Know about the purpose, types and platforms for computer games. 2. Be able to generate ideas and plan a game design.3. Be able to develop and present a game prototype. 4. Review the computer game design and prototype.
- 1. Know about the purpose, types and platforms for computer games. 2. Be able to generate ideas and plan a game design.3. Be able to develop and present a game prototype. 4. Review the computer game design and prototype.
- 1. Be able to understand different types of computer games. 2. Be able to design a computer game in response to a client brief. 3. Be able to develop and test a computer game. 4. Be able to review a computer game.
- 1. Be able to understand different types of computer games. 2. Be able to design a computer game in response to a client brief. 3. Be able to develop and test a computer game. 4. Be able to review a computer game.
Ready to learn?
AI-powered learning tailored to this unit