IA3 calibration exemplar

Secure data exchange, privacy, evidence and evaluation.

This calibration model is based on a high-performing athletics carnival registration assessment. It shows how to connect user needs, APPs, CIA, SQL, API exchange, DFDs, ERDs, pseudocode, testing and evaluation within a tighter 1500 word response.

Word limit

Keep the written response to 1500 words.

Counted words only

The counted response should focus on explanation and evaluation. Pseudocode, code, SQL, ERD diagrams, DFD diagrams, data tables, screenshots, raw testing evidence, appendices and the reference list sit outside the counted total where task conditions allow.

Section
Suggested words
Purpose
Problem, users and impacts
220
Show the problem, user types and key social, personal, economic and legal constraints.
Existing solution analysis
250
Analyse usability, CARP and visual communication.
Data, privacy and security
300
Explain the 3NF model, data exchange, APPs, CIA and access decisions.
Prototype evidence
300
Explain how the interface, API and database work together.
Testing and feedback
230
Use feedback and test results to judge success.
Statement of worth
200
Make a final judgement about effectiveness, safety, usability and improvements.

Scaffold

What a strong IA3 response needs to make visible.

Determining

User needs and constraints

Identify different user types and explain the need for registration, event details, secure login, role-based access and privacy-aware data handling.

Generating

Data and system design

Show 3NF tables, an ERD to prove relationships and a DFD to show how data moves between the interface, API endpoints and database storage.

Security

APPs and CIA

Connect APP 1, APP 6 and APP 11 to transparent collection, limited use and secure storage. Use confidentiality, integrity and availability to justify design decisions.

Evaluating

Evidence-based judgement

Use user feedback, screenshots, database evidence, error messages and test results to judge which criteria were achieved, partly achieved or not yet achieved.

Example paragraph pattern

Use evidence, then judgement.

Evidence: The prototype stores registration data in separate Student, Event and Registration tables, with foreign keys connecting the selected event to the user record. This reduces repeated event data and supports third normal form.

Judgement: This improves data integrity because event details are stored once and reused through the registration relationship. It also supports the admin user need because staff can view who is registered for each event without manually checking separate lists.

Improvement: The next improvement would be to add stronger validation and a confirmation message before registration data is submitted to the API.

Reference support

Useful sources for IA3 calibration.