SAC Task Materials

This page gives a public summary of the Unit 3 Outcome 1 school-assessed coursework focus areas.

The exact VCAA performance descriptors and grading language are not republished on this public site. Use the official VCAA document for the current wording, score bands and descriptor detail.

Open the official VCAA Unit 3 Outcome 1 performance descriptors (DOCX)

Outcome Focus

Unit 3 Outcome 1 assesses whether a student can interpret teacher-provided solution requirements and designs, then use appropriate features of an object-oriented programming language to develop working software modules.

Summary of the Assessed Areas

1. Interpreting requirements and designs

Students need to read and apply the teacher-provided requirements and design material accurately. Stronger work shows a clear understanding of both functional and non-functional requirements and uses design tools such as mock-ups, data dictionaries, IPO charts, pseudocode and object descriptions effectively during development.

2. Using data types, data structures and data sources

Students are expected to choose suitable data types and data structures for the problem and use appropriate data sources where required. Stronger work explains and justifies why particular variables, arrays, records and data files were selected.

3. Using OOP language features to build working modules

Students need to develop working software modules using appropriate object-oriented programming features. This includes selecting suitable control structures, variables, methods, algorithms, classes, objects and graphical user interfaces where required, then documenting why those features were used.

4. Applying naming conventions and validation

Students should apply clear and consistent naming conventions across solution elements and validate relevant input data properly. Stronger work uses suitable naming throughout the solution and applies complete validation, including checks for existence, type, range and reasonableness where appropriate.

5. Using internal documentation

Students are expected to document how modules function and explain the role of data, code structures and major solution elements. Stronger work uses clear internal documentation to justify design and implementation decisions and to support ongoing maintenance and future development.

6. Debugging and testing with suitable test data

Students need to demonstrate structured testing and debugging of their software modules. Stronger work includes complete testing tables, expected and actual output, evidence of debugging, documented fixes for failed tests and software modules that function correctly.

How to Use the Official Descriptors

1. Use the VCAA document for the exact descriptor wording and score ranges.
2. Use this page as a quick summary of what each assessment area is looking for.
3. Match your code, internal documentation and testing evidence to the language used in the official descriptors.