Engineering Design and Applied Science

The Engineering Design Process is a step-by-step way engineers solve problems and create useful things. Engineers design bridges, water bottles, playgrounds, robots, and even apps. They use science and math to help them make good choices.

One important thing to know is that the engineering design process is not always a straight line. Engineers may move forward, go back, change an idea, and try again. This is called an iterative process. Iterative means you repeat steps to make a solution better.

When engineers work on a problem, they do not just guess. They ask questions, learn about the problem, think of many ideas, build a model, test it, and improve it. This helps them create solutions that work well and are safe.

Why do engineers use a process?

• It helps them stay organized.
• It helps them solve real-world problems.
• It helps them learn from mistakes.
• It helps them improve designs over time.

Let’s learn the main parts of the engineering design process.

1. Define the problem

First, engineers figure out exactly what problem needs to be solved. They ask: What is wrong? Who needs help? What should the solution do?

They also think about criteria and constraints.

• Criteria are the things the solution must do. For example, a paper bridge must hold toy cars.
• Constraints are the limits on the design. For example, only 10 straws may be used, or the project must cost less than \(\$5\).

A clear problem statement might be: Design a small shade cover for the playground that blocks sunlight, stays standing in wind, and uses only cardboard, tape, and 6 craft sticks.

2. Research the problem

Next, engineers learn more. They might read books, look at pictures, watch how other designs work, or ask experts questions. Research helps them understand what has already been tried and what materials may work best.

For example, if students need to design a container to keep an ice cube from melting, they might research which materials are good insulators. An insulator slows down heat transfer.

Research can also include science ideas and math. If a ramp is being designed, students may measure length and height. If a garden is being planned, they may compare area and space.

3. Imagine and brainstorm ideas

Now engineers think of many possible solutions. This step is often called ideating or brainstorming. During brainstorming, it is smart to think of several ideas instead of only one.

At this stage, no one needs a perfect answer yet. The goal is to be creative and consider different designs. Engineers often draw sketches and label parts.

When comparing ideas, they may ask:

• Which idea best meets the criteria?
• Which idea fits the constraints?
• Which materials are strong, light, or easy to use?
• Which design seems safest?

4. Choose a solution and plan

After brainstorming, engineers choose one design to try first. Then they make a plan. A plan might include a drawing, a list of materials, steps for building, and measurements.

This is where math can help. Engineers may measure length, count materials, or compare costs. For example, if a team can use at most 8 craft sticks and one idea needs 10, that design does not fit the constraints because \(10 > 8\).

5. Build a prototype

A prototype is a first model of a design. It is built to test an idea. A prototype does not have to be perfect. It is made so engineers can see what works and what needs to change.

Some prototypes are small models. Others are made from simple classroom materials like paper, cardboard, tape, or straws. Even a drawing can be an early prototype if it helps show the design clearly.

6. Test the prototype

Testing shows whether the prototype meets the criteria. Engineers collect information during tests. They may observe, measure, compare, and record results.

Good tests are fair. That means they try to change only one thing at a time when possible. If students are testing paper airplanes, they should throw them in the same way each time. If they change both the paper type and the wing shape at once, it is hard to know which change made the difference.

Examples of test questions include:

• How much weight can the bridge hold?
• How far does the airplane fly?
• How long does the ice stay frozen?
• Does the tower stay standing when a fan blows on it?

7. Evaluate the results

After testing, engineers study what happened. They ask: Did the design work? What parts were successful? What problems showed up?

This step is called evaluating. Engineers compare their results to the criteria and constraints. If the design does not solve the problem well enough, they figure out why.

Suppose a bridge needed to hold 20 pennies but only held 12. The bridge did not meet the criteria. Engineers might notice that the middle sagged or that the supports were too weak.

8. Improve and iterate

This step is very important. Engineers use what they learned to improve the design. They may make the base wider, switch materials, change the shape, or add support.

Then they test again. This repeating cycle is called iteration. Each time, the design can become stronger, safer, cheaper, or more useful.

It is normal if the first design does not work well. In engineering, mistakes are not the end. They are clues that help engineers make a better solution.

The process is non-linear

The engineering design process is often shown in steps, but engineers do not always follow the steps in one exact order. They may test a prototype and then go back to research. They may brainstorm again after finding a problem. They may build a second or third prototype.

That is why we say the process is non-linear. Engineers move between steps as needed.

How science and math help engineering

Engineering uses science and math to solve problems. Science helps engineers understand how the world works. Math helps them measure, compare, and make careful plans.

• Science can help with ideas like force, motion, heat, light, sound, and properties of materials.
• Math can help with length, time, mass, temperature, counting, and comparing numbers.

For example, if a student designs a parachute, science helps explain how air slows the fall. Math helps measure how long the parachute stays in the air.

Worked Example 1: Designing a bookmark that stays in a book

Problem: A student needs a bookmark that does not fall out of a notebook when carried in a backpack.

Define the problem: The bookmark must stay in place and be easy to use. It must be made from paper and one paper clip.

Research: The student looks at different bookmarks and notices that some slide over the page corner while others clip onto a page.

Brainstorm: The student thinks of three ideas:

1. A plain strip of paper
2. A folded corner bookmark
3. A paper strip attached to a paper clip

Choose and plan: The student chooses the paper strip with a paper clip because it seems less likely to fall out.

Prototype: The student builds it.

Test: The student shakes the notebook gently 5 times. The bookmark stays in place 4 out of 5 times.

Evaluate: It works fairly well, but it slipped once.

Iterate: The student folds the top of the paper around the clip more tightly and tests again. This time it stays in place all 5 times.

This example shows that the first idea can improve after testing.

Worked Example 2: Building a paper bridge

Problem: Build a bridge from paper that can hold coins across a gap of 15 centimeters.

Criteria: The bridge must span 15 centimeters and hold at least 10 coins.

Constraints: Only 2 sheets of paper and tape may be used.

Research: Students learn that folded shapes can be stronger than flat paper. A triangle or accordion fold can add strength.

Brainstorm: The team sketches:

1. A flat paper strip
2. A rolled paper tube
3. A folded accordion bridge

Choose and plan: They choose the accordion bridge.

Prototype and test: Their first bridge holds 6 coins.

Evaluate: Since \(6 < 10\), the bridge does not meet the criteria.

Iterate: They make the folds smaller and add stronger taped ends. The second bridge holds 11 coins.

Result: Now \(11 \geq 10\), so the bridge meets the goal.

This example shows how math helps compare results to the criteria.

Worked Example 3: Keeping an ice cube cold

Problem: Design a small container that keeps an ice cube from melting as long as possible.

Criteria: The ice cube should still be partly frozen after 20 minutes.

Constraints: Only cotton, foil, paper, and tape may be used.

Research: Students learn that some materials trap air and slow heat transfer better than others.

Brainstorm: They think of wrapping the ice cube in:

1. Only foil
2. Only paper
3. Cotton inside foil

Choose and prototype: They build the cotton-inside-foil design.

Test: After 20 minutes, the ice cube is partly frozen, but water is leaking out.

Evaluate: The design meets one goal, but the leak is a problem.

Iterate: They add a folded paper layer outside to catch water and hold the shape. They test again.

Result: The second design keeps the ice cold and leaks less.

This example shows that a design can meet some goals but still need improvement.

Tips for using the engineering design process

• Ask clear questions about the problem.
• Write down criteria and constraints.
• Think of more than one idea.
• Sketch your plan before building.
• Test fairly and record what happens.
• Use results to improve your design.
• Do not give up if the first try fails.

Common mistakes to avoid

• Starting to build before understanding the problem
• Thinking of only one idea
• Ignoring the constraints
• Changing too many things at once during testing
• Not using test results to improve the design

Why iteration matters

Imagine trying to make the perfect design in one try. That would be very hard. Iteration gives engineers a chance to learn from each test. A weak design can become strong. A slow design can become faster. A costly design can become cheaper.

Each round of testing gives useful information. Engineers use that information to make better choices. That is why iteration is one of the most powerful parts of engineering.

Summary

The engineering design process helps people solve problems by thinking carefully, testing ideas, and improving them. The main parts are: define the problem, research, brainstorm, plan, build a prototype, test, evaluate, and iterate.

Remember, the process is not always in one straight line. Engineers often go back and change their designs. That is how they create solutions that work better for people and the world around us.

Defining Constraints and Criteria is an important part of engineering design. Engineers solve problems by creating and improving things people need. Before they build anything, they must be clear about what the design needs to do and what limits they must work within.

Two important words help engineers plan good solutions: criteria and constraints.

Criteria are the things a design must do to be successful. They are the goals or requirements for the solution.

Constraints are the limits or rules a design must follow. Constraints can include money, time, materials, size, and safety.

When engineers define criteria and constraints, they make a clear plan. This helps them choose the best idea, test it, and improve it.

Think of it this way:

• Criteria tell us, “What should this design do?”
• Constraints tell us, “What limits do we have?”

For example, imagine you are designing a lunch container for a student.

• A criterion might be: it must keep food from spilling.
• Another criterion might be: it must be easy to open.
• A constraint might be: it must cost less than \(\$10\).
• Another constraint might be: it must fit inside a backpack pocket.

Notice that criteria describe success, while constraints describe limits.

Good criteria are often written so they can be measured or checked. This is called quantifying. Quantifying means using numbers when possible.

Instead of saying, “The bridge should be strong,” an engineer might say, “The bridge should hold at least 20 toy cars.” That is better because it can be tested.

Instead of saying, “The project should be cheap,” an engineer might say, “The project must cost less than \(\$15\).” That is also clear and measurable.

Here are some examples of criteria that are quantified:

• The tower must be at least 30 centimeters tall.
• The model boat must hold 10 pennies.
• The water filter must clean 1 cup of water in less than 2 minutes.

Here are some examples of constraints:

• You may only use 20 straws.
• You have 30 minutes to build.
• You can spend no more than \(\$8\).
• The design must be safe to use.

Both criteria and constraints matter. A design might work very well, but if it costs too much or is unsafe, it is not a good solution. A design might follow all the limits, but if it does not solve the problem, it is also not successful.

Engineers usually ask questions like these when defining criteria and constraints:

• What problem are we trying to solve?
• What must the design do?
• How will we know if it works?
• What materials can we use?
• How much time do we have?
• How much money can we spend?
• How can we make sure it is safe?

Let’s look at criteria and constraints more closely.

1. Criteria describe success.

Criteria tell what the solution should accomplish. They help engineers know what they are aiming for.

• Should it be strong?
• Should it move fast?
• Should it hold a certain amount?
• Should it protect something?

The best criteria are specific. “Build a fast paper airplane” is not as clear as “Build a paper airplane that flies at least 5 meters.”

2. Constraints describe limits.

Constraints set boundaries. They may come from the classroom, the customer, or the real world.

• You may only use recycled materials.
• The design must fit on a desk.
• The project must be finished by Friday.
• The design cannot have sharp edges.

3. Criteria and constraints work together.

Designing is often a balance. Engineers try to meet the criteria while staying inside the constraints.

For example, a toy car ramp should help a car travel far. That is a criterion. But the ramp may need to be made from only cardboard and tape. That is a constraint. The best ramp is one that makes the car travel far and uses only the allowed materials.

4. Testing helps engineers check the criteria.

After building a design, engineers test it. They collect results and compare them to the criteria.

If the criterion says the tower must be 30 centimeters tall, they measure the height. If the criterion says the bridge must hold 20 toy cars, they test how many cars it can hold.

If the design does not meet the criteria, engineers improve it. This is part of the iterative design process, which means trying, testing, and making changes.

5. Safety is an important constraint.

Some constraints are about keeping people safe. Safety should always be considered in engineering.

• Materials should not be dangerous.
• Designs should not break easily in a harmful way.
• Tools should be used correctly.

Even if a design works well, it is not a good design if it is unsafe.

Worked Example 1: Building a Paper Bridge

Problem: Build a paper bridge that can hold coins.

First, we define the criteria:

• The bridge must hold at least 15 pennies.
• The bridge must stretch across a 20-centimeter gap.

Next, we define the constraints:

• You may use only 2 sheets of paper.
• You may use 30 centimeters of tape.
• You have 20 minutes to build.

How do we know if the design is successful?

We test the bridge. If it reaches across the 20-centimeter gap and holds 15 pennies, it meets the criteria. If it also uses only the allowed paper, tape, and time, it stays within the constraints.

Worked Example 2: Designing a Mini Parachute

Problem: Design a parachute to help a toy fall slowly.

Criteria:

• The parachute must keep the toy in the air for at least 3 seconds.
• The toy must land without falling out.

Constraints:

• You may use only string, plastic, and tape.
• The parachute must fit inside a shoebox before testing.
• You have only 25 minutes.

Why are these good criteria?

The time of 3 seconds can be measured with a stopwatch. Whether the toy stays inside can be observed. These are clear ways to test success.

Worked Example 3: Planning a School Garden Sign

Problem: Make a sign for the school garden that is easy to read.

Possible criteria:

• The sign must be readable from 5 meters away.
• The sign must include the words “School Garden.”
• The sign must stay standing outside for one week.

Possible constraints:

• The total cost must be less than \(\$12\).
• You may only use cardboard, markers, and wooden sticks.
• The sign must not have sharp points.

What makes this a little harder?

Now there is more than one criterion and more than one constraint. This is common in real engineering. Engineers often need to think about many needs at the same time.

Worked Example 4: Choosing the Best Water Bottle Holder

Problem: A class is designing a holder for a water bottle on a bike.

The class decides on these criteria:

• It must hold 1 water bottle.
• It must keep the bottle from falling during a short ride test.
• It must allow the bottle to be removed in less than 5 seconds.

The class also decides on these constraints:

• It must cost less than \(\$10\).
• It must be made from safe materials.
• It must be built in 40 minutes.

Suppose Team A makes a holder that keeps the bottle secure, but it costs \(\$14\). Team B makes a holder that costs \(\$8\), but the bottle falls out during the test.

Did either team succeed?

No. Team A met some criteria, but broke a constraint about cost. Team B met the cost constraint, but did not meet the criterion of keeping the bottle secure. A strong design must meet the criteria and follow the constraints.

Tips for Finding Criteria and Constraints

1. Start with the problem. Ask: What needs to be solved?
2. List what success looks like. These are your criteria.
3. Add numbers when possible. Numbers make criteria clear.
4. List the limits. Think about money, time, materials, size, and safety.
5. Check both before building. A plan works best when goals and limits are clear.

Common Mistakes to Avoid

• Mixing up criteria and constraints. Remember: criteria are goals; constraints are limits.
• Being too vague. “It should work well” is not clear. “It should hold 10 books” is clearer.
• Forgetting safety. Safety is an important constraint.
• Ignoring one part. A design must solve the problem and stay within the limits.

Quick Check

Imagine you are designing a backpack for a class pet to travel safely.

• Criterion: The backpack must hold the pet’s food and water.
• Criterion: The pet must have air holes.
• Constraint: The backpack must weigh less than 2 kilograms.
• Constraint: The backpack must be made from safe materials.

Ask yourself:

• Which statements describe success?
• Which statements describe limits?

If you said the first two are criteria and the last two are constraints, you are correct.

Summary

In engineering design, criteria are the requirements that show a design is successful. Constraints are the limits that a design must follow.

Good criteria are clear and often measured with numbers. Common constraints include budget, time, materials, size, and safety.

Engineers use criteria and constraints to plan, build, test, and improve solutions. A strong design solves the problem and stays within the limits.

Needs Assessment and Problem Framing are the first important steps in engineering design. Before people build something new, they need to understand what the real problem is and who is affected by it.

Sometimes a problem looks simple at first, but the first idea is not always the best answer. Engineers ask questions, gather information, and look for the root cause. The root cause is the main reason a problem is happening.

When engineers understand the real need, they can design a solution that works better. This saves time, money, and effort.

Think about this: If a plant is drooping, is the problem always that it needs more water? Not always. It could need sunlight, better soil, or a bigger pot. In the same way, engineers must find the true cause before solving a problem.

What is a needs assessment?

A needs assessment is the process of finding out what people need, what problem they have, and what would help them most.

• Who has the problem?
• What is happening?
• When does it happen?
• Where does it happen?
• Why is it a problem?
• What do people need most?

A needs assessment helps engineers focus on the people using the solution. These people are often called users.

What is problem framing?

Problem framing means clearly stating the problem in a useful way. A well-framed problem explains the need without jumping too quickly to one solution.

For example, suppose students are late to class because the hallway is crowded. A poorly framed problem would be: We need to build a faster bell.

That idea jumps straight to one answer. But the real problem may not be the bell at all.

A better problem frame would be: Students need a safer and faster way to move through the hallway between classes.

This statement focuses on the need, not just one guessed solution.

Why root cause matters

The root cause is the deepest main reason for a problem. If we only fix the surface problem, the problem may come back.

Look at this chain of thinking:

• Problem: The classroom floor is wet.
• Surface idea: Mop the floor.
• But why is it wet?
• Maybe a water bottle spilled.
• Or maybe the sink is leaking.

If the sink is leaking, mopping helps only for a short time. Fixing the leak solves the root cause.

Signs that you have not found the real problem yet

• You only have one possible solution in mind.
• You cannot explain why the problem is happening.
• You have not asked the users what they need.
• Your idea fixes the problem for only a short time.

Questions engineers ask during needs assessment

Engineers learn by observing, measuring, and asking questions. They may ask:

• Who is affected by this problem?
• How often does the problem happen?
• How serious is the problem?
• What have people already tried?
• What works and what does not work?
• What limits do we have, like time, money, or materials?

These limits are called constraints. Constraints are things that make the job harder or set boundaries.

Engineers also think about criteria. Criteria are the things a good solution must do. For example, a backpack hook might need to be strong, safe, and easy to use.

Needs, wants, and ideas

It is important to tell the difference between a need, a want, and an idea.

• Need: something people must have to solve the problem
• Want: something that would be nice, but is not required
• Idea: a possible solution

Example:

• Need: Students need a way to carry books safely.
• Want: Students want the carrier to come in bright colors.
• Idea: Make a rolling book cart.

Engineers should find the need first. Then they can come up with many ideas.

How to frame a problem well

A strong problem statement is clear and focused on the need. It often includes:

• Who has the problem
• What they need
• Why it matters
• Any important limits

A useful pattern is:

[User] needs [what is needed] because [reason].

Here are some examples:

• Gardeners need a way to water plants slowly because the soil dries out quickly in hot weather.
• Students need a quieter reading space because noise makes it hard to focus.
• Families need a safe way to store food during a power outage because food can spoil.

Worked Example 1: School lunch line

Scenario: The lunch line is too long, and students do not have much time to eat.

A quick guess might be: Buy a second lunch cart.

But first, we should do a needs assessment.

1. Who is affected? Students and cafeteria workers.
2. What is happening? Students wait a long time in line.
3. When does it happen? At lunch every day.
4. Why is it a problem? Students lose eating time.
5. Possible root causes? Too few servers, slow checkout, students cutting in line, or trays placed in the wrong spot.

After observing, we learn that the slowest part is picking up milk and utensils because they are at the end of the line in a crowded corner.

Root cause: The line slows down because important items are placed in a crowded area.

Better problem frame: Students need a faster way to move through the lunch line because they are losing time to eat, especially near the milk and utensil station.

Now engineers can think of several solutions, not just one.

Worked Example 2: Playground puddles

Scenario: After it rains, a large puddle forms on the playground, and students cannot use part of the area.

A fast idea might be: Put sand over the puddle.

But is that the real solution?

1. Who is affected? Students, recess teachers, and playground helpers.
2. What is happening? Water collects in one area.
3. Why is it a problem? It causes slipping and takes away play space.
4. What should we observe? Where the water comes from, how long it stays, and whether the ground is lower there.

After looking closely, we find that this part of the playground is lower than the rest, so water drains into it.

Root cause: The ground shape causes water to collect there.

Problem frame: Students need a safer, drier playground area after rain because water collects in a low spot and creates a slipping hazard.

This problem frame helps people think about drainage, ground level, or water flow.

Worked Example 3: Plants in the school garden

Scenario: The plants in the school garden are not growing well.

A first guess might be: Add more water every day.

That is a solution idea, but we still need to check the real problem.

1. Who is affected? Students and teachers caring for the garden.
2. What is happening? The plants are small and weak.
3. What information should we collect? Sunlight, water, soil condition, and space between plants.

Suppose we find these facts:

• The plants get only 3 hours of sunlight each day.
• They are already watered enough.
• The soil is okay.

The root cause is not lack of water. The main problem is lack of sunlight.

Problem frame: The garden plants need more access to sunlight because they are not getting enough light to grow well.

This is better than saying, “We need a bigger watering can.”

Worked Example 4: Noisy classroom

Scenario: Students say the classroom is too noisy during independent work time.

A quick idea might be: Tell everyone to be quiet.

That might help for a few minutes, but it may not solve the main cause.

1. Who is affected? Students and the teacher.
2. When does it happen? During independent work time.
3. Possible causes? Scraping chairs, loud air vent, students asking many questions, or materials stored in a busy area.

After observing, the class notices that many students get up to collect supplies from one shelf, and that area becomes noisy.

Root cause: The supply area is crowded and causes extra movement and noise.

Problem frame: Students need a quieter way to get supplies during work time because the crowded supply shelf creates noise and distractions.

Now the class can think of many possible solutions, such as supply bins at tables or a better shelf layout.

How to gather information

To understand a problem, engineers do more than guess. They gather evidence.

• Observe: Watch carefully and notice what happens.
• Ask: Talk to people who have the problem.
• Measure: Count, time, or compare when possible.
• Record: Write notes, make charts, or draw pictures.

For example, if students think the lunch line is too long, they can time how long it takes to get through the line. If 5 students take 7 minutes, that is useful information.

They could even find an average. If the times are 6, 7, 8, 7, and 7 minutes, the total is

$$6+7+8+7+7=35$$

and the average is

$$35 \div 5 = 7$$

So the average wait time is 7 minutes.

Simple math helps engineers understand the size of a problem.

Avoid these common mistakes

• Jumping to a solution too fast: “We need a new machine!”
• Guessing without evidence: “It is probably because of the weather.”
• Ignoring the users: not asking the people with the problem
• Solving only the surface problem: fixing the sign of the problem, not the cause

From problem framing to design

Once the problem is clearly framed, engineers can begin to design solutions. Because they understand the need, they can compare ideas and test which one works best.

A good design process often looks like this:

1. Identify the problem.
2. Do a needs assessment.
3. Find the root cause.
4. Frame the problem clearly.
5. Think of possible solutions.
6. Build and test a solution.
7. Improve it if needed.

This process is called iterative, which means engineers may repeat steps and make improvements over time.

Helpful checklist for students

• Did I say who has the problem?
• Did I explain what they need?
• Did I find the cause, not just the result?
• Did I ask questions and gather evidence?
• Did I avoid naming only one solution too soon?

Brief Summary

Needs assessment means finding out what people truly need before trying to solve a problem. Problem framing means writing the problem clearly so it focuses on the need and the root cause. When engineers understand the real cause of a problem, they can design better, smarter solutions.

Ideation and Brainstorming Techniques are important parts of the engineering design process. Engineers do not usually solve a problem with their very first idea. Instead, they think of many possible solutions before choosing one to build and test.

This part of the process is called ideation. Ideation means coming up with ideas. Brainstorming is one way to do that. During brainstorming, people share lots of ideas without saying “that won’t work” right away.

In science and engineering, this matters because a problem can often be solved in more than one way. If we only think of one idea, we might miss a better one. When we think of many ideas, we have a better chance of finding a strong solution.

For example, imagine a class needs to design a way to keep an ice cube from melting quickly on a hot day. One group might think of wrapping it in cloth. Another might use foam. Another might put it in shade. Another might build a small cooler. All of these are possible ideas, and brainstorming helps students create them.

Why engineers brainstorm

Brainstorming helps engineers:

• Generate many ideas instead of stopping at the first one
• Think in different ways about the same problem
• Work together and build on each other’s ideas
• Delay judgment until after ideas are collected
• Discover creative solutions that may not seem obvious at first

A very important idea in brainstorming is divergent thinking. Divergent thinking means letting your mind branch out in many directions. Instead of looking for one correct answer right away, you explore lots of possibilities.

You can think of divergent thinking like opening many doors. Behind each door is a different idea. Some ideas may be simple. Some may be unusual. Some may need changes later. But first, you open the doors and look.

The difference between brainstorming and choosing

Brainstorming is not the same as picking the best solution. First, you create ideas. Later, you study them, compare them, and test them.

It helps to think of the process in two parts:

1. Create many ideas
2. Evaluate the ideas after the brainstorming is finished

If students judge ideas too early, they may stop sharing. A quiet or unusual idea could turn out to be the best one. That is why engineers often say, “No judging yet!” during brainstorming.

Rules for good brainstorming

Good brainstorming works best when everyone follows a few simple rules.

• Share as many ideas as you can. A long list gives you more choices later.
• Do not criticize ideas at first. Save judging for later.
• Welcome unusual ideas. Sometimes a strange idea leads to a great solution.
• Build on others’ ideas. One person’s idea can help another person think of an even better one.
• Stay focused on the problem. Keep your ideas connected to the challenge you are trying to solve.

These rules help teams feel safe to speak. When people feel safe, they are more likely to share creative thoughts.

How to brainstorm step by step

Here is a simple way a 5th grade team can brainstorm.

1. State the problem clearly. Example: “How can we move water from one place to another without spilling much of it?”
2. Set a short time. You might use 5 to 10 minutes.
3. Write down every idea. Use sticky notes, a notebook, or a board.
4. Do not stop to judge. Keep the ideas coming.
5. Group similar ideas together. After brainstorming, sort them into groups.
6. Choose a few ideas to study. Then decide which ideas are worth testing.

Sometimes teams count the total number of ideas they made. If one student thinks of 4 ideas and another thinks of 5 ideas, then together they made \(4+5=9\) ideas.

$$4+5=9$$

This does not mean all 9 ideas will be used. It means the team now has more possible solutions to explore.

Brainstorming techniques

There are different ways to brainstorm. Each one can help you think in a new way.

1. Rapid listing

In rapid listing, students quickly write as many ideas as possible. Speed helps the brain keep moving. The goal is not to make each idea perfect. The goal is to create many possibilities.

Example: “List ways to make a bridge stronger.” Students might write: wider base, thicker paper, folded paper, tape supports, triangle shapes, more layers.

2. Sketch brainstorming

Some ideas are easier to show with a picture than with words. In sketch brainstorming, students draw simple diagrams of their ideas.

This is helpful in engineering because designs often have shapes, parts, and moving pieces. A quick sketch can help the team understand the idea better.

3. Build-on ideas

In this technique, one student shares an idea, and others add to it. For example, one student says, “Let’s make a container with a lid.” Another says, “What if the lid snaps shut?” Another says, “What if the inside is lined with soft material?”

The final idea grows from teamwork.

4. “What else?” questioning

When a team seems stuck, they can ask, “What else could we try?” This simple question helps people keep going.

They can also ask:

• Can we make it bigger or smaller?
• Can we change the shape?
• Can we use a different material?
• Can we make it lighter or stronger?
• Can we solve the problem in a completely different way?

5. Silent brainstorming

Sometimes one or two people talk more than others. In silent brainstorming, each person writes ideas quietly first. Then the team shares them.

This gives everyone a chance to think and contribute.

What makes ideas “radically different”?

Sometimes engineers try to think of solutions that are not just small changes of the same plan. They try to create radically different ideas. That means the ideas solve the problem in very different ways.

For example, if the problem is “How can we keep a plant watered over the weekend?” these are radically different kinds of ideas:

• A bottle that drips water slowly
• A sponge that holds water in the soil
• A string that carries water from a cup to the plant
• A shade cover that helps the soil stay cool and wet longer

These ideas are different because they use different materials and different methods. Thinking this way gives engineers more choices.

Worked Example 1: Brainstorming many ideas

Problem: Design a way to protect an egg from breaking when it drops.

Step 1: State the problem. The egg must land safely.

Step 2: Brainstorm without judging. A team writes these ideas:

• Wrap the egg in cotton
• Put the egg in a small box
• Use straws to make a frame
• Add a parachute
• Use foam padding
• Hang the egg with rubber bands inside a container

Step 3: Count the ideas. The team created 6 ideas.

$$6$$

Step 4: Notice the variety. Some ideas cushion the egg. One slows the fall. One suspends the egg. This is good brainstorming because the ideas are not all the same.

Worked Example 2: Building on ideas together

Problem: Create a device that can scoop up litter from the ground without bending down.

First idea: Use a stick with a cup on the end.

Build-on idea 1: Add a handle to make it easier to hold.

Build-on idea 2: Add pinchers instead of a cup.

Build-on idea 3: Add a trigger so the pinchers can open and close.

Result: The team moved from one simple idea to a more useful tool by listening and adding improvements.

This shows that brainstorming is not only about thinking alone. It is also about collaboration, or working together.

Worked Example 3: Choosing after brainstorming

Problem: Make a paper tower that can hold a small book.

Brainstormed ideas:

• Roll the paper into tubes
• Fold the paper into triangles
• Stack flat sheets
• Make a wide base with taped corners

Now the team evaluates. They ask:

• Which design looks strongest?
• Which uses materials we have?
• Which can we build in class time?

Decision: They choose folded triangles and paper tubes to test first.

Why? They did not pick a design during brainstorming. They waited until after all ideas were shared. That helped them make a smarter choice.

How brainstorming connects to testing and improving

Brainstorming is just one part of the engineering design process. After engineers think of ideas, they build a model or sample, test it, and learn from the results.

If the first design does not work well, they do not give up. They go back, think again, and improve the design. This is called an iterative process. Iterative means repeating steps to make something better.

For example, a team might brainstorm 8 ideas, choose 2 to test, and then learn that both need changes. They can return to their list or brainstorm new ideas. Each round helps them get closer to a strong solution.

Tips for being a strong brainstorming team member

• Listen carefully. Good ideas can come from anyone.
• Be respectful. Treat every speaker kindly.
• Share freely. Even simple ideas can help.
• Stay positive. Encourage others to keep thinking.
• Record ideas clearly. Writing them down helps the team remember them.

When teams work well together, they often create better solutions than one person could create alone.

Common mistakes to avoid

• Stopping after one idea instead of making a full list
• Judging too early and making people afraid to share
• Copying the same kind of idea again and again without trying different approaches
• Forgetting the problem and sharing ideas that do not match the challenge
• Not writing ideas down and then losing them

These mistakes can make a team miss out on useful solutions.

Quick check for understanding

Ask yourself these questions:

• Do I understand that brainstorming means creating many ideas first?
• Do I know that we should not judge ideas right away?
• Can I explain why unusual ideas can still be helpful?
• Can I name at least two brainstorming techniques?
• Can I tell how brainstorming helps engineering design?

Summary

Ideation means coming up with ideas, and brainstorming is a way to do it. In engineering, students use brainstorming to create many different possible solutions before choosing one to test.

Good brainstorming uses divergent thinking, teamwork, and delayed judgment. Teams share many ideas, welcome unusual ones, and build on each other’s thinking.

After brainstorming, engineers evaluate ideas, test solutions, and improve them. This helps them solve real problems in thoughtful and creative ways.

Testing and Failure Analysis is an important part of engineering. Engineers make things to solve problems, like bridges, toys, shoes, and cups. After they build a first model, called a prototype, they need to test it.

Testing means trying the prototype in a careful way to see how well it works. Sometimes the prototype works well. Sometimes it does not. When something does not work, that is called a failure. In engineering, failure is not the end. It is a way to learn.

Failure analysis means looking closely at what went wrong. Engineers ask questions like: What happened? Where did it happen? Why did it happen? What can we change to make it better next time?

Let’s learn how engineers test, observe, and improve their ideas.

1. What is a prototype?

A prototype is a first model of something you want to make. It does not have to be perfect. It is made so you can try it out and learn from it.

For example, if you want to make a paper bridge, your first bridge is your prototype. You test it before making a better one.

2. Why do engineers test?

Engineers test to find out if a design solves the problem. A design might look good, but testing shows what really happens.

Testing also helps engineers be fair and careful. They do not just guess. They watch, measure, and write down what they see.

3. What are controlled tests?

A controlled test is a test where you keep most things the same and change only one thing. This helps you know what caused the result.

Imagine you are testing two paper airplanes. If one is large and one is small, and one is thrown hard while the other is thrown softly, it is hard to know why one flew farther. Too many things changed.

But if both airplanes are the same size, folded the same way, and thrown from the same spot, then the test is more fair. Now you can compare them better.

4. What are stressors?

A stressor is something that puts a test on an object. It pushes, pulls, bends, drops, or uses the object to see if it stays strong and works well.

Here are some examples of stressors:

• Putting books on a paper bridge
• Dropping a box to see if it protects an egg
• Pouring water into a cup to see if it leaks
• Blowing wind on a tower with a fan

These tests help engineers learn where a design is strong and where it is weak.

5. What kind of data do engineers collect?

Data is information you collect during a test. Data helps you remember what happened.

Engineers collect data by:

• Counting
• Measuring
• Watching carefully
• Writing notes

Here are some examples of data:

• How many books a bridge held
• How far a car rolled
• Whether a tower fell or stayed up
• Where a crack or tear happened

Good data is clear and honest. Engineers write what really happened, even if the result is not what they wanted.

6. How do engineers find the failure point?

The failure point is the place or moment when something stops working.

For example:

• A bridge bends too much in the middle
• A paper chair leg folds
• A boat lets water in at one corner
• A taped joint comes apart

When engineers find the failure point, they learn what to fix.

7. Questions engineers ask after a test

After testing, engineers think carefully. They may ask:

• Did the prototype solve the problem?
• What part worked well?
• What part failed?
• When did it fail?
• What caused the failure?
• What should we change next?

These questions help them improve their design.

8. Testing more than once

Engineers do not test only one time. They test again and again. This is called improving or redesigning.

Each test teaches something new. Maybe the first bridge held 2 books. After adding folds, the next bridge held 4 books. Testing helps engineers make stronger and better designs.

You can think of the engineering steps like this:

1. Ask what problem to solve
2. Build a prototype
3. Test it
4. Collect data
5. Find the failure point
6. Improve the design
7. Test again

Worked Example 1: Testing a Paper Bridge

A class makes a paper bridge to hold toy blocks. They place blocks on the bridge one at a time.

Here is the data:

• After 1 block: bridge stays up
• After 2 blocks: bridge stays up
• After 3 blocks: bridge bends
• After 4 blocks: bridge falls

What is the failure point?

The bridge failed at 4 blocks because that is when it fell and stopped working.

What can we learn?

The middle of the bridge may be too weak. Next time, students could fold the paper to make it stronger or add support underneath.

Worked Example 2: Testing Two Cups

Two cups are made from different materials. Cup A is paper. Cup B is plastic. Students pour the same amount of water into each cup.

They watch carefully.

• Cup A gets soft and leaks at the bottom
• Cup B holds the water and does not leak

What happened?

Cup A failed because it leaked. The failure point was the bottom of the cup.

Why is this a fair test?

Both cups got the same amount of water. That helps students compare the cups fairly.

What can we learn?

Some materials are better for holding water. If students want to improve Cup A, they may need a different material or stronger bottom.

Worked Example 3: Testing a Tower in Wind

Students build a small tower from straws. They use a fan to act like wind.

First test:

• Low fan speed: tower stands
• Medium fan speed: tower shakes
• High fan speed: tower tips over

What is the failure point?

The tower failed at high fan speed because it tipped over.

Where might the problem be?

The bottom may be too narrow, or the tower may be too tall and wobbly.

How could students improve it?

They could make a wider base, use more supports, or make the tower shorter. Then they should test it again in the same way.

Worked Example 4: Looking at Data Carefully

A toy car rolls down a ramp three times.

The distances are:

• Test 1: 5 steps
• Test 2: 5 steps
• Test 3: 2 steps

What should students notice?

Most tests went 5 steps, but one test went only 2 steps. Students should look for what changed.

Questions to ask:

• Was the ramp in the same place each time?
• Was the car released the same way?
• Did something block the wheel?

What can we learn?

Careful testing matters. If one test is different, students should check what happened and test again fairly.

Tips for young engineers

• Test one thing at a time
• Keep the test fair
• Watch closely
• Write down what happens
• Do not be upset by failure
• Use failure to learn and improve

Why failure is helpful

Sometimes people think failure means they did a bad job. In engineering, failure can be very helpful. It shows what needs to change.

If a paper boat sinks, that does not mean the student should quit. It means the student learned something important. Maybe the sides were too low. Maybe there was a hole. Now the student can make a better boat.

Engineers learn by trying, testing, and improving. That is how many useful inventions are made.

Let’s remember

• A prototype is a first model
• Testing shows how well it works
• A stressor is something that tests the object, like weight, water, or wind
• Data is information collected during testing
• A failure point is where or when the object stops working
• Failure analysis helps engineers decide what to fix
• Testing again helps make designs better

Brief Summary

Engineers build prototypes and test them in fair, careful ways. They collect data, look for the failure point, and learn what went wrong. Then they improve the design and test again. Failure is not the end—it is a helpful step for making things better.

Rapid Prototyping is a way engineers and inventors test ideas quickly by making a simple model first.

Instead of spending a lot of time, money, and materials on a final product right away, they build a low-fidelity prototype. That means a basic version that is quick and easy to make.

This simple model helps them answer an important question: Will this idea work?

Rapid prototyping is part of the engineering design process. In this process, people:

1. Identify a problem.
2. Imagine possible solutions.
3. Plan a design.
4. Build a prototype.
5. Test it.
6. Improve it.

The word rapid means fast. The word prototype means an early model. So rapid prototyping means making a quick model to test an idea.

Engineers use rapid prototyping because it helps them learn before making the real product. If something does not work, they can fix it early.

This saves:

• Time
• Money
• Materials

It also helps people compare different ideas and choose the best one.

A rapid prototype does not need to look perfect. It only needs to help test an important part of the design.

For example, if a team is designing a backpack with a new pocket, they do not need to sew the whole backpack first. They can make a paper or cloth model of just the pocket to see if it opens and closes well.

That is the big idea of rapid prototyping: test small and simple before building big and expensive.

What can a rapid prototype be made of?

Rapid prototypes can be physical or digital.

A physical prototype is something you can hold. It might be made from:

• Paper
• Cardboard
• Tape
• Clay
• Straws
• Craft sticks
• Recycled materials

A digital prototype is made on a computer or tablet. It could be:

• A drawing of a new app screen
• A simple 3D model
• A slide show that shows how something works

Both kinds help people test ideas before making the final version.

What does low-fidelity mean?

Low-fidelity means simple, not detailed, and quick to change.

For example, imagine designing a new playground slide. A low-fidelity prototype might be:

• A sketch on paper
• A small model made from cardboard
• A toy-sized version made from blocks

It is not the full real slide. It is just enough to test shape, size, or safety ideas.

A low-fidelity prototype is useful because you can change it easily. If one part does not work, you can cut, fold, redraw, or rebuild it without wasting much.

Why is rapid prototyping important?

Many human problems are complex. That means they can have many parts, many needs, and more than one possible answer.

For example, if students want to design a better lunch tray, they might need to think about:

• How much food it holds
• Whether it is easy to carry
• Whether it spills
• How much it costs
• How easy it is to clean

It is hard to know the best design just by thinking about it. A prototype helps people test their ideas in a real way.

Rapid prototyping lets designers:

• See problems early
• Try more than one idea
• Get feedback from other people
• Improve the design step by step

This repeated process is called iteration. Iteration means doing something again and again, making it better each time.

Rapid prototyping and testing

When engineers make a prototype, they do not just look at it. They test it.

Testing means trying the prototype to see what it does well and what needs to improve.

Good tests focus on a question. For example:

• Can the bridge hold weight?
• Does the container stop water from leaking?
• Can a person use the handle easily?

After testing, engineers record what happened. Then they decide what changes to make.

Sometimes they measure results with numbers. Numbers help compare designs fairly.

For example, if one paper bridge holds 8 books and another holds 12 books, the second design held more weight.

We can compare with subtraction:

$$12 - 8 = 4$$

So the second bridge held 4 more books.

Steps for rapid prototyping

1. Choose one part of the problem to test.
   Do not try to test everything at once.
2. Build a simple model.
   Use easy materials and keep it basic.
3. Test the model.
   Observe what works and what does not.
4. Collect data.
   Write notes, measure, count, or time the results.
5. Improve the design.
   Change one or more parts based on the test.
6. Test again.
   See whether the new version works better.

This cycle can happen many times. Each version teaches something new.

Example 1: Designing a paper bridge

Problem: Build a paper bridge that can hold the most coins.

Prototype 1: A flat strip of paper across two books.

Test: It holds 5 coins before bending too much.

What was learned? A flat shape is weak for this job.

Prototype 2: Fold the paper into an accordion shape.

Test: It holds 14 coins.

Compare the results:

$$14 - 5 = 9$$

The second prototype held 9 more coins.

Conclusion: Folding the paper made the bridge stronger. Rapid prototyping helped test a better idea quickly.

Example 2: Designing a water scoop for a garden

Problem: Make a tool that scoops water without spilling much.

Prototype 1: A small cup shape made from paper.

Test: It holds water, but the paper gets soft and leaks.

Prototype 2: A scoop made from plastic and tape.

Test: It holds water better and does not leak.

What changed? The material changed from paper to plastic.

What was learned? Rapid prototypes help show whether the shape and the material are good choices.

Example 3: Designing a desk organizer

Problem: Create an organizer that holds pencils, scissors, and sticky notes.

Prototype 1: A drawing with three sections.

Why start with a drawing? A drawing is a fast digital or paper prototype. It helps plan size and placement.

Prototype 2: A cardboard model with small boxes.

Test: The pencil section works, but the sticky note section is too narrow.

Measurement: The sticky notes are 8 centimeters wide, but the space is only 6 centimeters wide.

We can find the difference:

$$8 - 6 = 2$$

The space is 2 centimeters too small.

Improvement: Make that section wider in the next prototype.

Conclusion: The prototype revealed a size problem before the final organizer was built.

Example 4: Designing a new app screen for students

Problem: Make a reading app easier for students to use.

Prototype 1: A simple digital drawing of the home screen.

Test: Students try to find the "Start Reading" button.

Result: 7 out of 10 students find it quickly.

Prototype 2: Make the button bigger and move it to the center.

Result: 9 out of 10 students find it quickly.

Compare:

$$9 - 7 = 2$$

The improved design helped 2 more students find the button quickly.

Conclusion: A digital rapid prototype can test ease of use without building a real app first.

What makes a good rapid prototype?

A good rapid prototype is:

• Simple enough to build quickly
• Focused on one main idea or problem
• Easy to test
• Easy to change

A good rapid prototype is not always pretty. It is useful because it helps people learn.

Things students should remember

• You do not need to build the whole final product first.
• A simple model can teach a lot.
• Testing gives evidence, not just guesses.
• Mistakes are helpful because they show what to improve.
• Designs often get better through many small changes.

Rapid prototyping in everyday life

People use rapid prototyping in many jobs and activities:

• Engineers test bridges, tools, and machines.
• Inventors test new products.
• Game designers test rules and parts.
• App designers test screen layouts.
• Students test science and engineering projects.

No matter the project, the goal is similar: learn quickly, improve quickly, and avoid wasting resources.

Summary

Rapid prototyping means making a quick, simple model to test a design idea.

These prototypes can be physical or digital, and they are often low-fidelity, which means basic and easy to change.

By building, testing, measuring, and improving prototypes, engineers and students can find better solutions to problems while saving time, money, and materials.

Rapid prototyping is powerful because it turns ideas into something testable, and every test helps make the design stronger.

Reverse engineering means taking something that already exists, looking closely at how it works, and using what you learn to understand its design.

Engineers do this when they want to learn from a tool, toy, machine, or device. They might take it apart, study each piece, and ask, “Why was it made this way?”

Reverse engineering is part of the engineering design process because it helps people improve old designs and create better new ones.

For example, if you look inside a flashlight, you can figure out how the battery, wires, switch, and bulb work together. Then you can think of ways to make the flashlight brighter, safer, or easier to use.

Why do engineers use reverse engineering?

• To understand how something works
• To learn why certain materials and shapes were chosen
• To find problems or weak parts
• To improve a design
• To create a new product inspired by an older one

Reverse engineering does not mean copying someone else’s work unfairly. In science and engineering, it means studying a design so you can understand it and make thoughtful improvements.

How reverse engineering works

1. Observe the object. Look at the outside first. What does it do? What problem does it solve?
2. Ask questions. What parts can you see? What materials were used? Why is it shaped this way?
3. Take it apart carefully. Study one piece at a time if it is safe and allowed.
4. Analyze the parts. Figure out what each part does and how the parts work together.
5. Infer the design choices. Make smart guesses about why the designer used those parts, shapes, and materials.
6. Think of improvements. Could it be stronger, cheaper, safer, lighter, or easier to use?

Important science and engineering ideas

When engineers reverse engineer something, they think about structure and function. Structure is how something is built. Function is what it does.

For example, a spoon has a curved bowl shape. That structure helps its function, which is holding food or liquid.

Engineers also think about materials. Materials are what an object is made from, such as plastic, metal, rubber, wood, or glass.

Each material has properties. Some are hard, soft, flexible, waterproof, or strong. A designer chooses materials that fit the job.

Engineers also think about manufacturing, which means how something is made. Was it cut, molded, glued, snapped together, or screwed together?

Looking at manufacturing helps engineers understand why a product costs more or less and how easily it can be built.

Questions to ask during reverse engineering

• What problem does this object solve?
• What are its main parts?
• What does each part do?
• How do the parts connect?
• What materials were used?
• Why might the designer have chosen those materials?
• What works well?
• What could be improved?

Worked Example 1: Reverse engineering a paper clip

Let’s start with a very simple object: a paper clip.

Step 1: Observe. A paper clip holds papers together.

Step 2: Analyze the structure. It is made from one piece of bent metal wire.

Step 3: Think about material. Metal is strong enough to hold papers, but flexible enough to bend into shape.

Step 4: Infer design choices. The loops help grip the paper without tearing it. Using one piece of wire makes it simple and cheap to make.

Step 5: Improve. A possible improvement could be a rubber coating so it grips better and slides less.

What we learned: Even a small object has a design, a purpose, and materials chosen for a reason.

Worked Example 2: Reverse engineering a water bottle

Now let’s look at a reusable water bottle.

Observation: It holds water so a person can drink while traveling, working, or playing.

Parts:

• The bottle body
• The lid
• The opening
• Sometimes a handle or straw

Materials: Many bottles are made of plastic or metal. The lid may have rubber around it to help stop leaks.

Why these choices?

• Plastic can be lightweight.
• Metal can keep drinks cold longer.
• Rubber can help make a tight seal.

Manufacturing clues: If the bottle has seams, it may have been made in parts and joined together. If it is smooth and one piece, it may have been molded.

Possible improvements:

• Add measurement marks on the side
• Make the lid easier for children to open
• Add a non-slip grip

What we learned: Reverse engineering helps us see how shape, material, and making method all matter.

Worked Example 3: Reverse engineering a flashlight

A flashlight is a great example because its parts work together in a system.

Main parts:

• Battery
• Wires or metal contacts
• Switch
• Bulb or LED
• Case

What each part does:

• The battery provides energy.
• The wires or contacts carry energy through the flashlight.
• The switch opens or closes the path for energy.
• The bulb or LED gives off light.
• The case protects the inside parts.

If the switch is on, the path is complete and the light turns on. If the switch is off, the path is broken and the light turns off.

You can think of it like this:

Switch on = complete path = light works

Switch off = broken path = light does not work

Design choices:

• The case is often plastic or metal to protect the parts.
• The lens is clear so light can pass through.
• The switch is placed where a hand can reach it easily.

Possible improvements:

• Make it waterproof
• Add a brighter LED
• Use a rechargeable battery

What we learned: Reverse engineering can help us understand systems with several connected parts.

Worked Example 4: Comparing two lunch boxes

Sometimes engineers reverse engineer by comparing two designs that do the same job.

Imagine two lunch boxes:

• Lunch Box A is soft and made of fabric.
• Lunch Box B is hard and made of plastic.

Question: Why did the designers choose different materials?

Analysis:

• Fabric is light and easy to carry.
• Plastic is stiff and protects food from being crushed.

Possible conclusion: The designers made different choices because they cared about different needs.

Improvement idea: Make a lunch box with a soft outside for comfort and a firm inside for protection.

What we learned: Reverse engineering can show that there is often more than one good solution to a problem.

Using math in reverse engineering

Engineers also use measurements when they study objects. They may measure length, width, mass, or how much something can hold.

For example, if one bottle holds 500 milliliters and another holds 750 milliliters, we can find the difference:

$$750 - 500 = 250$$

The second bottle holds 250 more milliliters.

If a flashlight uses 2 batteries and each battery is 1.5 volts, then the total is:

$$2 \times 1.5 = 3$$

The flashlight uses 3 volts in all.

These kinds of measurements help engineers compare designs and decide what works best.

How reverse engineering connects to improving solutions

In 5th grade science, you learn that engineers solve human problems by designing, testing, and improving solutions. Reverse engineering fits into this process because it gives engineers a place to start.

Instead of guessing, they can study a real object, find out what works well, and notice what needs to be changed.

Then they can build a new version, test it, and improve it again. This is called an iterative design process, which means repeating steps to make something better.

Safe classroom reverse engineering

If you do reverse engineering in class, always follow safety rules.

• Only take apart objects your teacher says are safe
• Use tools carefully
• Keep track of small pieces
• Do not touch batteries, wires, or sharp parts unless an adult says it is safe

Tips for being a good reverse engineer

• Look closely before taking anything apart
• Draw what you see
• Label parts
• Write down questions and ideas
• Think about both what works and what does not work
• Be respectful of the original design

Summary

Reverse engineering is the process of studying an existing object to understand how it works, why it was designed that way, and how it could be improved.

By observing parts, materials, structure, and manufacturing clues, engineers learn design principles they can use in new inventions.

When you reverse engineer, you are not just taking something apart. You are thinking like an engineer: asking questions, finding evidence, and using what you learn to solve problems better.

Evaluating Safety and Ethics in Design

When people make something new, like a toy, a chair, or a playground slide, they need to think about more than just how it works. They also need to think, Is it safe? and Is it kind and fair?

This is called thinking about safety and ethics in design. Safety means making sure people, animals, and nature do not get hurt. Ethics means making choices that are kind, fair, and helpful.

Good designers ask questions before they build something. They try to notice problems early so they can fix them.

What is safety?

Safety means keeping people protected from harm. A safe design helps stop cuts, falls, burns, or other injuries.

Here are some safety questions a designer can ask:

• Does it have sharp parts?
• Can someone trip or fall?
• Is it too hot?
• Is it too heavy?
• Could it break easily?
• Is it safe for small children to use?

Designers also think about what could happen by accident. Sometimes a new thing works well, but it may still cause a problem if people use it the wrong way or if it breaks.

What is ethics?

Ethics means doing what is right. In design, that means making things that are kind, fair, and helpful.

Here are some ethics questions a designer can ask:

• Will this help people?
• Could this hurt people or animals?
• Is it fair for everyone?
• Does it keep nature clean and healthy?
• Does it waste too much water, paper, or plastic?

A design should not only be useful. It should also be a good choice for people and the world around us.

Thinking about people

Designers make things for people to use. So they need to think about the people first.

They can ask:

• Can children use it safely?
• Can older people use it?
• Is it easy to hold, push, or carry?
• Will it make someone feel left out?

A good design should help people and not make life harder or more dangerous.

Thinking about nature

Designers also think about the natural world. Nature includes plants, animals, air, water, and land.

If a design makes too much trash or pollutes water, that is a problem. If it scares animals or hurts plants, that is also a problem.

Good designers try to:

• Use less waste
• Reuse materials when they can
• Keep water and air clean
• Protect plants and animals

Looking for hazards

A hazard is something that could cause harm. A designer looks for hazards before people use the new thing.

Some common hazards are:

• Sharp edges
• Slippery parts
• Loose pieces
• Very hot parts
• Toxic or unsafe materials

If a designer finds a hazard, the design can be changed. Fixing problems is an important part of engineering.

How designers evaluate a design

To evaluate means to look closely and decide if something is good, safe, and helpful.

A designer can follow simple steps:

1. Look at the design.
2. Ask what could go wrong.
3. Think about who could get hurt.
4. Think about how nature could be affected.
5. Change the design to make it better.

Sometimes designers test their ideas with models. A model is a small sample or first version. Testing helps them find problems before many people use the design.

Worked Example 1: A toy car

A student designs a toy car. It rolls fast and looks fun.

Now we evaluate it.

• Safety check: One wheel has a sharp metal pin sticking out.
• Problem: A child could get poked or scratched.
• Fix: Cover the sharp part or use a smooth piece instead.

Answer: The toy car is not safe yet. The designer should fix the sharp part before children play with it.

Worked Example 2: A water bottle for school

A designer makes a water bottle for children. It is strong and colorful.

Let us think about safety and ethics.

• Safety check: Is the lid easy to open without spilling?
• Safety check: Could a small piece come off?
• Ethics check: Can the bottle be used again and again, or is it thrown away after one use?

If the lid breaks into tiny pieces, that is not safe. If the bottle can be reused many times, that is better for nature because it makes less trash.

Answer: A better design has no loose tiny parts and can be reused.

Worked Example 3: A playground slide

A town wants to build a new playground slide.

The slide is tall and exciting. But designers must ask more questions.

• Safety check: Are there rails so children do not fall?
• Safety check: Does the slide get too hot in the sun?
• Ethics check: Can many children use the playground?
• Nature check: Will building it hurt nearby trees or plants?

If the slide gets too hot, it could burn skin. If the builders cut down healthy trees when they do not need to, that is not a good choice for nature.

Answer: A better slide has rails, safer materials, and careful building that protects plants.

Worked Example 4: A classroom trash helper

A class designs a small rolling bin to help collect paper scraps.

It sounds helpful, but we still evaluate it.

• Safety check: Are the wheels steady?
• Safety check: Is the handle smooth and easy to hold?
• Ethics check: Does it help the class keep the room clean?
• Nature check: Can the paper inside be recycled?

If the bin tips over easily, someone could trip. If the class uses it to collect paper for recycling, that is helpful for the Earth.

Answer: The best design is steady, easy to use, and helps reduce waste.

How to make a design better

Designers do not have to be perfect the first time. They learn by improving their ideas.

Here are ways to make a design better:

• Make sharp parts smooth
• Use strong materials that do not break easily
• Choose safe sizes and shapes
• Use less plastic or make less trash
• Protect plants, animals, and water
• Test the design and fix problems

Safety and ethics work together

Sometimes a design can be safe for people but still not be good for nature. Sometimes it can help one group but leave out others. That is why designers need to think about both safety and ethics.

A great design is:

• Safe for people
• Helpful and fair
• Careful with nature
• Improved when problems are found

Questions you can ask about any design

• Could someone get hurt?
• Could an animal or plant be hurt?
• Does it make too much trash?
• Is it kind and fair?
• How can we make it better?

Summary

When we evaluate a design, we look for hazards and think about what could go wrong. We ask if the design is safe for people and kind to nature.

We also think about ethics, which means doing what is right, fair, and helpful. Good designers test, notice problems, and make changes so their designs are safer and better for everyone.

Biomimetics and Bio-inspired Design is when people study living things in nature and use what they learn to solve human problems. Engineers look at plants, animals, and other living things to get ideas for new inventions.

The word biomimetics means “copying life.” Another way to say it is bio-inspired design, which means a design inspired by nature. Nature has had millions of years to “test” ways to survive, move, stay safe, and gather food. Because of that, many parts of nature are smart models for human design.

For example, a bird’s wing helps it move through air. A burr plant has tiny hooks that stick to animal fur. A lotus leaf can stay clean because water rolls off it. When engineers notice these helpful features, they ask, “Can we use this idea in something people make?”

Why do engineers look at nature? Nature can help people design things that are:

• Efficient — using less energy or fewer materials
• Strong — able to last a long time
• Safe — protecting people better
• Useful — solving a problem well

Biomimetics is part of the engineering design process. This is a series of steps engineers use to solve problems. They do not just build one thing and stop. They test it, learn from it, and improve it.

A simple design process looks like this:

1. Ask — What is the problem?
2. Imagine — What ideas could solve it?
3. Plan — Which idea will you try?
4. Create — Build a model or product.
5. Test — Does it work well?
6. Improve — Change it to make it better.

When engineers use biomimetics, they add one more important idea: observe nature. They look closely at how a plant or animal solves a problem in its environment.

Nature’s adaptations are features or behaviors that help living things survive. A duck’s webbed feet help it swim. A cactus has a thick stem to store water. An owl’s feathers help it fly quietly. These adaptations can inspire designs for people.

Here are some common examples of bio-inspired design:

• Velcro was inspired by burrs that stick to fur and clothing with tiny hooks.
• Airplanes were inspired in part by birds and how wings move through air.
• Swimsuits have been designed to move smoothly through water like shark skin.
• Fans and wind blades can be shaped using ideas from whale fins for smoother movement.
• Self-cleaning surfaces have been inspired by lotus leaves, which let water roll off and carry dirt away.

How does biomimetics work? Engineers usually follow a pattern:

1. Find a human problem.
2. Look for a similar problem in nature.
3. Study the adaptation that helps the plant or animal.
4. Use that idea to design a tool, product, or machine.
5. Test the design and improve it.

For example, if engineers want to make a train move more quietly, they might look for an animal that moves through air or water with little noise. If they find a bird with a beak shape that cuts through air smoothly, they can test whether a train nose with a similar shape works better.

Worked Example 1: Velcro and burrs

Problem: People need a fastener that is easy to open and close.

Nature idea: Burr seeds stick to animal fur using tiny hooks.

Design: Make one strip with tiny hooks and another strip with tiny loops.

Result: The hooks grab the loops, just like burrs grab fur. This makes a simple fastener called Velcro.

What we learn: A plant adaptation can inspire a useful human invention.

Worked Example 2: Bird wings and airplanes

Problem: People want to fly through the air.

Nature idea: Birds use wings shaped to move through air and create lift.

Design: Engineers build airplane wings with shapes that help air move above and below the wing.

Result: Airplanes can rise and travel long distances.

What we learn: Watching how birds fly can help engineers design better flying machines.

Worked Example 3: Shark skin and swim gear

Problem: Swimmers and boats want to move through water with less drag.

Nature idea: Shark skin has tiny patterns that help water flow past the body.

Design: Make swim gear or surfaces with special textures that reduce drag.

Result: The object may move more smoothly through water.

What we learn: Tiny surface details in nature can lead to better designs.

Worked Example 4: Lotus leaves and self-cleaning paint

Problem: Buildings get dirty and are hard to clean.

Nature idea: Lotus leaves have a surface that makes water bead up and roll away, carrying dirt with it.

Design: Create paint or glass with a similar surface texture.

Result: Rain can help wash off dirt.

What we learn: Engineers can copy a surface from nature to make cleaning easier.

Biomimetics uses science and math. Engineers measure, compare, and test their ideas. They may ask questions like:

• Which shape moves fastest?
• Which material is strongest?
• How much weight can it hold?
• How far does it travel?

They often collect data. Data is information gathered during tests. For example, if three paper airplane wing designs fly different distances, engineers can measure each distance and compare them.

Imagine three wing designs inspired by different birds. If they fly:

• Design A: 4 meters
• Design B: 6 meters
• Design C: 5 meters

The longest flight is 6 meters, so Design B worked best in that test. Engineers would still test more times, because one test is usually not enough.

They might find the average distance by adding the flights and dividing by the number of tests. If one design flew 5 m, 6 m, and 7 m, the average would be:

$$\frac{5+6+7}{3}=\frac{18}{3}=6$$

So the average distance is 6 meters.

Testing matters because a first idea is not always the best idea. Engineers improve designs step by step. This is called an iterative design process. Iterative means repeating the steps to make the solution better each time.

For example, an engineer making a bird-inspired paper glider might:

• Build a first model
• Test how far it flies
• Notice that it dips too quickly
• Change the wing shape
• Test again

Each test gives new information. That information helps the engineer improve the design.

Important idea: Engineers do not copy nature exactly. They usually copy the function, or job, of the adaptation. A plane does not flap exactly like a bird, but it uses wing ideas to move through air. Velcro is not a plant, but it copies the way burrs attach.

Biomimetics can help solve many kinds of problems, such as:

• Transportation problems, like moving faster or more quietly
• Building problems, like making stronger structures
• Clothing problems, like making fabric warmer or more waterproof
• Medical problems, like making tools that grip gently
• Environmental problems, like saving energy or water

How can you think like a bio-inspired engineer?

1. Look at a problem around you.
2. Ask, “Does nature solve a similar problem?”
3. Observe carefully.
4. Sketch your idea.
5. Build a model.
6. Test it fairly.
7. Improve it.

Suppose your problem is that a backpack gets wet in the rain. You might ask what in nature stays dry or lets water roll off. You could study duck feathers or lotus leaves. Then you might design a backpack cover with a water-shedding surface.

Suppose your problem is making shoes that grip slippery ground. You might look at geckos, mountain goats, or animals with padded feet. Then you could test different sole patterns.

Things to remember when testing a design:

• Change only one main thing at a time if possible.
• Measure carefully.
• Test more than once.
• Write down results.
• Use the results to improve the design.

Biomimetics shows that science and engineering are connected. Science helps us understand how living things work. Engineering uses that understanding to create helpful solutions for people.

Summary

Biomimetics, or bio-inspired design, means learning from nature to solve human problems. Engineers study adaptations in plants and animals, such as burr hooks, bird wings, shark skin, and lotus leaves. Then they use the engineering design process to build, test, and improve solutions. Nature gives great ideas, and careful testing helps turn those ideas into useful inventions.

Cost-Benefit and Life Cycle Analysis helps us think carefully about products we use every day. Engineers and scientists do not only ask, “Does this product work?” They also ask, “How much does it cost?” and “How does it affect the Earth?”

When we study a product from the very beginning to the very end, we are doing a life cycle analysis. This means looking at the product from getting raw materials, to making it, to using it, and finally to throwing it away or recycling it.

When we compare the good things and the not-so-good things about a product, we are doing a cost-benefit analysis. A benefit is something helpful or good. A cost can mean money spent, but it can also mean harm to the environment, like pollution or waste.

These ideas are important in engineering design. Engineers often test different ideas, compare them, and improve them. They want to build solutions that are useful, affordable, and better for the environment.

Part 1: What is a life cycle?

Every product has a life cycle. A product’s life cycle has several stages.

• Raw material extraction: getting materials from nature, such as wood from trees, metal from rocks, or oil from the ground.
• Manufacturing: turning those materials into a product in a factory.
• Transportation: moving the product from place to place by truck, train, ship, or plane.
• Usage: how people use the product and what it needs while being used, such as water, electricity, or batteries.
• Disposal or recycling: what happens when the product is no longer needed.

Looking at all these stages helps us understand the total effect of a product. Sometimes a product seems cheap at first, but later it may cost more money or create more trash. Another product may cost more at the start, but save money and resources later.

Part 2: What kinds of costs do we look at?

In science and engineering, cost does not only mean the price tag in a store. We can think about two big types of cost:

• Economic cost: money needed to make, buy, use, and get rid of a product.
• Environmental cost: effects on air, water, land, animals, plants, and natural resources.

Examples of economic costs include:

• cost of materials
• cost to build the product
• cost to ship it
• cost to use it, such as electricity or fuel
• cost to repair or replace it

Examples of environmental costs include:

• cutting down trees
• using a lot of water
• air pollution from factories or trucks
• trash left in landfills
• harm to habitats

Part 3: What are benefits?

A benefit is a helpful result. Benefits can also be about money and the environment.

Examples of benefits include:

• a product lasts a long time
• it is cheaper to use
• it makes less trash
• it can be recycled
• it uses less energy or water
• it helps people solve a problem safely

Good engineering design tries to increase benefits and reduce costs.

Part 4: Thinking through the whole life cycle

Let’s imagine a simple product: a plastic water bottle.

1. Raw materials: Plastic is often made from oil taken from the Earth.
2. Manufacturing: Factories use energy to shape the bottle.
3. Transportation: Trucks move the bottles to stores.
4. Usage: A person may use the bottle once.
5. Disposal: The bottle may be thrown away, recycled, or become litter.

Now compare that with a reusable metal water bottle.

1. Raw materials: Metal must be mined from the Earth.
2. Manufacturing: Making the bottle may take more energy than making one plastic bottle.
3. Transportation: It is sent to stores.
4. Usage: A person can use it many times.
5. Disposal: It may last for years and may be recyclable.

At first, the reusable bottle may cost more money. But over time, it may save money because you do not keep buying new bottles. It may also create less trash if used many times. This is why looking at the whole life cycle matters.

Part 5: How to do a simple cost-benefit analysis

You can follow a few steps:

1. Name the product or design.
2. List its life cycle stages.
3. Write the economic costs.
4. Write the environmental costs.
5. Write the benefits.
6. Compare choices and decide which is better for the job.

Sometimes engineers use numbers to compare choices. Even simple math can help.

For example, if one product costs \(\$8\) and another costs \(\$3\), the difference is:

$$8 - 3 = 5$$

So one product costs \(\$5\) more at the start.

But if the more expensive product lasts much longer, it might still be the better choice.

Worked Example 1: Paper bag or plastic bag?

A store is choosing between paper bags and plastic bags. Let’s compare them.

Paper bag:

• Made from trees
• Can often be recycled
• May tear if wet
• Usually costs more to make than a thin plastic bag

Plastic bag:

• Made from oil
• Usually costs less to make
• Can last a long time in the environment if littered
• May be harder to recycle in some places

Thinking it through:

• Economic cost: Plastic may be cheaper at first.
• Environmental cost: Plastic may create more long-lasting waste.
• Benefit: Paper may be easier to recycle.

Conclusion: There is not always one perfect answer. Engineers and communities must decide which choice gives the best balance of cost and environmental impact.

Worked Example 2: Light bulb choice

A family can buy one LED bulb for \(\$6\) or one older-style bulb for \(\$2\). The older-style bulb must be replaced 3 times while the LED lasts.

Step 1: Compare buying cost over time.

Older-style bulb total cost:

$$3 \times 2 = 6$$

LED bulb total cost:

$$1 \times 6 = 6$$

The buying cost is the same over that time.

Step 2: Think about usage.

The LED uses less electricity. That means it can save more money while being used.

Step 3: Think about waste.

Using 3 old bulbs creates more trash than using 1 LED bulb.

Conclusion: Even though the LED costs more at first, it may be the better choice because it saves energy and creates less waste.

Worked Example 3: Disposable lunch tray or reusable lunch tray

A school is comparing lunch trays.

Choice A: Disposable tray costs \(\$1\) each day.

Choice B: Reusable tray costs \(\$5\), and it can be used for 10 days.

Step 1: Find the cost for 10 days.

Disposable trays for 10 days:

$$10 \times 1 = 10$$

Reusable tray for 10 days:

$$5$$

Step 2: Compare.

Difference:

$$10 - 5 = 5$$

The reusable tray saves \(\$5\) over 10 days.

Step 3: Think about environmental cost.

The disposable tray makes 10 trays of trash. The reusable tray makes much less trash during those 10 days.

Conclusion: The reusable tray has a higher cost at the start, but it saves money over time and reduces waste.

Worked Example 4: Choosing a pencil

A student can choose:

• Option 1: a wooden pencil for \(\$1\)
• Option 2: a refillable pencil for \(\$4\)

The wooden pencil lasts 1 month. The refillable pencil lasts 4 months.

Step 1: Compare cost for 4 months.

Wooden pencils needed in 4 months:

$$4 \times 1 = 4$$

Refillable pencil needed in 4 months:

$$4$$

The money cost is the same for 4 months.

Step 2: Compare waste.

Option 1 uses 4 pencils. Option 2 uses 1 pencil body and refill material. This may create less waste.

Step 3: Think about materials.

The wooden pencil uses wood. The refillable pencil may use plastic and metal. Different materials have different environmental effects.

Conclusion: Looking at life cycle stages helps us make a smarter choice than just looking at the first price.

Part 6: Why engineers use this in design

Engineers solve problems for people. They may design bottles, lunch trays, buildings, machines, or tools. To choose the best design, they test ideas and compare them.

They may ask:

• Which design costs less over time?
• Which design uses fewer natural resources?
• Which design creates less pollution or trash?
• Which design still works well and is safe?

This is part of the iterative design process. That means engineers make a plan, build it, test it, learn from it, and improve it again. Cost-benefit and life cycle analysis help them improve their designs.

Part 7: Important idea to remember

The cheapest product at the store is not always the cheapest product in the long run. Also, the easiest product to use is not always the best for the environment.

A smart choice looks at the full life cycle and asks:

• How much money will this cost overall?
• How much waste will it make?
• How many resources does it use?
• How long will it last?
• Can it be reused or recycled?

Brief Summary

Cost-benefit analysis compares the good and bad parts of a product or design. Life cycle analysis looks at a product from raw materials to manufacturing, transportation, usage, and disposal. When engineers use both ideas, they can choose solutions that work well, cost less over time, and are better for the environment.

Work and Mechanical Advantage

Have you ever pushed a heavy box, lifted a backpack, or used a ramp to move something up? These are all examples of work.

In science, work happens when a push or pull makes something move. If you push on something and it does not move, you are using force, but you are not doing work yet.

Machines can help us do work. A machine does not make work disappear. Instead, it can make work feel easier by helping us push or lift in a better way.

This lesson will help you learn:

• what work means in science,
• how simple machines help us,
• what mechanical advantage means,
• and how machines trade more distance for less force.

1. What is work?

Work happens when two things go together:

• There is a force like a push or a pull.
• The object moves.

If a toy car is sitting still and you gently push it so it rolls forward, you did work on the toy car.

If you push on a wall as hard as you can, but the wall does not move, that is not work in science, because there was no movement.

We can say it like this:

$$\text{Work = force + movement}$$

You do not need big math here. Just remember: no movement means no work.

2. What is a machine?

A machine is a tool that helps us do work. Some machines are very simple. They help us lift, move, or push things in an easier way.

Here are some simple machines:

• Ramp — helps move things up
• Lever — helps lift or move things
• Pulley — helps lift things by pulling down or around
• Wheel and axle — helps things roll more easily

Machines do not always make a job smaller. They make it easier to do.

3. How do machines make work easier?

A machine can help in two big ways:

• It can help you use less force.
• It can change the direction of your force.

For example, lifting a box straight up can be hard. Using a ramp can make it easier because you push the box up slowly instead of lifting it straight up.

With a pulley, you may pull down to lift something up. The machine changes the direction of the force.

4. What is mechanical advantage?

Mechanical advantage means a machine helps you do work more easily.

If a machine lets you use a small force to move or lift something heavy, that machine gives you mechanical advantage.

Another way to think about it is this: the machine gives your push or pull some extra help.

But there is an important idea to remember: when a machine helps you use less force, you often have to move the object over a longer distance.

So machines often trade:

• less force
• for more distance

5. Less force, more distance

Imagine you need to get a box into a truck.

You could try to lift it straight up. That takes a big force.

Or you could push it up a ramp. That takes less force, but now the box travels a longer path.

The ramp makes the work feel easier because you do not need as big of a push all at once.

We can compare it like this:

• No ramp: bigger force, shorter distance
• With ramp: smaller force, longer distance

That is the big idea of mechanical advantage.

6. Looking at everyday machines

Ramp

A ramp helps you move things upward with less force. You push farther, but it feels easier.

Lever

A lever is a stiff bar that moves on a point. A seesaw is like a lever. A lever can help lift something heavy with less force.

Pulley

A pulley uses a wheel and rope. It can help lift a load. It may also change the direction of force so you can pull down to lift up.

Wheel and axle

A wagon or bicycle uses wheels. Wheels help objects move more easily from place to place.

Worked Example 1: Is it work?

Mia pushes a toy car. The toy car rolls across the floor.

Question: Did Mia do work?

Answer: Yes.

Why?

• Mia used a push.
• The toy car moved.

Since there was a force and movement, Mia did work.

Worked Example 2: Is it work or not?

Jay pushes on a big tree, but the tree does not move.

Question: Did Jay do work on the tree?

Answer: No.

Why?

• Jay used a push.
• But the tree did not move.

No movement means no work in science.

Worked Example 3: Which is easier?

Sara wants to move a heavy box onto a porch.

She has two choices:

1. Lift the box straight up.
2. Push the box up a ramp.

Question: Which choice uses less force?

Answer: Pushing the box up the ramp.

Why?

• The ramp is a simple machine.
• It gives mechanical advantage.
• Sara uses less force.
• But the box moves a longer distance.

So the ramp makes the job easier, even though the box travels farther.

Worked Example 4: Changing direction

Leo uses a pulley to raise a bucket from a well. He pulls down on the rope, and the bucket goes up.

Question: How is the pulley helping Leo?

Answer: The pulley changes the direction of the force.

Why?

• Leo pulls down.
• The bucket moves up.

The pulley helps Leo do the work in an easier way.

7. Important ideas to remember

• Work happens when a force makes something move.
• A machine helps us do work.
• Mechanical advantage means the machine helps make the job easier.
• Machines can help us use less force.
• Machines can also change the direction of a force.
• When we use less force, we often move the object a longer distance.

8. Try thinking about these

• If you pull a wagon and it rolls, are you doing work? Yes, because it moves.
• If you hold a heavy bag still in one spot, are you doing work on it in science? No, because it is not moving.
• If you use a ramp to move a toy up, does the toy travel farther? Yes, but you use less force.

Summary

Work in science means a push or pull makes something move. Simple machines like ramps, levers, pulleys, and wheels help us do work more easily.

Mechanical advantage means a machine helps us use less force or changes the direction of our force. But when a machine makes work easier, we often have to move the object a longer distance.