Higher Computing Science: Course, Exam, and What Makes the Difference

Higher Computing Science is growing — 3,962 entries in 2025 against 3,746 the year before — and for good reason. You build working code — a program, plus a database or a website — as a major part of your grade: the assignment alone is worth a third of the total. If you can code and you can problem-solve, this subject rewards you in a way few others do.

The short answer

Higher Computing Science is a one-year course covering software design and development, computer systems, and either database design and development or web design and development, plus a practical assignment set by Qualifications Scotland. One exam paper in May, plus the assignment completed in class. In 2025, 75.5% of entries achieved C or better and 42.1% an A. Graded A–D with a pass at C.

Course structure

The course covers four areas. The first two are compulsory in both the exam and the assignment; from the second pair your school picks one — database design and development or web design and development — and you are assessed on that one:

Software Design and Development — the programming unit:

• Programming in Python or Visual Basic (your school chooses the language)
• Data types: string, integer, real, Boolean, character
• Data structures: arrays (1D and 2D), records
• Control structures: selection (if/else), iteration (for, while), nested loops
• Subprograms: functions, procedures, parameter passing (by value and by reference)
• Standard algorithms: input validation, linear search, count occurrences, find minimum, find maximum
• Testing: normal, extreme, exceptional test data; trace tables; debugging techniques

Computer Systems — the theory unit:

• Processor architecture: fetch-execute cycle, buses (address, data, control), registers, cache memory
• Data representation: binary, two’s complement, floating point (mantissa and exponent), ASCII/Unicode, bitmap and vector graphics, sound sampling
• Networking: protocols (TCP/IP, HTTP, HTTPS), network topologies, IP addressing, routing
• Security: encryption, digital certificates, firewalls, malware types, ethical and legal issues
• Contemporary computing: cloud, AI, environmental impact

Database Design and Development (option A) — covers:

• Relational database concepts: entities, attributes, primary keys, foreign keys, relationships
• Entity relationship diagrams (one-to-one, one-to-many, many-to-many)
• SQL: SELECT, FROM, WHERE, AND, OR, ORDER BY, aggregate functions (SUM, COUNT, AVG, MIN, MAX), GROUP BY, HAVING
• Data validation and verification
• Data dictionary concepts

Web Design and Development (option B) — covers:

• HTML structure: semantic elements, forms, links, images, tables
• CSS: selectors, properties, layout, responsive design basics
• JavaScript: variables, arrays, events, DOM manipulation, functions
• UI design principles: navigation, consistency, accessibility, readability
• Testing across browsers and devices

Assessment

This structure dates from course specification version 3.0 (May 2023, valid from session 2023–24), which introduced the database-or-web option; it is unchanged for 2026–27.

Section 1 of the paper (55 marks) covers software design and development and computer systems, opening with short stand-alone questions and moving into longer context-based ones with multiple parts. Expect theory (explain how floating-point numbers are stored), code reading (what does this program output?) and code writing. Questions are written in Qualifications Scotland’s standardised reference language, but you can answer in any programming language — marks are for understanding, not syntax.

Section 2 or Section 3 (25 marks) is the optional half: database design and development (designing a structure from a description, writing SQL queries, validation) or web design and development (HTML, CSS, JavaScript, evaluating a design against usability principles). You answer one, not both — in 2025, 66% of candidates chose the database section. Very few questions in either section are direct recall; almost all ask you to apply what you know to a context.

The assignment is a 40-mark practical task set by Qualifications Scotland each year — you do not choose the problem. Task 1 (software design and development, 25 marks) is compulsory; Task 2 (database, 15 marks) or Task 3 (web, 15 marks) matches the option your school teaches. You work through analysis, design, implementation, testing and evaluation on a computer with a high-level programming language and tools for SQL, HTML and CSS, under supervision, within 6 hours spread over several sessions once the content has been taught. Externally marked.

The course specification at a glance

Everything in the assessment breakdown above comes from the official course specification — the definitive document Qualifications Scotland publishes on its Higher Computing Science course page, alongside the specimen question paper and marking instructions. The specification pins down the reference language used in exam code questions, which settles the perennial “which language do I answer in?” worry.

Grade boundaries and pass rate

Boundaries are set each year after marking. These are the published lines for every diet Qualifications Scotland still reports — marks out of the paper's total, with the C boundary shown as a share of marks:

In 2025, 3,962 candidates sat Higher Computing Science (up from 3,746 in 2024): 75.5% achieved C or better and 42.1% an A — but 14.2% received no award. Both ends are high for a reason: the subject self-selects motivated, technically minded pupils, and the assignment (a third of the marks) gives competent programmers a head start before the exam, while pupils who cannot write code fluently have nowhere to hide. Entries are growing as schools invest in computing departments and pupils recognise the career value.

Who takes Higher Computing Science and why

Higher Computing Science is increasingly valued by universities and employers as digital skills become essential across all sectors. It’s particularly useful for:

• Computer science degrees (the direct pathway)
• Software engineering — programming and systems design are directly relevant
• Data science and statistics — database and algorithmic thinking transfers well
• Cybersecurity — the networking and security content provides a foundation
• Game design and development — programming and design principles
• Engineering (electronic, mechanical) — computing is increasingly embedded
• Teaching (secondary computing science)

It also works as a strong complement to Maths, Physics or other STEM Highers. Pupils applying for any STEM degree benefit from demonstrating that they can code and think algorithmically. Even for non-STEM applications, Higher Computing Science signals structured problem-solving ability.

Common pitfalls

• Under-preparing for the assignment. At a third of the total, pupils who treat the assignment as a formality lose disproportionate marks. You cannot start it early — it is set annually and done in 6 supervised hours — so practise the specimen task, and get fast at writing, testing and documenting code under time pressure.
• SQL syntax errors. Exam questions regularly ask you to write SQL queries, and marks are lost for small errors: missing semicolons, incorrect use of WHERE vs HAVING, forgetting to use aggregate functions with GROUP BY. Practise writing queries by hand until the syntax is automatic.
• Confusing design with implementation. When asked to design a solution, markers want pseudocode, structure diagrams, wireframes or entity relationship diagrams. When asked to implement, they want actual code. Pupils who write Python when the question says “design” lose marks, and pupils who write vague descriptions when the question says “implement” lose marks too.
• Skipping computer systems theory. The programming and database content feels practical and engaging; the processor architecture and data representation content feels dry. But Section 1 always includes theory questions on the fetch-execute cycle, binary arithmetic, floating-point representation and networking. These are marks you cannot afford to throw away.

S5 vs S6

Higher Computing Science is typically taken in S5 by pupils who completed National 5 Computing Science in S4. Advanced Higher Computing Science is available in S6 and involves a major software development project with significantly more complex programming — object-oriented design, multi-module systems, and more rigorous testing. It is excellent preparation for a computing degree. The S6 retake route carries no penalty.

Recommended resources

• Hodder Gibson Higher Computing Science — course textbook with theory and programming exercises.
• Leckie Computing Science Revision Guide — revision guide with exam-style questions (covers N5 foundations relevant to Higher).
• Past papers — every Higher Computing Science paper back to 2016 at sqa.org.uk — our SQA past papers guide covers where they live and how to use the marking instructions. Practise the code-writing questions by hand.
• W3Schools (w3schools.com) — free tutorials for SQL, HTML, CSS and JavaScript that map closely to the course content.
• Python documentation (docs.python.org) — the official reference for the language most schools use.
• How to Pass Higher Computing Science (2nd edition) — exam-technique guide mapped to the current Higher course.

Book links above are affiliate links: buy through them and we may earn a small commission, at no extra cost to you. See our editorial policy.

The honest take

Higher Computing Science is the most practical Higher in the Scottish curriculum. You write real code and build a real database or website — and a third of your final grade comes from doing exactly that. If you enjoy problem-solving and building things, this subject will feel more rewarding than almost any other Higher. If you find programming frustrating or tedious, it will feel like a long year.

The assignment is your biggest asset or your biggest liability. At a third of the total it matters more than most coursework — and because it is a 6-hour supervised task set each year, it rewards pupils who are fluent, not pupils who are slow and careful. Clean working code with testing evidence can carry you to an A even with a modest exam performance; unfinished tasks can drag you below a pass even if you know the theory cold. Practise the specimen task until the process is automatic.