Crack Case-Based Questions: Master Reading Passages and Extracting Data

Case-based questions in CBSE, ICSE, and state board exams often test whether you can connect textbook formulas to real-world scenarios. Students often lose marks here not because they lack subject knowledge, but because they get bogged down by long paragraphs of text. To handle these questions efficiently under exam pressure, you need a systematic method to read the passage and isolate the core numbers and variables.

The Information Overload Trap

Examiners design case studies to look like reading comprehension passages. They include background history, practical applications, and conversational filler. Your first instinct might be to read every word sequentially from start to finish. This is a mistake.

When you read a case study like a novel, your brain spends cognitive energy processing irrelevant details. Instead, you must read with a targeted purpose: hunting for data points, constraints, and the core question.

Step 1: Read the Questions Before the Passage

Before you look at a single sentence of the case paragraph, jump straight to the sub-questions (usually labelled (a), (b), (c) or structured as multiple-choice items).

Reading the questions first acts as a mental filter. If question (a) asks you to calculate the maximum current in a circuit, or the probability of a specific genetic cross, or the profit function in a linear programming problem, you instantly know what data to look for. You are no longer reading passively; you are scanning for specific variables.

Step 2: Use the Highlighting and Tagging Method

As you read through the passage on your second pass, use your pen to categorize information. Look out for three types of text:

• Constants and Given Values: Numbers, percentages, rates, and initial conditions. Immediately assign them standard variables ($v, t, m, n$).
• Conditions and Constraints: Phrases like "at constant temperature", "for $x > 0$", or "excluding overhead costs". These dictate which formulas you can and cannot use.
• Directives: Words like "calculate", "derive", "state the ratio", or "verify". These tell you the exact mathematical or conceptual output required.

| Text Element in Passage | What It Means | Action to Take | | :--- | :--- | :--- | | Descriptive filler | Background context | Ignore or skim lightly | | Explicit numerical value | Given data for formulas | Write down as $u = 5\text{ m/s}$, etc. | | Conditional clause | Domain restriction | Note down constraints (e.g., $t \ge 0$) | | Comparative term | Inequality or ratio setup | Translate to math ($A$ is twice $B \implies A = 2B$) |

Step 3: Translate English into Mathematical Expressions

Case studies in Physics, Chemistry, and Mathematics require you to translate descriptive sentences into equations.

For instance, if a passage states: "The cost of production increases linearly with the number of units produced, with a fixed setup cost of ₹5,000 and an incremental cost of ₹200 per unit," you should instantly write down the linear function:

$C(x) = 200x + 5000$

Here, $x$ represents the number of units. By converting the prose into a clean mathematical model, you strip away the intimidation factor of the long paragraph.

Step 4: Check Units and Consistency

In science and math case studies, data extraction fails if you miss unit discrepancies. A passage might give speed in $\text{km/h}$ but ask for acceleration in $\text{m/s}^2$, or give volume in litres while dimensions are in centimetres.

Always convert all extracted data into SI units or a consistent system of measurement before you begin any calculation steps. Write down your conversion factors right next to the given data list on your rough sheet.

Quick Checklist

• [ ] Read all sub-questions before reading the passage text.
• [ ] Identify and list all numerical values with their proper units.
• [ ] Note down boundary conditions, constants, and operational limits.
• [ ] Translate word statements into algebraic equations or chemical reactions.
• [ ] Verify that all units are consistent before applying formulas.