SACE Stage 2 Digital Technologies study materials
SACE Stage 2 Digital Technologies study resources

SACE Stage 2 Digital Technologies study plan

SACE Stage 2 Digital Technologies · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Computational thinking

  • Decompose three unfamiliar problems into sub-problems and write the decomposition for each

  • Trace simple algorithms by hand, recording variable state after every step, for at least five short programs

  • Identify and name the control structures (sequence, selection, iteration) used in ten given code fragments

  • Explain in writing how abstraction and pattern recognition reduce a problem's complexity, using one worked example

Your checkpoint

A 4-page problem-decomposition workbook containing three decomposed problems, five completed trace tables, and a labelled control-structure inventory of ten fragments

Week 2

Computational thinking

  • Construct flowcharts or pseudocode for four algorithms, including one nested-selection and one nested-iteration case

  • Compare linear search with binary search by counting comparisons on a sorted list of 16 items

  • Write and hand-test a sorting routine on a 10-item list, recording each pass

  • Distinguish between algorithm correctness and efficiency and justify a choice between two candidate solutions

Your checkpoint

An algorithm portfolio with four pseudocode/flowchart solutions, a comparisons table for linear vs binary search, and a one-page written justification of efficiency choices

Week 3

Design and development

  • Write a requirements specification for a small application, separating functional from non-functional requirements

  • Produce user stories with acceptance criteria for at least six features

  • Draw a structure chart or module diagram that maps each requirement to a component

  • Select and justify a development approach (iterative vs waterfall-style) for the specified application

Your checkpoint

A requirements and design document: 10+ numbered requirements, six user stories with acceptance criteria, one module diagram, and a 200-word approach justification

Week 4

Design and development & Computational thinking

  • Implement a working prototype that satisfies at least four of the specified requirements

  • Apply defensive programming: validate inputs and handle at least three error conditions

  • Refactor one module to remove duplication and record what changed and why

  • Peer-review another solution against a checklist and log three actionable findings

Your checkpoint

A functioning prototype with a version-controlled change log, plus a completed peer-review checklist with three logged improvements

Week 5

Data and information

  • Design a normalised (to third normal form) relational schema for a described scenario

  • Write SQL queries using SELECT, WHERE, JOIN, GROUP BY and aggregate functions to answer five set questions

  • Distinguish between data, information and knowledge using three examples from your own project

  • Identify at least four data-quality issues (accuracy, completeness, timeliness, consistency) in a supplied sample dataset

Your checkpoint

A database workbook containing an ER diagram, normalised schema, five tested SQL queries with outputs, and a data-quality audit table of four issues

Week 6

Data and information & Digital systems and impacts

  • Collect and clean a small dataset, documenting each transformation step

  • Create two visualisations that answer a stated question and critique each for misleading design

  • Explain how encryption, authentication and access control protect stored data

  • Evaluate one legal or ethical obligation (privacy, intellectual property, or data minimisation) against your dataset handling

Your checkpoint

A data-handling report: cleaned dataset, two annotated visualisations, a security-measures summary, and a 250-word ethics/legality evaluation

Week 7

Digital systems and impacts

  • Describe the roles of hardware, operating systems, networks and protocols in a client-server interaction

  • Compare two network topologies or architectures against cost, reliability and performance criteria

  • Analyse two emerging technologies for benefits, risks and stakeholders affected

  • Explain the environmental and social impacts of one digital system using a lifecycle perspective

Your checkpoint

A two-page systems-and-impacts analysis covering one client-server walkthrough, a comparison table, and a stakeholder impact matrix for two technologies

Week 8

Computational thinking & Design and development & Data and information & Digital systems and impacts

  • Complete two full-length practice papers under timed conditions

  • Categorise every error by domain and root cause (knowledge gap vs misreading vs method)

  • Re-teach the three weakest sub-topics by writing summary notes and worked examples

  • Assemble a one-page formula/technique sheet for algorithms, SQL and design notation

Your checkpoint

A timed-practice results file with two scored papers, an error-categorisation table, three re-teach summaries, and a final one-page reference sheet

Milestones

Week 2: Can hand-trace an unfamiliar algorithm and justify an efficiency choice between two solutions without notes

Week 4: Prototype runs and meets at least four specified requirements; peer-review checklist completed

Week 6: Schema is in third normal form, all five SQL queries return correct results, and data-quality audit is complete

Week 8: Both timed papers scored and error table shows no domain below a self-set 70% threshold