The syllabus and course specifications
The documents the course and the HSC exam are written from. Start here.
Software Engineering 11–12 Syllabus (2022) (opens in a new tab)
NSW Curriculum · NESA
Rationale, aim, outcomes and course structure for Years 11 and 12.
Syllabus content: every focus area and dot point (opens in a new tab)
NSW Curriculum · NESA
The exact dot points these notes follow, part by part, for all seven focus areas.
HSC Course Specifications (opens in a new tab)
NESA
The pseudocode rules, flowchart and DFD symbols, structure charts and code conventions used in HSC questions.
Syllabus glossary (opens in a new tab)
NSW Curriculum · NESA
NESA's own definitions of the technical terms used in the syllabus.
Record of changes to the syllabus (opens in a new tab)
NSW Curriculum · NESA
Every official update, including changes to the course specifications examples.
Assessment and the HSC exam
The facts students and teachers need, each with its NESA source. Where NESA publishes nothing, this page says so.
School-based assessment
| Components and weightings | In both years two components are mandatory: knowledge and understanding of course content (50%) and knowledge and skills in the practical application of the content (50%).Source: School-based assessment (opens in a new tab) |
|---|---|
| Number and type of tasks | Schools decide the number, type and weighting of assessment tasks, subject to a limit of one take-home task worth no more than 15%. NESA does not fix a number of tasks.Source: School-based assessment (opens in a new tab) |
| NESA guidance (not mandatory) | Use a variety of tasks across the year, and give individual tasks a weighting between 10% and 40%.Source: School-based assessment (opens in a new tab) |
| Year 11 result | Schools submit a grade for each student at the end of the course, allocated by on-balance judgement using the Common Grade Scale for Preliminary courses.Source: School-based assessment (opens in a new tab) · Course standards (opens in a new tab) |
| Year 12 result | Schools submit a school-based assessment mark for each student, summing up achievement measured at several points through the course. Formal tasks should reflect the syllabus outcomes and content.Source: School-based assessment (opens in a new tab) |
| Notice and schedules | Students must get sufficient written notice of a task, typically 14 calendar days. The notice states the weighting, the syllabus outcomes assessed, the type of task, the date and time, and the marking criteria where appropriate. The school gives the formal assessment program, with schedules, at the start of the course.Source: ACE rules 2.1 (opens in a new tab) |
| Generative AI | Marks must reflect the student’s own knowledge, skills and understanding, not their use of generative AI. Schools decide whether generative AI is permitted in a task, and must not rely on software that detects generative AI to decide whether malpractice occurred.Source: ACE rules 2.1 (opens in a new tab) · ACE rules 10.1 (opens in a new tab) |
The HSC examination
| Format | One written examination, taken by students on a computer. It is worth 80 marks. The time allowed is 2 hours 30 minutes, including 10 minutes reading time.Source: HSC examinations (opens in a new tab) |
|---|---|
| Stimulus | Questions may contain stimulus material. Headphones are required for questions with video and audio stimulus.Source: HSC examinations (opens in a new tab) |
| Objective-response items | About 20 marks. There are 14 to 18 items, each worth 1 to 4 marks, and they may share stimulus with other items.Source: HSC examinations (opens in a new tab) |
| Short-answer items | About 60 marks. There are 16 to 18 items, and at least three are worth 4 to 8 marks. They may share stimulus with other items.Source: HSC examinations (opens in a new tab) |
| Sections | NESA describes two types of test item. It does not describe the paper as having sections.Source: HSC examinations (opens in a new tab) |
| Assumed knowledge | Questions may ask you to combine knowledge, understanding and skills from across the course. The Year 11 course is assumed knowledge for Year 12, and an understanding of the Python programming language is also assumed. The Course Specifications say students are expected to be able to code in Python.Source: HSC examinations (opens in a new tab) · Course Specifications (opens in a new tab) |
| Notation and depth | The Course Specifications are an integral part of the course content and indicate the depth of study required for some concepts. The syllabus must be applied in conjunction with them.Source: Course structure (opens in a new tab) · Course Specifications (opens in a new tab) |
| Online exam tools | The online exam has a code editor, a drawing tool and a screen design tool. NESA publishes a video and a transcript for each.Source: HSC examinations (opens in a new tab) |
| Practice material | NESA provides online familiarisation questions, with marking guidelines. An online sample exam is available to schools through Schools Online; only its marking guidelines are public.Source: HSC examinations (opens in a new tab) · Familiarisation questions (opens in a new tab) |
| Past papers | The 2025 exam is the only Software Engineering pack published. It has the online exam, marking guidelines, marker feedback by question and sample full-mark responses. NESA states there is no downloadable paper.Source: 2025 exam pack (opens in a new tab) · Exam papers index (opens in a new tab) |
| How answers are marked | Marking guidelines are based on criteria that relate to the quality of the response. Achievement is reported against the HSC Performance Band Descriptions for Software Engineering (Bands 1 to 6).Source: HSC examinations (opens in a new tab) · Course standards (opens in a new tab) |
| Marker advice (2025) | Read the question carefully, show you understand the key words and what the question requires, engage with any stimulus material, use course-specific terms, and practise the online tools with the familiarisation questions and past exams.Source: 2025 exam pack (opens in a new tab) |
| Exam provisions | Some students with disability may be eligible for HSC exam provisions.Source: Exam provisions (opens in a new tab) |
- No mandatory project task, project weighting, length limit or submission for Software Engineering. There is no HSC practical exam or submitted major work: the HSC is a single online written exam. Whether and how the project is assessed at school is the school’s decision within the rules above.
- No split between the school-based mark and the HSC examination mark appears on the Software Engineering pages, so this page does not state one.
- Sample assessment schedules and task notifications have headings but no files. NESA says they are being updated to align with the new ACE rules.
- No downloadable Software Engineering HSC paper. The Software Design and Development archive is for the earlier course.
- NESA’s cross-course glossary of key words is not linked from the Software Engineering pages. The syllabus glossary defines only evaluate and collaborate, so treat other command verbs as unofficial for this course.
Assessment documents, exam papers and the online exam
The official pages behind the facts above, and NESA’s own practice material. There is no downloadable Software Engineering paper: the exam is online.
Assessment: course standards (opens in a new tab)
NSW Curriculum · NESA
The Common Grade Scale (Year 11) and the HSC Performance Band Descriptions for Software Engineering.
School-based assessment (opens in a new tab)
NSW Curriculum · NESA
The mandatory components and weightings for Years 11 and 12, and the take-home task limit.
HSC examinations (opens in a new tab)
NSW Curriculum · NESA
The exam specification (80 marks, 2 hours 30 minutes, online), the exam tools and the sample exam materials.
ACE rules: assessment programs (2.1) (opens in a new tab)
NSW Curriculum · NESA
The rules for Preliminary and HSC school-based assessment programs, including take-home tasks and generative AI.
NESA 29/26: new limit on take-home assessment tasks (opens in a new tab)
NESA
The official notice of the one-task, 15% limit, which courses are exempt, and the start dates.
NESA 34/26: changes to the ACE rules (opens in a new tab)
NESA
The notice of the ACE rule changes on take-home tasks and artificial intelligence, with effect dates.
Software Engineering HSC exam papers (opens in a new tab)
NESA
The index of Software Engineering HSC exam packs. Only 2025 is listed.
Software Engineering 2025 HSC exam pack (opens in a new tab)
NESA
Links to the online exam, the marking guidelines, marker feedback by question and sample full-mark responses.
2025 HSC Software Engineering marking guidelines (opens in a new tab)
NESA
Criteria, marks and sample answers for every question of the 2025 exam, with the content and outcomes each question assesses.
2025 HSC sample full-mark responses (opens in a new tab)
NESA
Full-mark student responses to several 2025 questions: compare their depth with your own answers.
HSC online exam and familiarisation questions (opens in a new tab)
NESA
NESA’s online exam environment: practise with the code editor, drawing and screen design tools.
Marking guidelines: familiarisation questions (opens in a new tab)
NESA
Marking guidelines for the 14 HSC familiarisation questions.
Marking guidelines: online sample exam (opens in a new tab)
NESA
Marking guidelines for the online sample exam (schools reach the exam itself through Schools Online).
Online exam code editor: video transcript (opens in a new tab)
NESA
What the code editor does in the online exam.
Online exam drawing tool: video transcript (opens in a new tab)
NESA
What the drawing tool does in the online exam, used for diagrams such as class diagrams.
Online exam screen design tool: video transcript (opens in a new tab)
NESA
What the screen design tool does in the online exam.
HSC exam provisions (opens in a new tab)
NESA
Exam provisions for students with disability.
Planning and support materials
Sample programs NESA published alongside the syllabus.
Sample unit: Programming Fundamentals (opens in a new tab)
NESA
A full Year 11 unit: practical programming in context.
Sample unit: Software Engineering Project (opens in a new tab)
NESA
How the Year 12 major project can be planned and run.
Sample scope and sequence, Year 11 (opens in a new tab)
NESA
One way to order the Year 11 focus areas across 120 hours.
Sample scope and sequence, Year 12 (opens in a new tab)
NESA
One way to order the Year 12 focus areas across 120 hours.
Parent and carer guide (opens in a new tab)
NESA
A plain-language overview of the course for families.
Standards and official documentation behind the syllabus
Primary sources for concepts the syllabus names. These organisations are not NESA; each is the authority on its topic.
Python tutorial (opens in a new tab)
Python Software Foundation
The official tutorial for the language used across the course.
Learn web development (opens in a new tab)
MDN Web Docs (Mozilla)
HTML, CSS, JavaScript and HTTP from the reference browser makers use.
About the W3C (opens in a new tab)
World Wide Web Consortium
The organisation the syllabus asks you to explain the role of.
Web Content Accessibility Guidelines (WCAG) (opens in a new tab)
W3C
The accessibility standard behind designing for people with disability.
OWASP Top 10 (opens in a new tab)
OWASP Foundation
The most critical web application security risks, and how to prevent them.
Australian Privacy Principles (opens in a new tab)
Office of the Australian Information Commissioner
The law privacy by design has to satisfy in Australia.
Pro Git (opens in a new tab)
Git project
The official book on Git and version control.
SQL as understood by SQLite (opens in a new tab)
SQLite
The SQL reference for the database engine used with Python.
Arduino documentation (opens in a new tab)
Arduino
Official guides for the boards, sensors and actuators used in mechatronics.
Manifesto for Agile Software Development (opens in a new tab)
Agile Alliance authors
The four values and twelve principles behind Agile methods.