Glanz: aiMOOC über GPT aiMOOC Action erstellt

2026-08-13T09:05:41Z

aiMOOC über GPT aiMOOC Action erstellt

Neue Seite

{{T}}
[[Category:English]]
[[Category:Engineering Design Challenges]]

{{BR}}
= Introduction =

Engineering is about solving real problems for real people. In this aiMOOC for Grades 7–8, you will learn how to turn a need into a testable design, use evidence to improve it, and explain why your solution is a good choice. You will work like an engineer: define the problem, explore ideas, plan, build a [[English:Prototype|prototype]], test it, study the data, and improve the design.

A design challenge does not usually have one perfect answer. Different teams may create different solutions because they make different choices about materials, shape, cost, safety, environmental impact, and the needs of users. Your goal is not simply to make something that works once. Your goal is to create a solution that meets clear '''criteria''' while staying within important '''constraints'''.

[[File:SP14 DesignShowcase Edit-0889 (14362457175).jpg|500px|frameless|center]]

The image above shows student engineering projects being shared at a design showcase. Engineers often work in teams and communicate their results because a strong design must be understandable, testable, and open to feedback.

{{#ev:youtube|https://www.youtube.com/watch?v=owHF9iLyxic|500|center}}

{{BR}}
= What Is an Engineering Design Challenge? =

An [[English:Engineering design process|engineering design challenge]] gives you a problem that can be solved by designing an object, tool, process, or system. A good challenge has a clear purpose, but it still leaves room for creativity. For example, you might design a bridge from limited materials, a package that protects a fragile object, a device that helps someone carry school supplies, or a structure that stays stable when its base is shaken.

In Grades 7–8, engineering design becomes more precise. You are expected to define several criteria and constraints, compare possible solutions systematically, analyze data from tests, and use models or prototypes in repeated testing. These abilities align with the middle-school Next Generation Science Standards for Engineering Design, MS-ETS1-1 through MS-ETS1-4.

{{BR}}
== Criteria, Constraints, and Trade-Offs ==

'''Criteria''' describe what a successful solution should do. A bridge challenge might require the bridge to span a certain gap, hold a particular load, and remain stable. A carrying device might need to hold several objects securely and be comfortable to use.

'''Constraints''' are limits or restrictions. They may include the available time, materials, budget, dimensions, safety rules, or environmental requirements. A design that ignores an important constraint is not a successful engineering solution, even if it performs well in another way.

A '''trade-off''' happens when improving one feature makes another feature harder to improve. A stronger structure may use more material. A lighter design may be easier to carry but less durable. Engineers compare these competing needs and justify their choices with evidence.

{{BR}}
== From a Vague Problem to a Design Brief ==

A useful design brief makes the problem specific. It identifies the user, the need, the criteria, the constraints, and the way success will be measured. Compare these two statements:

'''Vague problem:''' Make a better bridge.

'''Engineering design brief:''' Design a bridge from the provided materials that spans a 30-centimeter gap, supports a set test load for at least 10 seconds, uses no more than the allowed material, and can be built within one class period.

The second statement is more useful because a team can test whether the design actually succeeds.

{{BR}}
= The Engineering Design Process =

Engineering design is '''iterative'''. That means you may return to earlier steps after you learn something new. A failed test is not the end of the process. It gives you evidence about what needs to change.

[[File:Engineering Design Process - NASA-JPL-Caltech.png|500px|frameless|center]]

The NASA/JPL diagram shows a design process that moves from identifying a problem and brainstorming to building, testing, evaluating, optimizing, and sharing. Different organizations use different names for the steps, but most engineering design models include the same core habits: understand the problem, develop possible solutions, create a model or prototype, test with evidence, and improve.

{{#ev:youtube|https://www.youtube.com/watch?v=fuwGvZ-eOrc|500|center}}

{{BR}}
== Ask and Research ==

Begin by understanding the problem before you build. Ask who experiences the problem, what the user needs, what scientific ideas are relevant, and what limits must be respected. Research existing solutions so that you can learn from what already works and notice problems that still remain.

Useful research questions include: What forces will act on the design? Which materials have useful properties? How will the user hold, move, or understand the object? What risks should be reduced? What environmental effects could result from the materials or energy used?

Good research does not tell you exactly what to build. It gives you evidence that helps you make better design decisions.

{{BR}}
== Imagine and Brainstorm ==

During brainstorming, generate several possible solutions before choosing one. At first, do not reject ideas too quickly. Sketch different shapes, mechanisms, materials, or arrangements. Combine strong features from several ideas when this improves the design.

A useful team rule is '''ideas first, judgment second'''. After the team has a range of possibilities, compare them against the same criteria and constraints. A simple decision matrix can help you avoid choosing a design only because it looks exciting.

{{BR}}
== Plan and Communicate ==

A plan should show enough detail that another person can understand what you intend to build. Include dimensions, materials, labeled parts, and the important functions of the design. You can communicate a plan with hand sketches, diagrams, or [[English:Computer-aided design|computer-aided design]] tools.

[[File:Engineering drawing-dessin de definition.png|500px|frameless|center]]

Technical drawings help engineers communicate shape, size, and relationships between parts. Even a simple classroom sketch becomes more useful when you label measurements and explain what each part is supposed to do.

{{BR}}
== Create a Prototype ==

A prototype is a model or early version built to learn from. It does not need to look like a finished commercial product. It needs to be detailed enough to test the important parts of your idea.

You can prototype with paper, cardboard, sticks, tape, reusable materials, digital models, or a 3D printer when one is available. Choose the simplest prototype that can answer your design question safely.

[[File:Prototyping with a 3D Printer.jpeg|500px|frameless|center]]

Rapid prototyping can shorten the time between an idea and a test. However, faster tools do not replace careful thinking. A quickly made prototype is useful only when you know what you want to learn from it.

{{BR}}
== Test, Measure, and Record Data ==

Testing should connect directly to your criteria. If your bridge must hold a load, measure the load it supports. If your package must protect an object from a drop, use the same drop height for each design. If your device must be easy to use, collect structured feedback from users.

Change one important variable at a time when possible. Use the same test procedure for competing designs so the results can be compared fairly. Record measurements immediately, including observations that may explain why a design behaved as it did.

Possible measurements include mass, distance, time, temperature, force, number of cycles, amount of material, cost, or a clearly defined rating scale. Use tables and graphs when they help you find patterns.

{{BR}}
== Improve Through Iteration ==

Iteration means testing, learning, changing the design, and testing again. A good redesign is based on evidence. Instead of saying, "We made it stronger," explain what test result showed a weakness, what feature you changed, and how the next test changed the performance.

{{#ev:youtube|https://www.youtube.com/watch?v=_EZAttVOvak|500|center}}

Failure can be valuable when it reveals useful information. Engineers do not celebrate unsafe or careless failure. They use controlled, safe tests to discover limits and improve a design before it is used in a real situation.

{{BR}}
= Forces, Structures, and Bridge Challenges =

Bridge challenges are useful because you can see how shape affects strength and stability. A [[English:Truss|truss]] uses connected members, often arranged in triangles. Triangles are useful because their shape resists changing unless the lengths of the sides change.

[[File:Landis Mill Covered Bridge Truss 2277px.jpg|500px|frameless|center]]

When a structure carries a load, some parts may be in '''tension''', which means they are pulled, while other parts may be in '''compression''', which means they are pushed. Bending can create both tension and compression in different parts of the same member.

Do not assume that "more material" always means "better design." Engineers often care about the strength-to-mass ratio, cost, ease of construction, and use of resources. A lighter structure that safely meets the criteria may be a better solution than a much heavier one.

{{BR}}
== Moving Structures and Mechanisms ==

Engineering challenges can also involve motion. A mechanism is a set of connected parts that changes or transfers motion and force. Hinges, linkages, gears, levers, cams, and pulleys can all be used in mechanisms.

[[File:Ford Bridge Schematic open-close (only one leaf).gif|500px|frameless|center]]

The animated bridge schematic shows how connected parts can coordinate motion. When you design a moving system, think about where forces enter the system, how parts move relative to one another, what could jam or bend, and how users can operate it safely.

{{BR}}
= Human-Centered, Accessible, and Ethical Design =

Engineering is not only about technical performance. A design affects people. Human-centered design asks you to understand the people who will use or be affected by a solution. You should avoid assuming that every user has the same body, experience, language, strength, vision, hearing, or mobility.

Interviewing users, observing how a task is completed, and testing prototypes with representative users can reveal needs that a design team might otherwise miss. Feedback should be treated as evidence, not as an interruption to the design.

[[File:3d printed hand prototype (15643030820).jpg|500px|frameless|center]]

Assistive technologies show why user needs matter. A device that performs mechanically but is uncomfortable, hard to control, too expensive, or difficult to repair may not meet the real design problem.

Ethical engineering also asks who benefits, who might be harmed, what data are collected, whether a design is safe, and what happens to materials at the end of a product's life. For classroom challenges, you should test models safely and never treat a prototype as a certified medical, safety, or structural device.

{{BR}}
= Sustainability and Responsible Material Choices =

A sustainable design tries to meet present needs while reducing unnecessary environmental harm. You can compare materials by more than strength alone. Consider how much material is needed, whether it can be reused or recycled, how long the product may last, and whether parts can be repaired or replaced.

A redesign that uses less material while still meeting the criteria can be an engineering improvement. So can a design that lasts longer, uses less energy, packs more efficiently, or can be disassembled for repair.

Sustainability can create trade-offs. A durable material may be harder to recycle. A lightweight design may use a material that is energy-intensive to produce. Engineers need evidence to compare alternatives rather than assuming that one feature makes a product automatically sustainable.

{{BR}}
= Working as an Engineering Team =

Engineering teams need both technical and communication skills. Assign useful roles, but do not let one person become the only builder or the only thinker. Rotate responsibilities when possible so that every team member can explain the design.

Good team communication includes asking questions, listening, drawing ideas, referring to data, and disagreeing respectfully about evidence. When two ideas compete, test them or compare them against agreed criteria instead of deciding only by vote or popularity.

{{#ev:youtube|https://www.youtube.com/watch?v=IbbxjA5e2hw|500|center}}

Professional engineers document decisions so that others can review the reasoning. In school, your engineering notebook can include the problem statement, research notes, sketches, measurements, photos, test results, calculations, redesign decisions, and reflections.

{{BR}}
= A Classroom Design Challenge Framework =

You can use this framework for many safe, low-cost challenges.

'''Challenge statement:''' Identify a user need and write a precise design problem.

'''Criteria:''' State what the solution must accomplish and how success will be measured.

'''Constraints:''' State limits such as materials, dimensions, time, cost, or safety rules.

'''Concepts:''' Generate at least three different ideas and show them with sketches.

'''Selection:''' Compare the ideas with the same criteria and explain why one is chosen.

'''Prototype:''' Build a model that can test the most important features.

'''Test plan:''' Decide what you will measure, what will stay the same, and how many trials you need.

'''Evidence:''' Record data and observations accurately.

'''Redesign:''' Change a feature because of what the evidence shows.

'''Communication:''' Present the problem, design, data, improvement, and remaining limitations.

{{BR}}
= Interactive Tasks =

{{BR}}
== Quiz: Test Your Knowledge ==

{{MC}}

'''What is a design criterion?'''
(A requirement a successful solution should meet)
(!A random idea that does not need testing)
(!A tool used only for drawing)
(!A limit that can never be measured)

{{E}}
<br>

{{MC}}

'''What is a design constraint?'''
(A limit or restriction on a solution)
(!A final decoration added after testing)
(!A measurement that always increases)
(!A guarantee that a prototype will work)

{{E}}
<br>

{{MC}}

'''Why do engineers build prototypes?'''
(To test important features before making a final solution)
(!To avoid collecting any data)
(!To prove the first idea is always best)
(!To remove all constraints from a problem)

{{E}}
<br>

{{MC}}

'''What does iteration mean in engineering design?'''
(Testing learning changing and testing again)
(!Building one design and refusing to change it)
(!Choosing materials without a plan)
(!Copying a design without understanding it)

{{E}}
<br>

{{MC}}

'''What makes a fair comparison between two prototypes?'''
(Using the same test procedure and criteria)
(!Changing several test conditions at once)
(!Testing only the design you prefer)
(!Ignoring results that disagree with your prediction)

{{E}}
<br>

{{MC}}

'''Why is a design brief useful?'''
(It makes the problem criteria and constraints clear)
(!It replaces the need for testing)
(!It guarantees one perfect answer)
(!It removes the need to understand users)

{{E}}
<br>

{{MC}}

'''What is a trade-off?'''
(A choice where improving one feature may reduce another)
(!A mistake that makes all data useless)
(!A rule that every design must be heavy)
(!A test that uses no measurements)

{{E}}
<br>

{{MC}}

'''Why are triangles common in truss structures?'''
(They help resist changes in shape)
(!They always use the most material)
(!They remove all compression forces)
(!They make testing unnecessary)

{{E}}
<br>

{{MC}}

'''What should guide a redesign after testing?'''
(Evidence from measurements and observations)
(!The color that looks most popular)
(!The first idea the team discussed)
(!A guess made before the test)

{{E}}
<br>

{{MC}}

'''Why should engineers consider users during design?'''
(A technically working solution may still fail to meet user needs)
(!Users always know the final technical answer)
(!User feedback removes all design constraints)
(!Engineering only concerns appearance)

{{E}}
<br>

{{BR}}
== Memory Game ==

<div class="memo-quiz">
{|
|-
| Criterion || A requirement used to judge whether a solution succeeds
|-
| Constraint || A limit involving resources time size cost or safety
|-
| Prototype || An early model built to learn from testing
|-
| Iteration || A cycle of testing learning redesigning and testing again
|-
| Trade-off || A balance between competing design goals
|-
| Tension || A pulling force within a material or structure
|-
| Compression || A pushing force within a material or structure
|-
| Benchmark || A reference result used for comparison
|}
{{E}}
<br>

{{BR}}
== Drag and Drop ==

<div class="lueckentext-quiz">

{| class="wikitable"
! Match the correct terms.
! Topic
|-
| '''Define the problem'''
| Identify the user need criteria and constraints
|-
| '''Brainstorm alternatives'''
| Generate several possible solutions
|-
| '''Plan the prototype'''
| Choose a concept and communicate dimensions and materials
|-
| '''Test with evidence'''
| Use measurements and observations to evaluate performance
|-
| '''Improve the design'''
| Change features in response to test results
|}
{{E}}

<br>
...
<br />

{{BR}}
== Crossword Puzzle ==

<div class="kreuzwort-quiz">
{|
|-
| Prototype || What do engineers call an early model built for testing?
|-
| Constraint || What word means a limit placed on a design solution?
|-
| Iteration || What word describes repeating design steps to improve a solution?
|-
| Tension || What force pulls on a structural member?
|-
| Compression || What force pushes on a structural member?
|-
| Tradeoff || What word describes balancing competing design goals?
|}
{{E}}
<br>

{{BR}}
== LearningApps ==

<iframe> https://learningapps.org/index.php?s=Engineering+Design+Challenges </iframe>

{{BR}}
== Cloze Text ==

<quiz display=simple>
{'''Complete the text.'''<br>
|type="{}"}
An engineering challenge starts with a clearly defined { problem } that matters to a user. A successful solution is judged against stated { criteria }. Designers must also respect each important { constraint }. Before building, a team should compare several possible { concepts }. An early testable model is called a { prototype }. Engineers collect { data } so that design decisions are based on evidence. Repeated testing and improvement is called { iteration }. When two design goals compete, engineers may need to make a { trade-off }.
</quiz>

<br>

{{BR}}
= Open-Ended Tasks =

{{BR}}
=== Easy ===
# [[English:Problem Hunt|Problem Hunt]]: Find one small problem in your classroom or home, identify who experiences it, and write a clear design brief with two criteria and two constraints.
# [[English:Paper Bridge Challenge|Paper Bridge Challenge]]: Build a bridge from a limited amount of paper and tape, test it with small safe loads, and record what shape gives the best strength for the material used.
# [[English:Engineering Sketch|Engineering Sketch]]: Choose a simple everyday object, draw an improved version with labels and dimensions, and explain how one feature would help the user.
# [[English:User Interview|User Interview]]: Interview a classmate about a simple school task that is inconvenient, summarize the need without proposing a solution first, and list questions that should guide a design.

{{BR}}
=== Standard ===
# [[English:Bridge Load Investigation|Bridge Load Investigation]]: Build two different truss-style bridge prototypes from the same amount of material, test them with the same procedure, graph the results, and explain which design better meets the criteria.
# [[English:Protective Package Design|Protective Package Design]]: Create a reusable package that protects a fragile model object during a controlled drop, measure its performance, and redesign one feature based on the evidence.
# [[English:Accessible Classroom Tool|Accessible Classroom Tool]]: Co-design a simple model that could make a classroom task easier for a user with a stated access need, gather feedback, and explain how the feedback changed your prototype.
# [[English:Engineering Data Story|Engineering Data Story]]: Photograph or sketch a prototype through at least two versions and create a short report showing how measurements led from the first design to the redesign.

{{BR}}
=== Advanced ===
# [[English:Sustainable Packaging Challenge|Sustainable Packaging Challenge]]: Compare several packaging concepts using protection, material use, reuse, and end-of-life considerations, build the strongest candidate, and defend the trade-offs you made.
# [[English:Shake Table Structure|Shake Table Structure]]: Build a small model structure for a classroom shake test, identify the forces and weak points, collect repeated test data, and modify the structure to improve stability.
# [[English:Assistive Design Investigation|Assistive Design Investigation]]: Research a real access challenge with guidance from reliable sources or an interview, create a non-medical low-risk prototype, and evaluate it for usability, cost, repair, and user feedback.
# [[English:Engineering Pitch Video|Engineering Pitch Video]]: Produce a three-minute video in which your team explains a design problem, shows test evidence, compares alternatives, presents one redesign, and identifies a limitation that still needs work.

{{:Open Task - Create a MOOC}}

{{BR}}
= Learning Assessment =

# [[English:Design Problem Analysis|Design Problem Analysis]]: Given a vague challenge, rewrite it as a precise engineering problem with measurable criteria, realistic constraints, and an explanation of why each one matters.
# [[English:Competing Solutions Evaluation|Competing Solutions Evaluation]]: Compare three design concepts with a decision matrix, justify the weights used for the criteria, and explain how changing a weight could change the preferred solution.
# [[English:Test Data Interpretation|Test Data Interpretation]]: Analyze a table or graph from prototype tests, identify patterns and possible sources of variation, and recommend one evidence-based redesign.
# [[English:Trade-Off Reasoning|Trade-Off Reasoning]]: Explain a case in which maximizing strength, minimizing mass, reducing cost, and improving sustainability cannot all be achieved equally, then defend a balanced design choice.
# [[English:Prototype Transfer|Prototype Transfer]]: Apply the same engineering design process to a new problem from a different subject area and explain which steps stay similar and which testing methods must change.
# [[English:Design Communication Review|Design Communication Review]]: Evaluate another team's engineering explanation for clarity, evidence, user awareness, and limitations, then provide specific feedback that could improve both the design and the presentation.

<br>
<br>

{{BR}}
= Evidence of Learning =

'''Knowledge:''' You can explain the difference between criteria and constraints, describe the purpose of prototypes and testing, recognize trade-offs, and explain why engineering design is iterative.

'''Skills:''' You can define a problem precisely, brainstorm alternatives, communicate plans, build a safe model, collect fair test data, interpret tables or graphs, compare solutions systematically, and justify a redesign with evidence.

'''Products:''' Strong evidence may include a design brief, engineering notebook, labeled drawings, a decision matrix, a prototype, test records, graphs, photographs of iterations, a final presentation, or a short engineering report.

'''Collaboration and communication:''' You can listen to users and teammates, explain technical choices clearly, use evidence during disagreement, and document how the team made decisions.

'''Transfer achievement:''' You can use the engineering design process in a new context such as environmental science, robotics, architecture, product design, assistive technology, or a community problem without assuming that the same solution will work everywhere.

<br>
<br>

{{BR}}
= OERs on the Topic =

<iframe> https://en.m.wikipedia.org/wiki/Engineering_design_process </iframe>

<br>

{{BR}}
= Linked Learning Areas =

{| align=center
{{:D-Tab}}
'''[[English:Engineering Design Challenges|Engineering Design Challenges]]'''
# [[English:Engineering design process|Engineering design process]]
# [[English:Prototype|Prototype]]
# [[English:Structural engineering|Structural engineering]]
# [[English:Computer-aided design|Computer-aided design]]
# [[English:Truss|Truss]]
# [[English:Mechanism|Mechanism]]
# [[English:Sustainable design|Sustainable design]]
# [[English:Assistive technology|Assistive technology]]
|}

{{BR}}
= aiMOOC Projects =
[[Category:English]]
[[Category:Engineering Design Challenges]]
[[Category:Engineering]]
[[Category:Technology education]]
[[Category:Design]]
[[Category:STEM education]]
[[Category:Grades 7-8]]
[[Category:AI_MOOC]]
[[Category:GPT aiMOOC]]
{{MT}}

English:Engineering Design Challenges - Versionsgeschichte

Glanz: aiMOOC über GPT aiMOOC Action erstellt