Criterion deep dives

Criterion A: Problem specification

You produce:

• A description of the problem scenario with measurable requirements
• An explained choice of computational context (language, platform, libraries, key concepts)
• A list of success criteria, each with a code (SC1, SC2…); the IA Guide recommends 8–10

Step by step, with a worked example:

1. Problem scenario (95–120 words)
2. Computational context (60–80 words)
3. Success criteria (5–30 words)

Criterion B: Planning

You produce:

• A decomposition of the problem into components and sub-tasks (a diagram plus short explanation)
• A chronological plan covering all five stages, with every task linked to success criteria (for example a Gantt chart or an Agile board)

Step by step, with a worked example:

1. Decomposition (35–60 words)
2. Plan (45–70 words)

Diagram examples: Decomposition diagram, Gantt chart

Criterion C: System overview

You produce:

• A system model: diagrams of the components, how they connect, how data is stored and the user interface
• Algorithms for the components: flowcharts, pseudocode or structured natural language
• A testing strategy that aligns with the success criteria, usually a test-plan table

Step by step, with a worked example:

1. System model (20–45 words)
2. Diagram selection guide: five design questions
3. Algorithms (20–45 words)
4. Testing strategy (15–50 words)

Diagram examples: 17 worked examples (use-case, architecture, ERD, wireframes, flowcharts and more), chosen with the five design questions. See them all.

Criterion D: Development

You produce:

• A short justification of the product's structure, at the beginning, before the first technique (recommended)
• At least five techniques (recommended), each in four parts: (1) a screenshot of the code, (2) an explanation of the code, (3) a justification of how you programmed it, briefly compared with another option, and (4) a brief justification of how you tested it
• Your full, commented source code in the appendix, which every code screenshot refers to

Step by step, with a worked example:

1. Structure of the product (50–80 words)
2. Technique 1: No double bookings (150–185 words)
3. Technique 2: The weekly limit (150–185 words)
4. Technique 3: The noise rule (150–185 words)
5. Technique 4: The waiting list (150–185 words)
6. Technique 5: Releasing no-shows (150–185 words)
7. Technique 6: The usage report (150–185 words)

Criterion E: Evaluation

You produce:

• An evaluation of every success criterion, in the same order as Criterion A, with evidence
• Justified improvements to the product, each linked to a weakness you found

Step by step, with a worked example:

1. Meeting the success criteria (260–320 words)
2. Improvements (150–190 words)

Your appendix

You produce:

• The full, commented source code of your product, with line numbers that match your code screenshots
• Any other resources you developed and refer to in your documentation (test results, data files, sample outputs)

Your video

You produce:

• A screen recording of the finished product showing every success criterion working
• Examples of your testing: normal, extreme and abnormal data, and any automated tests