Skip to main content
ScotlandComputer ScienceSyllabus dot point

How does the coursework project ask you to carry a real problem through the whole development process?

Plan and produce the Advanced Higher Computing Science project: analyse, design, implement, test and evaluate a substantial solution in one of software, database or web development, with appropriate documentation.

An overview of the SQA Advanced Higher Computing Science coursework project, the practical task that takes a substantial problem in software, database or web development through analysis, design, implementation, testing and evaluation toward the final grade.

Generated by Claude Opus 4.812 min answer

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

Have a quick question? Jump to the Q&A page

Jump to a section
  1. What this dot point is asking
  2. What the project is
  3. The stages and their evidence
  4. How to approach the project well
  5. Try this

What this dot point is asking

The SQA wants you to carry a substantial problem through the entire software development process as a single piece of coursework. The project is assessed work that contributes to your final grade alongside the question paper, and it is marked on how well you analyse, design, implement, test and evaluate a real solution.

What the project is

The project is the coursework component of the course. You choose one of the three practical areas and build a substantial solution to a problem, documenting each stage. It tests, under realistic conditions, the same skills the question paper assesses in short form: the ability to take an open problem and produce reliable, well-engineered software, a database, or a website. Together with the question paper it determines the A to D grade.

The stages and their evidence

The project is structured by the development process, and each stage produces evidence that is marked.

  • Analysis. Describe the problem and produce a specification of the requirements the solution must meet. This is the benchmark the whole project is judged against.
  • Design. Produce design evidence suited to the area: structure or class diagrams and data structures for software; an entity-relationship diagram and normalised tables for a database; a site structure diagram and wireframes for a website.
  • Implementation. Build the working solution, applying the techniques of your chosen area (object-oriented code, SQL, or HTML, CSS, JavaScript and PHP).
  • Testing. Produce a test plan with normal, extreme and exceptional data, run it, and record actual against expected results.
  • Evaluation. Judge the finished solution against the analysis: fitness for purpose, robustness or maintainability, and honest limitations.

How to approach the project well

The project rewards planning and disciplined documentation as much as coding skill.

  1. Pin down the analysis first. A clear, specific specification gives you both a build target and the criteria for the final evaluation.
  2. Design before you build. Produce the diagrams for your area; implementing from a design is faster and the design is itself marked.
  3. Test against expected results. Decide expected outcomes in advance and record actual against expected; testing is a marked stage, not an afterthought.
  4. Evaluate against the requirements. Go through the analysis point by point and judge honestly, including limitations; this is where fitness for purpose is demonstrated.
  5. Follow the current coursework instructions. The SQA publishes the coursework assessment task and conditions each year; read and follow the current version exactly.

Try this

Q1. State how many of the three practical areas the project is built in. [1 mark]

  • Cue. One: the project takes a single chosen area to depth, not all three.

Q2. Name the project stage whose requirements the evaluation must be measured against. [1 mark]

  • Cue. Analysis: fitness for purpose is judged against the specification agreed there.

Exam-style practice questions

Practice questions written in the style of SQA exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.

AH style: project stages4 marksState the stages of the development process assessed by the Advanced Higher Computing Science project and one piece of evidence each produces.
Show worked answer →

Analysis, producing a description of the problem and a specification of requirements (1 mark). Design, producing design evidence such as a structure or class diagram, an entity-relationship diagram, or wireframes for the chosen area (1 mark). Implementation, producing the working code or database or website (1 mark). Testing and evaluation, producing a test plan with results and an evaluation against the specification (1 mark). Markers want stages correctly paired with the evidence each generates.

AH style: evaluation3 marksExplain what the evaluation section of the project should contain and why it must refer back to the analysis.
Show worked answer →

The evaluation judges whether the finished solution meets the requirements set out in the analysis, item by item (1 mark), and comments on its fitness for purpose, robustness or maintainability and any limitations (1 mark). It must refer back to the analysis because fitness for purpose can only be measured against the requirements agreed at the start; an evaluation with no specification to check against has no criteria (1 mark). Markers reward linking the evaluation to the original requirements.

Related dot points

Sources & how we know this