๐งฉDiscrete Mathematics
Proof Techniques
Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Why This Matters
Proof techniques are the backbone of discrete mathematics and of all rigorous mathematical thinking. You're not just being tested on whether you can recite definitions; you're being tested on whether you can construct valid arguments and recognize which proof strategy fits which situation. Every theorem you encounter in this course was established using one of these techniques, and exam questions frequently ask you to either write proofs yourself or identify the method being used in a given argument.
Different proof techniques exploit different logical structures. Some work by building forward from assumptions, others by working backward from contradictions, and still others by systematic case analysis. Don't just memorize the names. Know when each technique is your best tool and why. If you can identify the logical structure of a claim, you can select the right proof strategy almost automatically.
Forward-Building Proofs
These techniques work by starting from what you know and logically progressing toward what you want to prove. They follow the natural direction of implication.
Direct Proof
A direct proof assumes the hypothesis and derives the conclusion. It's the most straightforward approach for statements of the form "If , then ."
The process looks like this:
- Assume is true.
- Unpack what means using definitions (e.g., if says " is even," write for some integer ).
- Apply logical steps, algebraic manipulation, or known theorems.
- Arrive at the conclusion .
Best choice when the path forward is clear. If you can see how to get from hypothesis to conclusion, don't overcomplicate it by reaching for an indirect method.
Proof by Construction
This technique explicitly builds the object whose existence you're claiming. It's used for statements like "There exists an such that ."
Rather than arguing abstractly that something must exist, you provide a concrete example or an algorithm that produces the desired object. This is common in combinatorics and algorithm design. For instance, to prove there exists a graph with 5 vertices where every vertex has degree 2, you'd just draw a 5-cycle and verify it works.
Proof by Equivalence
This technique proves two statements are logically equivalent by showing both and . It establishes "if and only if" (often written "iff") relationships, and both directions must be proven separately.
The two directions often call for different strategies. You might use a direct proof for one direction and contraposition for the other.
Compare: Direct Proof vs. Proof by Construction. Both build forward, but direct proof establishes that something must be true, while construction proves something exists by producing it. If a problem says "prove there exists," construction is your go-to.
Indirect Proofs
When the direct path is blocked, these techniques take a detour. They leverage logical equivalences or the impossibility of contradictions.
Proof by Contradiction
This technique assumes the negation of what you want to prove and derives a logical impossibility. If leads to absurdity, then must be true.
Here's the structure:
- Assume, for the sake of contradiction, that the statement you want to prove is false.
- Reason logically from that assumption.
- Arrive at a statement that contradicts a known fact, a given hypothesis, or the assumption itself.
- Conclude the original statement must be true.
The classic example is proving is irrational: you assume it is rational, write it as in lowest terms, and eventually show both and must be even, contradicting "lowest terms."
This technique is especially powerful for "there is no..." or uniqueness claims, where the negation gives you a concrete object to manipulate.
Proof by Contraposition
This technique proves "If , then " by instead proving "If , then ." These two statements are logically equivalent: .
It's ideal when the negation gives you more to work with. For example, proving "if is even, then is even" directly is awkward, but the contrapositive "if is odd, then is odd" flows naturally: write , square it, and factor out the 2.
Compare: Contradiction vs. Contraposition. Both are indirect, but contraposition proves the equivalent contrapositive statement using a standard forward argument, while contradiction assumes the opposite and derives impossibility. Use contraposition when you can clearly work with ; use contradiction when you need to show something simply cannot be.
Case-Based Proofs
These techniques handle complexity by breaking it into manageable pieces. They ensure no scenario is overlooked.
Proof by Cases
This technique partitions the problem into exhaustive, mutually exclusive scenarios and proves the statement holds in each case separately. For example, proving a property for all integers by handling even and odd cases separately.
Two requirements are non-negotiable:
- Exhaustive: Your cases must cover every possibility. If you miss a case, the proof is incomplete.
- Each case must be proven: You need a valid argument within every case, not just a claim.
Proof by Exhaustion
This technique checks every single instance when the total number of cases is finite and small. It guarantees completeness through brute force.
This is common in proofs involving small sets or specific numerical bounds (e.g., verifying a property for all integers between 1 and 10). For larger case counts, exhaustion is often computer-assisted. The Four Color Theorem famously required exhaustive computer verification of hundreds of configurations.
Compare: Proof by Cases vs. Proof by Exhaustion. Cases divide by type (like even/odd), while exhaustion checks every individual instance. Use cases when there's a natural partition; use exhaustion when you can literally enumerate all possibilities.
Inductive Reasoning
Mathematical induction is a specialized technique for proving statements about infinite sequences, particularly those indexed by natural numbers. It works by establishing a domino effect.
Mathematical Induction
Every induction proof has two parts:
- Base case: Verify the statement holds for your starting value (usually or , depending on the problem).
- Inductive step: Assume is true (this assumption is called the inductive hypothesis), and use it to prove .
The inductive hypothesis is your leverage. You're not assuming what you're trying to prove; you're assuming one case to establish the next, like pushing over one domino to topple the next.
Variants:
- Strong induction assumes for all (not just ) when proving . Use this when depends on multiple previous cases, not just the immediate predecessor. For example, proving every integer has a prime factorization requires strong induction because you might factor into parts much smaller than .
- Structural induction applies to recursively defined objects like trees, strings, or formulas. The base case handles the simplest structure, and the inductive step shows the property is preserved by each recursive construction rule.
Compare: Standard Induction vs. Strong Induction. Standard assumes only to prove , while strong assumes all at once. Both are logically equivalent in power, but strong induction is often easier to apply when the recursive structure doesn't depend on just the previous case.
Disproving and Limiting Claims
Not every proof establishes truth. Sometimes you need to show a claim is false or reveal fundamental limitations.
Proof by Counterexample
A single specific instance where a universal claim fails is enough to destroy it. If someone claims "all primes are odd," just point to .
Your counterexample must genuinely satisfy the hypothesis while violating the conclusion. Be precise: clearly state the example, verify it meets the conditions of the claim, and show where the claimed conclusion breaks down.
Proof by Diagonalization
This technique constructs an element guaranteed to differ from every item in a supposed complete list. It's used to show certain sets are uncountable or certain problems are undecidable.
Cantor's diagonal argument is the classic example. Suppose you could list all real numbers between 0 and 1. Cantor constructs a new real number by changing the th digit of the th number in the list, guaranteeing this new number differs from every listed number in at least one decimal place. This contradicts the assumption that the list was complete, proving the reals are uncountable.
The same core idea appears in computability theory to prove the Halting Problem is undecidable.
Compare: Counterexample vs. Diagonalization. Counterexample disproves a specific claim with one instance, while diagonalization proves structural impossibility (like "no enumeration can capture all reals"). Diagonalization is a specialized tool; counterexample is your everyday falsification method.
Quick Reference Table
| Concept | Best Examples |
|---|---|
| Forward-building proofs | Direct Proof, Proof by Construction, Proof by Equivalence |
| Indirect proofs | Proof by Contradiction, Proof by Contraposition |
| Case-based reasoning | Proof by Cases, Proof by Exhaustion |
| Infinite sequences | Mathematical Induction (standard and strong) |
| Disproving claims | Proof by Counterexample |
| Uncountability/limits | Proof by Diagonalization |
| Existence statements | Proof by Construction, Proof by Contradiction |
| "If and only if" statements | Proof by Equivalence |
Self-Check Questions
-
You need to prove "If is even, then is even." Would direct proof or contraposition be more efficient, and why?
-
What do Proof by Contradiction and Proof by Contraposition have in common, and what's the key difference in how they reach their conclusions?
-
A classmate claims "All functions from to can be listed." Which proof technique would you use to refute this, and what's the core idea?
-
When proving a statement about all natural numbers using induction, what happens to your proof if you establish the inductive step but forget the base case?
-
Compare Proof by Cases and Proof by Exhaustion: give an example of a claim where you'd use cases and another where exhaustion would be necessary.