Reasonable domain: The set of input values that make practical sense in the real-world situation.
Reasonable range: The set of output values that correspond to the reasonable domain.
- Identify the real-world constraints
- Determine the minimum and maximum possible values
- Consider physical limitations
- Account for business or operational constraints
- Verify that values make practical sense
- Express results in appropriate notation
Business scenario: selling t-shirts for $12 each
Store sells between 50 and 200 t-shirts per day
Cannot sell negative t-shirts: x ≥ 0
Store capacity limits sales: x ≤ 200
Store expects minimum sales: x ≥ 50
Based on business constraints: 50 ≤ x ≤ 200
Domain: [50, 200]
At x = 50: R(50) = 12(50) = $600
At x = 200: R(200) = 12(200) = $2400
Since R(x) = 12x is increasing, range is [R(50), R(200)]
Range: [$600, $2400]
| T-shirts Sold (x) | Revenue R(x) = 12x |
|---|---|
| 50 (min) | $600 |
| 100 | $1200 |
| 150 | $1800 |
| 200 (max) | $2400 |
Range: [$600, $2400]
Reasonable domain: [50, 200] t-shirts per day. Reasonable range: [$600, $2400] in daily revenue.
• Context matters: Real-world constraints limit the domain
• Physical limits: Cannot have negative quantities
• Business constraints: Operational limits affect domain
Physics context: The time period during which the physical event occurs and the corresponding heights.
Ball is thrown upward and eventually falls back to ground
Only consider time when ball is in flight (h ≥ 0)
Set h(t) = 0: -16t² + 32t + 10 = 0
Using quadratic formula: t ≈ 2.28 seconds
Ball starts at t = 0 (thrown)
Ball ends at t ≈ 2.28 (lands)
Domain: [0, 2.28]
Vertex occurs at t = -b/(2a) = -32/(2×(-16)) = 1 second
Maximum height: h(1) = -16(1)² + 32(1) + 10 = 26 feet
Minimum height: 0 (ground level)
Maximum height: 26 feet (at vertex)
Range: [0, 26]
| Time (t) | Height h(t) |
|---|---|
| 0 (start) | 10 ft |
| 1 (max) | 26 ft |
| 2.28 (end) | 0 ft |
Range: [0, 26] feet
Reasonable domain: [0, 2.28] seconds (ball in flight). Reasonable range: [0, 26] feet (height above ground).
• Physics constraints: Ball exists only when above ground
• Time direction: Only forward time is relevant
• Maximum height: Occurs at vertex of parabola
Resource management: Context where a finite resource is consumed over time, imposing natural constraints.
Water tank starts with 500 gallons
Water is drained at 25 gallons per hour
Cannot have negative water in tank
Set W(t) = 0: 500 - 25t = 0
25t = 500
t = 20 hours
Start time: t = 0 (initial state)
End time: t = 20 (tank empty)
Domain: [0, 20]
Initial water: W(0) = 500 gallons
Final water: W(20) = 0 gallons
Since function is decreasing: Range is [0, 500]
Cannot drain beyond empty tank: W(t) ≥ 0
Cannot have negative time: t ≥ 0
Function makes sense only within these limits
| Time (t) | Water W(t) |
|---|---|
| 0 (start) | 500 gal |
| 10 (half) | 250 gal |
| 20 (empty) | 0 gal |
Range: [0, 500] gallons
Reasonable domain: [0, 20] hours (until tank is empty). Reasonable range: [0, 500] gallons (amount of water in tank).
• Finite resources: Cannot go below zero
• Consumption rate: Rate determines when resource is depleted
• Non-negativity: Physical quantities cannot be negative
Complete Summary: Reasonable Domain and Range in Real-World Contexts
Reasonable domain: The set of input values that make practical sense in the real-world situation, considering constraints.
Reasonable range: The set of output values that correspond to the reasonable domain, considering real-world constraints.
Contextual constraints: Physical, business, or logical limitations that restrict the domain and range.
Mathematical vs. reasonable: Mathematical domain/range may be broader than reasonable domain/range.
Practical sense: Values that make logical and physical sense in the given scenario.
Physical constraints: Quantities like time, length, and amounts cannot be negative.
Resource limitations: Finite resources impose upper or lower bounds.
Operational constraints: Business or system limitations affect possible values.
Logical constraints: Values must make sense in the real-world scenario.
• Upper limits: capacity, budget, maximum capacity
• Lower limits: minimum requirements, thresholds
• Integer values: discrete quantities
• Physics: motion, energy, force functions
• Resource: consumption, inventory, supply functions
• Geometry: area, volume, dimension functions
• Determine physical/logical constraints
• Consider business/system limitations
• Verify practicality of values
| Context | Typical Constraints | Domain Example | Range Example |
|---|---|---|---|
| Age | Cannot be negative | [0, 120] | Varies |
| Money | Cannot be negative | [0, budget] | [0, total] |
| Count | Must be whole number | [0, capacity] | [0, total] |
| Time | Forward direction | [start, end] | [min, max] |
Domain: {0, 1, 2, 3, ...} (non-negative integers)
Cannot have negative or fractional people
Domain: [-273.15, ∞) (absolute zero)
Practical: [-50, 50] for most applications
Domain: [0, speed_limit] (cannot exceed legal limit)
Range: [0, max_speed] (depends on road conditions)
Method 1 - Physical Constraints: Identify what's physically possible
Method 2 - Business Constraints: Consider operational limitations
Method 3 - Logical Constraints: Determine what makes sense
Method 4 - Mathematical Verification: Check that values are valid
- Read the problem carefully: Understand the real-world scenario
- Identify variable meanings: What do x and y represent?
- Determine physical constraints: What limits are imposed?
- Consider business/system limits: Are there operational constraints?
- Establish reasonable domain: Based on all constraints
- Calculate reasonable range: Corresponding output values
• Always consider the real-world meaning of variables
• Physical quantities typically cannot be negative
• Finite resources impose upper bounds
• Operational systems have capacity limits
Contextual Analysis Workflow
Questions & Answers
Question: How do I know if I'm being too restrictive with the domain?
Answer: To avoid being too restrictive:
- Stick to stated constraints: Only apply limitations explicitly mentioned in the problem
- Consider physical possibility: What's actually possible in the real world?
- Be realistic: Don't add personal assumptions beyond what's stated
- Check mathematical validity: Ensure the function is defined for your domain
If the problem states "up to 100 items," use [0, 100]. Don't add other restrictions.
Question: Can the reasonable domain be different from the mathematical domain?
Answer: Yes, absolutely! The relationship is:
- Mathematical domain: All values where the function is mathematically defined
- Reasonable domain: Subset of mathematical domain that makes practical sense
- Example: For f(x) = √x, mathematical domain is [0, ∞), but if x represents number of cars, reasonable domain might be {0, 1, 2, 3, ...}
The reasonable domain is always contained within the mathematical domain.
Question: How do I handle constraints that aren't explicitly stated?
Answer: Use common sense for implicit constraints:
- Physical impossibilities: Negative time, distance, or quantities
- Real-world limitations: Capacity, budget, time constraints
- Context clues: The scenario itself suggests reasonable bounds
- Logical consistency: Values that make sense in the situation
For example, if modeling people in a room, you wouldn't consider negative or fractional people.