Mathematical Modeling and Problem Solving
What this domain asks you to know
This domain asks whether you can engage students in genuine modeling: formulating a problem from a real context, building and revising a model, and interpreting results critically.
Concepts to master
- Modeling cycle: identify a problem → make assumptions → build a model → analyze → interpret and validate → revise or report.
- Assumptions and simplification: real contexts require choices about what to ignore; those choices must be justified.
- Representation choice: deciding whether a situation calls for a linear, exponential, or other model, and testing fit.
- Problem-solving heuristics: Polya's phases-understand, plan, carry out, look back; and strategies like working backward, drawing diagrams, and special cases.
- Reasonableness and units: checking whether answers make sense in context, including dimensional analysis.
Traps to watch for
Distractors treat a single computation as a complete model, or skip validation. Another trap: choosing a model by pattern-matching ("it grows, so exponential") without checking whether the rate of change is constant or proportional. Watch for answers that ignore units or treat an assumption as a fact.
Rule of thumb
After computing, always ask: Does this answer make sense in the real world, and what did I assume to get here?
Worked example
A student models a cooling drink's temperature. A linear model fits the first minutes but predicts negative temperatures later. The validation step-comparing the prediction to reality-reveals the model's limits and motivates a decaying model, demonstrating the full cycle rather than a single calculation.