Engineering Systems
A single traffic light blinks out, and suddenly cars back up for miles in every direction. The problem started at one corner, but the whole city feels it.
What You'll Be Able to Do
By the end of this lesson, you will be able to:
- State what students will be able to do.
- Set a clear target before content begins.
- Goal setting
- Advance organizers
- Understand to Analyze
- DOK 1 to 3
- Plain "I can" statements
- Standard code shown for reference
- Short, scannable cards
Words You'll Meet
Choose a card to see what each word means.
- Front-load the terms students will meet.
- Lower the language barrier before reading.
- Pre-teaching vocabulary
- Reduced extraneous load
- Remember to Understand
- DOK 1
- One card open at a time
- Click to reveal, no hover
- Plain, short definitions
One Light, A Whole City
A traffic light is one small device on one street corner. Yet when it stops working at rush hour, the trouble does not stay at that corner. It spreads.
The Ripple From One Corner
A power surge knocks out a single traffic light downtown. Cars that used to flow through now pile up. The backup spills onto the next street, then the next. Buses fall behind schedule. A delivery truck misses its drop-off. Across town, someone is late to work because of a light they never even passed. How can one broken part cause problems so far away from where it failed?
The best answer is B. A city is not a pile of separate streets. It is a system of connected parts. Each intersection passes traffic to the next, so the parts depend on one another. When one part fails, the effect travels along those connections. To understand why failures spread, we have to look at how the parts of a system interact. That is exactly where this lesson goes next.
- Anchor the unit in a real phenomenon: a failure that spreads.
- Raise a question students will want answered.
- Curiosity gap
- Phenomenon-based learning
- Understand
- DOK 2
- Concrete, familiar example
- Short framing text
- Visual anchor
More Than a Pile of Parts
Before we can explain why failures spread, we need a clear idea of what a system is. The word gets used a lot, but it has a precise meaning in engineering.
A pile of bicycle parts on the floor is not a bicycle. The frame, wheels, chain, and pedals only become a bicycle when they are connected so they work together. That connection is what makes a system.
A system is a group of parts that work together to do something. The parts depend on one another, so what happens to one part can change the others.
A system is a set of connected parts that work together toward a purpose. The key word is connected. A bicycle, a cell phone, a school, an ecosystem, and a city's transportation network are all systems because their parts interact instead of acting alone.
Systems are everywhere. Some are machines, some are living, and some are made of people and rules. They all share one trait: connected parts working together.
- Define system before naming its parts.
- Establish "connected parts" as the core idea.
- Prior knowledge activation (bicycle parts)
- Concept formation with varied examples
- Understand
- DOK 1 to 2
- Everyday analogy (pile of parts)
- Wide range of familiar examples
- One plain test for the concept
The Parts of a System
Engineers describe a system by breaking it into its components. Most systems share the same kinds of parts. Click a component to see what it does, using the traffic intersection as our example.
- Name the common components of a system.
- Tie each part to one running example.
- Dual coding with the interactive diagram
- Worked example (one system throughout)
- Chunking the parts
- Remember to Understand
- DOK 1 to 2
- Click to reveal each part, no hover
- Labeled diagram paired with text
- One example carried throughout
How the Parts Connect
Knowing the parts is only half the picture. The reason a system behaves like a whole, and not a pile, is that its components interact.
On a bicycle, pushing the pedals turns the chain, the chain turns the rear wheel, and the wheel moves the bike forward. Each part passes its effect to the next. That passing along is an interaction.
Because parts interact, a change in one component does not stay put. It travels through the connections to the parts it touches.
An interaction is the way one component affects another. Interactions are the connections that turn separate parts into a working system. Trace the interactions and you can predict how the whole system will behave.
The same idea shows up across very different systems. In each case, one part is affecting another.
- Shift focus from parts to the connections between them.
- Set up why failures spread.
- Cause-and-effect reasoning
- Transfer across multiple examples
- Understand to Analyze
- DOK 2
- Concrete bicycle analogy
- Parallel example chips
- Direct link back to the phenomenon
Mapping a System
Systems can be large and tangled. To study one without getting lost, engineers build a model. A model is a simplified stand-in that shows the parts and how they connect.
You cannot hold an entire city's traffic in your head at once. A model lets you leave out the details that do not matter and keep the parts and connections that do. With a clear model, you can describe how a system is built and predict how it will behave.
A good model answers two questions: what are the parts, and how do they interact? The diagram of input, process, output, and feedback you used earlier was a model.
A model is a representation of a system used to understand it. A model does not show every detail. It shows the parts and interactions that matter for the question you are asking.
Engineers use several kinds of models. Each one represents the same system in a different way.
- A real object you can build or touch
- Example: a small model bridge tested with weights
- A labeled drawing of the parts
- Example: a cross-section of a machine
- Boxes and arrows showing order and flow
- Example: how input becomes output
- An idea or rule that explains behavior
- Example: "feedback keeps the system balanced"
- Introduce models as the tool for the standard.
- Show that one system can be modeled many ways.
- Abstraction and representation
- Comparison across model types
- Understand to Apply
- DOK 2
- Familiar subway-map analogy
- Four short, parallel cards
- Plain examples for each type
When One Part Fails
The way a system's parts are arranged is its structure. What the system does is its function. The two are tied together, which is exactly why a single failure can change everything.
The arrangement of parts decides what a system can do. The teeth of a zipper are arranged so they interlock, which is why a zipper holds closed. Rearrange those same parts and the function is lost.
Because structure and function are linked, the parts are not interchangeable. Some components matter more than others. A part that many others depend on is a part the whole system relies on.
When a component fails, the parts that depend on it lose what it was giving them. Those parts then pass the trouble to the parts that depend on them. The failure travels along the same interactions that normally make the system work.
This is the answer to our opening question. The broken traffic light fed cars to the next intersection. With it down, cars pile up, and that backup feeds into the next street, and the next. The more connected a part is, the wider its failure spreads.
The same pattern of a spreading failure appears in many systems.
- Connect structure and function to the spread of failure.
- Resolve the opening phenomenon directly.
- Cause-and-effect modeling (failure propagation)
- Transfer across systems
- Closing the curiosity gap
- Analyze
- DOK 2 to 3
- Concrete zipper analogy
- Plain causal language
- Parallel examples across systems
Brain Check
Three quick questions before we put it all together. These are not graded. Pulling answers from memory now will help them stick.
- Strengthen memory through retrieval before the wrap-up.
- Surface misconceptions early.
- Retrieval practice
- Generation effect
- Productive struggle
- Understand to Apply
- DOK 1 to 2
- Ungraded and low stakes
- Immediate feedback
- Short tasks reduce load
Why the Whole City Felt It
You started with a question: why does one broken traffic light cause problems throughout a whole city? Now you can trace the whole chain, step by step.
- Tie the pieces into one cause-and-effect chain.
- Answer the opening question directly.
- Schema building
- Elaboration
- Coherent narrative
- Understand to Analyze
- DOK 3
- Step-by-step beats
- Plain causal language
- Builds on prior sections
Check Your Understanding
Ten questions covering everything you explored, from what a system is to why failures spread. Answer every question, then submit.
Engineers don't just name the parts. They can trace how a failure in one part travels through the whole system.
Write your own explanation first. Then submit your work to compare your thinking with a model answer.
At rush hour, a single traffic light downtown goes dark. Minutes later, streets far across the city are backed up. Trace how that one broken part spreads to affect intersections it never touches directly. Name the parts involved and say why the trouble does not stay at one corner. Use the word interact.
- Check understanding against the lesson goals.
- Give students and teachers a clear signal.
- Retrieval practice
- Feedback loops
- Understand to Apply
- DOK 1 to 2
- Answer explanations provided
- Practice and classroom modes
- Plausible, evenly placed options
More Learning
Systems thinking is a tool you can point at almost anything: power grids, the internet, ecosystems, transportation networks, and manufacturing systems all work the same way. More investigations, simulations, and design challenges are coming soon.
- Offer pathways beyond the core lesson.
- Signal that learning continues past the quiz.
- Interest-driven extension
- Transfer to new contexts
- Apply to Analyze
- DOK 2 to 3
- Optional and self-paced
- Clear labels for what is available
- No penalty for skipping
Connections
Engineering is the work of designing systems whose parts work together. These lessons each look at a different kind of engineered system.