Developing a database with complex techniques (internal)
Internal 4 credits Normalisation Relationships SQL Integrity Informed & refinedThe internal builds a relational database using complex techniques: multiple related tables, enforced integrity, and queries that answer real questions. Achieved DEVELOPS the database; Merit develops an INFORMED one — using testing results to improve it, and structuring/organising/querying the data logically; Excellence develops a REFINED one — iterative improvement throughout, efficient techniques, and data presented effectively for the purpose and end users.
1 Reading the notation
Achieved / informed / refined, in the standard's own words.📖 Terms the schedule grades you on
3 terms- Develop a database (Achieved)
- Design the data structure; use appropriate tools/techniques to organise, query and present data for a purpose and end users; apply data integrity and testing; address implications.
- Develop an informed database (Merit)
- Use information FROM testing to improve quality; structure, organise and query the data logically.
- Develop a refined database (Excellence)
- Iterative improvement THROUGHOUT the process; efficient tools/techniques; data presented effectively for the purpose and end users.
2 Modelling the data
Entities, relationships and normalisation, before any table is built.The order that avoids rework
- List the real-world entities and the facts about each.
- Draw the relationships, resolving any many-to-many with a junction table.
- Normalise to 3NF, then check each fact is stored exactly once.
3 The complex techniques the standard names
Multi-table structure, modifying queries, customised multi-table displays, dynamic linking, access permissions.Build order that shows all five
- Create tables with correct types, keys and constraints, structured across multiple tables.
- Write queries that INSERT, UPDATE or DELETE, not only SELECT.
- Build at least one customised display pulling from multiple tables (a report, dashboard or program interface).
- Link the front end dynamically to the live database.
- Apply access permissions appropriate to who should see or change what.
4 Data integrity and testing
Constrain the database itself, then try to break it. ✕Validation only in the interface
A rule enforced only in a form is bypassed by any other route into the data — a direct query, an import, or a different interface. Put constraints in the database (CHECK, NOT NULL, UNIQUE, foreign keys) so they hold regardless of how data arrives.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.