Case analysis
This chapter critically examines various methodologies for case analysis, a fundamental skill in constructing rigorous mathematical proofs and solving complex problems. Mastery of these techniques, including identifying hidden assumptions, executing exhaustive case splits, and applying constraint-based elimination, is essential for demonstrating advanced logical reasoning and problem-solving capabilities required for the BS Hons course.
---
Chapter Contents
|
| Topic |
|---|-------| | 1 | Hidden assumptions | | 2 | Exhaustive case split | | 3 | Constraint-based elimination |---
We begin with Hidden assumptions.
Part 1: Hidden assumptions
Hidden Assumptions
Overview
Many incorrect arguments fail not because of bad algebra, but because they silently use something that was never given. These silent steps are called hidden assumptions. In olympiad and CMI-style reasoning, finding the hidden assumption is often the difference between a valid proof and a convincing-looking mistake. ---Learning Objectives
After studying this topic, you will be able to:
- Detect assumptions that are being used without proof.
- Separate what is given from what is inferred.
- Test whether a claim still holds after changing an unnoticed assumption.
- Recognize common hidden assumptions in algebra, geometry, and number theory.
- Repair flawed arguments by stating extra conditions explicitly.
Core Idea
A hidden assumption is an unstated condition used in a solution, proof, or argument.
It is not part of the original problem statement, but the argument depends on it.
- dividing by an expression without checking whether it is zero
- taking square roots and assuming signs
- assuming a diagram is to scale
- assuming variables are integers when only real numbers were given
- assuming a process always terminates
Very Common Hidden Assumptions
- Division step
If you divide by , you must know
- Square root step
From , you get , not only
- Cancellation
Cancelling a factor requires that factor to be nonzero
- Even/odd reasoning
This works only when the objects are integers
- Geometry diagrams
A picture may suggest parallel lines, equal angles, or symmetry that is not given
Domain Assumptions
A statement can change completely depending on whether the variable is:
- a real number
- an integer
- a positive real number
- a nonzero quantity
- a natural number
For example:
- is not true for all real
- needs
- parity arguments require integers
Hidden Assumptions in Equations
Suppose someone writes:
then multiplies, factors, and divides by .
This is invalid because when , we have
So the division step is illegal.
Hidden Assumptions in Geometry
Never trust:
- equal-looking lengths
- right angles that are not marked
- midpoints not stated
- parallel lines that only look parallel
- intersection points assumed inside the figure
In proof problems, only use what is given or already proved.
Hidden Assumptions in Counting and Number Theory
- assuming distinct objects are identical
- assuming order does not matter when it does
- assuming a remainder argument works over non-integers
- assuming every case has been covered when some are missing
- assuming a construction exists without checking constraints
Minimal Worked Examples
Example 1 Claim: If , then . This argument has a hidden assumption that is positive. The correct conclusion is --- Example 2 Claim: If two triangles look symmetric in a diagram, then the corresponding sides are equal. This uses a hidden assumption that the figure is drawn accurately enough to prove symmetry. A diagram may suggest symmetry without it being given. ---How to Test for Hidden Assumptions
Whenever you read a proof, ask:
- What exactly is given?
- Was anything assumed about sign, domain, or order?
- Was any division step justified?
- Was any diagram-based fact actually stated?
- Could a counterexample appear if the hidden assumption is removed?
Common Mistakes
- β Treating βlooks trueβ as βis provedβ
- β Using positivity without proving it
- β Assuming distinctness or nonzero-ness without checking
- β Ignoring negative solutions after squaring or square-root steps
- β Forgetting to state extra conditions in a proof
CMI Strategy
- Read the statement slowly and isolate the exact hypotheses.
- Mark every place where the solution uses sign, domain, or distinctness.
- If the result feels suspiciously strong, test small counterexamples.
- In proof writing, state every nontrivial condition you use.
- If a step fails in one special case, split that case separately.
Practice Questions
:::question type="MCQ" question="Which of the following is a hidden assumption in the step βdivide both sides by β?" options=[" is positive",""," is an integer",""] answer="B" hint="Division requires the divisor to be nonzero." solution="To divide by , we must know that So the hidden assumption is that . Hence the correct option is ." ::: :::question type="NAT" question="A student claims that from it follows that . How many real solutions were missed?" answer="1" hint="Check all real square roots of ." solution="The equation has the real solutions The student kept only , so exactly one real solution was missed. Hence the answer is ." ::: :::question type="MSQ" question="Which of the following are common hidden assumptions?" options=["Assuming a denominator is nonzero before dividing","Assuming a diagram is not to scale","Assuming variables are integers when the argument uses parity","Assuming an expression has a square root only when it is nonnegative"] answer="A,C,D" hint="One option is the opposite of the usual geometry warning." solution="1. True.Summary
- Hidden assumptions are unstated conditions that an argument secretly uses.
- The most common sources are division, sign, domain, and diagram-based reasoning.
- A valid proof must not rely on facts that were never given or proved.
- Counterexamples are often the fastest way to expose a hidden assumption.
- Good mathematical writing makes every needed condition explicit.
---
Proceeding to Exhaustive case split.
---
Part 2: Exhaustive case split
Exhaustive Case Split
Overview
An exhaustive case split solves a problem by dividing all possibilities into separate, non-overlapping cases and handling each one. This is a core proof and problem-solving method in olympiad mathematics. The power of the method comes from two requirements:- every possible situation must belong to some case,
- no case should overlap confusingly with another.
Learning Objectives
After studying this topic, you will be able to:
- Split a problem into complete and non-overlapping cases.
- Check whether the case division is exhaustive.
- Solve each case without losing conditions.
- Use parity, sign, order, and residue as natural case divisions.
- Avoid missing or duplicating cases.
Core Idea
A case split is exhaustive if every possible valid input falls into exactly one of the chosen cases.
- complete,
- simple,
- easy to analyze,
- logically clean.
Standard Ways to Split Cases
- By sign:
- By parity:
- By order:
- By residue:
- By geometric position:
inside / on / outside
How to Check Exhaustiveness
- Have I covered every valid possibility?
- Can the same object fall into two different cases?
If the answer to the first is no, the proof is incomplete.
If the answer to the second is yes, the proof may double count or repeat work.
Minimal Worked Examples
Example 1 Show that for any integer , the number is even. Split into two cases:- if is even, then is even
- if is odd, then is even, so is even
- if , then , so every such works
- if , then unless , but is not in this case
Case Splits in Inequalities
Case splitting is often the cleanest method when:
- modulus signs appear
- signs of expressions matter
- a variable appears in denominators or square roots
- floor or ceiling functions are involved
Case Splits in Counting
Sometimes the easiest way to count is to separate by a key feature:
- first digit is zero / nonzero
- number is even / odd
- selected object belongs / does not belong to a distinguished class
Common Mistakes
- β Missing a case entirely
- β Using overlapping cases without noticing
- β Solving one case and assuming the rest are similar without proof
- β Forgetting that the original condition still applies inside each case
- β Creating too many complicated cases when one clean split would work
CMI Strategy
- Choose the simplest natural partition.
- Make sure the cases are exhaustive.
- State the cases explicitly before solving.
- Keep the cases disjoint whenever possible.
- At the end, combine the results clearly.
Practice Questions
:::question type="MCQ" question="Which of the following is an exhaustive case split for an integer ?" options=[" or "," even or odd"," or "," prime or composite"] answer="B" hint="An exhaustive split must include every integer." solution="Every integer is either even or odd, and not both. So this is exhaustive and disjoint. Option A misses . Option C misses . Option D misses and also does not cover all integers cleanly. Hence the correct option is ." ::: :::question type="NAT" question="How many sign-based cases are needed to split a real variable exhaustively?" answer="3" hint="Think of positive, zero, and negative." solution="A real number can be:- positive,
- zero,
- negative.
Summary
- A case split must cover all possibilities.
- Good cases are usually disjoint and simple.
- Sign, parity, order, and residue are the most common natural splits.
- Case splitting is a proof method, not just a computational trick.
- Missing even one case makes the argument incomplete.
---
Proceeding to Constraint-based elimination.
---
Part 3: Constraint-based elimination
Constraint-based Elimination
Overview
Constraint-based elimination is a structured problem-solving method in which impossible cases are removed step by step until the valid possibilities become small enough to analyze completely. It is especially useful in logic puzzles, integer problems, digit problems, and finite search problems. ---Learning Objectives
After studying this topic, you will be able to:
- Translate verbal restrictions into precise mathematical constraints.
- Eliminate impossible cases using parity, bounds, divisibility, and uniqueness.
- Organize case analysis without missing or repeating cases.
- Narrow finite possibilities efficiently.
- Solve logic-style problems systematically rather than by guesswork.
Core Idea
A constraint is a rule that valid solutions must satisfy.
Examples:
- is even
- digits are distinct
- the number is prime
- exactly one of the statements is true
Constraint-based elimination means:
- list all constraints clearly,
- combine them,
- remove cases that violate any one of them.
Main Sources of Elimination
- Parity
- even/odd restrictions
- Bounds
- maximum/minimum possible values
- Divisibility
- residues mod
- Uniqueness
- digits or objects cannot repeat
- Ordering
- , ascending order, left-right conditions
Standard Workflow
- Write the constraints separately.
- Use the strongest one first.
- Cut the search space quickly.
- Check the remaining cases against all constraints.
- Confirm that all legal cases are covered.
Minimal Worked Example
Example 1 Find all positive integers such that Since and , we get Since is even and positive and at most , the possibilities are Then:- if , then
- if , then
Why Elimination Works
In many aptitude problems the search space is finite but too large to search randomly. Constraints are useful because each one removes many cases at once.
The best elimination solutions usually feel like:
- one strong filter,
- then one or two clean checks,
- then only a handful of possibilities remain.
Organizing Cases Correctly
A good case split should be:
- exhaustive,
- non-overlapping,
- easy to test.
Bad case splits create duplication or confusion.
- first split by last digit if divisibility is involved,
- not by random digit choice.
Common Mistakes
- β Checking some constraints early and forgetting the others later
- β Splitting into overlapping cases
- β Missing hidden domain conditions such as positivity
- β Guessing the answer from a few examples
CMI Strategy
- Turn every sentence into a mathematical condition.
- Look for parity or divisibility first.
- Use inequalities to reduce the size of the search.
- Keep the remaining candidates visible and test them one by one.
- At the end, state why no other cases survive.
Practice Questions
:::question type="MCQ" question="A positive integer is less than , odd, divisible by , and leaves remainder when divided by . Which of the following is ?" options=["","","",""] answer="A" hint="Check the constraints one by one." solution="Among the options, only is odd, divisible by , and satisfies . Therefore the correct option is ." ::: :::question type="NAT" question="Let be positive integers with , , and odd. How many possible values can take?" answer="3" hint="Use first." solution="Since and , we must have . Also is odd and positive, so the possible values are . Thus there are possible values of ." ::: :::question type="MSQ" question="Which of the following are standard valid elimination tools?" options=["Parity","Bounds","Divisibility","Ignoring one constraint temporarily and never returning to it"] answer="A,B,C" hint="Think of standard filters." solution="Parity, bounds, and divisibility are all standard elimination tools. Ignoring a constraint permanently is invalid. Hence the correct answer is ." ::: :::question type="SUB" question="Find all positive integers such that is divisible by and leaves remainder when divided by ." answer="" hint="List multiples of below and test mod ." solution="The multiples of less than are . Now reduce each mod : . Hence the required integers are ." ::: ---Summary
- Good elimination starts from precise constraints.
- Parity, divisibility, and bounds are the fastest filters.
- Case splits must be complete and non-overlapping.
- The goal is not random testing but systematic reduction.
- A finished solution must explain why no other cases remain.
Chapter Summary
Systematic Decomposition: Case analysis breaks down complex problems into a finite, manageable set of mutually exclusive and collectively exhaustive sub-problems.
Identifying Hidden Assumptions: Critical examination of problem statements is essential to uncover unstated conditions that may define or constrain the possible cases.
Exhaustive Case Split Principle: Ensure that every possible scenario is covered without omission, often by considering complementary conditions or partitioning a domain systematically.
Constraint-Based Elimination: Leverage given constraints and problem properties to logically rule out impossible or redundant cases, significantly simplifying the analysis.
Logical Justification: Each case must be rigorously justified, leading to a definitive conclusion or demonstrating its impossibility within the problem's scope.
Efficiency and Robustness: A well-executed case analysis provides a robust solution by systematically addressing all possibilities, preventing errors from overlooked scenarios.
Chapter Review Questions
:::question type="MCQ" question="When proving a statement for all integers , which case split is guaranteed to be exhaustive and non-overlapping in the most fundamental sense?" options=[", , ", " is even, is odd", " is prime, is composite, ", ", , "] answer=" is even, is odd" hint="Consider the definition of integers and the most basic way to partition them." solution="The parity split ( is even or is odd) covers all integers without overlap. While other options like modulo 3 are also exhaustive, parity is often considered the most fundamental and universally applicable for general integer proofs, as it directly relates to the definition of integers."
:::
:::question type="NAT" question="Given three distinct positive integers such that and . How many distinct sets are possible?" answer="4" hint="Systematically list possibilities for the smallest integer , applying all constraints at each step. Determine the maximum possible value for first." solution="We require to be distinct positive integers with and .
Since , the smallest possible values are , , .
Thus, , which implies , so , meaning .
Since is a positive integer, can only be 1 or 2.
Case 1: .
Then and .
If , then . Set: .
If , then . Set: .
If , then . Set: .
(If , then , which violates .)
Case 2: .
Then and .
If , then . Set: .
(If , then , which violates .)
Thus, there are 4 distinct sets: ."
:::
:::question type="MCQ" question="A proof states: 'If , then .' What hidden assumption, if any, makes this statement incomplete or potentially false in a general context?" options=["The domain of is real numbers.", "The problem implies must be positive.", "The value 9 is a perfect square.", "The equation has a solution." ] answer="The problem implies must be positive." hint="Consider all possible solutions to in the standard number system for ." solution="In the standard real number system, implies or . The statement 'If , then ' is only true if there's an implicit (hidden) assumption that must be positive (e.g., represents a length or magnitude). Without this hidden assumption, the statement is incomplete as it misses the case, making it potentially false as a general implication."
:::
What's Next?
Building on the systematic decomposition and logical rigor honed in this chapter, your CMI journey continues by formalizing these skills. 'Propositional and Predicate Logic' provides the foundational tools to precisely define and manipulate the conditions that form cases. 'Methods of Proof' integrates case analysis as a powerful technique for constructing rigorous arguments, especially when dealing with definitions involving multiple conditions or properties of integers. Finally, 'Combinatorics' extensively employs case analysis for exhaustive enumeration and classification, further solidifying your ability to approach complex problems systematically.