IP Year 3 English often asks students to move between concrete examples and abstract ideas. A comparison can make a difficult concept visible, but a weak analogy can also distort the reasoning. Students therefore need to know what two cases genuinely share, where the comparison stops working and which underlying principle can transfer.
This rebuilt 2019 Tampines page owns one distinct job: analogy control, abstraction and concept transfer. It does not duplicate Punggol Year 3 argument architecture or Yishun Year 3 source evaluation. The focus is reasoning across domains without smuggling in false equivalence.
Quick Read: Case A → Shared Structure → Case B → Boundary
- Describe A: what is actually happening?
- Abstract: what relationship or mechanism sits underneath?
- Map to B: which elements correspond?
- Test: does the same relationship still hold?
- Boundary: where does the analogy stop?
- Transfer: keep the principle, not every surface feature.
1. Analogy Is a Mapping, Not a Metaphor Sticker
Calling an argument “a bridge” is only useful if the student can explain what corresponds to the supports, span and load. We move from imagery to mapped relationships.
2. Surface Similarity Can Mislead
Two cases may both involve conflict yet operate through very different mechanisms. Students identify structural similarity rather than relying on shared appearance or topic.
3. Abstract the Relationship
Instead of memorising a specific example, students state the underlying relationship in general terms: increased pressure changes behaviour; delayed information changes decision quality; concentrated control reduces alternatives. The exact abstraction depends on the text.
4. Map Corresponding Parts Explicitly
If Case A has a source, constraint and outcome, students identify the corresponding source, constraint and outcome in Case B. Missing correspondences reveal a weak analogy early.
5. Every Analogy Has a Failure Boundary
A comparison may illuminate one relationship while failing on scale, intention, context or consequence. Strong writers state the useful overlap without pretending the cases are identical.
6. Counterexamples Test the Abstraction
Students search for a case where the proposed principle would predict the wrong outcome. If the counterexample succeeds, the abstraction needs refinement.
7. Transfer Should Preserve the Mechanism
The learner does not copy the original example’s language. They carry the relationship into a new context and explain why it remains relevant.
8. Use the Analogy Ledger
- Case A elements
- shared relationship
- Case B elements
- supported transfer
- known mismatch
- confidence boundary
9. Use the Swap Test
If the same reasoning is applied to a new domain, does it still produce a sensible prediction or explanation? This reveals whether the student learned the mechanism or merely remembered the example.
10. The Year 3 Analogy Diagnostic
- Surface-similarity mapping.
- Analogy used without correspondence.
- No abstraction of the shared mechanism.
- False equivalence.
- Failure boundary omitted.
- Counterexample ignored.
- Metaphor mistaken for proof.
- Transfer copies language instead of structure.
- No confidence calibration.
11. Why Three Students Works
- Students can propose competing analogies.
- Peers identify mismatched correspondences.
- One learner can provide a counterexample to another’s abstraction.
- The tutor can separate creative comparison from valid reasoning.
- Final transfer tasks remain individual.
12. A 90-Minute Tampines IP Year 3 Runtime
- 10 min — concrete case analysis.
- 15 min — abstraction.
- 15 min — correspondence mapping.
- 10 min — boundary detection.
- 15 min — counterexample testing.
- 15 min — transfer paragraph.
- 5 min — confidence calibration.
- 5 min — error ledger.
Conclusion: Transfer the Relationship, Not the Costume
A strong analogy identifies a shared mechanism, maps the relevant parts and states where the comparison stops. That discipline lets students use abstraction as a real reasoning tool rather than as decorative cleverness.