Bridge the gap between functions and inequalities! Learn to solve function inequalities, compare function values graphically, validate mathematical models with real data, and interpret solutions in practical contexts. Develop critical thinking skills for model evaluation.
Fundamental Connection: Solving is equivalent to finding where the graph of is above the graph of .
• Single function inequality: where c is a constant
• Two function comparison: for all x in domain
• Interval solutions: Express solutions as intervals where inequality holds
• Boundary points: Points where (intersection points)
Validation Process:
1. Data Collection: Gather real-world data points
2. Model Fitting: Determine model parameters from data
3. Prediction Testing: Use model to predict new values
4. Error Analysis: Compare predictions with actual values
5. Model Refinement: Adjust model based on validation results
Visual Problem-Solving:
• Intersection method: Find where graphs cross to determine boundary points
• Test point method: Choose points in different regions to determine solution sets
• Slope analysis: Use function slopes to predict behavior
• Domain restrictions: Consider practical limitations on variable values
Solve the inequality: using both algebraic and graphical methods.
Algebraic Method:
Graphical Method:
1. Graph (line with slope 2, y-intercept -1)
2. Graph (horizontal line at y = 3)
3. Find intersection: →
4. Since slope is positive (2 > 0), the line rises from left to right
5. For , the line is above
Solution: or in interval notation
Key Insight: For linear functions , the solution to depends on the sign of the slope m. If m > 0, solution is ; if m < 0, solution is .
Let and . Find all values of x for which .
Method 1: Algebraic Solution
Method 2: Graphical Analysis
1. Find intersection point: →
2. At intersection: , so point is (3, 3)
3. Analyze slopes: has slope 2 (rising), has slope -1 (falling)
4. For : (f is below g)
5. For : (f is above g)
6. For : (intersection point)
Solution: or in interval notation
Verification: Test x = 2: f(2) = 1, g(2) = 4, so f(2) < g(2) ✓. Test x = 4: f(4) = 5, g(4) = 2, so f(4) > g(4) ✓.
A phone's battery life follows the model where B is battery percentage and t is hours of use. Real data shows: t=1→85%, t=2→70%, t=3→55%, t=4→40%. Validate the model and find when battery ≥ 20%.
Step 1: Model Predictions vs. Actual Data
Model predictions: B(1) = 85%, B(2) = 70%, B(3) = 55%, B(4) = 40%
Actual data: 85%, 70%, 55%, 40%
Perfect match! Model appears accurate for this data range.
Step 2: Find when battery ≥ 20%
hours
Step 3: Validation Testing
Test t = 5: B(5) = -15(5) + 100 = 25% (above 20%)
Test t = 6: B(6) = -15(6) + 100 = 10% (below 20%)
Model predicts battery drops below 20% between 5 and 6 hours.
Step 4: Model Limitations
• Model assumes linear decline (may not hold for very low battery)
• Doesn't account for different usage patterns
• Battery behavior may change with age
• Temperature and other factors not considered
Practical Application: The phone should be charged before 5.33 hours of use to maintain battery above 20%. However, the model should be revalidated with more data points and different usage scenarios.
Two internet plans: Plan A costs $50/month + $1/GB, Plan B costs $30/month + $2/GB. For what data usage is Plan A more economical? Validate with actual usage data.
Step 1: Set up cost functions
Plan A: where x = GB used
Plan B: where x = GB used
Step 2: Find break-even point
At 20 GB, both plans cost $70.
Step 3: Determine when Plan A is cheaper
Plan A is cheaper when x > 20 GB.
Step 4: Validation with usage data
Monthly usage: 15 GB, 25 GB, 35 GB, 45 GB
At 15 GB: Plan A = $65, Plan B = $60 → Plan B cheaper
At 25 GB: Plan A = $75, Plan B = $80 → Plan A cheaper
At 35 GB: Plan A = $85, Plan B = $100 → Plan A cheaper
At 45 GB: Plan A = $95, Plan B = $120 → Plan A cheaper
Step 5: Practical recommendation
• If usage < 20 GB: Choose Plan B
• If usage > 20 GB: Choose Plan A
• If usage ≈ 20 GB: Either plan (same cost)
Decision Framework: The mathematical model provides a clear decision rule based on usage patterns. Users should track their actual usage over several months to make the optimal choice.
Quantitative Validation Methods:
• Mean Absolute Error (MAE):
• Root Mean Square Error (RMSE):
• Percentage Error:
• R-squared: Proportion of variance explained by the model
When functions have different behaviors in different intervals:
• Identify breakpoints: Points where function definition changes
• Solve each piece separately: Apply appropriate function rule
• Check continuity: Ensure function values match at breakpoints
• Combine solutions: Union of solution sets from each piece
Understanding how changes in parameters affect solutions:
• Parameter variation: Test how solutions change with different parameter values
• Robustness testing: Check if conclusions hold under uncertainty
• Scenario analysis: Consider best-case, worst-case, and most-likely scenarios
• Confidence intervals: Range of values within which true solution likely falls
Error: Solving function inequalities without considering practical domain limitations.
Solution: Always check if solutions make sense in the given context (e.g., negative time, impossible quantities).
Error: Creating models that fit training data perfectly but fail on new data.
Solution: Use cross-validation and test models on independent data sets.
Error: Using models to predict values outside the range of training data.
Solution: Clearly state model limitations and avoid predictions beyond observed data range.
Error: Assuming that mathematical relationships imply cause-and-effect relationships.
Solution: Distinguish between mathematical models and causal explanations.
Error: Treating all data points as equally reliable without considering measurement uncertainty.
Solution: Include error bars and uncertainty analysis in model validation.
Solve: and verify graphically.
Algebraic: →
Graphical: Graph y = 3x + 2 and y = 2x - 1, find intersection at x = -3
Solution: or
For and , find when .
Set up: →
Factor:
Solution: or
A car's fuel efficiency model is (mpg at speed v mph). Test data: (30, 38), (50, 50), (70, 38). Validate the model and find optimal speed.
Model predictions: E(30) = 38, E(50) = 50, E(70) = 38
Actual data: 38, 50, 38 - Perfect match!
Optimal speed: Vertex at v = 50 mph (maximum efficiency)
Two job offers: Job A pays $40,000 + $2,000 per year of experience, Job B pays $35,000 + $3,000 per year of experience. When is Job A better? Create a decision model.
Salary functions: A(x) = 40000 + 2000x, B(x) = 35000 + 3000x
Break-even: 40000 + 2000x = 35000 + 3000x → x = 5 years
Decision rule: Job A better if experience > 5 years