📚 Quantitative Aptitude – Caselets
Audience: Advanced university students (MIT‑level).
Goal: Master the art of solving “Caselets” – brief, data‑heavy word problems that test analytical thinking, mathematical modeling, and efficient computation.
1. What is a Caselet?
| Feature | Description |
|---|---|
| Length | 1–3 paragraphs, 200–400 words |
| Data | Multiple numeric facts, often contradictory or hidden |
| Objective | Usually a single numerical answer (integer, decimal, ratio, fraction) |
| Structure | Context → Data → Question |
| Difficulty | Requires synthesis of several steps – algebra, geometry, combinatorics, probability, etc. |
Why Caselets?
They mirror real‑world problem‑solving: you receive a chunk of information, must decide what’s relevant, formulate equations, and compute efficiently under time pressure (e.g., 1 minute per problem).
2. First Principles: Decomposing a Caselet
2.1. Parse the Text
- Identify nouns & verbs – Entities (people, objects, groups) and their relationships.
- Highlight numbers – Note all numerical values, units, and their positions.
- Mark constraints – “at most,” “exactly,” “more than,” “less than,” “if … then …” etc.
Tip: Underline or circle the numbers and write a quick sketch of the scenario.
2.2. List the Unknowns
- Assign symbols (x, y, z, …) to the quantities you need to find.
- If multiple unknowns, give each a distinct, memorable symbol.
2.3. Translate into Equations
- Linear relationships → algebraic equations.
- Ratios/percentages → proportional equations.
- Geometric contexts → use Pythagoras, area formulas, etc.
- Probabilities → combinatorial formulas or conditional probability.
2.4. Identify Edge Cases
- Zero or negative values – often impossible physically; check for contradictions.
- Maximum/minimum constraints – maybe a “least” or “most” scenario.
- Non‑integer solutions – decide whether rounding is needed.
2.5. Solve Efficiently
- Eliminate variables early.
- Use substitution when a variable appears in only one equation.
- Check units to avoid arithmetic mistakes.
2.6. Verify & Interpret
- Plug back into the original constraints.
- Interpret the result in context – does it make sense?
Example: “Number of students can’t be negative; if the answer is 0.5, maybe the problem expects a whole number.*
3. Advanced Theoretical Tools
| Tool | When to Use | Key Formula(s) |
|---|---|---|
| System of linear equations | Multiple unknowns, pairwise constraints | (Ax = b) |
| Inequalities | “More than”, “less than” | (ax + by \leq c) |
| Linear programming (simplex) | Optimization (max/min) under constraints | Standard LP form |
| Combinatorics | Counting arrangements, selections | (\binom{n}{k}), permutations |
| Probability | Random events, expected values | (P(A)=\frac{a}{b}) |
| Modular arithmetic | Remainders, divisibility | (a \equiv b \pmod{m}) |
| Generating functions | Counting partitions, sequences | (G(x)=\sum a_n x^n) |
| Graph theory | Network flows, connectivity | adjacency matrices |
Edge‑case insight: In many caselets, the maximum or minimum value of a variable is key. Use linear programming or “corner point” analysis to find these extremes.
4. Deep Dive Example
Problem (Caselet):
*“A company produces two types of widgets: A and B.
- The production cost per widget is ₹30 for A and ₹50 for B.
- The company’s total production cost in a month is ₹10 000.
- The total number of widgets produced is 400.
- The ratio of the number of A widgets to B widgets is 3:2.
Find the number of B widgets produced.”*
4.1. Translate
Let:
- (a) = number of A widgets
- (b) = number of B widgets
Equations:
- (a + b = 400) (total widgets)
- (30a + 50b = 10,000) (total cost)
- (\frac{a}{b} = \frac{3}{2}) → (2a = 3b) (ratio)
4.2. Solve
From (3): (a = \frac{3}{2}b).
Substitute into (1):
[ \frac{3}{2}b + b = 400 \implies \frac{5}{2}b = 400 \implies b = 160. ]
Check cost: (30(\frac{3}{2}160) + 50160 = 30*240 + 8000 = 7200 + 8000 = 15200).
Oops! Contradiction → our assumption wrong.
We must use two equations only (cost + total).
From (1): (a = 400 - b).
Insert into cost:
[ 30(400 - b) + 50b = 10,000 \ 12,000 - 30b + 50b = 10,000 \ 20b = -2,000 \ b = -100. ]
Negative → impossible → No solution → Inconsistency.
4.3. Edge‑Case Analysis
- The ratio constraint (3) is incompatible with the other two.
- Realistic interpretation: The company cannot satisfy all three simultaneously.
- Answer: No feasible solution; the constraints are contradictory.
Key takeaway: Always test consistency before solving; contradictions lead to “no solution” or “infinite solutions” scenarios.
5. Edge Cases & Common Pitfalls
| Pitfall | Explanation | How to Avoid |
|---|---|---|
| Mis‑reading units | Mixing rupees, dollars, kilograms | Keep units consistent; convert early |
| Overlooking hidden constraints | “At most”, “at least” statements |