Skip to main content
ScotlandComputer Science

Database Design and Development: study guide to the SQA Advanced Higher Computing Science database area

A study guide to the Database Design and Development area of SQA Advanced Higher Computing Science. Covers database analysis and design, normalisation to third normal form, SQL implementation, and database testing and evaluation, with advice on how the topics connect and how to study them.

Generated by Claude Opus 4.89 min readAdvanced Higher: Database Design and Development

Reviewed by: AI editorial process; not yet individually human-reviewed

Jump to a section
  1. What the area covers
  2. How the topics connect
  3. How to study this area
  4. Where to go next

Database Design and Development is the relational-database area of SQA Advanced Higher Computing Science. It takes you from a description of a real situation, through a normalised design, to a working SQL database that you test and evaluate. This guide maps the area and links to the full topic pages.

What the area covers

The area follows a single project from requirements to a tested database.

  • Database analysis and design. Entities, attributes and relationships, entity-relationship diagrams, the data dictionary, and primary, foreign and composite keys, including resolving many-to-many relationships with a link entity.
  • Normalisation. Working data from unnormalised form through first, second and third normal form using functional dependencies, to remove redundancy and anomalies.
  • SQL implementation. Data definition and data manipulation, multi-table joins, aggregate functions with GROUP BY and HAVING, subqueries, wildcards and computed columns.
  • Database testing and evaluation. Testing SQL queries against expected results, entity and referential integrity, and evaluating a database for fitness for purpose and data integrity.

How the topics connect

The four topics are stages of one pipeline. Analysis and design identifies the entities and relationships and produces the ERD. Normalisation is the formal check on that design, splitting the attributes into tables that hold each fact once; design and normalisation usually agree, and where they differ normalisation wins. The normalised tables, with their primary and foreign keys, become the CREATE TABLE statements of the SQL implementation, and the relationships become the join conditions in queries. Testing and evaluation then proves the queries return the right data and that referential integrity keeps the links between those tables valid. The keys you choose in the first topic are exactly what referential integrity enforces in the last.

How to study this area

Database Design and Development rewards a clean design and fluent SQL.

  1. Practise normalisation on paper. Take a flat table and drive it to 3NF, naming the partial and transitive dependencies you remove at each step.
  2. Write SQL by hand. Drill joins, aggregates with GROUP BY and HAVING, and subqueries until you can build a multi-part query without a reference.
  3. Learn WHERE versus HAVING. A condition on an aggregate goes in HAVING; this distinction is a frequent exam discriminator.
  4. Know the integrity rules. Be able to define entity and referential integrity and give an example of an action each one prevents.
  5. Practise past papers. Use SQA past papers and marking instructions to learn the query style and how marks are split across a complex SELECT.

Where to go next

Work through the four topic pages from this area, then test yourself with the area quiz. After that, move on to the Web Design and Development area, which often connects a web front end to a database like this one through server-side code.

Sources & how we know this

  • computer-science
  • sqa-advanced-higher
  • sqa-computing
  • database-design-and-development
  • advanced-higher
  • normalisation
  • sql