The Secondary 3 A-Math Dependency Map
Secondary 3 Additional Mathematics is easier to understand when it is viewed as a dependency network rather than a flat list of chapters.
Some capabilities sit upstream and support many others. When they fail, several later topics can appear weak even though the visible topic is not the true cause.
Do not ask only “Which topic is weak?” Ask “What does this topic depend on, and what depends on it next?”
A useful dependency map is:
Prerequisite → Capability → Downstream Use → Bottleneck.
1. Prerequisite: What Must Already Be Working?
Every new A-Math capability inherits earlier mathematics.
- equation manipulation;
- factorisation;
- fractions and indices;
- graph interpretation;
- coordinate relationships;
- symbolic fluency;
- clear multi-step working.
These are not merely “old topics”. They are services used by newer mathematics.
2. Capability: What New Operation Is Being Built?
For each current topic, translate the heading into actions.
- What must the student recognise?
- What relationship must be retrieved?
- What transformation must be executed?
- Which conditions must be preserved?
- What kind of output must be produced?
This exposes whether the student lacks the new idea itself or an older tool needed to operate it.
3. Downstream Use: Where Will This Capability Be Needed Later?
Some Secondary 3 capabilities carry much more downstream load than others.
For example, stable algebraic manipulation supports later work across functions, trigonometry, coordinate methods and calculus. Graph interpretation can support several different mathematical families. Retrieval and recognition affect almost every mixed question regardless of topic.
This is why two weaknesses of equal current mark cost may deserve different repair priority.
A weakness becomes strategically important when many later routes pass through it.
4. Bottleneck: Where Does the Network Actually Break?
A bottleneck is the smallest unstable capability that constrains a larger amount of performance.
Typical patterns include:
- Algebra bottleneck: advanced concepts are understood but execution repeatedly fails.
- Retrieval bottleneck: previously learned methods disappear after a delay.
- Recognition bottleneck: the student can solve once told the topic but cannot identify it independently.
- Representation bottleneck: a concept works symbolically but not graphically, or vice versa.
- Working-memory bottleneck: too many unstable small steps overload the student before the main idea can be used.
Why Flat Topic Lists Mislead
A flat list makes every chapter look separate.
But mathematics is connected. A student who appears weak in three chapters may actually have one shared upstream failure. Conversely, a student may be strong in the underlying mathematics but weak in one highly specific new concept.
The repair is different in each case.
Use a Dependency Question Before Re-teaching
- What is the visible topic?
- What prerequisite operations does it require?
- Which of those operations is failing?
- Does that same failure appear elsewhere?
- What later mathematics also depends on it?
If one prerequisite explains several failures, repair upstream before adding more topic-specific worksheets.
A Simple Dependency Example
Suppose a student understands the idea behind a new function problem but repeatedly breaks while rearranging equations.
The visible label may say “Functions”, but the bottleneck may be algebraic control. Re-teaching the function concept repeatedly will not necessarily improve the result.
The better route is:
Identify algebra break → repair algebra → return to function problem → test changed form.
Another Example: Strong Topical Work, Weak Mixed Work
If a student performs well inside every chapter but collapses when questions are mixed, the dependency problem may not be content at all.
The missing capability may be recognition: identifying which mathematical structure is present before choosing a route.
That is a cross-topic dependency and should be trained with unlabeled mixed work.
Dependencies Change as the Student Improves
An upstream weakness can be repaired. Once it is stable, the next bottleneck becomes visible.
A student may move through:
Algebra bottleneck → Retrieval bottleneck → Recognition bottleneck → Transfer bottleneck.
The learning plan therefore has to recompile as the network changes.
The Secondary 3 Dependency Audit
- Prerequisite: What earlier capability does this work require?
- Capability: What new mathematical operation is being built?
- Downstream Use: Where else will this capability be needed?
- Bottleneck: What is the earliest unstable point?
- Repair: What is the smallest intervention that restores the route?
The Dependency Map
Prerequisite → Capability → Downstream Use → Bottleneck → Repair → Retest.
This gives Secondary 3 A-Math a much clearer structure than a chapter list. It shows not only what students learn, but which capabilities carry load for the rest of the subject.
For the live state of each area, see The Secondary 3 A-Math Coverage Board. For the end-of-year readiness check, see Secondary 3 A-Math Foundation Audit.

