Comparing Systems by Their Parts and Functions | Singapore Primary Science Guide

eduKate Learning Manual — Systems

Did You Know a System Can Contain Every Correct Part and Still Be the Wrong System?

Put a battery, two wires, a bulb and a switch on a table.

You have every familiar component of a simple circuit.

Connect both wires to the same bulb terminal and the system still fails.

The inventory was correct.

The relationships were wrong.

A system is not a bag of correct parts. It is a bounded set of parts, relationships, flows and constraints whose interaction produces a whole-system outcome.

This is the final Systems-shelf idea.

Everything before it—digestion, respiration, circulation, plant transport, movement and circuits—becomes one reusable way of thinking.

RFE / Teaching goal: By the end of this manual, a learner should be able to define a useful system boundary; identify relevant components and jobs; trace relations, matter/energy/information flows and interfaces; identify receivers, controls, constraints and bottlenecks; distinguish necessary from sufficient conditions; predict failure propagation and possible feedback; compare systems without collapsing different mechanisms; choose evidence that tests the claimed link; change the system boundary deliberately; and transfer the same reasoning matrix to unfamiliar living, physical and designed systems.

1. The Systems RFE: Reconstruct Before You Memorise

For any system, ask:

BOUNDARY → COMPONENTS → JOBS → RELATIONS → FLOWS → INTERFACES → CONTROLS/CONSTRAINTS → RECEIVERS → BOTTLENECKS → FAILURE PROPAGATION → FEEDBACK → EVIDENCE → MODEL LIMIT → TRANSFER.

This is not a new vocabulary list.

It is a questioning sequence that can be applied to a digestive tract, electrical circuit, plant, water cycle, ecosystem, transport network or unfamiliar engineered system.

2. First Choose the Boundary

A system boundary defines what is being treated as inside the system for the current question.

The boundary is partly a modelling choice.

“heart” is a smaller system than “circulatory system”;
“respiratory system” is smaller than “whole-body oxygen-delivery system”;
“one branch of a circuit” is smaller than “the complete electrical circuit”;
“Singapore local catchment” is smaller than “the global water cycle”.

Changing the boundary changes which inputs, outputs and external influences must be named.

Many arguments about systems are really arguments about where the boundary was drawn.

3. Components Matter—but Only Relevant Components

A system description can fail by listing too few parts.

It can also fail by listing everything.

For a question about oxygen delivery to a muscle, the colour of a person’s hair is real but irrelevant.

For a question about a bulb’s current path, wire colour is usually irrelevant while terminal connectivity is crucial.

Good system models preserve causally relevant parts, not maximum detail.

4. Jobs: What Does Each Selected Part Contribute?

System	Selected component	Selected job
digestive	small intestine	major digestion/absorption interface
respiratory	lungs	gas-exchange interface
circulatory	heart	pressure/flow driver for blood
plant transport	roots	water/mineral entry interface
electrical	switch	controlled change in connectivity

But a job statement is not yet enough.

We still need to know how that part hands its output to the next part.

5. Relations Are the Missing Middle

Weak explanations jump:

“There is a heart, therefore the toe gets oxygen.”
“There is a battery, therefore the bulb lights.”
“There are roots, therefore the leaf gets water.”

Strong explanations fill the missing middle:

part state → interaction/handoff → flow changes → receiver condition changes → whole-system outcome.

Relationships are where systems become causal.

6. Flows: Name What Actually Moves

Do not draw an arrow and leave it anonymous.

System	Flow or transfer	Mechanism warning
circulatory	blood carrying gases, nutrients and other substances	pressure-driven biological fluid network
plant	water/minerals and manufactured sugars through specialised tissues	not heart-driven blood circulation
electrical	charge flows as current while energy is transferred	not liquid electricity consumed by devices
water cycle	water moves among stores and changes state	not a machine with one starting point
digestive	bulk food, secretions, absorbed nutrients and water	several different flows coexist

same abstract word “flow” can hide completely different physics and biology.

7. Interfaces: Where One System Hands Something to Another

An interface is a boundary across which a meaningful handoff occurs.

lung air ↔ blood;
small-intestine contents ↔ circulation;
soil ↔ root;
wire ↔ component terminal;
atmosphere ↔ leaf stoma.

An interface can fail even when the systems on both sides remain available.

Air can be present and blood can be present while exchange is impaired.

A battery and bulb can both be healthy while a poor contact prevents current.

many system failures live at the handoff rather than inside the famous components.

8. Receiver: Who or What Must Finally Benefit?

Systems explanations become clearer when the receiver is explicit.

a body cell receives oxygen/nutrients;
a leaf receives water;
a bulb receives electrical energy and transfers it to light/heat;
a reservoir receives runoff;
a root receives soil water across its interface.

This prevents the mistake:

resource available upstream = receiver supplied.

Availability and delivery are different states.

9. Necessary ≠ Sufficient

A battery may be necessary for a battery-powered circuit.

It is not sufficient by itself to light a bulb.

A functioning heart is necessary for normal human circulation.

It is not sufficient by itself to guarantee oxygen reaches every tissue.

Roots are necessary for normal water uptake in many land plants.

Healthy roots do not guarantee leaves receive water if the transport route is severed.

required part ≠ complete causal explanation.

10. Bottleneck: Which Link Limits Whole-System Performance?

A bottleneck is the link whose limited capacity constrains the system under the current conditions.

The bottleneck can move.

At rest, oxygen delivery may have spare capacity.
During exercise, delivery demand rises.
In a dry plant, water uptake may become limiting.
In a circuit, one poor contact can become the limiting connection.

the same system can be limited by different links in different states.

11. Failure Propagation: Local Failure Can Travel

Start at the failed part or interface.

Then trace downstream:

local change → lost/reduced handoff → next subsystem receives less/different input → receiver state changes → whole-system effect.

Do not jump directly from “part changed” to “whole system fails”.

Ask whether:

there is an alternative route;
another part can compensate;
the failure is partial;
the changed part is actually relevant to the current receiver.

12. Control, Constraint and Feedback Are Different Ideas

Control: a part deliberately or biologically changes system state—for example, a circuit switch changes connectivity.

Constraint: a boundary or rule limits what states are possible—for example, a joint restricts movement direction.

Feedback: information about system state influences later system behaviour—for example, living organisms adjust ventilation, circulation or stomatal opening in response to changing internal/external conditions.

Not every Primary system needs a detailed feedback model.

The useful boundary is:

do not call every interaction “feedback”; feedback requires an effect that returns to influence later system behaviour.

13. Whole-System Behaviour Can Emerge From Relationships

No individual circuit component possesses the property “working lamp circuit”.

That behaviour appears when source, route, receiver and connectivity are arranged correctly.

No individual organ alone produces “whole-body oxygen delivery”.

That outcome emerges from ventilation, exchange, blood flow and tissue delivery working together.

some important properties belong to the organised whole, not to any isolated part.

14. Analogy: Compare One Relationship at a Time

“Blood vessels are like wires.”

This can help if the only intended comparison is connected routes.

It misleads if the learner concludes:

blood is electric current;
the heart is a battery;
oxygen is electrical energy;
vessels and wires obey the same transport mechanism.

analogy should preserve a named relationship and expose the point where the mechanisms diverge.

15. Natural Function ≠ Human Design Intention

A designed circuit can have a purpose chosen by an engineer.

A biological system has functions produced through evolution, development and physiology.

It is normal at Primary level to say “the heart’s function is to pump blood”.

The deeper boundary is to avoid claiming that natural systems were consciously designed in the same sense as machines.

16. How Do We Know Which Link Matters?

Match evidence to the claimed relationship.

Claim	Useful evidence	Weak over-inference
this route is required	controlled interruption/restoration changes the receiver	“it is drawn in the diagram, so it must be causal”
this interface transfers material	tracer/measurement before and after interface	“the two structures are next to each other”
this part controls the system	repeatable controlled state change	“the part is labelled control”
this component is a bottleneck	changing its capacity changes whole-system performance while alternatives are controlled	“it is the biggest/most famous part”

evidence earns a specific causal link, not unlimited ownership of the whole system.

17. Representation: Different Questions Need Different Maps

anatomy diagram → where structures are;
flow diagram → what moves and where;
circuit schematic → topology/connectivity;
table → compare jobs;
graph → how variables change;
feedback loop → how system output influences later behaviour.

A representation is not automatically good because it is detailed.

use the representation that preserves the relationship needed for the question.

18. Cross-Domain Comparison Matrix

Lens	Human circulation	Plant transport	Electrical circuit
Boundary	heart + blood + vessels	selected root/stem/leaf transport network	source + conductors + devices + controls
Driver	heart-generated pressure	different physical/biological drivers in water and food transport	source maintains electrical potential difference
Route	blood vessels	specialised conducting tissues	conducting paths
Cargo/transfer	blood carries substances	water/minerals and sugars	charge flows; energy transferred
Receiver	organs/tissues	growing, photosynthetic or storage tissues	electrical device
Major analogy limit	living closed-loop fluid system	no central heart; two specialised cargo networks	not a fluid-transport system

This page owns the cross-domain comparison method.

The dedicated body-systems comparison owner remains responsible for the digestive/respiratory/circulatory comparison in depth.

19. The Water Cycle Breaks the “Machine” Model

The water cycle has stores and flows but no single central pump, no single starting point and no intended human-designed output.

Water moves through evaporation, condensation, precipitation, runoff, infiltration and storage under different physical drivers.

This is why a universal “input → machine → output” template eventually fails.

systems thinking must be flexible enough to represent cycles, networks and feedbacks—not only production lines.

20. The Worth-My-While Connection: Systems Thinking Is a Compression Tool for the World

You cannot hold every detail of a hospital, rainforest, city, computer network or human body in working memory at once.

Systems thinking lets you compress complexity while preserving causally important structure:

what is inside → what does what → what connects → what moves → who receives → what limits → what happens when a link changes.

The National Academies identifies systems and system models as a crosscutting concept precisely because this reasoning travels across scientific disciplines.

21. The Hero Test: Protect the Receiver and the Reality

Systems language becomes dangerous when the diagram becomes more important than the real receiver.

If the model predicts delivery but the receiver is not receiving, investigate the mismatch.

If the analogy predicts identical mechanisms but the evidence shows different mechanisms, break the analogy.

If every named part is present but the outcome fails, inspect relationships and interfaces.

The world gets to correct the system model.

22. Common Misconceptions — and Exact Repairs

“A system is a list of parts.” Relations and flows create system behaviour.
“All correct parts guarantee success.” Connections, states and interfaces may still be wrong.
“The biggest part is the most important.” Causal importance depends on the current system job.
“One failed part stops everything.” Branching, redundancy and partial function can preserve some outcomes.
“Two systems with routes are basically the same.” Identify cargo and mechanism before comparing.
“Analogy means identity.” State the shared relationship and the boundary.
“Every interaction is feedback.” Feedback must return to influence later system behaviour.
“Input–process–output works for everything.” Cycles and networks may require different representations.
“A model is wrong whenever reality disagrees.” First check interpretation and implementation; then update the model when evidence requires it.

23. Worked Reasoning: Every Part Present, Bulb Still Dark

A battery, bulb, switch and wires are all present.

The bulb is dark.

Weak answer:

“The system has all its parts, so the bulb must be broken.”

Strong answer:

Part inventory is insufficient. Trace the system boundary, terminal connectivity, switch state, conducting interfaces, source condition and receiver state. A correct component list can still form the wrong topology, contain a failed interface or include a failed component. Evidence should isolate the earliest failed handoff.

24. Changed-Problem Transfer: Build the Model From Nothing

An unfamiliar school rainwater system contains a roof, gutter, downpipe, filter, storage tank, overflow and garden outlet.

Draw the system boundary.
Classify the selected parts by job.
Label the water flow.
Identify at least two interfaces.
Name the final receiver.
Identify one control or constraint.
Predict the effect of a blocked filter.
Identify one alternative route or overflow.
State what evidence would locate the blockage.
Compare one relationship with a circuit and state where the analogy fails.

If the learner can do this without memorising a rainwater-system chapter first, the Systems shelf has transferred.

25. What Mastery Looks Like

Beginning: identifies parts and functions.
Developing: identifies relations, inputs, outputs and flows.
Secure: defines boundaries, interfaces, receivers and bottlenecks.
Strong: traces failure propagation, distinguishes necessary from sufficient and tests causal links with evidence.
Advanced for Primary: changes boundaries, reasons with control/constraint/feedback, evaluates analogy limits, chooses representations and transfers the full matrix to unfamiliar natural and designed systems.

26. Curriculum Boundary and Ownership Fence

MOE Primary Science repeatedly uses systems as a Core Idea across human, plant and electrical topics and emphasises interactions among parts.

This page is a synthesis and transfer manual, not a new examinable list of Systems vocabulary.

WP102219 remains the canonical body-systems comparison owner. Topic-specific digestive, respiratory, circulatory, plant, musculoskeletal and electrical mechanisms remain with their own pages. Formal systems dynamics, control theory, network science and mathematical modelling belong to later levels.

27. Continue From Systems Into Energy

28. Trusted References

29. Teaching Guide — Use This Last

Shock: give every correct circuit part but wire the system wrongly.
Draw the boundary.
Select only relevant parts and jobs.
Trace relations and label exact flows.
Find interfaces and receivers.
Separate necessary from sufficient.
Break one handoff and trace propagation.
Add control/constraint/feedback only where justified.
Compare two domains: preserve one relationship and expose one analogy limit.
Transfer cold: give an unfamiliar system and let the learner reconstruct it from the matrix.
Release: finish when “name the parts” has become “define the boundary, trace the relationships, test the evidence, locate the bottleneck, protect the receiver and know where the model stops.”

eduKate Learning Manual principle: The purpose of Systems Science is not to make the world look simple. It is to compress complexity without losing the relationships that decide whether the real receiver actually gets what the system was supposed to deliver.