Grade by Grade
A. Design Processes and Related Skills · Design Skills: From Idea to Tested Prototype

Testing, Troubleshooting and Analyzing Performance

A3.1 A3.2 A1.5About 75 minutes
Learning goals
  • I can write a test plan that checks a product or service against each criterion with fair, repeated trials.
  • I can record test data and calculate the mean and range.
  • I can analyze performance by comparing results with the criteria.
  • I can use problem-solving strategies such as root-cause analysis, divide and conquer, and changing one variable at a time to solve challenges.

Words to know

test plan
A document that says what will be tested, how, how many times, and what result counts as a pass.
fair test
A test in which only one variable changes and everything else is kept the same.
trial
One run of a test. Repeating trials makes results more reliable.
mean
The average: the sum of the values divided by the number of values.
range
The difference between the largest and smallest values; it shows how spread out the results are.
root cause
The underlying reason a problem happens, not just its symptom.
troubleshooting
A step-by-step search for the cause of a problem and a fix.
failure mode
The way something fails, such as tipping, bending, leaking or crushing.

Does it actually work?

Amira's prototype looks great. Sami taps the screen to answer a call... and the stand tips backward. A design is only as good as its test results.

The curriculum asks you to identify challenges that come up during development and apply critical thinking skills to address them (A3.1), and to analyze the performance of a product or service using appropriate criteria (A3.2).

Remember from Grade 8

In Grade 8 science you ran fair tests, repeated trials and calculated values like mechanical advantage and efficiency from your data. Testing a design uses the same skills.

Writing a test plan

For each criterion, decide:

  1. What you will measure (the variable) and the unit.
  2. How you will measure it (tool, method, conditions), keeping everything else the same.
  3. How many trials (at least 3, so one odd result does not mislead you).
  4. Pass condition, copied from your criteria.

Example for the tablet stand: Tipping test: hook a spring scale (or an elastic-band force meter) to the top edge of the tablet and pull slowly backward, horizontal to the table. Record the force at the moment the stand starts to tip. 3 trials, same tablet, same table. Pass: mean ≥ 5 N.

Worked example

Analyzing test data

Amira's prototype v1 results: tipping force 4.5 N, 5.0 N, 4.6 N (criterion: mean ≥ 5 N). Time to change angle (Sami): 7 s, 5 s, 6 s (criterion: ≤ 5 s each). Comfort rating by Sami: 3/5 (criterion ≥ 4/5). Analyze the performance.

  1. Tipping force: mean = (4.5 + 5.0 + 4.6) ÷ 3 = 14.1 ÷ 3 = 4.7 N. Range = 5.0 − 4.5 = 0.5 N. The mean is below 5 N: fails.
  2. Angle change: mean = (7 + 5 + 6) ÷ 3 = 6 s. Only one trial met ≤ 5 s: fails.
  3. Comfort: 3/5 is below 4/5: fails. Ask why: Sami says the screen is too low and he has to lean forward.
  4. Failure modes: tipping backward when tapped; notches too shallow so the tablet needs to be lifted out to move it; screen too low.
  5. Conclusion: v1 is a good start (it holds the tablet and looks tidy) but misses three criteria. These become the challenges to solve.

v1 fails tipping (mean 4.7 N), angle change (mean 6 s) and comfort (3/5). Each failure has a measured gap to close.

Problem-solving strategies

When something fails, avoid random changes. Use a strategy:

  • Define the problem precisely: not "it's bad" but "it tips backward at 4.7 N when 5 N is needed".
  • Root-cause analysis (the 5 whys): keep asking why. Why does it tip? The tablet's weight acts behind the back feet. Why? The base is too short behind the back support. Why? I shortened it to save cardboard. Root cause: base too short.
  • Divide and conquer: split the system into parts and test each one to find where the problem is.
  • Change one variable at a time (a fair test), so you know which change made the difference.
  • Reverse engineering: take apart or study a product that works to see how it solves the problem.
  • Parts substitution: swap a suspect part for a known good one (a common method in transportation and computer repair).
  • Ask an expert or look in the manual.

Brainstorm several possible fixes and pick the one most likely to work with the least cost or risk.

Problem:stand slidesFeet attachedand clean?Fix: clean orre-stick feetnoyesSame on anothersurface?noCause: slipperytable → add a matyesFeet too small /hard → softer, widerRetest: 3 trialsand record
A troubleshooting flowchart uses divide and conquer: each question rules out one possible cause. Every path ends with a retest, because a fix is only a fix once the data says so.

Analyzing a service

Services are tested too. Ethan's class ran a practice booth with 10 customers and timed each wait.

02468target: 5mean: 4.713.5243645.554.567738495104.5customer number (practice run)wait (minutes)
Wait times for 10 customers in the booth's practice run. The mean (4.7 min) meets the target, but 3 of 10 customers (shaded yellow) waited longer than 5 minutes, so the criterion "each customer waits 5 minutes or less" is met only 70% of the time.
Worked example

Analyzing the booth's practice run

Wait times (min): 3.5, 4, 6, 5.5, 4.5, 7, 3, 4, 5, 4.5. Criterion: each customer waits 5 minutes or less. Analyze the results and identify the challenge.

  1. Sum: 3.5 + 4 + 6 + 5.5 + 4.5 + 7 + 3 + 4 + 5 + 4.5 = 47. Mean = 47 ÷ 10 = 4.7 min.
  2. Range = 7 − 3 = 4 min: the times are quite spread out.
  3. Count over 5 min: 6, 5.5 and 7 → 3 of 10, so the criterion was met for only 70% of customers.
  4. Look for patterns: the class's notes show the long waits happened when a customer paid with a large bill and the server had to find change.
  5. Root cause: one person both serves and makes change. Possible fixes: a separate cashier, a change float with plenty of coins, or prepaid tickets.

The mean looks fine, but 30% of customers waited too long. The data points to making change as the bottleneck.

Hands-on activity

Test your prototype

You need: your prototype from the last lesson (or any product at home, such as a phone stand, a lunch container or a chair), a ruler, a timer, a kitchen or luggage scale, an elastic band and a paper clip (to make a simple force meter, as in Grade 8), and a notebook. Ask an adult to help with any test that involves weights above the table edge, and keep feet out from under hanging loads. Elastic bands can snap: stretch them only a little and point them away from faces.

  1. Write a test plan for at least three criteria (what, how, trials, pass condition).
  2. Run three trials for each. Record the data in a table with units.
  3. Calculate the mean and range for each.
  4. Mark each criterion pass or fail.
  5. For one failure, do a 5 whys analysis and list three possible fixes.
  6. Ask your user (a family member) to rate it and explain their rating.

What to look for: a clear test plan, three trials per test, correct means and ranges, honest pass/fail decisions, and a root cause that goes deeper than the symptom.

Just for fun

A tester walks into a café. She orders 1 coffee. Then 0 coffees. Then 999 999 coffees. Then −1 coffees. Then a lizard.

Testers try unusual cases on purpose, because that is where products break.

Your turn

1

What four things should a test plan state for each criterion?

2

Find the mean and range: 12 s, 15 s, 9 s, 12 s.

3

Why run at least three trials?

4

A stand tips at 4.2, 4.6 and 4.4 N. The criterion is mean ≥ 4.5 N. Pass or fail?

5

What is the difference between a symptom and a root cause? Use the booth as an example.

6

Why should you change only one variable at a time when fixing a design?

7

Name the problem-solving strategy: a mechanic swaps a suspect battery for a known good one to see if the car starts.

More practice: warm-up

1

What is a fair test?

2

How do you calculate the mean?

3

What is a failure mode?

4

What does troubleshooting mean?

5

What is the range of 3, 8, 5?

More practice: on your own

1

Do a 5 whys for: "The cookies at the bake sale were burnt."

2

A booth practice run gives waits of 2, 3, 3, 4, 8 min. Mean? Does the mean tell the whole story?

3

Explain how divide and conquer would help find why a string of holiday lights does not work.

4

A team changes the base length, the feet and the angle at once, and the stand stops tipping. What is the problem with their conclusion?

5

Write a test plan for a qualitative criterion: "The instructions are easy to follow."

Challenge

1

Prototype A tips at 6.0, 6.2, 5.8 N. Prototype B tips at 7.5, 4.0, 6.5 N. Both have the same mean. Which is better and why?

2

Using the booth data, Ethan's class adds a cashier. New waits: 3, 4, 3.5, 4.5, 3, 4, 5, 3.5, 4, 3.5. Analyze the new performance.

3

A cardboard bridge model fails during a load test. Describe how you would use a test plan, failure mode analysis and one problem-solving strategy to improve it.

Check your understanding

Quiz

1.

Which is a fair test of three glue types?

2.

Mean of 4, 6, 8, 6?

3.

Tipping forces 5.2, 4.8, 5.0 N; criterion mean ≥ 5 N. Result?

4.

The 5 whys method is used to find...

5.

Swapping a suspect part for a known good one is called...

6.

Why is the range useful along with the mean?

For parents and teachers

Big idea: Expectation A3.1 asks students to identify challenges during development and apply critical thinking skills to address them; A3.2 asks them to analyze the performance of products or services using appropriate criteria (the criteria from A1.5).

How to help at home:

  • When something breaks at home, model troubleshooting aloud: "Is it plugged in? Does another outlet work? Is it the cord or the device?"
  • Be a willing test user and give honest ratings with reasons.

Common difficulties:

  • One trial only. Insist on at least three.
  • Looking only at the mean. Ask, "Did any single trial fail?"
  • Fixing symptoms. Ask "why?" at least three times.

Safety: keep feet and hands out from under any hanging loads during force tests, and use only light loads (a few water bottles at most).