🇬🇧 T-Levels · flashcards

T-Levels Digital Production, Design and Development Flashcards

56 question-and-answer cards covering Digital Production, Design and Development as it is examined in T-Levels. 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.

56Cards in deck
24Free preview
20Syllabus topics
~200Chars per answer
FreePrice

24 sample cards from the Digital Production, Design and Development deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

  1. Differentiate functional and non-functional requirements with an example of each.

    Functional requirements describe what the system must do, e.g. 'the system shall let users reset their password'. Non-functional requirements describe how it performs/qualities, e.g. 'pages must load in under 2 seconds' (performance, security, usability).

  2. Name four techniques for gathering requirements from stakeholders.

    Interviews, questionnaires/surveys, observation (job shadowing), workshops/focus groups, and document/record analysis of existing systems.

  3. What does the MoSCoW method prioritise requirements into?

    Must have, Should have, Could have, and Won't have (this time) — a technique for ranking requirements by importance and agreeing scope.

  4. Define a 'user story' and give its standard format.

    A user story is a short, plain-language description of a feature from the user's perspective. Format: 'As a [type of user], I want [goal] so that [benefit/reason].'

  5. What is a Gantt chart used for in project management?

    A Gantt chart is a horizontal bar chart showing project tasks against a timeline, displaying start/end dates, durations, dependencies and milestones, used to schedule and track progress.

  6. Distinguish between verification and validation in quality assurance.

    Verification asks 'are we building the product right?' — checking it meets the specification (e.g. reviews, inspections). Validation asks 'are we building the right product?' — checking it meets the user's actual needs (e.g. acceptance testing).

  7. Compare white-box and black-box testing.

    White-box (structural) testing examines internal code/logic and paths, requiring knowledge of the implementation. Black-box (functional) testing checks inputs and outputs against requirements without knowledge of internal code.

  8. Put these test levels in order from smallest to largest scope: integration, acceptance, unit, system.

    Unit testing (individual components), Integration testing (combined modules), System testing (the whole application), then Acceptance testing (user confirms it meets requirements).

  9. Name the three basic control structures used in structured programming.

    Sequence (statements executed in order), Selection (decisions, e.g. if/else, switch), and Iteration (loops, e.g. for, while).

  10. Differentiate the data types integer, float, Boolean and string.

    Integer: whole numbers (e.g. 7). Float: numbers with a decimal/fractional part (e.g. 3.14). Boolean: a true/false value. String: a sequence of characters/text (e.g. "hello").

  11. What is the difference between a local variable and a global variable (variable scope)?

    A local variable is declared inside a function/block and is only accessible within it. A global variable is declared outside all functions and is accessible throughout the whole program.

  12. Compare an array and a record (struct) as data structures.

    An array stores multiple values of the same data type accessed by index. A record/struct stores multiple values of different data types (fields) grouped under one name and accessed by field name.

  13. What is pseudocode and why is it used in the design stage?

    Pseudocode is a structured, language-independent, plain-English description of an algorithm's logic. It is used to plan and communicate algorithms before coding, without worrying about specific syntax.

  14. Name three benefits of following coding standards and conventions.

    Improved readability and maintainability, easier collaboration/consistency across a team, fewer errors, and simpler debugging/onboarding. Examples include meaningful naming, indentation and commenting.

  15. Differentiate a syntax error, a runtime error and a logic error.

    Syntax error: breaks the language rules so code won't compile/run (e.g. missing bracket). Runtime error: occurs during execution and crashes the program (e.g. divide by zero). Logic error: code runs but produces incorrect results due to flawed logic.

  16. List the four types of software maintenance.

    Corrective (fix faults/bugs), Adaptive (adjust to a changed environment, e.g. new OS), Perfective (improve performance/add features), and Preventive (reduce future problems, e.g. refactoring).

  17. In UX/UI design, what are the seven (Norman) usability principles often summarised as, and name three.

    Principles guiding usable design; three examples are: visibility (users can see what actions are possible), feedback (the system responds to actions), consistency (similar elements behave similarly). Others include affordance, mapping, constraints and error tolerance.

  18. What is a wireframe, and how does it differ from a prototype?

    A wireframe is a low-fidelity, static skeletal layout showing structure and placement of elements without final styling. A prototype is an interactive, higher-fidelity model that simulates user flow and behaviour for testing.

  19. Distinguish front-end from back-end development, naming a core technology for each.

    Front-end (client-side) is what the user sees and interacts with — built with HTML, CSS and JavaScript. Back-end (server-side) handles logic, databases and processing — built with languages/runtimes like PHP, Python, Node.js, and databases such as MySQL.

  20. In web development, what are the roles of HTML, CSS and JavaScript respectively?

    HTML provides the structure/content of a page, CSS controls the presentation/styling and layout, and JavaScript adds interactivity and dynamic behaviour on the client side.

  21. What is an API, and why is it important for back-end/database integration?

    An API (Application Programming Interface) is a defined set of rules allowing software components to communicate. It lets the front-end request data and services from the back-end/database (e.g. via REST endpoints returning JSON) without exposing internal implementation.

  22. Name the four main HTTP methods used in RESTful APIs and the CRUD operation each maps to.

    GET (Read), POST (Create), PUT/PATCH (Update), and DELETE (Delete) — together implementing CRUD: Create, Read, Update, Delete.

  23. Define 'responsive design' and name one technique used to achieve it.

    Responsive design makes a web page adapt its layout to different screen sizes and devices. Techniques include CSS media queries, fluid/percentage-based grids, and flexible images.

  24. What is the purpose of evaluating a digital product after deployment, and name two methods of doing so.

    Evaluation checks whether the product meets requirements, user needs and success criteria, and identifies improvements. Methods: user feedback/surveys, usability testing, analytics on usage, A/B testing, and comparison against the original specification.

What this deck covers

The Digital Production, Design and Development deck follows the T-Levels Digital Production, Design and Development syllabus — 5 chapters and 20 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 11.2 cards per chapter.

Answers are written to be recallable, not just readable — averaging about 200 characters, which is long enough to carry the reasoning and short enough to say out loud.

A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.

Digital Production, Design and Development flashcards FAQ

How many Digital Production, Design and Development flashcards are in this T-Levels deck?

56 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.

Are these T-Levels flashcards free?

Yes. The preview here is free to read with no signup, and the full 56-card deck is free inside the Examius app.

What do the Digital Production, Design and Development cards cover?

They follow the T-Levels Digital Production, Design and Development syllabus — 5 chapters and 20 topics — so the questions track what is actually examinable.

How should I use these flashcards?

Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.