Printable · GCSE Higher · ages 14-16
Gradients and areas under graphs worksheet — GCSE Higher
Fifteen questions on "gradients and areas under graphs" — DfE statement A15. Print it, or print three versions so neighbours cannot copy by letter; the key gives the letter for each version.
Higher onlyNon-calculator
Answer key: Gradients and areas under graphs worksheet — GCSE Higher
MathsUKwww.geekhero.co.uk
- (b) The total volume of water, in litres, that has flowed in. — On a rate-time graph, the y-axis is in litres per minute and the x-axis is in minutes; multiplying a rate by a time gives litres per minute × minutes = litres, a total volume. So the area under the graph represents the total volume of water that has flowed in. Thinking the area itself represents the rate, rather than what the rate accumulates to, gives the wrong claim about the average rate of flow. Confusing the area with the gradient of the graph — which measures how the rate is changing — gives the wrong claim about litres per minute squared. Ignoring the flow-rate axis and focusing only on the time axis gives the wrong claim that the area is simply the total time.
- (c) Fastest at t = 2 min — steepest gradient. — The rate of cooling is given by the size (magnitude) of the gradient, ignoring its sign — the steeper the tangent, the faster the temperature is changing. Of −8, −3 and −0.5, the gradient −8 has the greatest magnitude, so the tea is cooling fastest at t = 2 minutes. 'Fastest at t = 20 min — largest gradient' confuses the signed value with the size of the rate: −0.5 is the largest NUMBER of the three, but it's the smallest in magnitude, meaning the tea is barely cooling at all by then. 'Cools at the same rate throughout' ignores that the three gradients are different sizes, not just all negative. 'Fastest at t = 10 min — the middle reading' isn't a mathematical reason at all — the gradients themselves have to be compared, not their position in the list.
- (b) 14 m/s — Average speed for a whole journey is total distance divided by total time: 350 ÷ 25 = 14 m/s. Multiplying the distance and time instead of dividing gives 350 × 25 = 8750 m/s. Adding the distance and time instead of dividing gives 350 + 25 = 375 m/s. Inverting the division, working out time divided by distance, gives 25 ÷ 350, which rounds to 0.07 m/s.
- (a) Underestimate: the chord lies below the curve — For a curve that is concave down (bending downward), the straight line joining any two points on the curve lies BELOW the curve. The trapezium's top edge is this straight line, so the trapezium's area is smaller than the true area under the curve — the trapezium rule UNDERESTIMATES the distance in this case. This is because a curve whose gradient keeps decreasing bends away from any chord joining two of its points, dropping the chord below every point of the curve in between. The reverse, a chord lying above the curve, is the rule for a concave-up curve, not this one — check which way the curve bends before deciding. The trapezium rule does not always overestimate or underestimate, and it is not exact except when the graph really is a straight line.
- (d) 300 m — For a constant speed, the speed-time graph is a horizontal line, and the area underneath is a rectangle: distance = speed × time = 15 × 20 = 300 m. Adding the two numbers instead of multiplying gives 35 m; dividing instead of multiplying gives 1.33 m; halving the product, as you would for a triangle, gives 7.5 m — but this section of the graph is a rectangle, not a triangle, so there is no halving to do.
- (d) Overestimate — the curve bends upward (convex). — The first differences of the speeds are 3, 5, 7 and 9, so the second differences are 2, 2 and 2 — constant and positive, which means the speed-time graph curves upwards (is convex). On a convex curve, each straight chord used by the trapezium rule lies above the curve, so the trapezium rule overestimates the true distance. 'Underestimate — the curve bends upward' states the same correct geometry but gets the conclusion backwards — a chord above the curve means too much area is counted, not too little. 'Overestimate — the speed values are increasing' uses the wrong evidence: increasing speed alone doesn't tell you whether the curve bends up or down, only the second differences do. 'Underestimate — second differences are constant' confuses a constant second difference with a steady rate of change in speed, which isn't what the second difference of a speed-time table measures.
- (c) 10 m/s — A symmetric chord gradient uses the two points either side of t = 3: (2, 40) and (4, 60). The gradient is the change in height divided by the change in time: (60 − 40) ÷ (4 − 2) = 20 ÷ 2 = 10 m/s. Using only the values either side of one gap, (2, 40) and (3, 54), instead of the full symmetric chord, gives (54 − 40) ÷ (3 − 2) = 14 m/s. Getting the correct number but dropping the time unit, leaving only metres, gives 10 m. Dividing time by height instead of height by time inverts the calculation to (4 − 2) ÷ (60 − 40) = 0.1 s/m.
- (b) 1.6 m/s² — Acceleration is the change in velocity divided by the time taken: (11 − 3) ÷ 5 = 8 ÷ 5 = 1.6 m/s². Forgetting to subtract the initial velocity and dividing the final velocity by the time instead gives 11 ÷ 5 = 2.2 m/s². Inverting the fraction, dividing the time by the change in velocity, gives 5 ÷ 8 = 0.625 m/s². Finding the change in velocity, 8 m/s, but stopping without dividing by the time gives 8 m/s².
- (a) Litres — The area under a graph is found by multiplying a y-value by an x-value, so its units are the y-axis units multiplied by the x-axis units: litres per minute × minutes = litres, since the 'per minute' cancels with the 'minutes'. Answering 'litres per minute' keeps the y-axis units unchanged, as if multiplying by time did nothing to the units at all. Answering 'litres per minute squared' treats the x-axis as also being measured 'per minute', squaring a unit that should instead cancel. Answering 'minutes' keeps only the x-axis units and drops the rate altogether.
- (a) Overestimates — trapezium edges lie above the curve. — For a concave-up curve, each chord connecting two points on the curve lies ABOVE the curve between those points, because the curve bends away from the chord underneath it. The trapezium rule uses these chords as the top edges of each trapezium, so the trapeziums cover a larger region than the true area under the curve — the estimate is an overestimate. Saying it underestimates because the edges lie below the curve gets the direction backwards: for a concave-up curve the edges lie above, not below. Saying it overestimates 'because more strips always increase it' gives the right verdict for the wrong reason — using MORE, narrower strips makes a trapezium estimate more accurate and brings it closer to the true area, it does not simply increase the total. Saying the estimate is exact ignores that straight edges cannot follow a curved line perfectly; there is always a gap between the chord and the curve on a bend, which is exactly what makes the rule an estimate rather than an exact calculation.
- (a) 4 — The gradient of a straight line through two points is the change in y divided by the change in x. Change in y = 21 − 5 = 16. Change in x = 6 − 2 = 4. Gradient = 16 ÷ 4 = 4. Dividing x by y instead of y by x gives 0.25; forgetting to divide by the change in x at all leaves 16; dividing by only one of the two x-coordinates, 16 ÷ 2 = 8, uses the wrong denominator.
- (a) −2 m/s² — The gradient of a line through two points is the change in the y-value divided by the change in the x-value: (6 − 22)/(16 − 8) = −16/8 = −2 m/s². The negative sign confirms the deceleration mentioned in the question. Writing 2 m/s² comes from subtracting the velocities in the wrong order, using (22 − 6) instead of (6 − 22), which loses the sign that shows the car is slowing down. Writing −0.5 m/s² comes from inverting the fraction, dividing the change in time by the change in velocity instead of the other way round. Writing −16 m/s² comes from finding the change in velocity, −16, but forgetting to divide by the change in time, 8 seconds.
- (d) 2 — The gradient between two points on a line is the change in y divided by the change in x. Using (5, 2) and (0, −8): (2 − (−8)) ÷ (5 − 0) = 10 ÷ 5 = 2. Inverting the fraction, dividing the change in x by the change in y instead, gives 5 ÷ 10 = 0.5. Reversing the order of the x-values in the denominator, giving (2 − (−8)) ÷ (0 − 5) = 10 ÷ (−5), gives −2. Misreading the y-intercept as 8 instead of −8, giving (2 − 8) ÷ 5 = −6 ÷ 5, gives −1.2.
- (d) 680 m — First find how long the acceleration takes: acceleration = change in speed ÷ time, so 2.5 = 20 ÷ t, giving t = 20 ÷ 2.5 = 8 seconds. The distance during this phase is the area of a triangle with base 8 and height 20: 1/2 × 8 × 20 = 80 m. The distance during the constant-speed phase is 20 × 30 = 600 m, since distance = speed × time at a constant speed. The total distance is 80 + 600 = 680 m. Using the given 30 seconds for the acceleration phase as well, 1/2 × 30 × 20 = 300, plus the correct 600, gives 900 m — but 30 seconds is only stated for the constant-speed phase. Leaving out the 1/2 and using the full rectangle for the acceleration phase, 8 × 20 = 160, plus the correct 600, gives 760 m — the speed is not constant during acceleration, so this area is a triangle, not a rectangle. Swapping the two times round, and using 8 seconds for the constant-speed distance instead of 30, 20 × 8 = 160, plus the correct triangle area of 80, gives 240 m.
- (b) 19 — A line through (x₁, y₁) with gradient m has equation y − y₁ = m(x − x₁). Substituting (6, 1) and m = −3: y − 1 = −3(x − 6), so y = −3x + 18 + 1, which simplifies to y = −3x + 19; at x = 0 this gives 19. Making a sign error when distributing, writing −3(x − 6) as −3x − 18 instead of −3x + 18, gives the wrong line y = −3x − 17, so −17 at x = 0. Forgetting to add the y₁ = 1 at the end, using y = −3(x − 6) alone, gives 18 at x = 0. Substituting the y-coordinate into the gradient term instead of using x, working out 1 + (−3 × 1), gives −2.
Build your own mix at the worksheet builder.