Skip to content

Unit 1 AoS2 Programming

This page maps the planning document for Unit 1 Area of Study 2 into grouped sections that suit a folio of programming exercises.

Why these sections are grouped this way

The planning document contains a lot of small knowledge points, but they do not all deserve their own standalone website section. For a folio-based assessment, the stronger approach is to group ideas that students naturally use together when building and refining short programs.

The grouping below is designed so that each section can support:

  • explicit theory notes
  • small worked examples
  • one or more folio exercises
  • a consistent page pattern like the Year 12 sister site

1. Responsible Programming and Code Quality

Combine:

  • emerging trends in programming languages
  • AI code generators
  • readability and maintainability
  • legal requirements, intellectual property and copyright

Why it works:

These ideas all shape how students think about writing code responsibly before they begin larger practical tasks.

2. Interpreting Requirements and Designing Solutions

Combine:

  • functional requirements
  • non-functional requirements
  • constraints
  • scope
  • design tools such as mock-ups, IPO charts, flowcharts and pseudocode

Why it works:

Requirements and design belong together because students should move directly from a case study into a planned solution before coding.

3. Programming Foundations: Data, Variables and Operators

Combine:

  • data types
  • variables
  • initialising, accessing and storing data
  • arithmetic, logical and conditional operators

Why it works:

These are the core building blocks of every folio task and should be established early in simple input-process-output programs.

4. Control Structures and Validation

Combine:

  • sequence, selection and iteration
  • existence checking
  • type checking
  • range checking

Why it works:

Validation makes the most sense once students are controlling program flow and handling user input.

5. Modular Programming, OOP Principles and Data Structures

Combine:

  • procedures, functions and methods
  • abstraction and encapsulation
  • one-dimensional arrays
  • lists
  • records

Why it works:

This section moves students from small single-step programs into larger, better-structured solutions that manage collections of data.

6. Testing, Debugging and Maintainability

Combine:

  • naming conventions
  • internal documentation
  • test tables and test data
  • breakpoints
  • debugging output statements

Why it works:

These practices all support refining code so that it is readable, testable and easier to maintain across the folio.

Section-to-Skill Mapping

Section Main Key Skills
1. Responsible Programming and Code Quality Interpret solution requirements in a responsible and legal context
2. Interpreting Requirements and Designing Solutions Interpret solution requirements; select and use appropriate design tools
3. Programming Foundations Use a range of data types; develop a software solution using OOP language features
4. Control Structures and Validation Develop a software solution; design and apply suitable validation techniques
5. Modular Programming, OOP Principles and Data Structures Use appropriate data structures; develop a software solution using OOP features
6. Testing, Debugging and Maintainability Document the functioning of a solution; design and apply debugging and testing techniques

Suggested Page Pattern for Each Section

To stay consistent with the Year 12 reference site, each section can be expanded into:

  • overview
  • what you need to know
  • test your knowledge
  • practical examples
  • applied folio task
  • extras

Recommendation

Keep the six-section structure for now. It is broad enough to reduce clutter, but specific enough that each folio exercise still has a clear home.