You're staring at a coordinate plane. And shading spreads across two quadrants like spilled ink. On top of that, two lines cut across it — one solid, one dashed. And the question on the worksheet just says: Which system of inequalities is shown by the graph?
Your brain freezes. Does the dashed line mean "greater than" or "less than"? Consider this: is that line y = 2x + 1* or y = 2x - 1*? And why does the shading go that* way?
Take a breath. It's a process. This isn't magic. And once you see the pattern, you'll wonder why it ever felt confusing.
What Is a System of Inequalities Graph
A system of inequalities graph shows all the points that satisfy two or more inequalities at the same time. So think of it like a Venn diagram drawn on a coordinate plane. Which means each inequality carves out a region. The solution to the system is where those regions overlap.
The graph gives you three visual clues:
- The boundary lines — the edges of each inequality
- The line style — solid or dashed — telling you whether the boundary counts
- The shading — showing which side of each line belongs to the solution
That's it. Three pieces of information. Your job is to translate them back into algebraic symbols. It's one of those things that adds up.
One Inequality, Two Halves
Every linear inequality splits the plane in two. The line itself is the border. The other side makes it false. One side makes the inequality true. The shading shows you the "true" side.
When you have a system, you're looking for the neighborhood where every* inequality is true simultaneously. That's the overlap. The intersection. The region that survives all the filters.
Why This Skill Actually Matters
You might wonder: when will I ever look at a graph and need to reverse-engineer the inequalities?
More often than you'd think.
In linear programming — the math behind optimization — you're given constraints as inequalities. Maybe a colleague sketched it. Maybe it came from software. But sometimes you start* with the graph. Also, the feasible region is that overlapping shaded area. Practically speaking, maybe you're checking your own work. You graph them. You need to read the graph and write the system.
Standardized tests love this too. Plus, the SAT, ACT, and state assessments regularly show a shaded region and ask for the matching system. It's a favorite because it tests multiple skills at once: slope-intercept form, inequality symbols, line types, test points.
And honestly? It's a great check on your own understanding. Still, if you can go from* graph to system, you actually get what the symbols mean. You're not just following steps. You're reading the language.
How to Read the Graph
Let's break this down into a repeatable process. Plus, no guessing. No hoping.
Step 1: Identify Each Boundary Line
Find every line that forms an edge of the shaded region. Ignore the axes unless they're part of the system (they usually aren't, unless you see x ≥ 0* or y ≥ 0* explicitly).
For each line, you need two things: the slope and the y-intercept. Write the equation in slope-intercept form: y = mx + b*.
Pro tip: Pick two clear points on the line. Integer coordinates are your friend. Count rise over run. If the line goes through (0, 2) and (3, 5), that's a rise of 3 over a run of 3. Slope = 1. Y-intercept = 2. Equation: y = x + 2*.
Do this for every* boundary line. Don't skip. Don't assume.
Step 2: Solid or Dashed? That's Your Symbol
This is where a lot of points get lost.
- Solid line → the boundary is included* → use ≤ or ≥
- Dashed line → the boundary is excluded* → use < or >
Think of it like a fence. Solid fence? But you can stand on it. Dashed fence? It's a warning line — stay off.
Step 3: Which Way Does the Shading Go?
Now you know the line equation and the line type. You still need the direction: less than* or greater than*?
Pick a test point not on the line. The origin (0, 0) is perfect unless* the line passes through it. Plug the test point into the inequality form of your line equation.
Say your line is y = x + 2* and it's solid. Test (0, 0):
- Is 0 ≤ 0 + 2? Yes, 0 ≤ 2 is true.
- Since the test point makes it true, and (0, 0) is in the shaded region → the inequality is y ≤ x + 2.
If (0, 0) had been outside* the shading, the answer would be y ≥ x + 2.
Wait — what if the line goes through the origin? Pick (1, 0) or (0, 1) or (-1, 0). Any point not on the line works. Just be consistent.
Step 4: Write the System
Once you have each inequality, combine them with curly braces or the word "and." That's your system.
Example:
- Line 1: solid, y = 2x - 1*, shading below → y ≤ 2x - 1
- Line 2: dashed, y = -x + 4*, shading above → y > -x + 4
System:
Want to learn more? We recommend how to find percentage of a number between two numbers and what are the function of mitosis for further reading.
{ y ≤ 2x - 1
{ y > -x + 4
Done. That's the whole process.
Writing the Inequalities from the Graph
Let's go deeper on the two trickiest parts: finding the line equation and choosing the symbol.
Finding the Line Equations
You've got the graph. The lines are drawn. Now you need y = mx + b*.
Slope (m): Count boxes. Rise over run. Up is positive. Down is negative. Right is positive. Left is negative. If you go up 2 and right 3, slope = 2/3. If you go down 4 and right 2, slope = -2.
Y-intercept (b): Where does the line cross the y-axis? That's b. If it crosses at -3, then b = -3*.
Watch for scale. The grid might count by 2s. Or 5s. Or the axes might not even be labeled the same. Always check the tick marks. I've seen students write y = 2x + 1* when the line actually crossed at (0, 2)
Step 5: Double‑Check Your Work
A quick sanity check can save you from a whole pile of headaches later.
- Re‑plot the inequalities on a fresh sheet. If the shading looks right, you’re good.
- Test a point on each boundary (besides the origin). Plug it into the inequality—if the inequality is strict (< or >), the point should not satisfy it; if it’s inclusive (≤ or ≥), the point should satisfy it.
- Check the intersection of the two boundaries. If the graph shows a single point of overlap, your inequalities should both be satisfied exactly at that point.
Common Pitfalls to Avoid
| Pitfall | What Happens | Fix |
|---|---|---|
| Using the wrong sign (e.Here's the thing — g. , ≤ instead of ≥) | The shaded region flips, leading to the wrong solution set. Now, | Remember: solid line = inclusive; dashed = exclusive. Think about it: |
| Misreading the slope | The line equation is wrong, so the entire system is off. | Count the boxes carefully; double‑check with two points. |
| Choosing a test point on the line | The inequality test becomes meaningless. Now, | Pick a point off the line—anywhere in the shaded or unshaded area. Now, |
| Ignoring the axis scale | Slopes and intercepts are off because the grid isn't unit‑based. | Read the tick marks; adjust calculations accordingly. |
Putting It All Together
Let’s walk through a full example that incorporates everything we’ve covered.
The Graph
-
Boundary 1: Solid line through (0, ‑1) and (2, 1).
Slope*: rise = 2, run = 2 → (m = 1).
Equation*: (y = x - 1).
Shading*: below the line (since the origin (0, 0) satisfies (0 \le 0 - 1) is false, we need (y \ge x - 1) for the shaded side). Actually test (0, ‑2): (-2 \le -1) true → shading below → (y \le x - 1). -
Boundary 2: Dashed line through (1, 3) and (4, 0).
Slope*: rise = ‑3, run = 3 → (m = -1).
Equation*: (y = -x + 4).
Shading*: above the line (test (0, 5): (5 > 4) true). Since the line is dashed, the boundary itself is excluded, so (y > -x + 4).
Final System
{ y ≤ x - 1
{ y > -x + 4
Graphically, the solution is the region that lies below the solid line (y = x - 1) and above the dashed line (y = -x + 4). The intersection of these two half‑planes is the shaded area you see in the diagram.
Visualizing in Higher Dimensions
If you’re tackling systems with three variables, the same principles apply. You’ll be dealing with planes instead of lines, but:
- Find the plane equation: (ax + by + cz = d).
- Decide solid vs dashed: solid plane means the inequality includes the plane; dashed means it doesn’t.
- Choose a test point in 3‑D space (often the origin works unless it's on a plane).
- Determine the shading direction: check if the test point satisfies the inequality; if yes, shade that side, otherwise shade the opposite side.
The algebra gets a bit heavier, but the logic chain remains identical.
The Take‑Away: A Quick Reference Checklist
| Step | What to Do | Why It Matters |
|---|---|---|
| 1. Determine inclusion | Solid = inclusive, dashed = exclusive | Controls the inequality symbol |
| 4. Write equations | Use two points → (y = mx + b) (or (ax + by + cz = d)) | Gives algebraic form |
| 3. Identify boundaries | Locate all lines/planes | Sets the stage for equations |
| 2. Pick a test point | Not on the boundary | Reveals shading direction |
| 5. Formulate inequalities | Combine with “and” or braces | Final system |
| 6. |
Final Thoughts
Mastering the translation from a shaded graph to a system of inequalities is like learning a new language. At first, the symbols and signs may feel foreign, but once you internalize the process—identify, equation, symbol, test, combine—you’ll find that every shaded region has a concise algebraic description waiting beneath it.
Think of each inequality as a gate: the line or plane is the fence, the solid or dashed line tells you whether the fence is a wall or a warning sign, and the test point tells you which side of the fence you’re allowed to step onto. With practice, you’ll be able to read any shaded diagram and write its corresponding system in a snap, turning visual intuition into algebraic precision.
