The last part of the IA covers building the product (Criterion C), showing it works and can grow (Criterion D), and judging it honestly (Criterion E). Evidence collected along the way makes the writing much easier.

Development: techniques and evidence

Criterion C rewards a product built with appropriate complexity and a clear explanation of how you did it. List the techniques you used and show where they appear in your code.

  • Examples of techniques: sorting and searching algorithms, recursion, file or database handling, object-oriented design, validation, hash tables, parsing, and use of libraries (explained and credited).
  • For each technique, say what problem it solves, show a short annotated code extract, and explain why it was suitable.
  • Use clear names, comments and consistent structure so the code is readable.
  • Keep a development log with dated screenshots of problems and fixes.
// Sort overdue loans by due date, oldest first
overdue.sort((a, b) -> a.getDueDate().compareTo(b.getDueDate()));

Explain the idea in your own words: the comparison sorts earlier dates first, which meets success criterion 3. Do not paste pages of code; choose extracts that show your thinking.

Testing and the demonstration video

Run the tests from your test plan and record the results, including failures and how you fixed them. Test with normal, invalid and boundary data. Ask the client to try the program too, and watch where they get stuck.

For Criterion D, make a short video (check the current time limit with your teacher) that walks through the working product against your success criteria. Also show how the product can be extended, for example through modular classes, separate data files, or documented code that lets a future developer add a feature.

Evaluation

Criterion E asks for a fair judgement, not a sales pitch.

  • Go through each success criterion and say whether it was met, with evidence from tests or client feedback.
  • Include the client’s feedback, ideally with their own words and the date.
  • Describe limitations honestly, such as slow searching with very large data or a missing feature.
  • Recommend realistic improvements and say how you would make them.

Example: “Criterion 4 was partly met: the export works for CSV but the client wanted PDF. I would add a PDF library in a next version.”

Check your understanding

What should an annotated code extract in Criterion C show?

  • All of the code
  • A technique, what it does and why it was chosen
  • Only the program’s name
  • Only the output

Answer: A technique, what it does and why it was chosen Short, explained extracts demonstrate your understanding of the complexity you built.

What is the purpose of the video in Criterion D?

  • To demonstrate the working product and its functionality
  • To advertise the school
  • To replace the written documentation
  • To show only the code

Answer: To demonstrate the working product and its functionality The video shows the product doing what the success criteria say it should.

How should the evaluation treat success criteria?

  • Ignore them
  • Check each one against evidence and state whether it was met
  • Say all were met
  • Replace them with new ones

Answer: Check each one against evidence and state whether it was met Honest, evidence-based judgement of each criterion is what Criterion E rewards.

Which makes a product easier to extend?

  • One huge function
  • Modular, documented code
  • Hard-coded values everywhere
  • Removing all comments

Answer: Modular, documented code Separate, well-documented parts let a future developer add features without breaking the rest.

Previous