An overview of the course assignment: an open-ended engineering problem solved by applying knowledge from across the course, with a report assessing analysis, simulation or construction, and evaluation.

What this key area is asking

This page is an overview of the course assignment, the coursework component of Higher Engineering Science. It is not a content topic in itself; it is the place where you apply knowledge from across the three areas to one open-ended engineering problem and write it up. Understanding what the assignment rewards helps you see why the rest of the course is taught the way it is.

Where the assignment sits

The Higher Engineering Science award has two components: a question paper that tests knowledge and problem-solving across the three areas, and the assignment, which is project work completed during the course under controlled conditions and submitted to the SQA. The two combine to the final A-to-D grade. The assignment is where the abstract techniques become a real piece of engineering, so it draws on electronics, mechanisms and structures together rather than testing them in isolation.

The stages of the assignment

The assignment follows the same disciplined loop as the design process introduced earlier in this area:

1. Analyse the problem. Read the brief, identify the requirements the solution must meet, and break the problem into manageable parts (commonly input, process and output sub-systems, or the mechanical, structural and control elements).
2. Apply knowledge to produce a solution. Use course techniques to analyse, simulate or build the solution: calculate component values or member forces, design and simulate a circuit, model a mechanism, or construct and wire a prototype.
3. Test and record. Gather results from calculation, simulation or a built prototype, and record them clearly in tables, graphs or annotated diagrams.
4. Evaluate. Judge the solution against each requirement of the problem, explain any shortfall, and suggest specific improvements.

What makes a strong report

How to approach it

Treat the assignment as the design process in miniature. Pin down measurable requirements early so you have an objective standard to evaluate against. Break the problem into sub-systems so you can analyse or build each part and connect them at clear interfaces. Show your working: in engineering, the analysis and the results are the evidence, so calculations, simulation outputs and test data all earn credit. Finish with an evaluation that is specific and honest rather than a blanket "it worked", because the evaluation is where the higher marks live.

Examples in context

A typical assignment problem might be to design a control system for a model vehicle, a monitoring device, or a small structure that carries a load. Whatever the context, the same shape applies: analyse the requirements, split the problem into parts, apply electronics or mechanisms or structures knowledge to each, test against the requirements, and evaluate with justified improvements. Because the problem is open-ended, two candidates can take very different valid routes; the marks follow the quality of the analysis, the testing and the evaluation, not a single "right answer".

Try this

Q1. State the four broad stages of the assignment in order. [2 marks]

• Cue. Analyse the problem, apply knowledge to produce a solution, test and record results, evaluate against the requirements.

Q2. Give one feature of a strong evaluation. [1 mark]

• Cue. It compares results to the requirements with evidence and suggests specific, justified improvements (rather than just describing what was done).

Q3. Explain why the assignment draws on more than one area of the course. [2 marks]

• Cue. Real engineering problems are multidisciplinary, so integrating techniques from across areas demonstrates genuine problem-solving rather than isolated recall.