VCE Software Development Unit 3 Student Timeline 2026
Overview
This page outlines the weekly learning program for VCE Software Development Unit 3, covering both Outcome 1: Programming and Outcome 2: Analysis & Design (SAT).
SAT-first mapping for Unit 3 AoS2
From Term 1 Week 10 onward, the AoS2 entries below are mapped directly to the SAT assessment blocks and Assessment Timeline. Each week is tied to the actual folio work that needs to be completed.
Term 1
| Week | Key Knowledge & Skills | Learning Activities | Assessment | Checklist |
|---|---|---|---|---|
| Week 1 (A) |
KK3.1.2 - characteristics of functional and non-functional requirements, constraints and scope KK3.1.4 - characteristics of data types, including: - text (character, string) - numeric (integer, floating point, date/time) - Boolean KK3.1.5 - characteristics of data structures, including: - one-dimensional arrays - two-dimensional arrays - records (varying data types, field index) |
- Students print and place SAT proposals into display folders - Students demonstrate progression in C# course - Review Test Your Knowledge questions from holiday HW - Explore Arrays, Lists and Records |
- | Data Types & Data Structures |
| Week 2 (B) |
KK3.1.8 - features of a programming language, including: - instructions and control structures (sequence, selection, iteration/repetition) - arithmetic, logical and conditional operators KK3.1.10 - validation techniques for data, including: - existence checking - type checking - range checking KK3.1.13 - types of errors, including: - syntax - logic - runtime (overflow, index out of range, type mismatch, divide by zero) |
- Sequence execution - Selection (IF...ELSE, SWITCH/CASE) - Iteration (FOR, WHILE, REPEAT...UNTIL) - Arithmetic operators (+, -, *, /, //, %, **) - Logical operators (AND, OR, NOT) - Conditional operators (<, <=, >, >=, ==, !=) |
- | Control Functions, Validation & Errors |
| Week 3 (A) School Photos |
KK3.1.9 - purposes and features of naming conventions for solution elements (variables, interface controls, code structures), including: - Hungarian notation - camel casing - snake casing KK3.1.11 - purposes of internal documentation, including: - explaining and justifying data and code structures - code maintenance - placeholder comments for future development (stubs) KK3.1.14 - debugging and testing techniques for checking modules function correctly |
- Variable declaration and naming conventions - Internal documentation basics - Debugging Statements, Test Data and Testing Tables |
- | Naming, Documentation & Testing |
| Week 4 (B) Ash Wednesday |
KK3.1.2 - characteristics of functional and non-functional requirements, constraints and scope KK3.1.3 - design tools for representing modules, including: - data dictionaries - mock-ups - object descriptions - IPO charts - pseudocode Review of all KK and KS points so far as relevant to upcoming SAC |
- Analyze sample requirements - Identify constraints in scenarios - Define scope for practice problems - Apply all KK and KS to software solutions as will be applicable to upcoming SAC |
U3 Outcome 1 SAC - Coding Module 1 (of 4) 2x class periods this week |
Solution Requirements Design Tools for Modules |
| Week 5 (A) Yr 12 Group photo |
KK3.1.6 - characteristics of data sources (plain text (TXT), delimited (CSV) and XML files), including: - Structure - Reasons for use |
- File operations (open, close, read, write) - Plain text file structure - CSV file format and delimiters - XML elements, attributes, and structure - Parsing file data |
- | Data Sources: TXT, CSV & XML |
| Week 6 (B) Swimming carnival |
KK3.1.12 - algorithms for sorting and searching, including: - selection sort - quick sort - binary search - linear search |
- C# implementations of sorting and searching algorithms - Exam pseudocode implementations of sorting and searching algorithms |
U3 Outcome 1 SAC - Coding Module 2 (of 4) 2x class periods this week |
Searching & Sorting Algorithms |
| Week 7 (A) Labour Day holiday |
3.1.7 - principles of OOP, including: - abstraction - encapsulation - generalisation - inheritance 3.1.8 - features of a programming language, including: - local and global variables, and constants - data types - instructions and control structures (sequence, selection, iteration/repetition) - arithmetic, logical and conditional operators - graphical user interfaces (GUIs) - functions and methods - classes and objects |
- C# implementations of sorting and searching algorithms - Exam pseudocode implementations of sorting and searching algorithms - C# implementations GUI systems with existing Console Application programs - C# implementations of functions, methods, classes and objects |
- |
Variables, Functions & Classes OOP Principles |
| Week 8 (B) Pupil free day |
3.1.7 - principles of OOP, including: - abstraction - encapsulation - generalisation - inheritance 3.1.8 - features of a programming language, including: - local and global variables, and constants - data types - instructions and control structures (sequence, selection, iteration/repetition) - arithmetic, logical and conditional operators - graphical user interfaces (GUIs) - functions and methods - classes and objects |
- C# implementations GUI systems with existing Console Application programs - C# implementations of functions, methods, classes and objects |
U3 Outcome 1 SAC - Coding Module 3 (of 4) 3x class periods this week |
Variables, Functions & Classes OOP Principles |
| Week 9 (A) | U3O1 SAC Task - Module 4 | U3O1 SAC Task - Module 4 |
U3 Outcome 1 SAC - Coding Module 4 (of 4) All class periods this week (total 12 periods) |
- |
| Week 10 (B) Good Friday (end of term) |
SAT Block 1 launch: problem, need or opportunity + brief + proposed Gantt chart Key focus: - confirm a feasible SAT idea with teacher approval - define the client and intended users - begin the written brief - begin the proposed Gantt chart for Unit 3 Outcome 2 and Unit 4 Outcome 1 - consider privacy, ownership and data-collection implications from the start |
- Confirm the real-world problem, need or opportunity in consultation with the teacher - Identify the intended users / client and explain why a software solution is needed - Start the brief using the SAT template structure - Start the proposed Gantt chart with analysis, design, development and evaluation stages, tasks, order, dependencies, milestones and the critical path - Set up an evidence trail for later authentication |
Block 1 observation Brief and proposed Gantt chart started in class |
SAT Idea Approval Solution Brief & Project Plan Solution Brief Template Assessment Timeline Block Checklists |
Term 2
Unit 3 AoS2 is driven by the SAT checkpoints
The weeks below follow the SAT Assessment Timeline directly. Each block is cumulative, so earlier folio pieces stay active while later ones are developed.
| Week | SAT Checkpoint | Tasks to complete this week | Assessment / Authentication | Links and templates |
|---|---|---|---|---|
| Term 1 Break | Block 1 catch-up if needed |
- Tighten the brief and proposed Gantt chart if anything is incomplete - Make sure the client, intended users and proposed programming language are clear - Bring any missing approval notes, client responses or planning evidence back for Week 1 |
- |
Assessment Timeline Block Checklists Solution Brief & Project Plan |
| Week 1 (A) Practice GAT (Mon), Retreat (Thu/Fri) |
Block 1 submission Brief + proposed Gantt chart Block 2 setup Data-collection planning |
- Finalise and submit the brief - Finalise and submit the proposed Gantt chart covering Unit 3 Outcome 2 and Unit 4 Outcome 1 - Check that the Gantt chart includes tasks, order, time allocation, dependencies, milestones and the critical path - Choose the data-collection methods you will actually use for Block 2 - Prepare interview questions, survey prompts, observation focus points or report sources |
Block 1 submission Brief + proposed Gantt chart Authentication checkpoint |
Solution Brief & Project Plan Solution Brief Template Data Collection Data-Collection Evidence Template Block 1 Checklist |
| Week 2 (B) |
Block 2 observation Analysis documentation underway |
- Carry out the actual data collection and save the evidence you gather - Record interview notes, survey responses, observation notes or report extracts clearly - Draft the context diagram, data flow diagram and use case diagram from the collected evidence - Check that the analytical tools are consistent with each other and with the existing process / system being analysed |
SAT authentication session Block 2 observation Teacher progress check and admin-record update |
Analysis Overview Data Collection Analytical Tools Data-Collection Evidence Template Block 2 Checklist |
| Week 3 (A) |
Block 2 submission Analysis package completed Block 3 setup SRS drafting begins |
- Finalise and submit the data-collection evidence package - Finalise and submit the context diagram, data flow diagram and use case diagram - Extract user characteristics, technical environment, requirements, constraints and scope from the evidence - Set up the software requirements specification with the correct formal sections and headings |
Block 2 submission Data-collection evidence + 3 analytical tools |
Analytical Tools Software Requirements Specification SRS Template Block 2 and 3 Checklists |
| Week 4 (B) |
Block 3 observation SRS draft in progress |
- Draft the formal SRS with cover page, version, table of contents, numbered headings and page numbers - Write the problem, need or opportunity section, user characteristics and technical environment - Write the functional requirements, non-functional requirements, constraints and scope - Insert the analytical tools and organise appendices / supporting evidence for the final SRS |
SAT authentication session Block 3 observation Teacher progress check and admin-record update |
Software Requirements Specification SRS Template Block 3 Checklist |
| Week 5 (A) Student free day |
Block 3 submission SRS completed Block 4 observation Design ideas + evaluation criteria begin |
- Finalise and submit the SRS - Generate two to three genuinely different design ideas that respond to the same SRS - Draft the evaluation criteria table as questions - Record initial evaluation results for each design idea - Start identifying the likely preferred design for the detailed-design stage |
SAT authentication session Block 3 submission Block 4 observation |
Design Overview Design Ideas & Evaluation Criteria Design Ideas and Evaluation Template Block 3 and 4 Checklists |
| Week 6 (B) |
Block 4 submission Design ideas + evaluation criteria completed Block 5 observation Detailed designs begin |
- Finalise and submit the design ideas, evaluation criteria table and recorded design evaluations - Select and justify the preferred design - Start the detailed design package for that preferred design - Begin the data dictionary, object descriptions, mock-ups, IPO charts and pseudocode - Check that the detailed designs stay consistent with the SRS and analytical tools |
SAT authentication session Block 4 submission Block 5 observation |
Design Ideas & Evaluation Criteria Detailed Designs Detailed Design Package Template Block 4 and 5 Checklists |
| Week 7 (A) Last week Unit 1 & 3 |
Block 5 submission Detailed design package completed Unit 3 Outcome 2 SAT submission Criteria 1-5 packaged and submitted |
- Finalise every detailed design component: data dictionary, object descriptions, mock-ups, IPO charts and pseudocode - Check that the preferred design, SRS and analytical tools all align - Complete a final quality-control pass across Criteria 1-5 - Keep editable copies of the Gantt chart, evaluation criteria and detailed design package ready for Unit 4 Outcome 1 - Submit the full Unit 3 Outcome 2 folio as required |
SAT authentication session Block 5 submission Unit 3 Outcome 2 SAT Submission |
Detailed Designs Detailed Design Package Template Block 5 Checklist SAT Overview |
| Week 8 (B) King's Birthday, Unit 2 & 4 starts |
Transition into Unit 4 Outcome 1 |
- Carry the editable Gantt chart, evaluation criteria and detailed design package into Unit 4 - Prepare to develop directly from the preferred design and detailed-design package |
- |
Unit 4 Overview Development Requirements |
| Week 9 (A) GAT |
No new Unit 3 AoS2 checkpoint | - Keep SAT folio files organised, backed up and ready for Unit 4 development work | - | Unit 4 Overview |
| Week 10 (B) End of term |
No new Unit 3 AoS2 checkpoint | - Review any returned feedback and make sure your Unit 4 working documents are ready to use | - | Unit 4 Overview |
Need Help?
If you have questions about the learning program or need clarification on any topics, please speak with your teacher during class time.