Read

Engineering Design: Solving Real Problems

This lesson shows how students apply mathematical reasoning, such as averages, ratios, and data comparison, to the engineering design process. It covers setting measurable criteria, building prototypes, testing designs, analyzing numeric results, and refining a solution through repeated cycles.

Introduction

Engineering design is the process of using evidence and math reasoning to solve a real problem. Instead of guessing which idea will work best, engineers set measurable goals, build prototypes, test them, and use numbers to decide what to improve. This lesson focuses on how math, including averages, ratios, and data comparison, drives every stage of that process.

What Is the Engineering Design Process?

The engineering design process is a repeating cycle, not a single straight line. A team identifies a problem, sets criteria for success, brainstorms ideas, builds a prototype, tests it, and studies the results. If the data shows the design is not good enough, the team goes back and revises it. This loop can happen many times before a final solution is reached.

The engineering design cycle repeats until the data shows the solution meets its criteria.

Step 1: Define Measurable Design Criteria and Constraints

Good engineering starts with numbers, not opinions. Design criteria describe exactly what a solution must do, stated in measurable terms. For example, if a problem is food waste in a cafeteria, a criterion might be "reduce waste by at least 30 percent" rather than just "make less waste."

Constraints are the limits the solution must work within, such as a maximum budget, a time limit, or a maximum size or mass. A good solution satisfies the criteria while staying inside every constraint. Writing criteria and constraints as numbers makes it possible to test a design fairly later on.

Step 2: Brainstorm, Then Build a Prototype

Once criteria and constraints are set, students brainstorm several possible solutions without judging them right away. The strongest ideas are then turned into prototypes, which are simple models built to be tested and improved. A prototype does not need to be perfect. Its job is to show whether an idea works before time and materials are spent on a final version.

Step 3: Test and Collect Data

Testing is where math reasoning becomes essential. Instead of testing a prototype once, engineers run several trials, because a single result can be affected by chance. Suppose three paper bridge designs are tested for how much load, in grams, each can hold before it bends.

Design A is tested three times and holds 140, 150, and 160 grams. Design B holds 210, 220, and 230 grams. Design C holds 170, 180, and 190 grams. Collecting repeated trials like this gives a more reliable picture than trusting just one test.

Average load held by three prototype bridge designs across repeated trials.

Step 4: Use Math to Analyze the Results

To compare designs fairly, students calculate the average, or mean, of the trials for each prototype using \( \bar{x} = \dfrac{\sum x}{n} \), where \( \sum x \) is the sum of the trial results and \( n \) is the number of trials.

For Design A, \( \bar{x} = \dfrac{140 + 150 + 160}{3} = 150 \) grams. For Design B, \( \bar{x} = \dfrac{210 + 220 + 230}{3} = 220 \) grams. For Design C, \( \bar{x} = \dfrac{170 + 180 + 190}{3} = 180 \) grams. Based on average load alone, Design B performs best.

But raw load is not the only factor. Suppose Design B also has the greatest mass, at 40 grams, compared to 25 grams for Design A. A strength to weight ratio, \( \dfrac{220}{40} = 5.5 \) for Design B versus \( \dfrac{150}{25} = 6 \) for Design A, shows Design A actually uses its material more efficiently. Comparing more than one ratio helps students make a decision based on evidence rather than a single number.

Step 5: Refine the Design Through Iteration

Data rarely points to a finished solution right away. If a design fails to meet its criteria, students look for patterns in the test data to decide what to change. Maybe the weakest part of the bridge always bends in the same spot, which tells the team exactly where to add support. The design is rebuilt, tested again, and the new data is compared to the old data. This cycle of testing, analyzing, and rebuilding is called iteration, and it continues until the solution meets its design criteria within its constraints.

Key Terms

Design Criteria: Specific, measurable requirements a solution must meet.

Constraints: The limits a solution must work within, such as cost, time, or mass.

Prototype: An early, testable model of a possible solution.

Trial: One test of a prototype, repeated to check for reliable results.

Average (Mean): The sum of a set of results divided by how many results there are.

Ratio: A comparison of two quantities, such as strength compared to mass.

Iteration: Repeating the test and refine cycle to improve a design.

Data: The numbers and measurements collected from testing a prototype.

Related lessons

Innovation And Design Proposing Solutions