Advanced programming techniques (internal)
Internal 6 credits Program structure Data structures Testing Error handling DocumentationAS 91896, 6 credits — the largest internal at this level. This standard has a strict DEFINITION of what counts as "advanced" (note 4) and its OWN develop → informed → refined ladder (distinct wording from the other techniques family) — a program built to it, tested against a real plan, and structured so someone else can read it.
1 Reading the notation
This standard has its own strict five-point definition of "advanced" — separate from the achievement ladder itself.📖 Terms the schedule grades you on
4 terms- Develop (Achieved)
- Write code for the task; use advanced techniques; document clearly; test on EXPECTED cases.
- Informed (Merit)
- Document function/behaviour; follow language conventions; test EXPECTED + BOUNDARY cases.
- Refined (Excellence)
- Well-structured/logical; FLEXIBLE AND ROBUST; COMPREHENSIVE testing (expected+boundary+invalid).
- "Advanced program" (note 4)
- 2+ data types; sequence/selection/iteration; input; output; 2+ advanced techniques.
2 What each grade requires
A distinct wording from the rest of the DigiTech family — but the same develop → informed → refined shape.| Grade | What it takes | The half people drop |
|---|---|---|
| Achieved | Advanced techniques for the purpose/end users; data integrity and testing; EXPLAIN implications | Explaining an implication in the abstract, unconnected to this outcome |
| Merit ("informed") | Use information FROM TESTING to improve quality; ADDRESS implications with a visible decision | Testing that never feeds back into an actual change |
| Excellence ("refined") | ITERATIVE improvement across design/development/testing; JUSTIFY the choices made | One single round of testing, not a genuine iteration loop |
The verb escalates every time: explain → address → justify. Each is a distinct, checkable action, not just "more effort".
3 Advanced techniques and structure
Two or more of the six named techniques, each with a stated reason.What the evidence needs
- The requirements the program must meet, written before you build.
- Functions that each do one job, with meaningful names.
- TWO OR MORE advanced techniques actually used, with a reason for each.
4 Validation, robustness, and testing scope
The test plan's required scope escalates exactly with the grade. ✕A test plan with only normal cases
A plan proving the program works when nothing goes wrong evidences Achieved at best. Merit specifically requires boundary cases; Excellence requires comprehensive coverage including invalid input too — testing scope is not incidental, it is graded directly.5 Testing plans and comments
Input, expected result, actual result, pass/fail — for every case the grade requires.What a strong test plan and comments show
- Every test row: input, expected result, actual result, pass/fail.
- Boundary cases: zero, one, empty, maximum, one past maximum.
- Comments that explain WHY, not restate WHAT the code does.
Practice
Recall it first, then use it — testing yourself builds the memory, where rereading the notes above only feels easier.
Recall and application shuffled together — you have to work out what each item wants before you can answer it, which is the part the exam actually tests. Both kinds feed the same spacing schedule, so anything you miss comes back sooner.
Say the answer out loud before flipping — that attempt is where the learning happens, even when you get it wrong.
Exam-style only. Instant feedback, shuffled each attempt, best score saved on this device.