Proofs Involving Disjunctions
Learning objectives
- Prove a disjunction by cases or by deriving one disjunct
- Use a disjunctive hypothesis by considering each case separately
- Apply proof by cases (case analysis) effectively
- Recognize when case analysis simplifies a proof
What do you do when a proof refuses to go through in one shot? You split the universe into cases that you can handle one at a time. Case analysis — the proof strategy for both proving and using disjunctions — is the universal "when in doubt, split" tactic. It turns a hard global argument into several easier local arguments, each of which only needs to handle a restricted situation. Done well, case analysis is elegant; done carelessly, it produces sprawling proofs that are correct but exhausting. This section teaches both the structural rule and the judgment of when to reach for it.
Proving a disjunction: two strategies
To prove , you have two options:
Strategy 1 — Establish one disjunct directly. Show that is true (or that is true). One disjunct suffices.
Strategy 2 — Assume and prove . This relies on the equivalence . By adding to your givens, you may get exactly the leverage needed to derive .
Strategy 2 is the workhorse. The equivalence is worth committing to memory: it turns "or" goals into conditional goals, which you already know how to attack.
Using a disjunctive given: proof by cases
If your givens include and your goal is , the standard strategy is proof by cases:
- Case 1: Assume . [Argue toward .] Conclude in this case.
- Case 2: Assume . [Argue toward .] Conclude in this case.
- Since and follows in both cases, holds.
Inside Case 1 you may use (and any earlier givens). Inside Case 2 you may use . The two arguments are independent: they share givens that precede the case split but not the case-specific assumption.
Three or more cases
Case analysis is not limited to two cases. To prove something about an integer , you might split:
• Even vs odd (mod 2) • • , ,
The cases must be exhaustive — they must cover every possibility — but need not be mutually exclusive (though disjoint cases produce cleaner proofs). State the case split explicitly: "either or ; we handle each case."
When to reach for case analysis
Use case analysis when the goal involves a function that is defined piecewise (absolute value, max/min, floor/ceiling), when a given is naturally disjunctive ( means ), or when a parity/sign distinction unlocks an otherwise sticky algebraic step. Avoid it when a single uniform argument works — case analysis is a tool of last resort because it bloats proofs. Two cases is fine; ten cases probably means you missed a unifying observation.
Common case splits in undergraduate proofs
- Parity: every integer is even or odd. Used in irrationality, divisibility, and number-theory proofs.
- Sign: , , . Standard for absolute-value arguments.
- Set membership: for a fixed , either or . Used in set-equality proofs.
- Modular arithmetic: . Used to prove divisibility identities like .
Pause and think: To prove "for every integer , is even," the parity split is irresistible. Why? What concrete identity falls out of each case?
Try it
- Predict the case split before writing: which natural disjoint cases would you use for (a) "prove is even for all integers ," (b) "prove for real ," (c) "prove every integer is the sum of two integers of the same parity"?
- Spot the flaw: a student writes "Case 1: is even. ... Case 2: is positive. ... Both cases handled, done." What went wrong?
- Disjunction goal: prove using Strategy 2 (assume the negation of one disjunct, derive the other).
- Skeleton-only: write the first sentence of each case for "for every integer , either or ."
- When NOT to use cases: rewrite "prove that for all integers , " without any case split. (Hint: a single observation suffices.)
A trap to watch for
The most insidious case-analysis error is non-exhaustive cases: splitting into Case 1 and Case 2 in a way that misses some scenarios. "Case 1: . Case 2: " forgets . "Case 1: is prime. Case 2: is composite" forgets and negative integers. Before declaring the proof complete, list your cases and verify they cover every possibility implied by the domain. A close cousin is overlapping cases that you treat as exclusive — harmless if the conclusion is the same in the overlap, but a source of subtle bugs otherwise. Best practice: aim for disjoint and exhaustive cases, and say so explicitly.
What you now know
You can prove a disjunction by establishing one disjunct or by the equivalence-trick of assuming and deriving . You can use a disjunctive given by case analysis — one sub-argument per case, with the cases exhaustive and (ideally) disjoint. You recognise common case splits (parity, sign, residue, membership) and you know when case analysis is the right tool versus when a uniform argument is cleaner. Combined with the conditional, quantifier, and biconditional strategies from earlier sections, you now have the full toolkit for the bulk of undergraduate-level proofs.
References
- Velleman, D. J. (2019). How to Prove It: A Structured Approach (3rd ed.). Cambridge University Press, §3.5.
- Hammack, R. (2018). Book of Proof (3rd ed.). Open-source textbook, ch. 7 (Cases).
- Solow, D. (2014). How to Read and Do Proofs (6th ed.). Wiley, ch. 11 (Cases).
- Pierce, B. C. et al. (2018). Software Foundations, Vol. 1: Logical Foundations. Online textbook (Coq), ch. 'Logic' (or destruct, case tactic).
- Bloch, E. D. (2011). Proofs and Fundamentals. Springer, §3.4 (Proof by cases).