Programme / Coding

Write code that another person can read, test and improve.

Coding at BIAA is a way to model decisions, automate repeatable work and communicate precise instructions—not an exercise in memorising syntax.

A short readiness discussion should determine whether visual, mixed or text-based work is appropriate.
OPENQUESTION
01 / Question02 / Understand03 / Build04 / Verify
01
BIAA / FIT

Who this learning direction is for

Placement is based on readiness, prior experience and learning goals rather than age alone.

  • 01Beginners who want to understand how programs are constructed
  • 02Makers who need stronger code for robots, data or interactive projects
  • 03Prerequisite: Introductory work can begin without prior coding
  • 04Prerequisite: Text-based progression assumes comfort with variables, conditions and iteration
02
BIAA / QUESTIONS

Questions learners investigate

Each unit begins with a question that can be explored through observation, code, construction or evidence.

  • 01How can a large task be decomposed into testable parts?
  • 02What makes code predictable and understandable?
  • 03How does evidence help locate a bug?
03
BIAA / LEARNING

What learners practise

Technical knowledge is developed alongside planning, documentation, testing and explanation.

  • 01Sequence, selection, iteration and state
  • 02Functions, data structures and interfaces
  • 03Input validation and error handling
  • 04Testing, debugging and version history
  • 05Readable naming, comments and technical explanation
04
BIAA / OUTCOMES

What learners produce

The expected outcome is a documented learning artefact, not an unverified promise of awards or certification.

  • 01An interactive program, simulation or control module with a stated user or task
  • 02A small test suite or repeatable test checklist
  • 03A code walkthrough that explains choices and known limitations
05
BIAA / PROCESS

Learning process and assessment

Learners move through a repeatable cycle and receive feedback against visible criteria.

  • 01Describe expected behaviour before coding
  • 02Build the smallest working version
  • 03Test normal and edge cases
  • 04Refactor after the behaviour is understood
  • 05Assessment: The program meets stated behaviour
  • 06Assessment: Code structure supports reading and change
  • 07Assessment: Debugging notes show how evidence guided revision
06
BIAA / RESPONSIBILITY

Safety, ethics and the next step

Responsible making is part of the curriculum whenever tools, data, AI or autonomous systems are involved.

  • 01Personal data and credentials are excluded from learning repositories
  • 02External libraries and generated code are credited and reviewed
  • 03AI coding assistance does not replace learner explanation or testing
  • 04Next: Apply code in robotics, IoT, AI or a capstone
  • 05Next: Move from visual blocks to mixed and then text-based programming when ready
BIAA / PROGRAMME FRAMEWORK

What learners make visible

01

Who it is for

  • Beginners who want to understand how programs are constructed
  • Makers who need stronger code for robots, data or interactive projects
02

Starting point

  • Introductory work can begin without prior coding
  • Text-based progression assumes comfort with variables, conditions and iteration
03

Core questions

  • How can a large task be decomposed into testable parts?
  • What makes code predictable and understandable?
  • How does evidence help locate a bug?
04

What learners investigate

  • Sequence, selection, iteration and state
  • Functions, data structures and interfaces
  • Input validation and error handling
  • Testing, debugging and version history
  • Readable naming, comments and technical explanation
05

Project evidence

  • An interactive program, simulation or control module with a stated user or task
  • A small test suite or repeatable test checklist
  • A code walkthrough that explains choices and known limitations
06

Learning process

  • Describe expected behaviour before coding
  • Build the smallest working version
  • Test normal and edge cases
  • Refactor after the behaviour is understood
07

How progress is reviewed

  • The program meets stated behaviour
  • Code structure supports reading and change
  • Debugging notes show how evidence guided revision
08

Safety & ethics

  • Personal data and credentials are excluded from learning repositories
  • External libraries and generated code are credited and reviewed
  • AI coding assistance does not replace learner explanation or testing
09

Where this can lead

  • Apply code in robotics, IoT, AI or a capstone
  • Move from visual blocks to mixed and then text-based programming when ready

Questions to ask

Which programming language does BIAA use?

The content model is tool-agnostic. A language is selected for the task and learner readiness; confirmed delivery tools should be listed before enrolment.

Can AI write the code?

AI may be examined as an assistant, but learners remain responsible for understanding, testing and explaining submitted work.

BIAA / NEXT STEP

Choose a coding pathway

A short readiness discussion should determine whether visual, mixed or text-based work is appropriate.

Choose a coding pathway