Engineering Design and Technological Systems

Engineering Design Process is a step-by-step way people solve problems and create useful things. Engineers use this process to design bridges, phones, water filters, playgrounds, and even tools for space.

In 6th Grade science, the engineering design process helps you take what you know about science and math and use it to solve a real-world problem. It is not just about building something once. It is about trying ideas, testing them, and improving them.

One important thing to remember is that the engineering design process is iterative. That means engineers often repeat steps. If a design does not work well, they go back, change it, and test again.

Why is the engineering design process useful?

• It helps solve problems in an organized way.
• It helps people use evidence instead of guessing.
• It encourages creativity and teamwork.
• It helps make products and systems safer and better.

The Main Steps of the Engineering Design Process

1. Identify the problem
2. Research the problem
3. Brainstorm possible solutions
4. Choose the best solution and plan
5. Build a prototype
6. Test the prototype
7. Improve or redesign
8. Share the solution

Let’s look at each step more closely.

1. Identify the problem

Every engineering project starts with a problem or need. Engineers ask: What needs to be fixed? What could work better? What do people need?

A good problem statement is clear. It tells what must be solved. For example: “Design a container that keeps water cold during a school field trip.”

When identifying the problem, engineers also think about criteria and constraints.

• Criteria are the things the solution must do.
• Constraints are the limits, such as time, cost, size, or materials.

Example:

• Problem: Build a paper bridge.
• Criteria: It must hold 20 pennies.
• Constraints: Only 2 sheets of paper and 30 cm of tape may be used.

2. Research the problem

Before building, engineers learn as much as they can. They may read, observe, ask questions, or look at similar designs.

Research helps engineers avoid mistakes and discover useful ideas. If you are designing a water filter, you might research which materials trap dirt best. If you are designing a shade structure, you might research how sunlight moves during the day.

3. Brainstorm possible solutions

Brainstorming means thinking of many possible ideas. At this stage, engineers do not stop at the first idea. They list several options.

Good brainstorming is creative and open-minded. Some ideas may seem unusual at first, but they could lead to a great solution.

• Draw sketches.
• Label parts.
• List materials.
• Think about advantages and disadvantages.

4. Choose the best solution and plan

After brainstorming, engineers compare their ideas. They choose the one that best meets the criteria and fits the constraints.

Then they make a plan. A plan might include:

• a drawing
• a list of materials
• steps for building
• ways to test the design

Planning is important because it helps engineers build carefully instead of randomly.

5. Build a prototype

A prototype is a model or first version of a design. It may not be perfect. Its job is to help engineers see how the idea works.

Prototypes can be small, simple, and made from inexpensive materials. For example, a student designing a desk organizer might first build one from cardboard before making a stronger version from plastic or wood.

6. Test the prototype

Testing shows whether the design works. Engineers collect data during testing so they can make decisions based on evidence.

For example, if you are testing a paper airplane design, you might measure how far it flies. If you are testing a bridge, you might count how much weight it holds before bending.

Testing should connect to the criteria. If the design must hold 20 pennies, then the test should measure how many pennies it can hold.

7. Improve or redesign

Very few designs work perfectly the first time. Engineers study the test results and ask:

• What worked well?
• What did not work well?
• What should be changed?

Then they redesign the prototype and test again. This is why the process is called iterative. Engineers repeat steps to improve their solution.

8. Share the solution

Engineers often explain their design to others. They may show drawings, test results, and reasons for their choices.

Sharing is important because other people can learn from the design, suggest improvements, or use the idea to solve similar problems.

Engineering Design Uses Science, Math, and Careful Thinking

Engineering is connected to science because engineers use scientific ideas to understand how things work. For example, they may use what they know about forces, energy, weather, or materials.

Engineering also uses math. Engineers measure length, mass, time, volume, and temperature. They compare data and look for patterns.

Here is a simple example of using math in testing. Suppose a prototype bridge holds 18 pennies, and the goal is 20 pennies. The bridge is short by

$$20 - 18 = 2$$

So the design needs to hold 2 more pennies to meet the goal.

Sometimes engineers test more than once and find an average. For example, if a paper airplane flies 4 m, 6 m, and 5 m, the average distance is

$$\frac{4 + 6 + 5}{3} = \frac{15}{3} = 5 \text{ m}$$

This helps engineers judge performance more fairly.

Technological Systems and Engineering Design

A technological system is a group of parts that work together to do a job. A bicycle is a system. So is a school bus, a flashlight, or a computer.

When engineers design something, they often think about how different parts work together in a system. For example, in a water bottle with a filter, the cap, filter, container, and straw all need to work together.

This means engineers do not just think about one part. They think about the whole system and how each part affects the others.

Worked Example 1: Designing a Bookmark That Does Not Fall Out

Problem: A student needs a bookmark that stays in a book even when the book is carried in a backpack.

Step 1: Identify criteria and constraints

• Criteria: The bookmark must stay in place and not damage the pages.
• Constraints: Only paper, tape, and one paper clip may be used.

Step 2: Research

The student looks at different bookmark shapes and notices that some slide out easily, while others hook onto a page.

Step 3: Brainstorm

• A long strip of paper
• A folded corner bookmark
• A paper strip with a paper clip attached

Step 4: Choose and plan

The student chooses the paper strip with a paper clip because it may grip the page better.

Step 5: Prototype

The student builds a bookmark from paper and attaches the clip near the top.

Step 6: Test

The book is shaken gently 5 times. The bookmark stays in place 4 out of 5 times.

Step 7: Improve

The student folds the top of the bookmark to make it thicker. After testing again, it stays in place 5 out of 5 times.

Conclusion: Testing and improving helped the student make a better design.

Worked Example 2: Building a Paper Bridge

Problem: Build a bridge from paper that can hold 20 pennies.

Criteria: Hold at least 20 pennies.

Constraints: Use only 2 sheets of paper and 30 cm of tape.

Brainstormed ideas:

• Flat bridge
• Folded bridge with layers
• Accordion-fold bridge

Best choice: The accordion-fold bridge, because folds often make paper stronger.

Test results: The first prototype holds 14 pennies.

The bridge does not yet meet the goal because

$$20 - 14 = 6$$

It needs to hold 6 more pennies.

Redesign: The student adds sharper folds and places the bridge more evenly between the supports.

Second test: The new design holds 22 pennies.

Conclusion: The redesign meets the criteria because 22 is greater than 20.

Worked Example 3: Designing a Small Water Filter

Problem: Make a simple filter that removes visible dirt from water.

Important note: This classroom filter may make water look cleaner, but it does not mean the water is safe to drink.

Criteria: The water should come out clearer than before.

Constraints: Use a plastic bottle, gravel, sand, and cloth.

Research: The student learns that larger pieces of dirt may be trapped by gravel, while smaller pieces may be trapped by sand and cloth.

Brainstorm: The student thinks about different orders for the materials.

Plan: Put cloth at the bottom, then sand, then gravel.

Test: Dirty water is poured in. The water that comes out is clearer, but some dirt is still visible.

Improve: The student adds another cloth layer and packs the sand more evenly.

Second test: The water comes out even clearer.

Conclusion: The student used test results to improve the design.

How to Tell If You Are Using the Engineering Design Process

Ask yourself these questions:

• Did I clearly identify the problem?
• Did I think about criteria and constraints?
• Did I research before building?
• Did I create more than one possible idea?
• Did I test my design in a fair way?
• Did I use data to improve it?

If the answer is yes, then you are using the engineering design process.

Common Mistakes to Avoid

• Starting to build too soon: Good planning saves time.
• Ignoring constraints: A design may be good, but it must still fit the limits.
• Choosing the first idea only: Brainstorming more ideas often leads to better solutions.
• Skipping testing: Without testing, you cannot know how well the design works.
• Giving up after one try: Improvement is a normal part of engineering.

Why Iteration Matters

Iteration means repeating steps to improve a design. This is one of the most important ideas in engineering.

A failed test does not mean the engineer failed. It means the engineer learned something useful. Each test gives information that can lead to a better solution.

Engineers often follow a pattern like this:

Design → Build → Test → Improve → Test again

This cycle continues until the design works as well as possible.

Brief Summary

The engineering design process is a systematic way to solve problems. Engineers identify a problem, research it, brainstorm ideas, choose a solution, build a prototype, test it, and improve it.

The process is iterative, which means steps may be repeated. Engineers use science, math, creativity, and evidence to create solutions that meet criteria and work within constraints.

Systems and System Models

In science, we often study things by looking at them as a system. A system is a group of parts that work together.

A system can be something in nature, like a plant, or something people make, like a bicycle. When we look at a system, we pay attention to its parts and how the parts help each other.

A system model is a simple picture, chart, or idea that helps us understand a system. A model does not have every tiny detail. It shows the most important parts and how they connect.

Learning about systems helps us answer questions like:

• What are the parts?
• How do the parts work together?
• What comes into the system?
• What goes out of the system?

1. What is a system?

A system has parts. Each part does a job. When the parts work together, the whole system can do something.

Think about a flashlight. A flashlight has a bulb, batteries, and a switch. These parts work together to make light.

If one part is missing, the system may not work well or may not work at all.

2. What are system boundaries?

A boundary helps us decide what is part of the system and what is outside the system.

For example, if we are studying a fish tank, the fish, water, plants, rocks, and tank can be part of the system. The table under the tank may be outside the system if we are only studying what happens inside the tank.

Boundaries help us stay focused on the system we want to understand.

3. What goes into a system? Inputs

An input is something that goes into a system.

Inputs can be things like:

• water
• food
• air
• sunlight
• electricity

For a plant system, inputs might be water, air, and sunlight. These things help the plant grow.

4. What comes out of a system? Outputs

An output is something that comes out of a system.

Outputs can be things like:

• light
• sound
• heat
• movement
• grown fruit or flowers

For a flashlight, the output is light. For a plant, outputs can include oxygen, flowers, or fruit.

5. How do parts in a system interact?

Interact means to work together or affect each other.

In a bicycle system, the pedals, chain, and wheels interact. When you push the pedals, the chain moves. When the chain moves, the wheels turn.

This shows that one part can change what another part does.

6. Why do scientists use system models?

Sometimes a real system is too big, too small, or too tricky to study all at once. A model helps us think about the system in a simple way.

A model can be:

• a drawing
• a labeled picture
• a diagram with arrows
• a small copy of something real

Arrows in a model can show what moves into, out of, or between parts of a system.

Example: In a plant model, arrows can show sunlight going to the plant and water going from the soil to the roots.

Worked Example 1: A Plant System

Let us study a plant as a system.

Parts: roots, stem, leaves, flower

Inputs: water, sunlight, air

Outputs: oxygen, flowers, fruit, growth

How parts interact: The roots take in water. The stem helps move water. The leaves use sunlight and air to help the plant make food. The flower can grow into fruit.

Simple model:

• Sunlight  plant
• Water  roots
• Air  leaves
• Plant  growth and oxygen

This model helps us see what goes in and what comes out.

Worked Example 2: A Flashlight System

Now let us study a flashlight.

Parts: batteries, bulb, switch, case

Input: energy from the batteries

Output: light

How parts interact: When you turn the switch on, the batteries send energy to the bulb. The bulb lights up.

Boundary: If we are studying only the flashlight, your hand is outside the system, even though your hand turns it on.

This helps us see that a system has limits. We choose what we are studying.

Worked Example 3: A Fish Tank System

A fish tank is a system with living and nonliving parts.

Parts: fish, water, plants, tank, food

Inputs: fish food, light, clean water

Outputs: fish waste, plant growth, movement

How parts interact: The fish eat the food. The fish swim in the water. The plants grow in the water and need light. The water helps all the living things in the tank.

Boundary: If we are only studying the fish tank, the room around it is outside the system.

Worked Example 4: A Bicycle System

A bicycle is a system people made.

Parts: pedals, chain, wheels, handlebars, seat

Input: a rider pushing the pedals

Output: movement

How parts interact: The rider pushes the pedals. The pedals move the chain. The chain turns the wheels. The bicycle moves forward.

If the chain breaks, the system will not work the same way. This shows that the parts depend on one another.

How to find a system

When you look at something in science, you can ask these questions:

1. What am I studying?
2. What parts does it have?
3. Where is the boundary?
4. What goes in?
5. What comes out?
6. How do the parts work together?

Let us practice with a simple object: a fan

If we study a fan as a system, we can say:

• Parts: blades, motor, switch, cord
• Input: electricity
• Output: moving air, sound
• Interaction: The motor spins the blades, and the blades push the air.

This is a simple system model. It helps us understand what the fan does and how it does it.

Important idea

A system model is not the real thing. It is a helpful way to think about the real thing.

Good models help us notice the main parts, the inputs, the outputs, and the way the parts interact.

Summary

A system is a group of parts that work together. A system model is a simple way to show those parts and how they connect.

When scientists study systems, they look at the boundary, the inputs, the outputs, and the way the parts interact. We can use this idea to understand plants, fish tanks, flashlights, bicycles, and many other things in science.

Criteria and Constraints are two very important ideas in engineering design. Engineers solve problems by creating and improving designs. Before they build anything, they need to know what the design must do and what limits they must work within.

When engineers understand criteria and constraints, they can make smarter choices. This helps them design products, tools, and systems that work well in the real world.

Criteria are the goals or requirements for a successful design. Criteria describe what the solution should do. They answer the question, “What must this design accomplish?”

Constraints are the limits or restrictions on a design. Constraints describe what the engineers must stay within. They answer the question, “What limits do we have?”

Think of it this way:

• Criteria = what you want
• Constraints = what limits you

Both ideas matter. A design is not successful if it meets the criteria but breaks the constraints. For example, a bridge design may be very strong, but if it costs too much money or uses materials that are not allowed, it is not a good solution.

Here are some common criteria in engineering:

• It must solve a specific problem.
• It must be safe to use.
• It must be strong enough.
• It must hold a certain amount of weight.
• It must move fast enough or work efficiently.
• It should be easy for people to use.

Here are some common constraints in engineering:

• Materials: Only certain supplies can be used.
• Budget: There is a limit on cost.
• Time: The design must be finished by a deadline.
• Size: The design can only be a certain height, length, or width.
• Safety rules: The design must follow rules to protect people.
• Physics: The design must follow the laws of nature, like gravity and motion.

Physics is an important constraint because engineers cannot design something that breaks how the world works. For example, a paper tower cannot hold an unlimited amount of weight. Gravity pulls down on objects, and materials have strengths and weaknesses.

In the engineering design process, criteria and constraints are usually identified near the beginning. Engineers first ask questions about the problem. Then they list the criteria and constraints before brainstorming solutions.

This is helpful because it keeps the team focused. If students are asked to design a water bottle holder, they should know the holder must fit the bottle and keep it from falling over. They should also know if they can only use cardboard, tape, and 20 minutes of class time.

How to tell the difference between criteria and constraints:

• If it tells what the design should do, it is probably a criterion.
• If it tells a limit on the design, it is probably a constraint.

For example:

• “The boat must float.” → Criterion
• “You may only use aluminum foil and 1 sheet of paper.” → Constraint
• “The bridge must hold 10 books.” → Criterion
• “You have only \(\$5\) to spend.” → Constraint

Sometimes a design challenge has more than one criterion and more than one constraint. Engineers must balance them. A design might be cheap but weak. Another design might be strong but too large. The best design is one that meets the criteria while staying within the constraints.

Worked Example 1: Designing a Bookmark

A class is asked to design a bookmark for younger students.

Problem: Make a bookmark that helps students keep their place in a book.

Possible criteria:

• It must fit inside a book.
• It must clearly mark the page.
• It should be easy to use.

Possible constraints:

• Only paper and crayons may be used.
• Students have 15 minutes.
• The bookmark must be shorter than 20 centimeters.

Why? The criteria describe what the bookmark must do. The constraints describe the limits on materials, time, and size.

Worked Example 2: Building a Paper Bridge

Students must build a bridge from paper and tape.

Problem: Build a bridge that can hold toy cars.

Criteria:

• It must stretch across a gap of 20 centimeters.
• It must hold at least 3 toy cars.
• It must stay standing for 10 seconds.

Constraints:

• Only 2 sheets of paper and 30 centimeters of tape may be used.
• The bridge must be built in 25 minutes.
• The bridge cannot be taped to the table.

Thinking it through: A student may want to use lots of tape to make the bridge stronger, but the tape limit is a constraint. The student may also want a very wide bridge, but with only 2 sheets of paper, material is limited. So the student must choose a design that uses materials wisely while still meeting the goal of holding 3 cars.

Worked Example 3: Designing a Lunch Container

A team is designing a container to keep a sandwich safe in a backpack.

Criteria:

• It must protect the sandwich from being squished.
• It must be easy to open and close.
• It must fit inside a backpack pocket.

Constraints:

• The cost must be less than \(\$8\).
• Only plastic or cardboard may be used.
• The mass must be less than 200 grams.

Thinking it through: A hard plastic box may protect the sandwich well, but it could cost too much. A cardboard box may be cheap, but it might not protect the sandwich enough. The team must compare ideas and find one that best fits all the needs and limits.

Worked Example 4: Looking at a Simple Budget Constraint

A group is building a model shelter. They can buy craft sticks for \(\$2\) per pack and tape for \(\$1\) per roll. Their budget is \(\$7\).

If they buy 2 packs of craft sticks and 3 rolls of tape, the total cost is:

$$2 \times 2 + 3 \times 1 = 4 + 3 = 7$$

This meets the budget exactly, so the design stays within the budget constraint.

If they buy 3 packs of craft sticks and 2 rolls of tape, the total cost is:

$$3 \times 2 + 2 \times 1 = 6 + 2 = 8$$

This goes over the budget, so it does not meet the constraint.

This example shows that even if a design idea seems strong, it may still fail if it breaks a limit like cost.

Why engineers test designs

After choosing an idea, engineers build models or prototypes and test them. Testing helps them see if the design really meets the criteria and stays within the constraints.

For example, if a tower must hold a textbook, students should actually place the textbook on the tower. If the tower falls, it does not meet the criterion. If students needed extra materials that were not allowed, they broke a constraint.

Improving a design

Sometimes the first design does not work well. That is normal. Engineers improve their ideas by looking at what went wrong.

• If the design did not do the job, the team may need to improve the criteria.
• If the design used too much money, too much time, or too many materials, the team may need to better follow the constraints.

For example, if a paper bridge holds only 1 car instead of 3, it did not meet the criterion. If it needed 4 sheets of paper when only 2 were allowed, it did not meet the constraint.

Quick check: Is it a criterion or a constraint?

1. The design must keep water from leaking out. → Criterion
2. You can only use 10 straws. → Constraint
3. The car must travel 2 meters. → Criterion
4. You have 30 minutes to build. → Constraint
5. The seat must safely hold one student. → Criterion

Tips for students

• Read the design challenge carefully.
• Underline what the design must do. Those are likely criteria.
• Circle any words about limits like only, at most, less than, or by tomorrow. Those are likely constraints.
• Check your design against both lists before you build.
• After testing, ask: Did it do the job? Did it stay within the limits?

Summary

In engineering, criteria are the things a design must do to be successful. Constraints are the limits on the design, such as cost, materials, time, size, and physics. Good engineers pay attention to both. A strong solution solves the problem and stays within the limits.

Brainstorming and Ideation means thinking of many ideas to solve a problem.

In engineering, people do not stop at the first idea. They brainstorm, which means they think of lots of possible solutions. Then they pick one idea to try.

This is an important part of the engineering design process. Engineers ask, “What is the problem?” Then they think of many ways to help.

Introduction

Imagine your class needs a way to keep crayons neat and easy to carry. What could you make? A box? A bag? A holder with pockets?

All of these are ideas. When we come up with many ideas, we are using brainstorming and ideation.

Main Teaching Points

1. What is brainstorming?

Brainstorming is a time to share many ideas. During brainstorming, all ideas are welcome.

You do not say, “That is a bad idea,” right away. First, you collect ideas. Later, you can choose the best one.

Brainstorming helps because one idea can lead to another idea. A small idea can grow into a great solution.

Brainstorming rules

• Think of many ideas.
• Share ideas kindly.
• Listen to others.
• Do not laugh at ideas.
• Build on ideas. For example, “We can add wheels!”

2. What is ideation?

Ideation means coming up with ideas. It is like filling your mind with possible answers to a problem.

If the problem is, “How can we water a plant when we are away?” ideation might give us ideas like:

• A bigger cup of water
• A bottle that drips slowly
• Asking a neighbor to help
• A string that moves water to the plant

Some ideas may work better than others. That is okay. The goal is to think of lots of choices first.

3. Ways to brainstorm

There are many simple ways to brainstorm.

• Say ideas out loud: Take turns sharing.
• Draw ideas: Make quick sketches.
• Make a list: Write down every idea.
• Think of changes: Ask, “Can it be bigger, smaller, softer, stronger, faster, or easier?”

4. Choosing an idea

After brainstorming, engineers choose an idea to test. They do not just pick any idea. They think about which idea will help the most.

They may ask:

• Will it solve the problem?
• Is it safe?
• Is it easy to make?
• Will it cost too much?

5. A simple decision chart

A decision chart helps us compare ideas. We look at each idea and see how well it fits what we need.

For 2nd graders, a decision chart can use check marks. More check marks can mean a better choice.

Example needs for a crayon holder:

• Holds many crayons
• Easy to carry
• Does not break easily

If Idea A gets 3 check marks and Idea B gets 2 check marks, Idea A may be the better idea to test first.

We can think about the total like this:

Idea A: \(3\) checks

Idea B: \(2\) checks

Since \(3 > 2\), Idea A fits more needs.

Worked Examples

Example 1: Brainstorming many ideas

Problem: A student’s books keep falling off the desk. What could help?

Brainstorm ideas:

• A book box
• A shelf under the desk
• A strap to hold books
• A bigger desk

What we learn: We do not stop after one idea. We think of many possible solutions.

Example 2: Building on an idea

Problem: The classroom floor gets wet by the sink.

First idea: Put a towel by the sink.

Build on it:

• Add a tray under the towel
• Use a bigger towel
• Hang the towel so it dries faster

What we learn: One idea can grow into better ideas.

Example 3: Using a decision chart

Problem: We need a container to carry seeds for planting.

Ideas:

• Paper cup
• Plastic box
• Cloth bag

What we need:

• Easy to carry
• Does not spill
• Can be used again

Decision chart:

Paper cup:

• Easy to carry: ✔
• Does not spill: ✘
• Can be used again: ✘

Plastic box:

• Easy to carry: ✔
• Does not spill: ✔
• Can be used again: ✔

Cloth bag:

• Easy to carry: ✔
• Does not spill: ✘
• Can be used again: ✔

Count the checks:

• Paper cup: \(1\)
• Plastic box: \(3\)
• Cloth bag: \(2\)

We can compare the totals:

$$3 > 2 > 1$$

Best choice to test first: The plastic box, because it fits the most needs.

Example 4: Choosing a playground shade idea

Problem: The playground is too sunny.

Ideas:

• Plant a tree
• Use a big umbrella
• Build a shade roof

Needs:

• Gives shade
• Safe
• Stays up on windy days

Decision chart:

Plant a tree:

• Gives shade: ✔
• Safe: ✔
• Stays up on windy days: ✔

Big umbrella:

• Gives shade: ✔
• Safe: ✔
• Stays up on windy days: ✘

Shade roof:

• Gives shade: ✔
• Safe: ✔
• Stays up on windy days: ✔

Count the checks:

• Tree: \(3\)
• Umbrella: \(2\)
• Shade roof: \(3\)

Here, two ideas tie. When that happens, engineers can talk more, draw both ideas, or test both if they can.

Helpful Tips for Students

• Be creative.
• Think of more than one answer.
• Draw your ideas if words are hard.
• Pick an idea that matches the need.
• If one idea does not work, try another one.

Why this matters

Brainstorming and ideation help people solve real problems. Engineers use these skills to make tools, buildings, toys, machines, and other helpful things.

When we think of many ideas and choose carefully, we have a better chance of making something that works well.

Brief Summary

Brainstorming means thinking of many ideas. Ideation means coming up with possible solutions to a problem.

First, engineers collect lots of ideas. Next, they compare the ideas with a simple decision chart. Then they pick the idea that fits the needs best and test it.

Systems Thinking and Feedback Loops

In science and engineering, many things work as systems. A system is a group of parts that work together to do a job. A bicycle, a washing machine, a school bus, and even a garden can all be thought of as systems.

Systems thinking means looking at the whole system and also looking at how the parts connect. Instead of studying just one part by itself, we ask questions like: What goes in? What happens inside? What comes out? How do the parts affect each other?

This way of thinking is very useful in engineering design. Engineers solve problems by building or improving systems. To do that, they need to understand how each part helps the whole system work.

Feedback loops are an important part of many systems. A feedback loop happens when information from the output of a system is used to change what the system does next. In simple words, the system “checks” what is happening and then responds.

1. The parts of a system

Most systems can be described using four basic ideas:

• Input – what goes into the system
• Process – what the system does with the input
• Output – what comes out of the system
• Feedback – information that helps the system adjust

Here is a simple way to picture it:

Input → Process → Output

If feedback is added, the output can help control the process:

Input → Process → Output → Feedback → Process

2. What is a subsystem?

A subsystem is a smaller system inside a larger system. Large technologies are often made of many subsystems.

For example, a car is one big system, but it contains smaller subsystems:

• the braking subsystem
• the steering subsystem
• the engine subsystem
• the lighting subsystem

Each subsystem has its own inputs, processes, and outputs. These smaller parts must work together for the whole car to work well.

3. Why systems thinking matters

If one part of a system changes, other parts may change too. Systems thinking helps us notice these connections.

For example, imagine an engineer wants to make a fan spin faster. That might improve cooling, but it could also use more electricity, make more noise, or wear out the motor faster. A good engineer thinks about all of these effects, not just one.

Systems thinking helps engineers:

• find the real cause of a problem
• understand how parts work together
• predict what might happen if one part changes
• design safer and more efficient technology

4. Understanding feedback loops

A feedback loop happens when a system uses information about its output to guide what happens next. Feedback helps a system stay on track or respond to change.

There are two main types of feedback loops:

• Negative feedback loop
• Positive feedback loop

Negative feedback helps keep a system stable. If something gets too high or too low, the system acts to bring it back toward the target.

Positive feedback increases change. If something starts happening, the system causes even more of it to happen.

The words “positive” and “negative” here do not mean “good” or “bad.” They describe what the feedback does.

5. Negative feedback examples

A thermostat in a house is a common example of negative feedback.

• Input: the temperature setting chosen by a person
• Process: the thermostat compares the room temperature to the setting
• Output: the heater turns on or off
• Feedback: the new room temperature is measured again

If the room gets too cold, the heater turns on. If the room gets warm enough, the heater turns off. The system keeps checking and adjusting. That is negative feedback because it keeps the temperature near the goal.

Another example is a refrigerator. If the inside gets too warm, the cooling system turns on. When the temperature drops enough, it turns off.

6. Positive feedback examples

A microphone placed too close to a speaker can create a loud squeal. Here is what happens:

• the microphone picks up sound
• the speaker makes that sound louder
• the microphone picks up the louder sound again
• the cycle repeats and grows

This is a positive feedback loop because the output keeps increasing the effect.

Another simple example is sharing a video online. If more people watch it, more people may share it, and then even more people may watch it. The change grows larger and larger.

7. Systems can be natural or technological

In this lesson, we focus on technology and engineering, but systems thinking can be used in many areas. A plant watering system, traffic lights, a computer, and a robot are all technological systems.

Each system has:

• parts that interact
• a purpose or job
• inputs and outputs
• sometimes a feedback loop to help control the system

8. Worked Example 1: A flashlight

Let’s start with a simple system: a flashlight.

• Input: energy from batteries and a person pressing the switch
• Process: electricity flows through the circuit
• Output: light

Does a basic flashlight have a feedback loop? Usually, no. It gives an output, but it does not measure that output and change itself.

This example shows that not all systems have feedback loops. But all systems still have connected parts working together.

9. Worked Example 2: An automatic hand dryer

Now let’s look at a more advanced system: an automatic hand dryer in a restroom.

• Input: electrical energy and hands placed under the sensor
• Process: the sensor detects hands and turns on the motor and heater
• Output: warm moving air dries hands
• Feedback: when hands move away, the sensor detects that and turns the dryer off

This system uses feedback because the sensor keeps checking for hands. The output changes based on new information.

10. Worked Example 3: A smart irrigation system for a garden

An irrigation system waters plants. A smart irrigation system can use feedback to make better choices.

• Input: water, electricity, and soil moisture information from a sensor
• Process: the controller checks if the soil is dry
• Output: water sprays onto the garden
• Feedback: the sensor measures the soil again after watering

If the soil is still too dry, the system may water more. If the soil is wet enough, it stops. This is a negative feedback loop because the system adjusts to reach a target moisture level.

We can describe the idea with a simple comparison:

If target moisture is 8 units and current moisture is 5 units, then the difference is

$$8 - 5 = 3$$

Because the soil is below the target, the system keeps watering. If the moisture later reaches 8, then

$$8 - 8 = 0$$

Now the system can stop watering because it has reached the goal.

11. Worked Example 4: Traffic lights with sensors

Some traffic lights are part of a larger traffic control system. They may use sensors to detect cars waiting at an intersection.

• Input: electricity and sensor signals from waiting cars
• Process: the control system decides when lights should change
• Output: red, yellow, or green lights
• Feedback: sensors continue checking traffic

This is a system made of subsystems. The sensors, timer, computer controller, and lights are all subsystems.

If traffic builds up on one side, the system may keep the green light longer there. That shows systems thinking: the controller is not just changing lights randomly. It is responding to what is happening in the whole intersection.

12. How engineers use systems thinking in design

When engineers design something, they often follow steps such as:

1. identify a problem
2. imagine solutions
3. plan and build
4. test the design
5. improve it

Systems thinking is useful at every step.

• When identifying the problem, engineers ask which parts of the system are not working well.
• When planning, they think about inputs, processes, outputs, and subsystems.
• When testing, they collect feedback from the system.
• When improving, they change parts carefully because one change can affect the whole system.

13. Questions to ask about any system

When you study a system, these questions can help:

• What is the job of the system?
• What are the main parts?
• What are the inputs?
• What process changes the inputs?
• What are the outputs?
• Are there smaller subsystems inside it?
• Is there a feedback loop?
• If one part changes, what else might change?

14. Common mistakes to avoid

• Mistake 1: Thinking a system is just one object. A system is made of parts working together.
• Mistake 2: Forgetting about inputs and outputs. These help explain how the system works.
• Mistake 3: Thinking all systems have feedback loops. Some do, and some do not.
• Mistake 4: Thinking positive feedback is always good. Positive feedback simply means the change grows.
• Mistake 5: Looking at one part only. Systems thinking means looking at connections between parts.

15. Quick compare: negative vs. positive feedback

• Negative feedback: reduces the difference from a goal and helps keep a system steady
• Positive feedback: increases change and pushes the system farther in the same direction

Think of it this way:

• If a room is too cold and the heater turns on to fix it, that is negative feedback.
• If a sound gets louder and louder because it keeps being repeated, that is positive feedback.

16. Brief summary

A system is a set of connected parts that work together to do a job. Systems often include inputs, processes, outputs, and sometimes feedback.

Systems thinking means studying not only the parts, but also how the parts affect one another. This helps engineers understand complex technologies and improve them.

A feedback loop happens when a system uses information about what is happening to change what it does next. Negative feedback helps keep a system stable, while positive feedback makes change grow larger.

When you look at technology this way, you can better understand how real-world devices and designs solve problems.

Material Selection for Structural Engineering

We build many things, like houses, bridges, chairs, and towers. Engineers are people who plan and build things so they work well and stay safe.

When engineers build something, they must choose the right material. A material is what something is made of, like wood, metal, rubber, plastic, or glass.

Picking the right material is called material selection. This means choosing what works best for the job.

Different materials act in different ways. Some are hard. Some are soft. Some bend. Some stay stiff. Engineers think about these differences before they build.

Why does material choice matter?

If you use a soft material for something that must hold a lot of weight, it may bend or break. If you use a hard, strong material for something that needs to stretch, it may not work well.

So engineers ask, "What does this structure need to do?" Then they pick a material that matches that job.

What is a structure?

A structure is something built to hold up, carry, or protect. A bridge is a structure. A building is a structure. A table is a structure.

Important material ideas

Here are some simple ways materials can be different:

• Strong means it can hold weight.
• Hard means it is not easy to scratch or dent.
• Stiff means it does not bend much.
• Bendy means it can bend.
• Stretchy means it can pull longer and then go back.
• Soft means it feels easy to press.
• Waterproof means water does not go through it easily.

Let us look at some common materials.

• Metal: often strong and stiff
• Wood: often strong and hard
• Rubber: stretchy and bendy
• Plastic: can be light and waterproof
• Glass: hard, but it can break

Matching the material to the job

A tall tower needs materials that are strong and stiff. A rubber band needs a material that is stretchy. Boots for rain need a material that keeps water out.

This is called a match. Engineers match the material to the job.

Think about a bridge. A bridge must hold up cars, bikes, or people. It should not sag too much. So a bridge often needs strong, stiff materials.

Now think about a playground ball. A ball may need to bounce and squeeze a little. A very stiff material would not be a good choice for that job.

Questions engineers ask

1. What am I building?
2. What does it need to do?
3. Does it need to be strong, stiff, bendy, soft, or waterproof?
4. Which material matches those needs best?

Worked Example 1: Choosing a material for a chair

A chair must hold a person up. It should not flop over or bend too much.

Let us compare:

• Rubber: bendy and stretchy
• Wood: strong and hard

A chair needs to hold weight, so wood is the better choice.

Answer: Choose wood because it is strong and works better for holding a person.

Worked Example 2: Choosing a material for a rain boot

A rain boot needs to help keep feet dry. It may also need to bend a little when we walk.

Let us compare:

• Paper: not good in water
• Rubber: waterproof and bendy

Rubber is the better choice because water does not go through it easily, and it can bend when we walk.

Answer: Choose rubber for a rain boot.

Worked Example 3: Choosing a material for a toy bridge

A toy bridge must hold up small toy cars. It should stay up and not droop.

Let us compare:

• Metal: strong and stiff
• Cloth: soft and bendy

The bridge needs to stay stiff and hold weight. Metal is a better match.

Answer: Choose metal because it is strong and stiff.

Worked Example 4: Choosing a material for a bouncing part

A small toy needs a part that can stretch and snap back.

Let us compare:

• Rubber: stretchy
• Glass: hard, not stretchy

The toy part needs to stretch. Rubber is the better choice.

Answer: Choose rubber because it can stretch and go back.

Easy ways to think about materials

• For holding weight, pick something strong.
• For not bending much, pick something stiff.
• For stretching, pick something stretchy.
• For keeping water out, pick something waterproof.

Look at the job first

Sometimes no material is perfect for every job. A glass cup is hard, but it can break if it falls. Rubber is stretchy, but it may not be best for holding up a heavy table.

That is why engineers do not just pick any material. They think carefully about what the structure needs.

Try thinking like an engineer

If you wanted to build a small tower, would you pick sponge or wood? Wood is a better choice because a sponge is soft and squishy.

If you wanted to make something that can bend around your foot, would you pick metal or rubber? Rubber is a better choice because it bends more easily.

Summary

Materials are what things are made of. Different materials have different properties, like strong, stiff, soft, bendy, stretchy, and waterproof.

Engineers match the material to the job. Strong, stiff materials are good for structures like chairs and bridges. Stretchy, bendy materials are good for things like boots and rubber bands.

When we choose the right material, our design can work better and stay safer.

Prototyping and Iteration are important parts of the engineering design process. Engineers rarely build a perfect solution on the first try. Instead, they make a model, test it, learn what works and what does not, and then improve it.

This cycle of build, test, and improve helps engineers solve real-world problems. In 6th Grade science, learning how prototypes and iteration work helps you think like an engineer.

Imagine you are designing a bridge from craft sticks, a water filter from gravel and sand, or a shoe box that keeps an ice cube cold. You would not want to spend a lot of time and money making a final version before checking whether your idea works. That is why engineers use prototypes.

A prototype is a test model of a design. It is made so people can try out an idea before making the final product. A prototype helps show the shape, size, materials, and function of a design.

There are different kinds of prototypes. Engineers choose the kind that best helps them answer questions about their design.

• Low-fidelity prototype: a simple, quick, low-cost model. It may be made from paper, cardboard, tape, clay, or other easy materials.
• High-fidelity prototype: a more detailed and realistic model. It is closer to the final product and may use stronger materials, moving parts, or technology.

A low-fidelity prototype is useful early in the design process. It helps engineers explore ideas quickly. If something needs to change, it is easy to rebuild.

For example, if you are designing a playground shade structure, you might first sketch it and build a small cardboard model. This simple model helps you think about size, shape, and where the poles should go.

A high-fidelity prototype is helpful later in the process. It lets engineers test the design in a more realistic way. It often looks more like the real product and behaves more like it too.

For the playground shade structure, a high-fidelity prototype might use stronger materials and be tested outside in wind or sunlight. This kind of model gives better information about how the final design might perform.

After making a prototype, engineers do not just look at it. They test it. Testing means gathering evidence about how well the design works.

Good testing is empirical. That means it is based on observations and measurements from real trials, not just guesses. Engineers collect data so they can make smart decisions.

When engineers test a prototype, they often look for failure points. A failure point is a place or condition where the design stops working well. Finding failure points is useful because it shows what needs improvement.

Failure points can include many things:

• a bridge bends too much under weight
• a water filter does not clean the water enough
• an insulated container lets heat in too quickly
• a model car wheel falls off after a short distance

Finding a failure point does not mean the project has failed. It means the test gave useful information. Engineers learn from problems.

Iteration means repeating the design process to make a solution better. After each round of testing, engineers change the design based on what they learned.

The process often looks like this:

1. Identify the problem.
2. Imagine possible solutions.
3. Build a prototype.
4. Test the prototype.
5. Study the results.
6. Improve the design.
7. Test again.

This process may happen many times. Each round is called an iteration. With each iteration, the design can become safer, stronger, cheaper, easier to use, or more effective.

Engineers use data to compare versions of a design. For example, if one bridge holds 8 books and the next version holds 12 books, the second version shows improvement. The change can be measured by subtraction:

$$12 - 8 = 4$$

This means the improved bridge held 4 more books than the first one.

Sometimes engineers also look at averages when they test more than once. If a model car travels 120 cm, 135 cm, and 125 cm in three trials, the average distance is:

$$\frac{120 + 135 + 125}{3} = \frac{380}{3} \approx 126.7$$

This helps engineers understand the design's typical performance instead of relying on just one test.

Why not just build the final product right away? There are several reasons:

• Prototypes save time.
• Prototypes save money.
• Prototypes help find problems early.
• Prototypes let engineers test ideas safely.
• Prototypes make it easier to improve a design before final production.

Think of prototyping as practicing before a big game or revising a writing draft before turning it in. A first version is a starting point, not the end.

In science and engineering, testing should be fair. A fair test means changing one main variable at a time while keeping other conditions the same. This helps engineers know which change caused the result.

For example, if you are testing paper airplane designs, you should try to keep the same paper type, same thrower, and same throwing force. If you change too many things at once, it becomes hard to tell why one plane flew farther.

During testing, engineers record data carefully. They may write measurements in a table, draw diagrams, or take notes about what happened. Clear records help them compare one prototype to the next.

Here is an example of a simple test record for a bridge prototype:

• Prototype A held 6 books before bending.
• Prototype B held 9 books before bending.
• Prototype C held 11 books before bending.

These results suggest that changes from A to B to C improved the bridge's strength.

Worked Example 1: Low-fidelity prototype

Problem: A student wants to design a device that can scoop up small trash from the floor without bending down.

First, the student builds a low-fidelity prototype using cardboard, tape, and string. The model is quick and simple. It does not look perfect, but it helps test the idea of how the scooping arm will move.

Test: The student tries to pick up 10 small paper balls. The prototype only picks up 3 because the scoop is too floppy.

What was learned? The failure point is the weak scoop. The student now knows the design needs a stiffer material or extra support.

Why this matters: A simple prototype helped uncover a problem early, before more time and materials were used.

Worked Example 2: Iteration after testing

Now the student improves the scooping device. They add folded cardboard to make the scoop stronger.

Second test: This new version picks up 7 out of 10 paper balls.

The improvement can be measured as:

$$7 - 3 = 4$$

The second version picked up 4 more paper balls than the first version.

This is an example of iteration. The student used test results to improve the design.

Worked Example 3: High-fidelity prototype

After more changes, the student builds a high-fidelity prototype using lightweight plastic pieces, a stronger handle, and a hinge that moves smoothly.

This version is closer to a real product. It is tested on paper balls, bottle caps, and small blocks.

Results:

• picked up 10 out of 10 paper balls
• picked up 8 out of 10 bottle caps
• picked up 6 out of 10 small blocks

What was learned? The design works very well for light objects, but it still struggles with heavier or oddly shaped objects. The failure point now is grip strength.

Next step: Improve the gripping part instead of redesigning the whole tool.

Worked Example 4: Testing with repeated trials

Suppose a team is designing a small model boat that must carry pennies without sinking. They build Prototype 1 and test it three times.

• Trial 1: 18 pennies
• Trial 2: 20 pennies
• Trial 3: 19 pennies

The average is:

$$\frac{18 + 20 + 19}{3} = \frac{57}{3} = 19$$

Then they redesign the bottom of the boat and test Prototype 2.

• Trial 1: 24 pennies
• Trial 2: 23 pennies
• Trial 3: 25 pennies

The average is:

$$\frac{24 + 23 + 25}{3} = \frac{72}{3} = 24$$

Prototype 2 carried more pennies on average. That means the new design improved the boat's performance.

When students work on engineering projects, they sometimes think they should hide mistakes. But in engineering, mistakes are useful when they teach you something. A broken part, a weak joint, or a slow test result can all point to a better design.

Here are good habits during prototyping and iteration:

• Start simple. Use easy materials first.
• Test fairly. Keep conditions as similar as possible.
• Measure results. Use numbers when you can.
• Look for failure points. Ask where and why the design struggles.
• Improve one step at a time. Small changes make results easier to understand.
• Repeat. Better designs usually come from many tries.

It is also important to remember that a design must meet the needs of the problem. A stronger design is not always the best if it becomes too heavy, too expensive, or too hard to use. Engineers must balance many goals.

For example, a lunch container that keeps food cold for a long time might work well, but if it is too large to carry, it may not be the best design. Testing helps engineers see these trade-offs.

In short, prototyping and iteration help engineers turn ideas into better solutions. A prototype is a model used for testing. Low-fidelity prototypes are simple and quick, while high-fidelity prototypes are more detailed and realistic.

Testing gives evidence about how a design performs. Engineers use that evidence to find failure points and make improvements. By repeating this cycle, they create designs that work better and better over time.

Computational Thinking and Modeling helps scientists and engineers solve problems by using computers, math, and step-by-step thinking. Sometimes building and testing a real object is too expensive, too slow, or too dangerous. In those cases, people use models and simulations to test ideas safely.

In 6th Grade Science, this idea connects to engineering design. Engineers ask questions, imagine solutions, plan, test, improve, and try again. Computational thinking and modeling help with the testing and improving parts of the design process.

This lesson will explain what computational thinking is, what a model is, how computer-aided design (CAD) works, and how simulations help us make good decisions.

What is computational thinking?

Computational thinking is a way of solving problems by breaking them into smaller parts and looking for patterns. It does not only mean coding. It means thinking in an organized way so a person or a computer can follow the steps.

Computational thinking often includes these skills:

• Breaking a problem into parts – solving one small piece at a time
• Looking for patterns – noticing what stays the same or what changes
• Focusing on important details – ignoring details that do not matter right now
• Creating steps – making a clear plan or process to follow

For example, if students want to design a better water bottle, they might break the problem into parts:

• How big should it be?
• What shape is easiest to hold?
• Will it leak?
• How much material will it use?

Instead of guessing, they can use a computer model to test different bottle shapes.

What is a model?

A model is something that represents an object, system, or idea. A model helps us study something without always using the real thing.

Models can be different types:

• Physical models – like a small bridge made from craft sticks
• Drawing models – like a labeled diagram
• Math models – using numbers and equations
• Computer models – digital versions built on a computer

A computer model can show how something might look or act in real life. It is not exactly the same as the real object, but it can be very useful for testing ideas.

What is CAD?

CAD stands for computer-aided design. CAD is software that helps people draw and build designs on a computer. Engineers, inventors, architects, and designers use CAD to make detailed plans before creating a real object.

With CAD, a student or engineer can:

• Draw a design neatly and accurately
• Change the size or shape easily
• View the object from different sides
• Compare different designs
• Fix problems before building a real model

Imagine designing a helmet. Making many real helmets for testing could cost a lot of money. With CAD, a designer can change the thickness, shape, and materials in a computer model first.

What is a simulation?

A simulation is a computer-based test that imitates what might happen in real life. A simulation can show how a design works under certain conditions.

For example, a simulation can help answer questions like these:

• Will a bridge hold a heavy load?
• Will a car design be safe in a crash?
• Will a rocket part survive very hot temperatures?
• How far will a storm spread?

Simulations are useful when real testing is:

• Too dangerous – such as testing a crash or explosion
• Too costly – such as building many large machines
• Too time-consuming – such as waiting years to see long-term results

Why do scientists and engineers use computational thinking and modeling?

These tools help people make better choices. Instead of building every idea in real life, they can test ideas on a computer first. This saves time, money, and materials.

Computational thinking and modeling also help people stay safe. If an engineer wants to know whether a roller coaster design is safe, it is much better to test it in a simulation before real people ride it.

These tools also allow many trials. A person can test one version, change one detail, and test again. This supports the iterative design process, which means improving a design through repeated testing and revision.

How computational thinking fits into engineering design

Engineering design is often a cycle. The steps may be written in different ways, but they usually include these ideas:

1. Ask – What is the problem?
2. Imagine – What are some possible solutions?
3. Plan – Which solution will you try?
4. Create – Build a model or design
5. Test – See how well it works
6. Improve – Make changes and try again

Computational thinking helps during planning and testing. Modeling and simulation help during creating, testing, and improving.

For example, if a team is designing a school garden watering system, they might use computational thinking to organize the problem:

• How much water do plants need?
• How many rows of plants are there?
• How long should the water run?
• Which design wastes the least water?

Then they can use a model or simulation to compare ideas before building the real system.

Important idea: models have limits

Even though models are helpful, they are not perfect. A model is a simplified version of real life. It may leave out some details.

For example, a computer model of a bridge might include the weight of cars and the length of the bridge, but it may not fully show damage from years of weather. That means engineers must understand that a model gives useful information, but it does not guarantee perfect results.

This is why good scientists and engineers compare model results with real-world evidence when possible.

Using math in models

Many models use math to predict what will happen. Math helps people measure, compare, and look for relationships.

Suppose a machine makes 3 parts each minute. We can model the number of parts made with:

$$\text{parts} = 3 \times \text{minutes}$$

If the machine runs for 5 minutes, then:

$$\text{parts} = 3 \times 5 = 15$$

This is a simple mathematical model. It helps predict results without watching the machine for the full time.

Worked Example 1: Choosing a safer bike helmet

A student team is designing a bike helmet. They want it to protect a rider's head better.

Step 1: Break the problem into parts.

• What shape covers the head well?
• How thick should the foam be?
• How much should the helmet weigh?

Step 2: Make a computer design.

The team uses CAD to draw three helmet shapes.

Step 3: Run a simulation.

The computer simulates a fall and shows how each helmet design spreads out the force.

Step 4: Compare results.

Design A cracks. Design B protects well but is too heavy. Design C protects well and is lighter.

Conclusion: Design C is the best choice to improve and test further.

This example shows how CAD and simulation can test something dangerous without hurting anyone.

Worked Example 2: Testing a bridge design

A class wants to design a small bridge for a model town. They cannot build every possible bridge, so they use a computer model.

The class creates three bridge designs. A simulation tests how much weight each bridge can hold.

• Bridge 1 holds 20 kilograms
• Bridge 2 holds 35 kilograms
• Bridge 3 holds 28 kilograms

If the bridge needs to safely hold at least 30 kilograms, which design works?

Solution:

Compare each bridge to 30 kilograms.

• Bridge 1: 20 kilograms, not enough
• Bridge 2: 35 kilograms, enough
• Bridge 3: 28 kilograms, not enough

Answer: Bridge 2 is the only design that meets the goal.

This example shows how a simulation helps engineers choose a strong design before building it.

Worked Example 3: Using a math model to save time

A water filter prototype can clean 4 liters of water each hour. We can model the amount of water cleaned with:

$$w = 4h$$

In this model, \(w\) is liters of water and \(h\) is hours.

How much water can the filter clean in 6 hours?

Solution:

Substitute \(h = 6\).

$$w = 4 \times 6 = 24$$

Answer: The filter can clean 24 liters of water in 6 hours.

This simple model helps engineers predict performance without waiting and measuring each time.

Worked Example 4: Improving a design after testing

A team designs a model emergency shelter using CAD. They run a wind simulation.

The first design tips over in strong wind. The students study the results and notice that the shelter is too tall and has a narrow base.

Using computational thinking, they focus on the most important details:

• Height of the shelter
• Width of the base
• Shape of the walls

They change the design by making the shelter shorter and widening the base. Then they run the simulation again.

The second design stays upright in stronger wind.

Conclusion: Modeling helped the team find a weakness, improve the design, and test again. This is the engineering design process in action.

Real-world uses of computational thinking and modeling

People use these skills in many jobs and situations:

• Doctors and scientists model how diseases spread
• Weather experts simulate storms
• Car designers test safety features
• Game designers create digital worlds and systems
• Architects and engineers design buildings, roads, and bridges

Even students use computational thinking in everyday life. Planning a schedule, organizing materials for a project, or comparing choices all use step-by-step problem solving.

How to know when a model is useful

A good model should:

• Match the problem you are studying
• Include important details
• Be clear and organized
• Help you make predictions
• Be tested and improved if needed

If a model leaves out too much information, its predictions may not be very helpful. If it includes the right details, it can guide better decisions.

Common misunderstandings

• Misunderstanding: A model is always a tiny physical object.
  Truth: A model can also be a math rule, a diagram, or a computer design.
• Misunderstanding: Simulations are just games.
  Truth: Simulations are important tools for science and engineering.
• Misunderstanding: Computers give perfect answers.
  Truth: Computers are helpful, but the results depend on the quality of the model and data.
• Misunderstanding: Testing once is enough.
  Truth: Engineers usually test, improve, and test again.

Summary

Computational thinking means solving problems in an organized, step-by-step way. Modeling means creating a representation of an object, system, or idea so it can be studied. CAD helps engineers make digital designs, and simulations help them test those designs in ways that may be too dangerous, costly, or slow in real life.

These tools are important in the engineering design process because they help people compare solutions, predict outcomes, and improve designs. By using computational thinking and modeling, students and engineers can solve real-world problems more safely and effectively.

Biomimicry in Design is when people look at nature for ideas to solve human problems. The word can be broken into two parts: bio, which means life, and mimicry, which means copying. So biomimicry means copying ideas from living things.

Engineers and designers use biomimicry because plants, animals, and ecosystems have been solving problems for a very long time. Over many generations, living things have developed body parts, behaviors, and systems that help them survive. Humans can study those solutions and use them to design tools, buildings, materials, and machines.

This is an important part of engineering design. In engineering, people ask questions, define a problem, test ideas, improve designs, and try again. Biomimicry gives engineers a smart place to look for ideas: nature.

Why do engineers use biomimicry?

• Nature often solves problems in efficient ways.
• Natural designs can inspire safer and stronger products.
• Biomimicry can help people use less energy and fewer materials.
• It can lead to inventions that work better with the environment.

What kinds of things in nature inspire designs?

Engineers may study structures, processes, and systems.

• Structures are body parts or shapes, like a bird's wing, a turtle's shell, or a burr's hooks.
• Processes are actions in living things, like how spiders make silk or how leaves move water.
• Systems are groups of parts working together, like an ant colony or a forest ecosystem.

Biomimicry is not the same as just copying how something looks. A design should copy how nature solves a problem. For example, a building shaped like a flower is not automatically biomimicry. But a building that opens and closes to control sunlight the way a flower does would be a biomimicry idea.

Steps in biomimicry design

1. Identify the problem. What needs to be solved?
2. Look for a similar problem in nature. What living thing has already solved it?
3. Study the natural solution. How does it work?
4. Apply the idea to a human design. Build a model or plan.
5. Test and improve. See what works and make changes.

Let us look more closely at these steps.

First, engineers define the problem clearly. For example, maybe shoes keep slipping on wet floors, buildings get too hot, or a robot needs to move over rough ground.

Next, they search in nature. Many animals and plants face similar challenges. A gecko needs to climb. A cactus needs to survive in hot, dry places. A fish needs to move smoothly through water.

Then engineers investigate the natural solution. They observe, measure, draw diagrams, and ask how the structure or behavior helps the organism survive.

Finally, they use that idea to make a design. They test it, gather data, and improve it. This is called an iterative process, which means repeating steps to make something better.

Common examples of biomimicry

• Velcro and burrs: Burr seeds stick to animal fur using tiny hooks. This inspired Velcro, which uses small hooks and loops.
• Airplanes and birds: Birds helped inspire wing design because their wing shapes help them move through air.
• Swimsuits and shark skin: Shark skin has tiny patterns that help reduce drag in water. This inspired materials for faster movement through water.
• Gecko-inspired tape: Geckos can climb walls because of tiny structures on their feet. This inspired adhesives that can stick without glue.
• Termite mound buildings: Some termite mounds keep a steady inside temperature. Architects have used similar ideas to help buildings stay cooler.

How biomimicry connects to scientific knowledge

Biomimicry depends on science. Engineers must understand life science to study organisms, physical science to understand forces and materials, and Earth science to think about climate and resources.

For example, if a designer studies bird wings, they need to understand air movement. If they study cactus skin, they need to understand heat and water. If they study a forest, they need to understand how living things depend on one another.

How biomimicry connects to math

Engineers use math to compare designs and decide which one works best. They may measure length, mass, area, temperature, time, or speed.

For example, if one model car travels 12 meters in 3 seconds, its average speed is

$$\text{speed} = \frac{\text{distance}}{\text{time}} = \frac{12}{3} = 4 \text{ meters per second}$$

If another model car travels 15 meters in 3 seconds, then its average speed is

$$\frac{15}{3} = 5 \text{ meters per second}$$

The second design moves faster, so it may better copy the streamlined shape seen in animals like fish or birds.

How biomimicry connects to computational thinking

Computational thinking means solving problems in organized steps. Engineers may collect data, look for patterns, make models, and test different versions.

For example, a team designing a fan based on whale fins might compare blade shapes. They could make a table of each blade shape and how much air it moves. Then they can choose the design that works best.

Worked Example 1: Velcro from burrs

Problem: A designer wants to make a fastener that can be opened and closed many times.

Nature idea: Burr seeds attach to fur using tiny hooks.

Study: The designer looks closely and sees that the burr does not use glue. It catches on loops in fur.

Human design: Make one strip with tiny hooks and another strip with tiny loops.

Result: When pressed together, they stick. When pulled apart, they separate.

Why this is biomimicry: The design copies how the burr solves the problem of attaching, not just what the burr looks like.

Worked Example 2: A cooler building inspired by termites

Problem: A building in a hot place uses too much electricity for air conditioning.

Nature idea: Termite mounds can stay at a more steady temperature inside.

Study: Air moves through tunnels in the mound. This helps move heat out and fresh air in.

Human design: Engineers add vents and air pathways to a building so air can move naturally.

Result: The building may stay cooler while using less energy.

Why this matters: Biomimicry can help save energy and lower costs.

Worked Example 3: Designing a fast train inspired by a bird

Problem: A train is noisy and uses too much energy as it moves through air.

Nature idea: A kingfisher bird has a beak shape that helps it move smoothly into water with little splash.

Study: The beak is long and narrow, which reduces sudden resistance.

Human design: Engineers redesign the front of the train to be longer and more pointed.

Result: The train can move more smoothly and quietly.

Why this is a strong example: The engineer matched a nature solution to a similar human problem: moving through a fluid, such as air or water, with less resistance.

Worked Example 4: Choosing the best shoe tread using biomimicry

Problem: Students want to design shoes that grip wet ground better.

Nature idea: Mountain goats and geckos move safely over tricky surfaces.

Design test: Three tread patterns are tested on a ramp sprayed with water.

• Pattern A slips after 2 steps.
• Pattern B slips after 5 steps.
• Pattern C slips after 8 steps.

Compare the data: The best design is the one that grips the longest before slipping.

Since 8 is greater than 5 and 5 is greater than 2,

$$8 > 5 > 2$$

Conclusion: Pattern C performed best in this test, so engineers would likely study and improve that pattern.

Important idea: Biomimicry is not guessing. It uses evidence from testing.

Benefits of biomimicry

• Can make products more efficient.
• Can reduce waste.
• Can save energy.
• Can inspire creative ideas.
• Can help people design in ways that fit better with nature.

Challenges of biomimicry

Biomimicry is useful, but it is not always easy.

• Nature can be complex and hard to study.
• Some natural materials are difficult to copy.
• A design that works in nature may need changes to work for humans.
• Testing takes time.

For example, a spider makes silk that is strong and light, but people may not be able to make that material in exactly the same way. Engineers often have to use the natural idea as inspiration rather than copying it perfectly.

Biomimicry and the environment

One major goal of biomimicry is to create designs that work well without harming the environment. Nature usually avoids waste because materials are reused in ecosystems. Engineers can learn from this.

For example, instead of designing something that is thrown away quickly, a team might design a product that lasts longer, uses fewer materials, or can be reused.

How to tell if something is biomimicry

Ask these questions:

• What problem is being solved?
• What organism or ecosystem solves a similar problem?
• What natural feature or process is being copied?
• Is the design based on evidence and testing?

If the answer includes a real nature-based solution and a tested human design, then it is probably biomimicry.

Practice thinking like an engineer

Imagine you need to design a water bottle that stays cool in the sun. You might ask:

• Which animals stay cool in hot places?
• How do they do it?
• Can that idea help with the bottle design?

You might study camels, desert foxes, or cacti. Then you would test materials, shapes, or surfaces based on what you learn.

Key vocabulary

• Biomimicry: designing something by copying how living things solve problems.
• Engineer: a person who designs and improves solutions to problems.
• Structure: the shape or physical part of something.
• Process: a set of actions or steps.
• System: parts working together.
• Iterative: repeated again and again to improve.
• Prototype: an early model used for testing.
• Efficiency: doing a job well without wasting time, energy, or materials.

Summary

Biomimicry in design means learning from nature to solve human problems. Engineers study structures, processes, and systems in living things, then apply those ideas to inventions and technologies. Good biomimicry uses science, math, testing, and repeated improvement. By looking closely at nature, people can create designs that are smarter, more efficient, and often better for the environment.

Life Cycle Assessment (LCA) is a way to study how a product affects the environment during its whole life.

Instead of looking at only one part, like how a product is used, LCA looks at every stage: where the materials come from, how the product is made, how it is used, and what happens when people are done with it.

This helps scientists and engineers make better choices. A product that seems helpful in one stage might cause a lot of pollution in another stage. LCA helps us see the big picture.

For example, think about a plastic water bottle. Many people notice the trash it creates at the end. But LCA asks more questions. Where did the plastic come from? How much energy was used to make the bottle? How far was it shipped? Can it be recycled?

Why is Life Cycle Assessment important?

People use products every day, but every product uses materials and energy. Products can also create waste, pollution, and greenhouse gases.

LCA helps us:

• compare products in a fair way
• find stages that cause the most environmental harm
• design products that use fewer resources
• reduce waste and pollution
• make smarter choices as consumers and engineers

The main stages in a life cycle

Most LCAs look at four big stages. You can think of them as the story of a product from the beginning to the end.

1. Raw material extraction
   This is when materials are taken from Earth. Examples include cutting trees for paper, pumping oil from the ground for plastic, or mining metal for a can.
2. Manufacturing
   This is when the materials are turned into a product in a factory. Machines may use electricity, water, and fuel. Factories may also create waste.
3. Use
   This is what happens while people use the product. Some products need a lot of energy during use, like a lamp or washing machine. Other products, like a spoon, need very little energy once made.
4. Disposal
   This is what happens when the product is no longer wanted. It may be thrown away, recycled, reused, or composted, depending on the material.

A simple way to remember the stages

You can remember LCA as:

Take it - Make it - Use it - Lose it or Reuse it

This is not the scientific name, but it can help you remember the order.

What kinds of environmental impacts do scientists look at?

In a Life Cycle Assessment, scientists and engineers often measure things like:

• Energy use - How much electricity or fuel is needed?
• Water use - How much water is used?
• Air pollution - Does the product create smoke or gases?
• Waste - How much trash is left over?
• Greenhouse gases - Does the product add gases that warm Earth?
• Resource use - Does it use up trees, metals, oil, or other materials?

LCA is about the whole system

A technological system has many connected parts. A product does not appear by magic. It is part of a system that includes workers, machines, transportation, stores, and waste systems.

When students study LCA, they learn to ask system questions such as:

• What materials are needed?
• Where do the materials come from?
• How is the product made?
• How does it get to people?
• What happens while people use it?
• What happens when it is thrown away?

Important idea: One product is not always better in every way

Sometimes people ask, “Which is better for the environment?” The answer is not always simple.

For example, a reusable bottle may take more material to make than a single-use bottle. But if it is used many times, it may create less waste over time. LCA helps compare the full life cycle instead of guessing.

How to do a simple Life Cycle Assessment

In 6th Grade, you can do a basic LCA by following a few steps.

1. Choose a product
   Pick something simple, like a bottle, bag, can, notebook, or toothbrush.
2. List the life cycle stages
   Write down raw materials, manufacturing, use, and disposal.
3. Ask questions about each stage
   What materials are needed? How much energy is used? Is there waste?
4. Look for the biggest impacts
   Which stage seems to use the most energy, water, or materials?
5. Suggest improvements
   Could the product be made from recycled materials? Could it last longer? Could it be reused or recycled?

Worked Example 1: Paper bag vs. plastic bag

Suppose a store is choosing between paper bags and plastic bags. Which one is better for the environment?

Step 1: Raw materials

• Paper bags come from trees.
• Plastic bags come from oil.

Step 2: Manufacturing

• Paper bags often use a lot of water and energy to make.
• Plastic bags often use less material and are lightweight.

Step 3: Use

• Both can carry groceries.
• Some plastic bags can be reused more than once.
• Some paper bags can also be reused, but they may rip more easily if wet.

Step 4: Disposal

• Paper can break down faster in nature and can often be recycled.
• Plastic may last a very long time if littered.

Conclusion

LCA shows that this is not a simple choice. Paper may be better in one stage, while plastic may be better in another. A very important idea is that reusing a bag many times often lowers harm more than using a new bag once.

Worked Example 2: Disposable water bottle vs. reusable water bottle

Now compare a disposable plastic water bottle to a reusable metal bottle.

Disposable bottle

• Uses less material per bottle.
• Must be made again and again for each use.
• Can create a lot of trash if used once and thrown away.

Reusable bottle

• Takes more material and energy to make at the start.
• Can be used many times.
• Creates less trash over time if it replaces many disposable bottles.

Conclusion

If a student uses a reusable bottle only once, it may not be much better. But if the student uses it every day for months, it can lower waste a lot. LCA reminds us that how we use a product matters.

Worked Example 3: Finding total energy from life cycle stages

Sometimes we can use numbers in a simple LCA. Imagine a toy has these energy costs:

• Raw materials: 4 energy units
• Manufacturing: 6 energy units
• Use: 2 energy units
• Disposal: 1 energy unit

To find the total life cycle energy, add all the stages:

$$4 + 6 + 2 + 1 = 13$$

So the toy uses 13 energy units during its life cycle.

Now ask: which stage uses the most energy? Manufacturing uses 6 units, so that is the biggest part. Engineers may try to improve the factory process first.

Worked Example 4: Comparing two lunch containers

A student can pack lunch in:

• Choice A: one disposable foam container each day
• Choice B: one reusable lunch box used for 100 days

Suppose the disposable container creates 1 unit of waste per day. After 100 days, the waste is:

$$100 \times 1 = 100$$

So Choice A creates 100 waste units.

Suppose the reusable lunch box creates 20 waste units when made and 5 waste units when thrown away. Its total waste is:

$$20 + 5 = 25$$

So Choice B creates 25 waste units over 100 days.

Conclusion

Even though the reusable lunch box may take more resources to make at first, it can create much less waste over time. This is a key idea in LCA.

What engineers do with LCA

Engineers use LCA to improve products. If one stage causes the most harm, they can redesign that part.

For example, engineers might:

• use recycled materials
• make products lighter so shipping uses less fuel
• design products that last longer
• make products easier to repair
• reduce packaging
• make products easier to recycle

LCA and the engineering design process

LCA fits well with the engineering design process because engineers do not stop after one idea. They test, improve, and redesign.

A simple design cycle might look like this:

1. Ask what problem needs to be solved.
2. Imagine possible solutions.
3. Plan a design.
4. Create and test it.
5. Improve it using what you learned.

LCA helps during the test and improve parts. It shows whether a design reduces waste, saves energy, or uses fewer materials.

Common mistakes to avoid

• Looking at only one stage
  A product may seem eco-friendly in one stage but harmful in another.
• Ignoring reuse
  Many products become better choices when they are used again and again.
• Forgetting transportation
  Moving products long distances can use a lot of fuel.
• Thinking recycling solves everything
  Recycling helps, but it still uses energy and does not remove all impacts.

Questions you can ask about any product

• What is it made from?
• How were those materials collected?
• How much energy was needed to make it?
• How far did it travel?
• How long will it last?
• Can it be reused?
• Can it be repaired?
• Can it be recycled or composted?

Mini practice

Think about a notebook.

• Raw materials: paper from trees, metal for staples or spiral wire
• Manufacturing: cutting paper, printing lines, binding pages
• Use: writing notes over time
• Disposal: recycling, reusing leftover pages, or throwing it away

If you use all the pages and recycle the notebook, its life cycle impact may be lower than if you use only a few pages and throw it away. This shows that responsible use matters.

Brief summary

Life Cycle Assessment is a tool for understanding the full environmental impact of a product.

It looks at raw materials, manufacturing, use, and disposal. By studying all four stages, scientists and engineers can compare products fairly and design better solutions.

The main goal of LCA is not just to label products as good or bad. The goal is to find ways to use fewer resources, make less waste, and protect the environment.

Risk-Benefit Analysis is a way to think carefully about a new technology before people decide to use it. In science and engineering, a risk is a possible danger or problem. A benefit is a helpful result or advantage.

Engineers use risk-benefit analysis to ask an important question: Do the good results of this technology outweigh the possible harms? This helps people make smart, fair, and safe choices.

For example, a new machine might help farmers grow more food. That is a benefit. But the machine might also cost a lot of money, use a lot of fuel, or be dangerous if used the wrong way. Those are risks.

Risk-benefit analysis does not mean a technology must be perfect. Almost every tool or system has some risks. Instead, it helps us compare the risks and benefits, and then decide whether the technology should be used, improved, or avoided.

Why Risk-Benefit Analysis Matters

New technologies can change how people live, work, travel, communicate, and stay healthy. Some technologies solve big problems, but they can also create new ones.

Before using a new technology, engineers and communities want to know:

• Will it help people?
• Could it hurt people or the environment?
• How likely are the risks?
• How serious are the risks?
• Can the risks be lowered?

These questions are important because a choice that helps one group of people might create problems for another group. A strong decision looks at the whole picture.

Key Idea: Risks and Benefits Can Be Measured

Sometimes risks and benefits can be described with words, such as low, medium, or high. Other times, they can be estimated with numbers.

For example, a school might compare two water bottle filling stations. One is cheaper, but breaks more often. The other costs more, but lasts longer and saves more plastic bottles. Engineers might collect data to compare both choices.

Even when exact numbers are not available, people can still make a thoughtful risk-benefit analysis by using evidence, observations, and testing.

Parts of a Risk-Benefit Analysis

A risk-benefit analysis usually includes several steps.

1. Identify the technology or solution.
   What new product, system, or idea is being considered?
2. List the benefits.
   How could it help people, animals, or the environment?
3. List the risks.
   What could go wrong? Could it cause injury, pollution, waste, unfairness, or extra cost?
4. Estimate size and chance.
   How big is each benefit or risk? How likely is it to happen?
5. Compare the evidence.
   Do the benefits seem greater than the risks?
6. Decide what to do.
   Use the technology, improve it, add safety rules, or choose a different idea.

Thinking About Risk

Not all risks are the same. Engineers often think about two parts of a risk:

• Probability: How likely is it to happen?
• Severity: If it happens, how bad would it be?

A risk that is very unlikely and small may not matter much. A risk that is very likely or very harmful needs more attention.

You can think of risk in a simple way like this:

$$\text{Risk level} \approx \text{chance of harm} \times \text{size of harm}$$

This is not a perfect rule, but it helps us organize our thinking.

Thinking About Benefit

Benefits can also be judged by size and importance. A benefit may be:

• Small: Helps a little
• Medium: Helps some people or solves part of a problem
• Large: Helps many people or solves an important problem

Engineers may ask:

• How many people will this help?
• How much time, energy, or money will it save?
• Will it improve health or safety?
• Will it protect natural resources?

Important Idea: Lowering Risk

If a technology has useful benefits but also has risks, engineers do not always throw it away. Often, they try to reduce the risks.

They might:

• Add safety features
• Use stronger materials
• Give better instructions
• Train users
• Test the technology more
• Limit where or when it is used

This is part of the engineering design process. Engineers test, improve, and redesign solutions so they work better and more safely.

Worked Example 1: Playground Surface

A school is choosing a new surface to put under playground equipment.

Choice A: Concrete
Choice B: Rubber tiles

Let us compare the risks and benefits.

• Concrete benefits: cheaper, lasts a long time
• Concrete risks: hard surface can cause more injuries when children fall
• Rubber tile benefits: softer, helps reduce injuries
• Rubber tile risks: costs more money

Now think about the decision. Injury risk on concrete is a serious safety problem. Rubber tiles cost more, but they help protect students.

Conclusion: Even though rubber tiles are more expensive, the safety benefit is greater. The school may decide the benefits of rubber tiles outweigh the extra cost.

Worked Example 2: Delivery Drone

A company wants to use drones to deliver medicine to people in remote places.

Possible benefits:

• Medicine arrives faster
• People in hard-to-reach areas get supplies
• Emergency help can arrive quickly

Possible risks:

• Drones may crash
• Batteries may fail
• Drones may disturb wildlife
• People may worry about privacy

Suppose engineers test the drones and find that crashes are rare, but battery failure can happen in cold weather. They improve the battery design and create rules for safe flying.

Conclusion: The drones have strong benefits, especially for health and safety. Because engineers lowered the risks through testing and redesign, the technology may be a good choice.

Worked Example 3: Comparing Two Streetlights

A town is choosing between two kinds of streetlights.

• Old lights: Cost \(\$100\) each, use more electricity, need more bulb changes
• LED lights: Cost \(\$180\) each, use less electricity, last longer

Suppose one old light uses \(10\) units of electricity each month, and one LED light uses \(4\) units each month.

The electricity saved each month is:

$$10 - 4 = 6$$

So each LED light saves \(6\) units of electricity per month.

Now think about the benefits and risks.

• Benefits of LED: saves energy, lasts longer, may save money over time
• Risks of LED: higher starting cost

If the town wants to save energy for many years, the long-term benefits of LED lights may outweigh the higher cost at the beginning.

Conclusion: A higher cost right now can still be worth it if the future benefits are large.

Worked Example 4: Water Filter for a Community

A community is deciding whether to install a new water filter system.

Benefits:

• Cleaner drinking water
• Better health for families
• Less need to buy bottled water

Risks:

• The system is expensive to install
• Workers need training to maintain it
• If it is not maintained, it may stop working well

Now let us reason through it. Clean water is a very important benefit because it affects health every day. The biggest risks are cost and maintenance. These risks can be reduced by training workers and making a maintenance schedule.

Conclusion: Because the health benefit is large and the risks can be managed, the community may decide the water filter is a strong choice.

How Scientists and Engineers Use Evidence

Risk-benefit analysis should be based on evidence, not just opinions. Evidence can come from:

• Tests and experiments
• Measurements
• Models
• Observations
• Past data from similar technologies

For example, if engineers build a new bike helmet, they do not just guess whether it works. They test it to see how well it protects the head during impacts.

Good evidence helps people make better decisions and avoid choices based only on feelings.

Different People May View Risks and Benefits Differently

One technology can seem helpful to one person and harmful to another. That is why it is important to listen to different points of view.

For example:

• A factory machine may help make products faster
• Workers may worry about safety
• Neighbors may worry about noise
• Owners may focus on cost and production

A fair risk-benefit analysis considers all of these concerns, not just one.

Questions to Ask During Risk-Benefit Analysis

When you are asked to analyze a technology, these questions can help:

• What problem is this technology trying to solve?
• Who benefits from it?
• What could go wrong?
• How likely is each problem?
• How serious would each problem be?
• Can the design be improved to lower risk?
• Do the benefits outweigh the risks?

Common Mistakes to Avoid

• Looking only at benefits: A technology may sound exciting, but it can still have dangers.
• Looking only at risks: Some risks are small compared with the help a technology can provide.
• Ignoring evidence: Good decisions use data and testing.
• Forgetting long-term effects: A choice that seems cheap now may cause bigger problems later.
• Assuming all people are affected the same way: Different groups may experience different risks and benefits.

Simple Strategy for Students

If you need to do a risk-benefit analysis in class, you can use this simple plan:

1. Name the technology.
2. Write at least two benefits.
3. Write at least two risks.
4. Decide whether each one is small, medium, or large.
5. Explain whether the benefits outweigh the risks.
6. Suggest one way to reduce a risk.

This keeps your thinking clear and organized.

Practice Thinking

Imagine a school wants to install automatic hand dryers in bathrooms.

You might list:

• Benefits: less paper waste, fewer trash bags, lower paper cost
• Risks: use electricity, may be noisy, may stop working

Then you would decide: Are the benefits greater? Can the risks be reduced? Maybe the school could choose energy-saving dryers and place them where noise is less of a problem.

That is risk-benefit analysis in action.

Summary

Risk-benefit analysis is the process of comparing the possible harms and the possible advantages of a technology. Engineers use it to make smart choices about whether a design should be used, changed, or replaced.

To do a risk-benefit analysis, identify the technology, list the risks and benefits, think about how likely and serious they are, and use evidence to compare them. A good solution is not just useful. It should also be as safe, fair, and effective as possible.

Ethics in Technology means thinking about what is right, fair, safe, and responsible when people create and use technology.

Technology can solve many problems. It can help doctors find diseases, help farmers grow food, and help people communicate. But technology can also create new problems if people do not think carefully about its effects.

In engineering design, people do not just ask, “Does it work?” They also ask, “Who does it help?” “Who could be harmed?” “Is it fair?” “Does it protect privacy?” and “Does it hurt the environment?”

This is why ethics is an important part of science, engineering, and technological systems.

Why ethics matters in technology

When engineers design a new tool or system, their choices affect real people. A machine, app, or robot may change how people live, learn, travel, or work.

If a new technology is powerful, it can do a lot of good. But if it is used carelessly, it can cause harm. Ethical thinking helps people make better decisions before problems grow.

Ethics in technology often focuses on three big ideas:

• Societal impact — how technology affects people and communities
• Privacy — how technology collects, stores, and shares personal information
• Environmental impact — how technology affects Earth’s air, water, land, plants, animals, and natural resources

1. Societal impact

Societal impact means the effect technology has on society, or the way people live together.

Some technologies make life easier and safer. For example, GPS helps people travel, and medical devices help patients. But technology can also create hard questions.

Here are some questions engineers and citizens might ask:

• Does this technology help everyone, or only some people?
• Could it replace jobs people depend on?
• Could it be used in unfair ways?
• Does it make communities safer, or could it create danger?

For example, artificial intelligence (AI) can help sort information, recognize speech, and answer questions. It can be useful in schools, hospitals, and businesses.

But AI systems are designed by people, and people can make mistakes. If the data used to train an AI system is unfair or incomplete, the AI may also make unfair choices.

That means engineers must test systems carefully and ask whether the results are fair for different groups of people.

2. Privacy

Privacy means keeping personal information safe and allowing people to control what others know about them.

Many technologies collect data. Data is information. This can include a person’s name, location, voice, photos, health information, or online activity.

Some data collection is helpful. For example, a fitness watch can track steps, and a navigation app can show the fastest route. But collecting too much information can be risky.

Important privacy questions include:

• What information is being collected?
• Why is it being collected?
• Who can see it?
• How long is it kept?
• Did the person agree to share it?

For example, if an app tracks a student’s location all day, that may help in some situations. But it also raises privacy concerns if the student and family do not know how that information is used.

Ethical technology should be clear and honest. People should understand what data is collected and should have choices when possible.

3. Environmental impact

Environmental impact means how technology affects the natural world.

Building and using technology often requires energy and materials. Phones, computers, batteries, and robots are made from metals, plastics, and other resources taken from Earth.

Technology can help the environment, such as solar panels, electric buses, and sensors that check water quality. But technology can also harm the environment if it creates pollution or waste.

Some important environmental questions are:

• How much energy does this technology use?
• What materials are needed to make it?
• Can it be reused or recycled?
• Will it create trash or pollution?
• Does it help conserve natural resources?

For example, when people throw away old electronics, the waste is called e-waste. E-waste can be harmful if it is not recycled properly.

Ethical engineers try to design products that last longer, use less energy, and create less waste.

Emerging technologies and ethical questions

New and fast-growing technologies are often called emerging technologies. These can be exciting, but they also bring new ethical questions.

Artificial intelligence (AI)

• Can AI make fair decisions?
• Should people always check important AI decisions?
• What happens if AI gives wrong information?

Biotechnology

Biotechnology is technology that uses living things or parts of living things. This can include making medicines, improving crops, or studying genes.

• Could it help cure diseases?
• Could changing living things have unexpected results?
• Who should decide how far biotechnology should go?

Autonomous systems

Autonomous systems are machines that can do tasks on their own, such as self-driving cars or delivery robots.

• What if the machine makes a mistake?
• Who is responsible if someone gets hurt?
• How should the machine be tested before public use?

Ethics and the engineering design process

The engineering design process is a series of steps used to solve problems. Ethics should be considered during every step, not just at the end.

1. Ask — What is the problem? Who is affected?
2. Imagine — What possible solutions are there?
3. Plan — Which design seems best and safest?
4. Create — Build a model or product.
5. Test — Does it work? Is it fair? Is it safe? Does it protect privacy?
6. Improve — Fix problems and make the design better.

Ethical engineers think about both the benefits and the risks of a design.

A simple way to compare them is:

$$\text{Overall effect} = \text{Benefits} - \text{Harms}$$

This is not an exact math rule, but it reminds us to look at both sides. A technology with many benefits may still need changes if it causes serious harm.

Questions to ask about a technology

When you study or debate a technology, you can use these ethical questions:

• Safety: Can it hurt people?
• Fairness: Does it treat people equally?
• Privacy: Does it protect personal information?
• Usefulness: Does it solve a real problem?
• Responsibility: Who is accountable if something goes wrong?
• Environment: Does it protect or damage natural resources?

Worked Example 1: A school app

A school wants to use an app that helps students organize homework. The app asks for student names, class schedules, and location.

Step 1: Identify the benefits.

• Students can remember assignments.
• Teachers can post reminders.
• Families can track homework.

Step 2: Identify the concerns.

• The app collects personal information.
• Location tracking may not be needed.
• Students may not know who can see the data.

Step 3: Make an ethical judgment.

The app could be useful, but it should collect only the information it truly needs. If location is not necessary for homework, the school should turn that feature off. The school should also explain clearly how student data is protected.

Worked Example 2: A delivery robot

A town wants to test small robots that deliver food on sidewalks.

Benefits:

• Fast deliveries
• Less car traffic in some areas
• Useful for people who cannot drive

Concerns:

• Robots might block sidewalks
• They could bump into people or pets
• They may use cameras, which raises privacy questions

Ethical decision:

The town should test the robots carefully in limited areas first. Engineers should make sure the robots move safely, do not block people, and use cameras only when needed. Rules should be made before robots are used widely.

Worked Example 3: A smart trash can

Engineers design a smart trash can that sorts recycling automatically. It uses electricity and cameras to identify items.

Good effects:

• More recycling may be sorted correctly
• Less waste may go to landfills
• People may learn better recycling habits

Possible problems:

• It uses energy
• It may cost a lot of money
• Cameras could capture images of people nearby

Ethical decision:

This design may help the environment, but engineers should try to lower energy use and protect privacy. For example, they could use a sensor that identifies trash without recording people’s faces.

Worked Example 4: AI helping in a hospital

A hospital uses AI to help doctors look at medical images.

Benefits:

• AI can examine many images quickly
• Doctors may find problems sooner
• Patients may get treatment faster

Concerns:

• AI could make mistakes
• Private health information must be protected
• If the AI was trained on limited data, it may not work equally well for everyone

Ethical decision:

AI can be a helpful tool, but doctors should still review the results. The hospital must protect patient data and test the system to make sure it works fairly for many different people.

How to have a strong ethics debate

When students debate ethics in technology, the goal is not just to say “good” or “bad.” The goal is to use evidence, ask questions, and think about different points of view.

Here are some debate tips:

• State the technology clearly.
• List the benefits.
• List the risks.
• Think about who is helped and who might be harmed.
• Suggest ways to reduce the risks.

For example, instead of saying, “AI is bad,” a stronger statement is, “AI can be useful, but it should be checked by humans and designed to protect privacy and fairness.”

Ways to make technology more ethical

• Test products carefully before people use them.
• Collect only the data that is truly needed.
• Explain clearly how the technology works.
• Include many kinds of people when testing designs.
• Use materials and energy wisely.
• Repair, reuse, and recycle when possible.

Important idea to remember

Ethics in technology is not about stopping invention. It is about making sure inventions are used in safe, fair, thoughtful, and responsible ways.

Good engineers and scientists solve problems, but they also think about people and the planet. The best technologies do more than work well. They also respect privacy, support society, and protect the environment.

Space Exploration Technologies are the tools and machines people use to explore space. These technologies help us leave Earth, travel beyond our planet, live in space, and learn about faraway worlds.

Over time, space technology has changed a lot. Early rockets were simple and could only do a little. Today, scientists and engineers build powerful rockets, reusable launch vehicles, space stations, satellites, and rovers that can explore planets without a person inside.

In this lesson, you will learn how space exploration technology has grown from early rocketry to modern spacecraft. You will also see how each new invention helps people discover more about the universe.

1. Early Rocketry

A rocket is a vehicle that pushes itself forward by shooting gas out of its engines. This push is called thrust. Rockets are important because they can travel where airplanes cannot go: into space.

Long ago, the earliest rockets were much simpler than today’s rockets. They were not used for space travel at first. Over many years, people improved rocket design so rockets could go higher and carry more weight.

Rockets need a lot of force to escape Earth’s pull of gravity. Earth’s gravity pulls everything toward the ground. To reach space, a rocket must launch upward with great power.

2. Parts of a Rocket

Most rockets have several important parts:

• Engines that create thrust
• Fuel that the engines burn
• Stages that can separate during flight
• Cargo such as astronauts, satellites, or supplies

A stage is one section of a rocket. Some rockets have more than one stage. When one stage uses up its fuel, it can drop away. This makes the rocket lighter, so the next stage can keep going more easily.

This is helpful because lifting less mass takes less energy. By dropping empty parts, the rocket can travel farther and faster.

Worked Example 1: Counting Rocket Stages

A rocket starts with 3 stages. After launch, the first stage separates. Later, the second stage separates.

Question: How many stages are still attached at the end?

Step 1: Start with 3 stages.

Step 2: 2 stages separate.

Step 3: Subtract:

\(3 - 2 = 1\)

Answer: 1 stage is still attached.

3. Satellites

A satellite is an object that moves around a planet or another object in space. The Moon is Earth’s natural satellite. Human-made satellites are machines launched into space.

Satellites do many jobs. They can:

• Take pictures of Earth
• Help predict weather
• Send TV and phone signals
• Help people find locations with maps and navigation tools
• Study space

Many satellites travel in an orbit. An orbit is a path around a planet, moon, or star. A satellite stays in orbit because it is moving forward while gravity pulls it inward.

4. Spacecraft and Space Probes

A spacecraft is a vehicle made to travel in space. Some spacecraft carry astronauts. Others do not.

A space probe is a robotic spacecraft sent to explore space and send information back to Earth. Probes can travel to planets, moons, asteroids, and even far beyond our solar system.

Probes are very useful because they can go to places that are too far away or too dangerous for people right now. They use cameras, sensors, and antennas to collect and send data.

5. Reusable Launch Vehicles

In the past, many rockets were used only one time. After launch, big parts of the rocket fell away and were not used again. This made space travel very expensive.

A reusable launch vehicle is a rocket or spacecraft that can be used again after landing. Reusing parts can save money and materials. It can also help people launch more often.

Think of it like this: using a rocket once is like throwing away a bicycle after one ride. Reusing a rocket is like riding the same bicycle many times.

Some modern rockets can return to Earth and land safely. Engineers inspect them, repair what is needed, and prepare them for another launch.

Worked Example 2: One-Time Use or Reusable?

A company has 4 rocket boosters. If each booster can be used 3 times, how many total booster uses are possible?

Step 1: There are 4 boosters.

Step 2: Each is used 3 times.

Step 3: Multiply:

$$4 \times 3 = 12$$

Answer: The company has 12 total booster uses.

This shows why reusable technology can help. One machine can do the job many times.

6. Space Stations

A space station is a large spacecraft where astronauts can live and work for a long time in orbit. A space station is not made to land on a planet like a rocket or capsule. Instead, it stays in space and circles Earth.

Space stations are like science labs in orbit. Astronauts use them to:

• Study how the human body changes in space
• Do science experiments
• Watch Earth and space
• Test technology for future missions

Living in space is different from living on Earth. Astronauts float because of the conditions in orbit. They need air, water, food, and power. Space stations must be carefully built to provide these needs.

Supplies are often delivered by spacecraft. These cargo spacecraft bring food, tools, and experiment materials.

Worked Example 3: Counting Supply Shipments

A space station gets 2 supply spacecraft each month for 5 months.

Question: How many supply spacecraft arrive in all?

Step 1: 2 arrivals each month

Step 2: 5 months

Step 3: Multiply:

\(2 \times 5 = 10\)

Answer: 10 supply spacecraft arrive in all.

7. Rovers on Other Worlds

A rover is a robot vehicle that moves across the surface of a planet or moon. Rovers are built to explore places where people cannot easily go.

Rovers can have wheels, cameras, drills, arms, and tools for testing rocks and soil. They send pictures and information back to Earth.

Some rovers are autonomous. This means they can make some simple choices on their own, using computer instructions and sensors. For example, a rover may detect a rock in its path and move around it.

This is important because signals from Earth can take a long time to reach a rover on another planet. The rover must sometimes act by itself to stay safe and keep working.

8. How Technology Improved Over Time

Space exploration technology has changed step by step. Each improvement solved a problem.

• Early rockets showed that machines could travel very high
• Better engines and stages helped rockets carry more cargo
• Satellites allowed people to study Earth and space from orbit
• Space stations made long stays in space possible
• Reusable launch vehicles helped lower costs
• Autonomous rovers explored distant surfaces without astronauts

All of these technologies work together. A rocket may launch a satellite. A spacecraft may carry supplies to a space station. A rocket may send a rover to another planet.

9. Why Space Exploration Technologies Matter

These technologies help people learn about the universe. They also help life on Earth. For example, satellites can improve communication and weather reports. Space research can lead to new tools, materials, and ideas.

Space technology also helps scientists ask big questions. What are planets made of? Could humans live on another world someday? How did our solar system form? Better tools help us search for answers.

Worked Example 4: Comparing Missions

A mission plan includes:

• 1 rocket launch
• 1 satellite placed in orbit
• 1 rover sent to a planet
• 3 experiments done on a space station

Question: How many total space activities are listed?

Step 1: Count each activity.

1 launch + 1 satellite job + 1 rover mission + 3 experiments

Step 2: Add:

$$1 + 1 + 1 + 3 = 6$$

Answer: There are 6 total space activities.

10. Important Ideas to Remember

• A rocket uses thrust to travel upward into space.
• Stages help rockets by dropping empty parts.
• A satellite is a human-made object that orbits Earth or another body in space.
• A spacecraft travels in space, and a probe explores without astronauts.
• A reusable launch vehicle can be used more than once.
• A space station is a place where astronauts live and work in orbit.
• A rover is a robot that explores the surface of another world.
• Autonomous means able to do some tasks on its own.

Brief Summary

Space exploration technologies have grown from simple early rockets to advanced reusable rockets, orbiting space stations, and smart robotic rovers. Each new technology helps people travel farther, work longer in space, and learn more about planets, moons, and the universe.

When scientists and engineers improve space tools, they open new doors for discovery. Space exploration is a team effort between people, machines, and great ideas.