2.2 Engineering Design Process
Key Takeaways
- Engineering begins by defining a problem in terms of human needs or societal challenges, not by jumping straight to a favorite solution
- Criteria are measurable standards for success; constraints are limits on the design such as cost, materials, time, safety, or regulations
- Engineers generate multiple solutions, then build, test, and evaluate prototypes against the stated criteria
- Optimization improves a design through systematic modification and retesting; failure data reveal missed criteria and guide the next iteration
- Classroom engineering tasks should make criteria and constraints explicit so students can justify trade-offs
2.2 Engineering Design Process
Quick Answer: Praxis I.A.2 centers on the engineering design process: define the problem, specify criteria (measurable success standards) and constraints (limits such as cost, materials, time, and safety), generate and build solutions, test/evaluate against criteria, then optimize through systematic modification and retesting. Science explains nature; engineering designs solutions that work under real limits.
Engineering design is a systematic, iterative approach to solving problems under real-world limits. On Praxis Middle School Science (5442), Content Topics I.A expects you to distinguish engineering from pure scientific inquiry while recognizing that both rely on evidence, testing, and revision. Science often seeks to explain natural phenomena; engineering seeks to design solutions that meet human needs within constraints.
Define the Problem
Engineering starts with a clearly defined problem or need. A strong problem statement identifies:
- Who is affected (users or stakeholders)
- What is not working or what need is unmet
- Why a solution matters (impact, safety, efficiency, accessibility)
- The context in which the solution must operate
Weak problem statement: “Make a better bridge.” Stronger problem statement: “Design a model bridge that spans 40 cm, supports at least 2 kg at midspan, and can be built from no more than 50 craft sticks and glue in one class period so that teams can compare load performance fairly.”
Students should learn to avoid solution-first thinking (“Let’s use motors”) before the need is clear. Defining the problem frames every later decision.
Identify Criteria and Constraints
After defining the problem, engineers specify criteria and constraints. Mixing these up is a frequent exam and classroom error.
Criteria are the measurable attributes of a successful solution—the goals you score against. Criteria answer: “How will we know the design works well?”
Constraints are limitations on the design space—the boundaries you must respect. Constraints answer: “What are we not allowed to exceed or ignore?”
| Concept | Meaning | Question it answers | Classroom example |
|---|---|---|---|
| Criterion | Standard for success | Did the solution meet the goal? | Tower must hold 500 g for 30 seconds |
| Constraint | Limit on resources or conditions | What restricts the design? | Use only 20 index cards and 30 cm of tape |
Classroom examples that clarify the difference
Egg-drop device
- Criteria: Egg survives a 3-meter drop; landing zone accuracy within a 50 cm target; device mass under a preferred maximum if scored for “light and protective”
- Constraints: Budget of $3 in recycled materials; no glass; must fit in a 20 cm cube; completed in two class periods
Water filtration challenge
- Criteria: Reduce turbidity below a stated clarity level; produce at least 100 mL filtrate in 5 minutes; improve odor on a simple rating scale
- Constraints: Only sand, gravel, cotton, and charcoal from a kit; no proprietary filters; total column height ≤ 30 cm
Assistive grabber for a desk object
- Criteria: Pick up a 50 g block from 40 cm away; complete the task in under 15 seconds; require no more than two hands to operate
- Constraints: Materials limited to classroom craft supplies; no powered motors; sharp edges prohibited for safety
Notice that “must not cost more than $5” is a constraint, while “retrieve the object in under 15 seconds” is a criterion. Cost can sometimes be framed as a scored criterion (“lower cost earns more points”), but on Praxis items, treat limits imposed by resources, rules, or safety as constraints unless the prompt clearly scores them as success metrics.
Generate, Design, and Build Possible Solutions
Once criteria and constraints are clear, teams brainstorm multiple ideas before committing. Divergent thinking first (many options), then convergent thinking (select promising designs) reduces fixation on the first idea. Students may sketch, compare trade-offs, and choose a prototype approach.
Useful practices:
- Require at least two distinctly different concepts before building
- Check each concept against constraints early (eliminate impossible designs quickly)
- Plan how the prototype will be tested using the criteria
- Document materials and assembly so tests can be repeated
Engineering notebooks or design logs strengthen evidence-based iteration and mirror authentic engineering communication.
Test and Evaluate Solutions Against Criteria
Testing is not a celebration at the end; it is a measurement process tied to criteria. Evaluation asks:
- Which criteria were met, partially met, or missed?
- Which constraints were violated (if any)?
- What failure modes appeared (buckling, leaking, tipping, overheating)?
- How consistent were results across trials?
Example evaluation table for a model wind turbine blade set:
| Criterion | Target | Trial mean | Met? |
|---|---|---|---|
| Voltage output | ≥ 0.5 V in a box fan breeze | 0.42 V | No |
| Structural integrity | No blade cracks after 2 min | No cracks | Yes |
| Noise rating | ≤ 3 on 5-point scale | 2 | Yes |
Because voltage missed the target, the team has specific evidence for redesign rather than a vague sense that the device “didn’t work.”
Controlled testing matters in engineering just as in science: keep test conditions comparable (same drop height, same fan speed, same water sample) so differences can be attributed to design changes.
Optimize Through Systematic Modification and Testing
Optimization means improving a design by making deliberate changes and retesting, often balancing competing criteria. Real designs involve trade-offs: a thicker bridge deck may increase strength (good for load criterion) but increase material use (harder under a material constraint) or cost.
A systematic optimization cycle looks like this:
- Identify the unmet criterion or the most important trade-off
- Propose a single primary modification (or a small, documented set) based on evidence
- Rebuild or adjust the prototype
- Retest under the same conditions
- Compare new data to previous data and to criteria
- Repeat until criteria are met or constraints make further gains impractical
Random tinkering without recording changes is weak engineering practice. Systematic modification might vary one feature at a time—blade angle, number of supports, filter layer order—so cause-and-effect between change and performance is clearer.
Distinguishing Engineering Design from Scientific Inquiry
Both processes are iterative and evidence-based, but their aims differ:
| Feature | Scientific inquiry | Engineering design |
|---|---|---|
| Primary goal | Explain phenomena; answer questions about nature | Meet needs; create solutions that work under limits |
| Central products | Claims, models, theories supported by evidence | Prototypes/solutions evaluated against criteria |
| Success looks like | A well-supported explanation or prediction | A solution that satisfies criteria within constraints |
| Typical question | Why does this happen? What factors affect Y? | How can we design X to do Y under limits Z? |
In middle school classrooms, a unit may weave both: students investigate how insulation affects heat loss (science), then design a container that keeps water warm for 20 minutes using limited materials (engineering).
Teaching Moves That Align with Praxis Expectations
- Post criteria and constraints before building begins
- Score designs with rubrics tied to measurable criteria
- Require students to justify trade-offs in writing (“We reduced sail area to meet the size constraint even though it lowered speed”)
- Treat failed tests as data, not as student failure
- Emphasize iteration: first prototypes are starting points
When exam scenarios describe students building devices, look for whether they defined the problem, respected constraints, tested against criteria, and optimized with evidence. That sequence—define, specify, design, test, evaluate, improve—is the engineering design process Praxis 5442 targets.
A class must build a paper-tower that holds a textbook. The rules say teams may use at most 10 sheets of paper and 50 cm of tape, and the tower must support the book for at least 20 seconds. Which statement correctly classifies these requirements?
After testing, a student team’s bridge holds only 1.2 kg, but the criterion requires 2.0 kg. Which next step best represents optimization in the engineering design process?
Which activity is the best example of defining an engineering problem rather than asking a scientific research question?
A team’s water filter clears water quickly but leaves a strong odor. The criteria require both clarity and reduced odor within five minutes, and materials are limited to sand, gravel, cotton, and charcoal. What is the best evidence-based next move?