SADT / PR / 01
Python for teens
A general-purpose language, from constructs to modules.
Open the syllabusSouth Australia · SACE Stage 2 · Live online
Stage 2 Digital Technologies asks a South Australian student to do what working developers do: pick a real problem, talk to a client, build something in stages and explain it on camera. Most of the marks sit with the school, and most of the stress comes from projects that grow faster than the time left to finish them.
Subject outline read at source · Your project stays your own work · Lessons on Adelaide time
In short
SACE Stage 2 Digital Technologies is a 20-credit subject (code 2DGT20) with four focus areas: computational thinking, design and programming, data analytics, and iterative project development. Project Skills counts 50 per cent and the Collaborative Project 20 per cent, both school assessed. The Individual Digital Solution, worth 30 per cent, is assessed externally.
Where to begin
Programming fluency first, then data, then the habits that keep a project on schedule.

SADT / 01
A general-purpose language written well, with selection, repetition and sequencing used deliberately rather than by accident.
Open the syllabus →
SADT / 02
Reading, cleaning and modelling data sets, the work at least one project skills task must contain.
Open the syllabus →
SADT / 03
A history of every change, which turns a walkthrough video into a story the student can actually prove.
Open the syllabus →Inside the subject outline
Everything here comes from the SACE Board Stage 2 Digital Technologies Subject Outline, read on 7 October 2026. The outline says students study all four focus areas, and that the areas are not intended to be taught independently.
| Focus area | What the outline emphasises | Where it shows up |
|---|---|---|
| 1. Computational thinking | Decomposition, pattern recognition, abstraction and algorithm design, with algorithms written in pseudocode or drawn as a structure chart or flow chart | Every task, and the algorithm design required in the individual solution |
| 2. Design and programming | Program design, pseudocode, simple constructs, array processing and modularisation in a general-purpose language, with comments that explain the code | Programming skills tasks and both digital solutions |
| 3. Data analytics | Collecting, extracting, interpreting and modelling data sets to identify trends and make predictions | At least one project skills task |
| 4. Iterative project development | Building a product, prototype or proof of concept in stages, following agile practices, with testing at each stage | The collaborative project and the individual solution |
The outline frames the subject around problems of interest to the student, and it repeats that phrase often enough to be a design principle. A student who chooses a problem they genuinely care about writes a stronger designer's statement, because the statement asks what makes the solution effective and what could count as innovative.
Programming is assessed in a general-purpose programming language. The outline does not prescribe one, so schools choose. Python is common in South Australian classrooms, and the skills transfer: arrays, functions, files and a little object-oriented design if the student wants to explore it.
Data analytics is the area students most often underestimate. The outline asks for simple and complex data sets, patterns and trends, conclusions and predictions, which is statistics done in code rather than in a spreadsheet alone.
The subject is also part of the SACE Board's subject renewal program. Its renewal page lists Digital Technologies as a group 3 subject working through the Develop phase in 2026, so details may change for later cohorts. Students should always use the outline their school gives them for their own year.
Sources: SACE Board, Digital Technologies overview (credits, codes and weightings); Stage 2 Digital Technologies Subject Outline (docx) linked from that page; subject renewal page. Read on 7 October 2026.
How the result is built
The outline asks for five to six assessments in total, including the external one. Each limit below is copied from the outline, because these limits shape how a project has to be planned.
| Assessment type | Weight | What the student submits | Limits |
|---|---|---|---|
| AT1 Project Skills (school) | 50 per cent | Three or four tasks applying computational thinking, data analysis, design and programming, and iterative development | Together a maximum of 20 minutes in multimodal form |
| AT2 Collaborative Project (school) | 20 per cent | An individual Project Solution Walkthrough and an individual Technical Walkthrough about a group solution built for a client | Up to 5 minutes and up to 3 minutes; recordings no more than 1GB |
| AT3 Individual Digital Solution (external) | 30 per cent | A solution or prototype with source code, design comments, algorithm design and a user interface or instructions, plus a designer's statement | Solution no more than 1 GB and 15 minutes; statement up to 3 minutes oral or 500 words written |
Inside Project Skills, the outline sets four floors: at least one task involves collaboration, at least one analyses data sets, at least one assesses programming skills, and in at least one the student discusses the ethics of data use or digital solutions. Teachers decide how those floors are met, which is why tasks differ between schools.
The Collaborative Project needs an identifiable client outside the student group, consulted throughout development. The group solution itself is presented and discussed but not submitted to the SACE Board. Each student's walkthroughs are what the teacher assesses.
The assessment design criteria have three groups. Computational thinking runs from CT1 to CT4, development and evaluation from DE1 to DE4, and research and ethics is RE1. The individual solution is assessed against CT1, CT2 and CT4, and DE1, DE2 and DE3.
Performance standards describe five levels of achievement, A to E. The outline also expects a broad definition of collaboration: face to face or online, with students, teachers, relatives or community members.
Weights, limits and criteria: Stage 2 Digital Technologies Subject Outline, sections on evidence of learning, assessment design criteria and the three assessment types, read on 7 October 2026. External assessment summary: SACE Board, Digital Technologies external assessment.
A worked lesson
Iterative development only works if the first version is small enough to finish. MoSCoW is a common way to sort a client's wish list into Must have, Should have, Could have and Won't have this time. The client, requirements and hour estimates below are invented for teaching; the arithmetic is ours.
A canteen manager wants students to pre-order lunch. The group has about 36 working hours left before walkthroughs are due, shared across the team.
Ten requirements arrive in the first meeting. Every one sounds reasonable, and together they need 41 hours, which is more than the group has.
Sorting by MoSCoW keeps 34 hours of work, leaves a 2 hour buffer for testing, and tells the client plainly what waits for a later version.
| Priority | Requirement | Estimate | Kept in version 1? |
|---|---|---|---|
| Must | Show today's menu | 4 | Yes |
| Must | Order form with input validation | 6 | Yes |
| Must | Order list for canteen staff | 5 | Yes |
| Must | Save orders to a file between sessions | 5 | Yes |
| Should | Search the menu | 3 | Yes |
| Should | Filter out items with a chosen allergen | 5 | Yes |
| Should | Daily totals for the kitchen | 4 | Yes |
| Could | Colour themes | 2 | Yes, fits the time left |
| Could | Order history for each student | 7 | No, deferred |
| Won't (this time) | Online payment | Not estimated | No, out of scope |
| Iteration | Contents | Hours | What the client sees afterwards |
|---|---|---|---|
| 1 | Menu display and order form | 10 | A working form that rejects a blank name or a quantity of zero |
| 2 | Staff order list and saving to file | 10 | Orders that survive closing the program |
| 3 | Search, allergen filter, daily totals | 12 | The features that make it useful at 12.30 pm |
| 4 | Colour themes, then testing and fixes | 4 | A tested version and a list of what comes next |
The four Musts add to 20 hours and the three Shoulds to 12, so together they use 32 of the 36 hours. Of the two Coulds, only the 2 hour colour themes fit, leaving 2 hours of buffer. The 7 hour order history is deferred, and online payment is ruled out for this version because it raises security and privacy questions the group cannot answer properly in the time available.
Writing the Won't list down matters as much as the Must list. It is evidence of client consultation, it stops scope creep in week four, and it gives every student something honest to say in a Project Solution Walkthrough about decisions and trade-offs.
The same habit protects the individual solution. A student working alone has no teammates to absorb an overrun, and the outline caps the submission at 15 minutes and 1 GB. A solution with three finished features beats one with seven half-built ones, both for the student and for an external assessor watching a walkthrough.
In lessons we practise the sorting on invented briefs, then ask the student to defend each priority aloud, as a client would challenge it. That rehearses the explanation without anyone touching the student's real project.
MoSCoW is a general prioritisation technique; the outline itself asks for iterative development, client consultation and evaluation. The project, requirements, estimates and plan are invented for teaching and checked by our own arithmetic on 7 October 2026.
The external 30 per cent
The outline lists what the solution or prototype should include, and the integrity rule that applies to everything a student submits. Both are quoted or closely paraphrased from the outline below.
| Element | What the outline asks for |
|---|---|
| Code | Original source code and/or adapted code displaying selection, repetition, and sequencing, accompanied by design comments |
| Design | Algorithm design |
| Use | A graphical user interface and/or instructions for use |
| Statement | A designer's statement discussing the effectiveness of the solution and a feature or features that could be considered innovative |
| Size and length | No more than 1 GB, with a maximum time limit of 15 minutes; the statement up to 3 minutes oral or 500 words written |
| Starting point | May build on an aspect of a problem from AT1 or AT2, but must be the student's own independent work |
The SACE Board states that, to ensure academic integrity, assessment must be based on the work students have produced without undue assistance from other people or sources. We take that literally. We teach selection, repetition and sequencing, design comments, algorithm notation and evaluation with problems we invent, and we never write, debug or review a student's assessed code, recordings or statement.
Source: Stage 2 Digital Technologies Subject Outline, Assessment Type 3; integrity wording from the SACE Board school assessment page, read on 7 October 2026.
Getting ready for Stage 2
Most students start the subject able to code a little. The gap is usually design and finishing, not syntax.
| When | Rung | The sign it is secure |
|---|---|---|
| Year 10 | 1. Constructs | Writes loops and conditions that work first time on small problems |
| Stage 1 | 2. Structure | Splits a program into functions and explains what each one is for |
| Early Stage 2 | 3. Data | Loads a data set, cleans it and states one trend it shows |
| Later Stage 2 | 4. Iteration | Ships a small version, gathers feedback and plans the next one |
Short daily practice beats long weekend sessions. A small problem solved and explained every day builds the fluency that a programming skills task assumes.
Reading other people's code aloud, line by line, is the fastest way to learn what clean code looks like.
Plan in iterations and protect the Musts. Our understand the code, don't copy-paste page explains why every line in a solution must be one the student can explain.
Students in other states can compare with HSC Software Engineering in New South Wales.
The catalogue
Grouped by focus area. Every card opens a full syllabus.
SADT / PR / 01
A general-purpose language, from constructs to modules.
Open the syllabusSADT / PR / 02
Object-oriented design for students who want to explore it.
Open the syllabusSADT / PR / 03
Algorithm design under time pressure.
Open the syllabusSADT / DA / 01
Trends and predictions from real data sets.
Open the syllabusSADT / DA / 02
The statistics behind honest conclusions.
Open the syllabusSADT / DA / 03
Models trained on data, for students heading that way.
Open the syllabusSADT / BU / 01
Every change recorded and explainable.
Open the syllabusSADT / BU / 02
User interfaces that a client can try.
Open the syllabusSADT / BU / 03
Web solutions with a front end and stored data.
Open the syllabusHow lessons run
Lessons are live and come from our tutors in India. Adelaide runs four hours ahead of India time in winter and five hours ahead once daylight saving starts on 4 October 2026, until 4 April 2027, according to the IANA time zone database. A 5 pm lesson in Adelaide in summer is noon India time, within our working day.
Weekday after school
Weekly programming and design practice.
Weekend morning
Longer sessions on data and algorithms.
School holidays
Short intensive blocks on one skill.
Every project we work on in class is made up, never the assessed one.
Students talk through code the way a walkthrough requires.
Pseudocode or a structure chart before the editor opens.
Fifteen to twenty students at one level, reviewing each other's practice code.
For one skill, such as data cleaning, that needs focused repair.
We never predict a SACE grade; the work and the result belong to the student.
Student work
Projects students made outside school, never assessed work. More in our student labs.

AI and ML
An AI nutrition coach that reads what you eat and works you toward a target.

AI and ML
A chatbot that answers mathematics and programming questions, built and deployed by a student.

AI and ML
An assistant that helps a young person recognise unsafe situations online.

Web app
A weather forecasting site with live conditions for any location.
Fees
Lessons are billed monthly in US dollars, one rate for every family outside India, with no joining fee and nothing owed beyond the month in progress.
Free first class
USD 0
no card required
Group batch
USD 100
a month, billed in US dollars
One to one
USD 150
a month, billed in US dollars
What families say
Reviews copied exactly as families and students wrote them on Google.
★★★★★
"The one step solution for my son. Modern Age Coders make learning coding so simple that kids love it. The teachers explain complex concepts clearly with practical exercises and interactive content."
Ria Mukherjee
Parent
★★★★★
"Modern Age Coders has been a game-changer for me. I struggled to grasp IT concepts and coding before joining, but their classes transformed everything. I can now confidently write complex programs with ease."
Samriddha Mondal
Student
★★★★★
"One of the most wonderful education centres out there. Education is not limited to school syllabus but focuses on skill development."
Vansh Agarwal
Student
★★★★★
"My child Dhairya is really enjoying the Modern Age Coders classes. This is his first online class and he eagerly looks forward to it. I can already see his improvement, and the teachers are very cooperative."
Sonam Oswal
Parent of Dhairya
★★★★★
"Modern Age Coders have wonderful teachers who teach in a clear, easy and practical way. The teacher boosts students' confidence and inspires them to learn without hesitation."
Sonu Goyal
Parent
★★★★★
"I highly recommend this computer coding class! The teachers are incredibly knowledgeable and passionate about coding."
Ritu Kedia
Parent
Questions about Stage 2
It is a 20-credit Stage 2 subject, code 2DGT20, in which students solve problems of interest through computational thinking, design and programming, data analytics and iterative project development. School assessment counts 70 per cent and external assessment 30 per cent.
Project Skills (50 per cent, three or four tasks), the Collaborative Project (20 per cent, assessed through individual walkthroughs) and the Individual Digital Solution (30 per cent, assessed externally).
The outline sets the Project Solution Walkthrough at up to 5 minutes and the Technical Walkthrough at up to 3 minutes, with recordings no larger than 1GB.
Source code showing selection, repetition and sequencing with design comments, algorithm design, a graphical user interface or instructions for use, and a designer's statement of up to 3 minutes oral or 500 words written. The solution may be no more than 1 GB and 15 minutes.
The outline asks for a general-purpose programming language without naming one, so schools decide. We teach Python by default and Java for students whose school uses it.
A way of sorting requirements into Must have, Should have, Could have and Won't have this time, so the first version of a product is small enough to finish and the client knows what is deferred.
The SACE Board lists it as a group 3 subject in its subject renewal program, working through the Develop phase in 2026. Always follow the outline your school provides for your year.
We teach the skills with invented projects. We never write, debug or review your assessed code, recordings or designer's statement, because the SACE Board requires assessed work to be produced without undue assistance.
It helps a great deal. Students who can already write loops, conditions and functions spend Stage 2 learning design and data rather than syntax.
Late afternoon in Adelaide suits most students and falls within our tutors' day. The weekly time is agreed after the free lesson.
Related pages
The SACE maths subjects that pair with computing, and the wider picture across Australia.
Calculus and statistics for Stage 2.
Vectors, complex numbers and proof.
How senior computing differs between states.
The New South Wales computing course for comparison.
Coding competitions through the school year.
Our national hub, from first blocks to AI.
Start here
Tell us your stage, the language your school uses, and whether programming, data or finishing is the hard part. The free lesson works on that skill with a problem we invent.
Before booking, browse every syllabus in the course atlas, read about the lesson method on how we teach, or see our other Australian pages.
WhatsApp us · +91 91233 66161 · connect@modernagecoders.com
We reply to WhatsApp messages first. The number begins +91 because our school is in India; we have no office in South Australia or anywhere else in Australia.
A priority demo is a full class of about 45 to 60 minutes. After the class the mentor sends a written skill report and a personal learning roadmap on WhatsApp. If you enrol, the demo fee is adjusted against your first month's fee. Share your demo Order ID with us on WhatsApp and we take it off.
Book a priority demo