English:The Engineering Design Process
The Engineering Design Process
Introduction
The Engineering Design Process is a way to solve problems by thinking, making, testing, and improving. Engineers use design processes to create and improve objects, systems, tools, buildings, software, and many other solutions. You can use the same kind of thinking in school when you design a paper bridge, a container, a model vehicle, a water-saving idea, or a better way to organize something.
A design process is not a race to the first idea. You first understand the problem. Then you think of possible solutions, choose a promising idea, make a plan, build a prototype, test it, and improve it. You may move backward and forward between steps as you learn. This repeated improvement is called iteration.
The NASA/JPL diagram above shows an engineering design process as a cycle. Different organizations may name or group the steps in different ways, but they share an important idea: engineers learn from evidence and improve their designs.
In this aiMOOC, you will learn how to:
- Define a problem clearly.
- Describe what a successful solution must do.
- Recognize limits such as time, materials, size, safety, and cost.
- Generate several possible solutions.
- Plan with sketches, labels, and measurements.
- Build a prototype from suitable materials.
- Run a fair test and record useful data.
- Improve a design using evidence.
- Explain your design choices to other people.
What Engineers Do
An engineer uses knowledge, creativity, tools, mathematics, science, and teamwork to solve problems. Engineers do not only build machines. They may design safer roads, cleaner water systems, useful apps, medical devices, energy-saving buildings, robots, playgrounds, packaging, or ways to make everyday tasks easier.
A strong engineer asks questions such as: Who needs this solution? What should it do? What could make it unsafe? What materials are available? How will we know whether it works? What evidence will help us improve it?
Engineering also involves communication. A great idea is more useful when you can explain it with clear words, sketches, labels, measurements, models, tables, and test results.
Problems, Needs, and Wants
A design problem begins with something that people want to change, improve, or create. Some problems involve a need, such as a safer way to cross a small stream. Others involve a want, such as a more convenient pencil holder.
A useful problem statement is specific. Instead of saying, "The bridge is bad," you could say, "Our class needs a model bridge that spans 30 centimeters and can hold a 500-gram load using only the allowed materials." The second statement gives you something you can test.
The Design Cycle
For this course, you will use seven connected actions: Ask, Research, Imagine, Plan, Create, Test, and Improve. Think of them as a cycle rather than a straight line. If testing shows a weakness, you may return to planning. If research reveals a new constraint, you may change your ideas.
Ask: Define the Problem
Start by asking what needs to be solved. Find out who is affected and what a good solution should accomplish.
Two important words are criteria and constraints.
A criterion is something a successful design should do. For example, a paper tower might need to stand at least 40 centimeters tall for 30 seconds.
A constraint is a limit or rule. For example, you might have only ten sheets of paper, 40 centimeters of tape, and 20 minutes.
Before you build, write a short design brief that includes the problem, the user, the criteria, and the constraints.
Research: Learn Before You Build
Research helps you understand the problem and learn from existing ideas. You might observe people, measure objects, read reliable sources, interview a user, examine an existing product, or run a small investigation.
Good research does not mean copying another design. It gives you information that can help you make better choices. For example, if you are designing a lunchbox handle, you could measure hand sizes, compare handle shapes, and ask users what feels comfortable.
Keep notes and record where your information came from. When you use measurements, always include units.
Imagine: Generate Several Ideas
During brainstorming, try to produce several possible solutions before deciding which one to build. At first, focus on possibilities. Sketch quickly, combine ideas, and ask "What if...?"
Then compare your ideas with the criteria and constraints. A solution that looks exciting is not automatically the best one. The best choice is the one that is most likely to solve the defined problem within the limits.
A simple decision table can help. List your ideas and check how well each one meets the important criteria. You can also combine strong parts from different ideas.
Plan: Make the Idea Clear
Before building, turn your chosen idea into a plan. A useful plan may include:
- A labeled sketch showing the main parts.
- Measurements and units.
- A materials list.
- Notes about how parts will connect.
- A safe order for building.
- A prediction about how the design will work.
Your drawing does not have to be artistic. Its job is to communicate. Use straight lines, readable labels, arrows, and measurements so another person can understand your idea.
Create: Build a Prototype
A prototype is an early version of a design that is made so you can learn from it. A prototype may be full-size or smaller. It can be made from cardboard, paper, wood, recycled materials, digital tools, or other safe materials.
A prototype is not supposed to be perfect. It should be good enough to test an important idea. Building a simple model first can save time and materials because you can discover problems before making a final product.
When you build, follow classroom safety rules. Ask an adult before using sharp tools, hot tools, electricity, chemicals, or heavy objects.
Test: Collect Evidence
Testing tells you how the design behaves. A useful test connects directly to the criteria.
If the criterion says a bridge must hold a certain load, test how much load it can hold. If a container must resist leaking, test it with a measured amount of water in a safe place. If a paper airplane should fly far, measure its flight distance several times.
.jpg){kind=link}
A fair test changes one important factor at a time when possible. Keep other conditions the same so you can understand what caused a difference. Repeat trials when useful, because one result may happen by chance.
Record evidence in a data table. Useful evidence can include length, time, mass, number of objects held, temperature, user ratings, observations, and photographs.
Improve: Use What You Learned
After testing, ask:
- Which criteria did the design meet?
- Which criteria did it miss?
- Where did it bend, break, leak, slow down, wobble, or become difficult to use?
- What evidence shows the main weakness?
- Which change could improve the result?
Change your design for a reason. For example, "I will add two triangular supports because the middle bent during the load test" is stronger engineering thinking than "I will add more tape because I think it might help."
Then build and test again. This cycle of testing, learning, and redesigning is iteration.
Criteria and Constraints
Criteria and constraints help you judge ideas fairly.
Criteria describe success. A design may need to be strong, light, stable, waterproof, comfortable, fast, easy to use, or energy-efficient.
Constraints describe limits. Common constraints include available materials, time, budget, size, weight, safety rules, tools, environmental impact, and the needs of users.
Sometimes criteria compete. A very strong bridge may also become heavy. A very large container may hold more but use more material. Engineers often make trade-offs: they decide which features are most important while still meeting the problem requirements.
A Mini Example: Design a Desk Organizer
Imagine that pencils, erasers, rulers, and notes keep getting lost on a desk.
A possible problem statement is: "A student needs a desk organizer that keeps four kinds of school supplies easy to reach."
Possible criteria could include holding at least four types of items, staying upright when used, and fitting on a 20-by-20-centimeter area.
Possible constraints could include using only clean recycled cardboard, paper fasteners, and 30 centimeters of tape, with a building time of 35 minutes.
You might sketch three ideas, compare them, choose one, build a cardboard prototype, test it with real school supplies, ask a classmate to use it, and improve the parts that tip over or are hard to reach.
Testing, Data, and Failure Points
A failure point is a place or situation where the design does not work as intended. Finding a failure point is useful because it tells you what to improve.
For example, if a bridge model collapses where two pieces join, the joint may be a failure point. If a container leaks only when tipped sideways, the lid or seam may need improvement.
Professional engineers also use models and tests. The aircraft model above is an example of a prototype used in wind-tunnel testing. A model lets engineers study behavior before making changes to a full-size system.
When you test, write down what happened instead of relying only on memory. Measurements and observations are evidence. Evidence helps you explain why one design is more successful than another.
Make a Fair Comparison
Suppose you are testing two paper helicopter designs. If one is dropped from 1 meter and the other from 2 meters, the comparison is not fair. Keep the drop height, paper type, timing method, and test area the same. Change only the design feature you want to compare.
For repeated tests, record every result. You can find the average when that makes sense, but also look for unusual results and think about what caused them.
Teamwork and Communication
Many engineering projects are done by teams. Good teamwork means listening, explaining ideas, sharing tasks, asking respectful questions, and using evidence when people disagree.
Useful team roles can include a recorder, materials manager, builder, tester, timekeeper, or presenter. Roles can change so everyone practices different skills.
When giving feedback, be specific. Instead of saying, "I don't like it," try, "The handle is hard to grip because it is too narrow for my hand." Specific feedback gives the team something they can test or change.
Design Notebooks
A design notebook is a place to record your thinking. It can include:
- The problem statement.
- Criteria and constraints.
- Research notes.
- Brainstorm sketches.
- The chosen plan.
- Building notes.
- Test data.
- Photos or drawings of each version.
- Explanations of changes.
- A final reflection.
Do not erase every mistake. Old ideas and failed tests can show how your thinking developed.
Safety and Responsible Design
Engineering should protect people and consider the wider effects of a solution. Before building or testing, think about safety, accessibility, waste, energy use, and who may be affected.
Use classroom tools only as instructed. Keep test areas clear. Wear protective equipment when your teacher says it is needed. Never test a design in a way that could hurt people or animals.
Responsible design also asks whether materials can be reused, repaired, or recycled. A solution that works well but creates unnecessary waste may still need improvement.
Engineering in the Real World
The engineering design process appears in many fields. Civil engineers design structures and transportation systems. Mechanical engineers work with machines and moving parts. Electrical engineers design circuits and electrical systems. Environmental engineers develop solutions related to water, waste, pollution, and resources. Software engineers create and improve digital systems.
The exact design steps can look different in each field, but engineers still need to understand problems, make decisions, test ideas, and improve solutions.
As you watch, notice how real engineers use testing and revision. Ask yourself which parts of their work are similar to a classroom design challenge.
Reliable Sources and Further Reading
- NASA/JPL Engineering Design Process Flow Chart: A clear overview of identifying a problem, designing, building, testing, and improving a solution.
- NGSS Grades 3-5 Engineering Design: Standards describing criteria, constraints, multiple solutions, fair tests, and improvement.
- NGSS Middle School Engineering Design: A useful bridge into more advanced work with criteria, constraints, testing, and optimization.
- TeachEngineering Engineering Design Process: School-friendly explanations and activities focused on iterative problem solving.
Interactive Tasks
Quiz: Test Your Knowledge
What is a prototype? (An early version built to test an idea) (!A final product that cannot be changed) (!A list of classroom rules) (!A measurement unit)
What does a criterion describe? (Something a successful design should do) (!A limit that can never be measured) (!A random idea from brainstorming) (!A tool used only for drawing)
What is a constraint? (A limit or rule for a design) (!A perfect final answer) (!A type of test result) (!A drawing without labels)
Why do engineers generate several ideas? (To compare possible solutions) (!To avoid defining the problem) (!To skip testing) (!To make every design identical)
What makes a test fair? (Keeping important conditions the same while comparing one change) (!Changing many conditions at once) (!Testing only the favorite design) (!Ignoring unusual results)
Why should test results be recorded? (To provide evidence for decisions) (!To make the prototype look better) (!To remove all constraints) (!To avoid repeating trials)
What is iteration? (Repeating parts of the process to improve a design) (!Choosing the first idea immediately) (!Building without a plan) (!Stopping after one test)
What is a failure point? (A place or situation where a design does not work as intended) (!The strongest part of every design) (!A rule that prevents testing) (!A finished drawing)
What should a useful design plan include? (Labels measurements and materials) (!Only decorative colors) (!Only the name of the builder) (!No information about size)
What is a good reason to improve a design? (Test evidence shows a specific weakness) (!A random change seems fun) (!The first design must always be wrong) (!The materials have not been checked)
Memory Game
| Criterion | A feature a successful solution should have |
| Constraint | A limit or rule the design must follow |
| Prototype | An early version built to learn from testing |
| Iteration | Repeating design work to make an improvement |
| Brainstorming | Generating several possible ideas |
| Evidence | Information from measurements or observations |
| Tradeoff | A choice that balances competing advantages |
Drag and Drop
| Match the correct terms. | Topic |
|---|---|
| Define the problem | Ask what needs to be solved and for whom |
| Generate ideas | Think of several possible solutions |
| Make a plan | Draw and label the chosen design |
| Build a prototype | Create an early version for testing |
| Improve the design | Use evidence to make a useful change |
...
Crossword Puzzle
| Prototype | What do engineers call an early version built for testing? |
| Constraint | What word means a limit or rule in a design problem? |
| Criterion | What word means a feature used to judge success? |
| Iteration | What word means repeating design work to improve a solution? |
| Testing | What activity collects evidence about how a design works? |
| Engineer | What kind of person designs solutions to problems? |
LearningApps
Cloze Text
Open-Ended Tasks
Easy
- Problem Hunt: Find three small problems at school or at home that could be improved by design. Write one clear problem statement for each and choose your best example.
- Sketch Three Solutions: Choose one simple problem and draw three different possible solutions. Label the important parts and explain one strength of each idea.
- Prototype Photo Story: Build a safe paper or cardboard prototype of a useful object. Take or draw three images showing the beginning, middle, and finished prototype, then add short captions.
- Engineer Interview: Interview an adult who solves practical problems in their work. Ask how they plan, test, fix mistakes, and know when a solution is good enough.
Standard
- Paper Bridge Challenge: Design a paper bridge that spans a gap chosen by your teacher. Set criteria and constraints, test the bridge with equal loads, record results, and improve one feature.
- User Test: Design a simple organizer, holder, or stand for a classmate. Ask the user to try your prototype, record specific feedback, and revise the design.
- Design Process Video: Make a short video that explains a safe classroom design project from problem definition through testing and improvement. Include your own sketches, prototype, and evidence.
- Engineering Field Visit: Visit a suitable place such as a makerspace, science center, workshop, construction viewing area, or technology lab with adult supervision. Record examples of planning, tools, testing, safety, or teamwork that you observe.
Advanced
- Controlled Test Investigation: Create two versions of a paper aircraft, parachute, or other teacher-approved model that differ in one design feature. Run repeated trials under the same conditions and use the data to decide which version better meets your criterion.
- Sustainable Redesign: Choose a common package or school object and redesign it to use less material, last longer, or be easier to reuse. Explain the trade-offs and build a model if practical.
- Design for Accessibility: Identify a classroom task that may be difficult for a person with a particular access need. Research the need respectfully, develop several ideas, and present a prototype or detailed model that improves access.
- Community Design Proposal: Identify a real local problem that can be addressed safely through design. Gather evidence from observations or interviews, define criteria and constraints, compare possible solutions, and present a reasoned proposal with drawings or a model.
Learning Assessment
- Evidence-Based Redesign: You receive test results showing that a model bridge is strong but too heavy. Explain two possible design changes, predict their effects, and describe what you would test next.
- Criteria and Constraints Analysis: For a school water-bottle holder, create three clear criteria and three realistic constraints. Explain why each one matters to the user.
- Compare Solutions: Compare two proposed solutions to the same problem using a decision table. Choose the stronger option and justify your choice with the criteria and constraints.
- Fair-Test Planning: Design a fair test for two paper-airplane wing shapes. Identify what you will change, what you will keep the same, what you will measure, and how many trials you will run.
- Failure-Point Reasoning: A cardboard container leaks at one folded corner during every test. Use this evidence to explain a likely failure point and propose a focused redesign.
- Transfer Challenge: Choose a problem outside the classroom and explain how Ask, Research, Imagine, Plan, Create, Test, and Improve could guide a safe solution.
Evidence of Learning
Knowledge: You can explain the purpose of criteria, constraints, prototypes, fair tests, evidence, failure points, trade-offs, and iteration.
Skills: You can define a design problem, generate several ideas, make a labeled plan, build a safe prototype, collect useful data, compare solutions, and improve a design using evidence.
Products: Your work may include a design brief, sketches, a decision table, a prototype, a test plan, data records, photographs, a redesign, and a final presentation.
Communication: You can explain your design choices clearly, use measurements with units, listen to feedback, and support claims with observations or data.
Transfer: You can recognize when the engineering design process is useful in new situations and adapt the process to different problems, users, materials, and constraints.
OERs on the Topic
Linked Learning Areas
The engineering design process connects strongly with Science, Mathematics, Technology, Design and technology, Computer science, Environmental science, Art, Communication, and Project-based learning. In Grades 5–6, it is especially useful for hands-on STEM projects that ask you to apply knowledge, collect evidence, explain choices, and improve a solution.