Top

Week 12

In this week's content we will be looking at from client brief to software design through a realistic Level 3 IT context. You will be required to turn a client description for a device-loan tracker into testable requirements, pseudocode and a documented software design.

Steps to complete:
1. Classify sample requirements as functional, non-functional, constraint or acceptance criterion.
2. Read the Library Device Loan Tracker brief and highlight rules that must be implemented exactly.
3. Rewrite the brief as numbered, testable requirements and identify ambiguities to clarify.
4. Create data items, modular structure and pseudocode for borrowing eligibility and fees.
5. Exchange designs and respond to three client questions or change requests.
6. Write a 200-word rationale linking design choices to requirements.

By the end of the session you should have a testable requirements specification, pseudocode and a client-reviewed software design rationale.

Week 12 Student Resource Pack


Last Updated
2026-09-14 09:20:30

English and Maths

English

requirements reading; precise paraphrase; technical documentation; explanation; responding to feedback.


Maths


Stretch and Challenge

Stretch and Challenge


Homework

Homework


Equality and Diversity Calendar
How to's

How to's Coverage





Links to Learning Outcomes

Links to Assessment Criteria

AQA AO1, AO5, AO6, AO8: interpret a client text, write coherent design documentation and respond to questions/feedback.

Unit 4: Programming — B: design a software solution to meet client requirements; decomposition, algorithms, data structures and design documentation.

 


Files that support this week


| | | | |

Next

Prev