Skip to content
Engineering · Year 12

Active learning ideas

Case Studies in Engineering Failures

Data Exchange and APIs (Application Programming Interfaces) are the 'connective tissue' of the modern internet. In this topic, students explore how different software systems communicate by sending and receiving data in standardised formats like JSON and XML. This is a vital skill for Year 12 students as they move toward building integrated solutions that use external data sources, such as weather updates or social media feeds.

ACARA Content DescriptionsACENG12-07ACENG12-08
20–50 minPairs → Whole Class3 activities

Activity 01

Simulation Game30 min · Pairs

Simulation Game: The Human API

One student acts as the 'Client' and another as the 'Server'. The client sends a 'GET request' on a slip of paper; the server must find the requested 'JSON data' in a folder and return it in the correct format or send a 404 error code.

What were the root causes of historical engineering failures like the West Gate Bridge collapse?
ApplyAnalyzeEvaluateCreateSocial AwarenessDecision-Making
Generate Complete Lesson

Activity 02

Inquiry Circle50 min · Small Groups

Inquiry Circle: API Treasure Hunt

In small groups, students use tools like Postman or a browser console to explore public APIs (e.g., OpenWeather or the Australian Bureau of Statistics). They must find specific data points and explain the structure of the JSON response to the class.

How does society respond to catastrophic engineering errors?
AnalyzeEvaluateCreateSelf-ManagementSelf-Awareness
Generate Complete Lesson

Activity 03

Think-Pair-Share20 min · Pairs

Think-Pair-Share: JSON vs. XML

Students are given the same dataset in both JSON and XML formats. They must identify the pros and cons of each for a mobile app project, focusing on readability, file size, and ease of parsing.

In what ways do failures inform current engineering standards?
UnderstandApplyAnalyzeSelf-AwarenessRelationship Skills
Generate Complete Lesson

A few notes on teaching this unit


Watch Out for These Misconceptions

  • An API is a database.

    An API is a messenger that requests data from a server; it doesn't store the data itself. Using a 'restaurant' analogy (API as the waiter, database as the kitchen) in a role-play helps clarify this distinction.

  • JSON is a programming language.

    JSON is a data format, not a language. Having students manually write a JSON object to represent a 'Student' helps them see it as a structured way to organise information that many languages can read.


Methods used in this brief