Developing Computer Games and Puzzles
This element introduces learners to the fundamental principles of graphic animation, decision-making logic in game programs, storyboarding for game design specifications, and modifying existing game code. It focuses on practical application of these concepts to create interactive computer games and puzzles, fostering skills in planning, coding, and iterative development.
Assessment criteria
Quick Revision Summary (Key Takeaway)
The TLM Level 2 Certificate in IT User Skills in Open Systems and Enterprise (ITQ) covers practical digital skills for the modern workplace, including word processing, spreadsheets, databases, presentations, and safe internet use. This qualification is assessed through portfolio-based evidence and online tests, focusing on real-world application of IT skills.
Topic Overview
The TLM Level 2 Certificate in IT User Skills in Open Systems and Enterprise (ITQ) is a vocational qualification designed to equip learners with the essential digital skills required in today's workplace. It covers a broad range of IT applications, including word processing, spreadsheets, databases, presentations, email, and internet safety. The qualification emphasises practical, hands-on competence, ensuring that students can apply their knowledge in real-world scenarios.
This qualification is particularly valuable because it is recognised by employers and educational institutions, demonstrating that the holder has a solid foundation in IT user skills. It also provides a pathway to further study, such as Level 3 qualifications or apprenticeships. The course is assessed through a combination of portfolio evidence and online tests, allowing students to showcase their skills in a variety of contexts.
By studying this qualification, students will develop confidence in using IT tools efficiently and safely, which is crucial in almost every career. The skills learned are transferable across different software packages and operating systems, making the qualification versatile and future-proof. Whether you are aiming for an office role, further education, or self-employment, this certificate provides a strong starting point.
Key Concepts
Core ideas you must understand for this topic
- →Understanding the difference between open source and proprietary software.
- →Using spreadsheets for data manipulation, including formulas, functions, and charts.
- →Creating and formatting professional documents using word processing software.
- →Designing effective presentations with appropriate multimedia elements.
- →Understanding the importance of data protection and online safety.
Learning Objectives
What you need to know and understand
- Understand the principles of graphic animation., Understand decision making in a games program., Use story boards to make games specifications., Modify existing games code to make changes to a game.
- Understand the principles of graphic animation.Use storyboards to make games specifications.Modify existing games code to make changes to a game.
- Identify key elements of graphic animation, such as frames and sprites.
- Create a simple storyboard to plan a game or puzzle.
- Modify existing game code to change functionality or appearance.
- Test that code alterations produce expected outcomes.
- Explain how changing variables affects game behaviour.
- Understand the principles of graphic animation., Understand decision making in a games program., Use story boards to make games specifications., Modify existing games code to make changes to a game.
- Understand the principles of graphic animation., Understand decision making in a games program., Use story boards to make games specifications., Modify existing games code to make changes to a game.
- Understand the principles of graphic animation., Understand decision making in a games program., Use story boards to make games specifications., Modify existing games code to make changes to a game.
Assessment Criteria
Key criteria assessors look for in your portfolio
- Award credit for demonstrating an understanding of keyframe animation principles, such as tweening and frame-by-frame techniques, in the context of sprite movement.
- Expect clear evidence of decision-making structures (e.g., IF-THEN-ELSE, loops) within game logic, accurately determining game character behavior or puzzle outcomes.
- Require a detailed storyboard that includes game narrative, character positions, user interactions, and screen transitions, directly usable for game specification and development.
- Credit should be given for successfully modifying existing game code to produce a visible, deliberate change in gameplay or visual output, accompanied by an explanation of the code alteration.
- Demonstrate understanding of frame-based animation by creating a simple sprite animation sequence.
- Produce a comprehensive storyboard that maps out game flow, including at least three distinct scenes or levels, with annotations explaining interactions.
- Effectively modify provided source code to implement a new feature, such as a scoring system or extra life, with evidence of testing and debugging.
- Show ability to integrate animated assets into a game environment, linking graphic animation principles to interactive elements.
- Award credit for demonstrating understanding of animation by identifying sequence of images that create movement.
- Accept storyboard evidence showing clear sequence of game screens or levels, even if hand-drawn.
- Credit given for successfully changing at least one aspect of the game code, such as character speed or score.
- Learner provides evidence of testing the modified game, e.g., a screenshot of the changed outcome.
- Award credit for accurately describing key concepts of graphic animation, such as frame rate, tweening, and sprite sheets.
- Award credit for demonstrating the use of conditional statements and loops to control game flow and player decisions.
- Award credit for producing a detailed storyboard that clearly illustrates game scenes, character actions, and program logic.
- Award credit for successfully modifying a provided game code snippet, with clear comments explaining the purpose of changes.
- Award credit for demonstrating an understanding of keyframe animation, tweening, or sprite sheet techniques to create smooth motion effects in a game environment.
- Award credit for correctly implementing conditional logic (e.g., if-else statements) to control game events based on user input or game state.
- Award credit for producing a coherent storyboard that clearly outlines game flow, character actions, and user interactions, with appropriate annotations.
- Award credit for successfully modifying existing code (e.g., changing game variables, adding new assets) to effectively alter a game's behavior or appearance, with documented changes.
- Award credit for demonstrating understanding of animation principles like frame-based movement and sprite manipulation.
- Expect evidence of decision-making structures (e.g., if-else statements) used to control game logic.
- Look for a clear storyboard with annotated panels showing game flow and user interactions.
- Assess ability to modify variables or functions in provided code to change game parameters successfully.
Assessment Guidance
Guidance for achieving higher grades
- 💡In the assignment, explicitly annotate your code or design documentation to highlight where animation principles and decision logic are applied, linking theory to practice.
- 💡When storyboarding, use clear numbering or labels that correspond directly to the game's states and scripts, demonstrating a systematic approach to specification.
- 💡For code modification tasks, begin by commenting out small sections and testing incrementally. Provide before-and-after screenshots or descriptions to evidence your changes effectively.
- 💡Practice reading and interpreting simple game scripts written in pseudocode or a block-based language before attempting modifications, to solidify your understanding of program flow.
- 💡Always include a planning stage: submit your storyboard before starting any coding to demonstrate systematic design thinking.
- 💡When modifying code, comment your changes clearly to show understanding of what each modification does.
- 💡Test your modified game extensively and document test cases to evidence quality assurance.
- 💡Use a simple animation principle first, then build complexity; for example, make a sprite move correctly before adding multiple animations.
- 💡Keep a log of any errors encountered and how you solved them, as this demonstrates problem-solving skills.
- 💡Keep a record of all changes made to code, with before-and-after screenshots.
- 💡Draft storyboards on paper first to clarify ideas before moving to digital tools.
- 💡Make small, incremental changes to code and test each one to understand its effect.
- 💡Follow provided templates and worked examples closely to minimise errors.
- 💡Always plan the game logic using a storyboard before attempting any coding; it serves as a blueprint.
- 💡When modifying code, isolate changes and test incrementally to quickly identify any issues.
- 💡Use comments generously to annotate your code changes; this demonstrates understanding to the examiner.
- 💡Revise basic programming structures (if-else, loops) and how they relate to in-game decision making.
- 💡When explaining animation principles, always reference practical examples from your own game project to demonstrate applied understanding.
- 💡For decision-making coding tasks, structure your code with clear comments and use flowcharts if required to evidence your logic before implementation.
- 💡Before modifying game code, thoroughly read and understand the original code's structure, then plan and document your changes incrementally to avoid errors and show your process.
- 💡When modifying code, comment out original lines instead of deleting them to preserve a fallback.
- 💡For storyboards, ensure each screen state is clearly represented with arrows for navigation.
- 💡Practice basic animation by altering X/Y coordinates in code snippets to see movement effects.
- 💡In decision-making tasks, always test edge cases (e.g., what happens when the player does nothing).
- 💡Always read the question carefully and identify the command word (e.g., 'describe', 'explain', 'evaluate') to know how much detail is required.
- 💡In practical assessments, save your work regularly and name files appropriately to avoid losing marks for poor file management.
- 💡Use the correct terminology in your answers, such as 'cell reference', 'formatting', 'attachment', and 'encryption', to demonstrate your knowledge.
Common Mistakes
Common errors to avoid in your coursework
- Confusing graphic animation with mere image display; failing to implement actual motion or change over time.
- Misunderstanding relational and logical operators in decision-making structures, leading to incorrect game branching (e.g., using assignment '=' instead of equality '==').
- Producing storyboards that are too vague, missing critical details like user input triggers or resource states, making them unfit for specification.
- When modifying code, making changes without understanding the underlying logic, resulting in unintended side effects that break the game.
- Misunderstanding the difference between keyframes and in-between frames, leading to jerky animations.
- Creating storyboards that lack sufficient detail on user interactions, such as missing button presses or mouse clicks required to progress.
- Attempting to modify code without first understanding the existing logic, resulting in unintended changes that break the game.
- Neglecting to save original code versions before making modifications, making it difficult to revert changes.
- Not aligning animation frame rates with game loop timing, causing animations to play too fast or slow.
- Confusing graphic animation with playing a video file.
- Believing all game code must be written from scratch rather than building on existing templates.
- Not saving work regularly or losing unsaved code changes.
- Assuming a single code change will only affect one aspect of the game.
- Confusing the concept of animation with simply moving an object, neglecting frame refresh and timing.
- Misplacing or incorrectly nesting conditional blocks, leading to logic errors or unintended game behavior.
- Creating storyboards that lack sufficient detail on user interactions and program responses.
- Making code modifications without proper testing, resulting in syntax errors or broken game mechanics.
- Confusing frame-by-frame animation with tweening and failing to optimise animation sequences, leading to inefficient or jerky motion.
- Overcomplicating decision-making logic with unnecessary nested conditions instead of using logical operators or state machines, resulting in hard-to-read code.
- Producing storyboards that lack sufficient detail on scene transitions or user interactions, making it difficult to translate into program logic.
- Confusing animation principles with video playback, not realizing games use real-time rendering.
- Overcomplicating decision-making without considering all possible user inputs or game states.
- Creating storyboards that lack detail, such as missing transitions or user actions.
- Making code changes without understanding the original logic, leading to errors.
- Misconception: 'Open source software is always free and has no restrictions.' Correction: While often free, open source software can have costs for support or distribution, and it still has licensing terms (e.g., GPL) that must be followed.
- Misconception: 'Spreadsheet formulas are only used for simple addition.' Correction: Spreadsheets can perform complex calculations, data analysis, and even automate tasks using macros.
- Misconception: 'Email is not a formal communication method.' Correction: Email is a primary professional communication tool, and it must be used with proper etiquette and security awareness.
Revision Plan
How to revise this topic in 1–2 weeks
- 1Week 1: Focus on word processing and presentation skills. Practise creating documents with formatting, tables, and images. Create a short presentation with slides, transitions, and animations.
- 2Week 2: Move to spreadsheets and databases. Learn to use formulas, functions, and charts. Create a simple database with tables, queries, and reports.
- 3Week 3: Revise email, internet safety, and legal considerations. Practise writing professional emails and understand data protection laws.
- 4Week 4: Complete practice assessments and review your portfolio. Identify weak areas and seek extra help if needed.
Exam Question Types
How this topic typically appears in the exam
- 📋Multiple-choice questions testing knowledge of software concepts, such as 'Which of the following is an example of open source software?'
- 📋Practical tasks where you must perform actions in a simulated environment, such as 'Create a spreadsheet with the given data and calculate the average.'
- 📋Short-answer questions asking you to explain a concept, e.g., 'Explain the purpose of using absolute cell references in a spreadsheet.'
- 📋Scenario-based questions where you must apply your skills, e.g., 'You are asked to prepare a presentation for a meeting. Describe the steps you would take.'
Command Word Expectations (THE LEARNING MACHINE)
What examiners look for when using specific command words in this specification
Provide a detailed account of the features or characteristics of a topic. For example, 'Describe the features of a professional email' requires you to list and explain each feature.
Give reasons or causes for something, showing understanding. For example, 'Explain why data protection is important' requires you to discuss the consequences of not protecting data.
Weigh up the pros and cons of a topic and make a judgement. For example, 'Evaluate the use of open source software in a business' requires you to discuss advantages and disadvantages and conclude.
How Students Lose Marks (Examiner Pitfalls)
Common mark loss traps and how to write 100% full-mark answers
Step-by-Step Worked Solutions
Detailed solution breakdown for typical exam problems
Question: You are creating a spreadsheet to track monthly expenses. Column A lists items, Column B lists costs, and you need to calculate the total cost in cell B10. Write the formula you would use and explain how you would format the result as currency.
- 1.Step 1: Identify the range of cells containing the costs (e.g., B2:B9).
- 2.Step 2: Use the SUM function: =SUM(B2:B9).
- 3.Step 3: To format as currency, select cell B10, go to the Home tab, and choose 'Currency' from the number format dropdown, or use the shortcut Ctrl+Shift+$.
Question: You need to send a professional email to a client. List three key features of a professional email and explain why each is important.
- 1.Step 1: Identify features such as a clear subject line, proper greeting, and concise body.
- 2.Step 2: Explain that a clear subject line helps the recipient understand the purpose immediately.
- 3.Step 3: A proper greeting (e.g., 'Dear Mr Smith') shows respect and professionalism.
- 4.Step 4: A concise body respects the recipient's time and ensures the message is easily understood.
Active Recall Memory Test
Test your memory before revealing the key facts
Frequently Asked Questions
Common questions students ask about this topic
Pass / Merit / Distinction Evidence Checklist
How your portfolio evidence is graded for THE LEARNING MACHINE Developing Computer Games and Puzzles
Every vocational unit is marked against named criteria rather than an exam percentage. Your tutor's brief lists the exact codes for this unit — here is what each band is asking you to do.
Demonstrate baseline knowledge, accurate terminology, and core practical application.
Provide detailed analysis, structured explanations, and clear workplace reasoning.
Deliver thorough evaluation, original problem solving, and fully justified recommendations.
Before You Start
Prior knowledge that will help with this topic
- •Basic computer literacy, including using a keyboard and mouse.
- •Familiarity with common software applications like Microsoft Word or Google Docs.
- •Understanding of file management, such as saving, opening, and organising files.
Coursework AI Review
Paste your assignment brief and check your draft against its P/M/D criteria
Key Terminology
Essential terms to know
- Understand the principles of graphic animation., Understand decision making in a games program., Use story boards to make games specifications., Modify existing games code to make changes to a game.
- Understand the principles of graphic animation.Use storyboards to make games specifications.Modify existing games code to make changes to a game.
- Graphic animation principles
- Storyboarding for game design
- Code modification techniques
- Interactive puzzle creation
- Testing game changes
- Understand the principles of graphic animation., Understand decision making in a games program., Use story boards to make games specifications., Modify existing games code to make changes to a game.
- Understand the principles of graphic animation., Understand decision making in a games program., Use story boards to make games specifications., Modify existing games code to make changes to a game.
- Understand the principles of graphic animation., Understand decision making in a games program., Use story boards to make games specifications., Modify existing games code to make changes to a game.
Ready to learn?
AI-powered learning tailored to this unit