English:Engineering Design Process
Engineering Design Process
Introduction
The engineering design process is a structured but flexible way to turn a need, problem, or opportunity into a practical solution. You can use it when you design a component, improve a workstation, plan a simple electrical enclosure, modify a production aid, create a digital tool, reduce waste, or solve many other technical problems. The process helps you move from an unclear situation to a solution that can be justified with evidence.
For apprentices, trainees, and vocational students, engineering design is closely connected with everyday workplace practice. You may receive a customer request, a maintenance problem, a quality issue, a safety concern, or a production target. Your job is not only to build something that works. You also need to understand the user, define requirements, respect constraints, compare alternatives, communicate with colleagues, document decisions, test safely, and improve the design when evidence shows that a change is needed.
A useful way to think about the process is as an iterative cycle. You may move forward, test a prototype, discover a weakness, and return to an earlier step. This is normal engineering practice. A design that fails a test is not automatically a failed project; the test can provide data that makes the next version better.
This course uses a practical sequence: understand the need, research the context, define criteria and constraints, generate alternatives, select a concept, develop and communicate the design, prototype, test, evaluate, iterate, and hand over the result. Different companies and engineering disciplines may use different names or numbers of stages, but the underlying logic is similar.
Learning Goals
By the end of this aiMOOC, you should be able to explain why engineering design is iterative, write a clear design brief, separate criteria from constraints, generate more than one solution, compare alternatives with transparent reasoning, create useful technical documentation, plan meaningful tests, interpret test data, improve a prototype, and communicate a defensible final recommendation.
You should also be able to connect design decisions with safety, quality, cost, time, manufacturability, maintainability, sustainability, accessibility, and user needs. These factors often compete with one another, so engineering involves trade-offs rather than a single perfect answer.
A Workplace Scenario
Imagine that a workshop wants a new holder for frequently used hand tools beside an assembly bench. The existing arrangement causes wasted motion, tools are sometimes returned to the wrong place, and the bench has limited free space. A weak response would be to sketch the first idea and start making it. A stronger engineering response would first ask who uses the bench, which tools must be stored, how quickly they must be reached, what space is available, what loads the holder must carry, what materials and processes are available, how cleaning will work, what safety rules apply, and how success will be measured.
That scenario can be solved in many ways: a pegboard layout, a shadow board, a modular rail, a drawer insert, or a custom bracket system. The engineering design process gives you a disciplined way to compare these possibilities instead of choosing by personal preference alone.
The Engineering Design Process
Define the Need and the Problem
A good design begins with a problem worth solving. The first task is to distinguish the underlying need from a preferred solution. If a customer says, "We need a steel bracket here," the requested bracket may be only one possible response. The real need might be to support a sensor at a stable position, protect it from vibration, or make adjustment easier.
A practical problem statement identifies the user or stakeholder, the need, and the reason the need matters. Keep it specific enough to guide design work but open enough to allow several solutions. For example: "Assembly technicians need a secure and adjustable way to position the inspection light because the current clamp moves during repeated use." This statement describes the situation without deciding the final design too early.
Before designing, clarify the scope. Ask what is inside the project and what is outside it. Record assumptions, unknowns, responsibilities, interfaces with existing equipment, required approvals, and the deadline. In a workplace, this is also the point to confirm who has authority to approve changes.
Research the Context and Existing Solutions
Background research reduces avoidable mistakes. You may inspect the existing system, interview operators, check drawings, read manuals, review maintenance records, examine previous failures, study supplier data, and compare similar products. Research should answer questions that affect your design decisions.
For vocational projects, direct observation is especially valuable. Watch how the equipment is actually used rather than assuming that written procedures describe every detail. Ask users what causes difficulty, but also observe measurable facts such as reach distance, cycle time, vibration, noise, temperature, available space, or the frequency of a fault.
Research also includes applicable legislation, company rules, standards, and manufacturer instructions. Do not treat a prototype as permission to ignore normal workplace controls. If a task involves machinery, electricity, pressure, chemicals, lifting, hot work, or other hazards, follow the relevant supervision, isolation, authorization, and safe-work procedures.
Identify Stakeholders and User Needs
A stakeholder is anyone who affects the design or is affected by it. Depending on the project, stakeholders may include operators, customers, maintenance staff, supervisors, production planners, quality staff, purchasing, installers, cleaners, people with accessibility needs, and end users.
User needs are often expressed in ordinary language: "easy to clean," "comfortable," "fast to change," "not too heavy," or "easy to see." Engineering work converts these statements into clearer requirements that can be checked. For example, "easy to carry" could become a maximum mass and a requirement for a safe gripping area. The exact value must come from the real application, not from guesswork.
Define Criteria, Constraints, and Requirements
Criteria describe what a successful solution should achieve. They can include performance, accuracy, capacity, reliability, ergonomics, serviceability, appearance, energy use, or environmental impact. A criterion should be stated so that you can judge how well a design meets it.
Constraints are limits that the design must respect. Typical constraints include maximum dimensions, available budget, permitted materials, delivery time, existing interfaces, legal requirements, machine capacity, or a specified power supply.
A requirement is a clear statement of what the design must do or comply with. Good requirements are unambiguous, necessary, realistic, and testable. Instead of writing "The guard should be strong," define what condition it must withstand and how compliance will be checked. Avoid inventing numerical values merely to make a requirement look technical; obtain values from the customer, standards, calculations, measurements, or validated engineering data.
It is useful to keep requirements in a simple table with an identifier, statement, source, priority, verification method, and status. This creates traceability between what was requested and what you later test.
Safety, Risk, and Ethics in Design
Safety is not a final inspection step. It belongs throughout the design process. Identify hazards early, consider who could be exposed, and prefer solutions that remove or reduce hazards by design before relying only on warnings or personal protective equipment. Follow the hierarchy and procedures required by your workplace and jurisdiction.
Design decisions also have ethical consequences. A cheaper material may shorten product life; an inaccessible interface may exclude some users; a difficult maintenance task may encourage unsafe shortcuts; a disposable design may increase waste. Engineering judgment should consider foreseeable use, misuse, maintenance, environmental impact, and the people who will live with the result.
Generate Multiple Concepts
Concept generation is the stage where you deliberately create alternatives. Separate idea generation from evaluation at first. If you judge every idea immediately, you can stop the creative process before useful alternatives appear. Methods include individual sketching, group brainstorming, mind mapping, morphological charts, analogies, reverse thinking, and studying how similar functions are achieved in other industries.
Aim for variety, not just small variations of one idea. For the workshop tool-holder example, you could generate concepts based on hooks, slots, magnets, rails, drawers, foam cut-outs, or modular clips. Some may later be rejected because of constraints, but they broaden the solution space.
Keep sketches simple during early concept generation. A rough sketch can communicate layout, movement, interfaces, and dimensions before time is invested in detailed CAD.
Compare Alternatives and Choose a Concept
Engineering selection should be transparent. First remove options that clearly violate mandatory constraints. Then compare the remaining concepts against the criteria.
A simple decision matrix can help. List the criteria, give each an agreed importance, score each concept against the same scale, and record the reasoning behind the scores. The numbers do not make the decision automatically; they make assumptions visible and support discussion.
| Criterion | Importance | Concept A | Concept B | Concept C |
|---|---|---|---|---|
| Ease of access | High | Strong | Medium | Strong |
| Ease of cleaning | Medium | Medium | Strong | Medium |
| Manufacturing effort | Medium | Strong | Medium | Weak |
| Adaptability | High | Medium | Strong | Strong |
If two concepts are close, build quick mock-ups, obtain user feedback, or test the uncertain feature before committing to a detailed design. Record why the chosen concept was selected and why important alternatives were rejected.
Develop the Design
Concept development turns a promising idea into something that can be made, assembled, tested, used, and maintained. You may calculate dimensions, select materials, define fits and tolerances, design interfaces, choose standard components, estimate cost, plan assembly, and consider production methods.
At this stage, check whether the design can actually be manufactured with available tools and skills. A shape that is easy to model in CAD may be difficult or expensive to machine, bend, weld, print, wire, inspect, or service. Consultation with experienced technicians can prevent costly redesign.
Communicate with Sketches, Drawings, CAD, and Specifications
Technical communication is part of engineering quality. A design cannot be reproduced reliably if important information exists only in the designer's head.
Use the level of documentation appropriate to the task: hand sketches for early discussion, dimensioned drawings for manufacture, wiring diagrams for electrical work, schematics for systems, CAD models for geometry and fit, bills of materials for purchasing and assembly, and written specifications for requirements that are not clear from a drawing alone.
Good documentation uses consistent units, revision information, clear identifiers, and only the necessary tolerances. A tolerance communicates acceptable variation; it should be related to function, manufacturing capability, inspection method, and cost. Excessively tight tolerances can increase production cost without improving the product.
Build Models and Prototypes
A model represents selected features of a design. A prototype is a version built to learn whether a design works in practice. A prototype may be rough, partial, scaled, digital, or close to production quality depending on the question you need to answer.
The best prototype is not always the most realistic one. If you only need to check reach and layout, cardboard may be better than machined metal because it is faster and cheaper to change. If you need to check load, heat, sealing, electrical behavior, or wear, the prototype must represent the relevant conditions closely enough for the test to be meaningful.
Rapid prototyping methods such as 3D printing can shorten feedback cycles, but they do not remove the need to understand material properties, manufacturing limits, or the difference between prototype behavior and final production behavior.
Plan Tests Before You Test
A useful test begins with a question. Ask what requirement is being checked, what variable will be measured, what equipment is needed, what conditions must be controlled, what result counts as acceptance, and how the data will be recorded.
Avoid changing several important design features at once unless the test method is designed to separate their effects. Otherwise, you may not know which change caused the improvement or failure. Repeat measurements where variation is expected and use suitable measuring equipment.
Measurement quality matters. Check the instrument range, resolution, condition, zero, calibration status when required, and correct use. A reading with many decimal places is not automatically accurate. Record units and measurement conditions so that another person can understand the result.
Verification and Validation
Verification asks whether the design meets specified requirements: "Did we build the design correctly?" Examples include checking a dimension, confirming an electrical output, measuring load capacity, or inspecting whether the required material was used.
Validation asks whether the solution meets the real user need in its intended context: "Did we build the right solution?" A holder may meet every drawing dimension and still be frustrating to use. That is why user trials, workplace observation, or realistic operating scenarios can be as important as technical measurements.
Verification and validation often overlap in small vocational projects, but keeping the distinction in mind helps prevent a design from becoming technically compliant yet practically unsuitable.
Evaluate Data and Make Evidence-Based Decisions
After testing, compare results with the requirements and acceptance criteria. Separate observation from interpretation. "The prototype deflected 4 mm under the specified test condition" is an observation. "The support is too flexible for the current requirement" is an interpretation based on an agreed limit.
When a result is unexpected, check the test method, equipment, assembly, material, and assumptions before changing the design. A failed test can come from the product, the test setup, or both.
Use tables, photographs, sketches, graphs, and short notes to preserve evidence. This helps teammates understand what happened and prevents the same unsuccessful idea from being repeated later.
Iterate and Improve
Iteration means repeating part of the process using what you learned. You might change geometry, material, fastening, layout, software logic, component selection, or a requirement that was based on a wrong assumption. Each revision should have a reason.
Do not treat every change as an improvement. Compare the new version with the previous one using the same relevant criteria. A change that improves strength may increase mass or cost. A change that speeds assembly may make maintenance harder. This is why trade-offs must remain visible throughout iteration.
Use revision control. Label versions clearly, record what changed, why it changed, who approved it when approval is required, and which test evidence belongs to which version.
Design for Manufacture, Assembly, Maintenance, and Quality
A successful design must survive contact with the real production and service environment. Consider how parts will be made, held, joined, inspected, assembled, transported, cleaned, adjusted, and replaced.
Ask whether a tool can reach each fastener, whether similar components could be assembled incorrectly, whether inspection points are accessible, whether consumable parts can be replaced safely, and whether standard components could reduce cost or lead time. Design changes that simplify assembly often improve quality because they reduce opportunities for error.
Quality planning connects design intent with inspection. Define which characteristics are critical, how they will be measured, and what records are needed. The aim is not to inspect quality into a poor design but to create a design and process that can produce acceptable results consistently.
Sustainability and Life-Cycle Thinking
Engineering design influences resource use long after the first prototype. Consider material quantity, energy use, durability, repairability, modularity, spare parts, packaging, transport, recyclability, and end-of-life options.
A lightweight design is not automatically more sustainable if it wears out quickly. A durable design is not automatically better if it uses unnecessarily scarce material. Life-cycle thinking compares consequences across sourcing, manufacture, use, maintenance, and disposal rather than focusing on one stage only.
For vocational learners, practical sustainability questions include: Can the product be repaired instead of replaced? Can standard parts be reused? Can waste from cutting or printing be reduced? Can energy consumption be measured? Can disassembly be made easier?
Communicate, Handover, and Learn from the Project
Engineering work ends with communication, not merely with a finished object. A handover may include the final drawing, bill of materials, operating instructions, test results, risk information, maintenance notes, software version, inspection criteria, and unresolved limitations.
A short design review should explain the need, requirements, alternatives considered, chosen concept, important calculations or evidence, test results, changes made, remaining risks, and recommended next steps. Good communication allows another competent person to understand and continue the work.
NASA's engineering examples illustrate the same principle at a larger scale: technical systems evolve because teams continue to learn from requirements, operating conditions, testing, and user needs. The scale may be different from an apprenticeship project, but the logic of evidence-based improvement is transferable.
Vocational Design Toolkit
A Practical Design Notebook
Keep a design notebook or digital log from the first day. Record dates, observations, sketches, measurements, questions, decisions, test results, photographs, and changes. Entries should be understandable later, not just in the moment.
A useful project record can include the problem statement, stakeholder notes, requirement list, concept sketches, comparison matrix, calculations, drawing revisions, prototype photographs, test plan, raw data, evaluation, change log, and final recommendation. This creates a chain of evidence from need to solution.
Questions to Ask at Each Stage
When defining the problem, ask: Who needs what, and why? When researching, ask: What do we know, what is uncertain, and what already exists? When defining requirements, ask: How will success be measured? When generating concepts, ask: What fundamentally different ways could achieve the function? When selecting, ask: Which evidence supports the decision? When prototyping, ask: What are we trying to learn? When testing, ask: Is the method safe, repeatable, and connected to a requirement? When iterating, ask: What did the data teach us? When handing over, ask: Could another competent person understand, manufacture, use, inspect, and maintain this solution?
Common Mistakes and Better Practice
Jumping to the first idea reduces your chance of finding a better solution. Generate alternatives before committing.
Writing vague requirements makes objective testing difficult. Convert important needs into clear, checkable statements.
Overbuilding the first prototype wastes time if the main idea is still uncertain. Prototype the riskiest assumption first.
Testing without acceptance criteria produces data without a decision rule. Define what result would count as acceptable before testing.
Changing many things at once makes learning difficult. Change deliberately and preserve revision information.
Ignoring the operator or maintainer can create a technically impressive but impractical design. Include real users in reviews and validation.
Treating documentation as paperwork after the project causes missing evidence and revision confusion. Document decisions as you go.
Engineering Design and the Scientific Method
The engineering design process and the scientific method are related but have different primary goals. Science often investigates and explains phenomena, while engineering creates solutions that satisfy needs and constraints. Engineering projects still use experiments, measurement, mathematics, and scientific knowledge. The difference is that test results are used to judge and improve a designed solution.
Reliable Reference Basis
The process described here is consistent with educational engineering guidance from Science Buddies, NASA Jet Propulsion Laboratory, NASA STEM, and MIT OpenCourseWare. These sources use different stage names and levels of detail, which reinforces an important point: engineering design is a flexible framework rather than one universal sequence that every organization must follow word for word.
Interactive Tasks
Quiz: Test Your Knowledge
Why is the engineering design process usually described as iterative? (Test results can lead you back to improve an earlier design decision) (!Every project must repeat all stages the same number of times) (!A final design should be selected before research starts) (!Iteration means avoiding measurements until the end)
Which statement best describes a design criterion? (A characteristic used to judge how well a solution succeeds) (!A limit that the design is not allowed to exceed) (!A drawing revision that has already been approved) (!A tool used only for final inspection)
Which statement is a constraint? (The solution must fit within the available installation space) (!The handle should feel comfortable to most users) (!The concept should be easy to maintain) (!The design should score highly for appearance)
What is the main reason to generate several concepts before selecting one? (To compare genuinely different ways of meeting the need) (!To avoid defining requirements) (!To ensure the most expensive option is chosen) (!To remove the need for testing)
What should a prototype primarily help you do? (Learn whether important design assumptions work in practice) (!Replace all technical documentation) (!Guarantee that the final product has no risk) (!Avoid collecting user feedback)
What does verification mainly ask? (Whether the design meets its specified requirements) (!Whether the design is the cheapest available product) (!Whether every stakeholder prefers the same concept) (!Whether brainstorming produced enough ideas)
What does validation mainly ask? (Whether the solution meets the real user need in context) (!Whether every dimension has three decimal places) (!Whether the prototype was built from final production material) (!Whether the design notebook contains only final results)
Why should acceptance criteria be defined before a test? (So the result can be compared with an agreed decision rule) (!So failed measurements can be removed from the record) (!So the prototype cannot be changed after testing) (!So only one measurement needs to be taken)
Why is revision control important during iteration? (It links each design version to its changes and evidence) (!It prevents any design from being modified) (!It replaces the need for drawings) (!It guarantees that all concepts have equal cost)
Which action best supports sustainable engineering design? (Considering repairability material use energy use and end of life) (!Selecting the lightest material without further analysis) (!Ignoring maintenance because it happens after production) (!Replacing every failed part with a complete new assembly)
Memory Game
| Criterion | A characteristic used to judge how well a solution performs |
| Constraint | A limit that the design must respect |
| Prototype | A version built to learn how a design works in practice |
| Iteration | Repeating part of the process using evidence to improve the design |
| Tolerance | The permitted variation from a specified dimension or value |
| Traceability | The connection between a requirement and the evidence used to verify it |
Drag and Drop
| Match the correct terms. | Topic |
|---|---|
| Design brief | States the problem scope and important needs |
| Decision matrix | Compares alternative concepts against agreed criteria |
| Test plan | Defines what will be measured and how success will be judged |
| Change log | Records what was modified between design versions |
| Handover package | Gives others the information needed to use support or continue the solution |
...
Crossword Puzzle
| Criteria | What do you call the characteristics used to judge design success? |
| Constraint | What do you call a limit that the design must respect? |
| Prototype | What do you call a version built to learn how a design works? |
| Iteration | What do you call repeating part of the process to improve a design? |
| Tolerance | What term describes permitted variation from a specified value? |
| Traceability | What term links requirements with their verification evidence? |
LearningApps
Cloze Text
Open-Ended Tasks
Easy
- Problem statement: Find one small inconvenience in your training workshop or classroom and write a solution-neutral problem statement that names the user, need, and reason it matters.
- Stakeholder analysis: Choose a familiar product or workstation and create a one-page map of at least four stakeholders and the different needs each one may have.
- Concept sketch: Produce three quick sketches for a simple storage, holding, carrying, or organization problem and label the important functions without choosing a winner yet.
- Design notebook: Start a dated design log for one week and record observations, questions, sketches, measurements, and decisions from a real learning task.
Standard
- Requirements engineering: Turn five informal user wishes for a vocational product into clear testable requirements and state how each requirement could be verified.
- Decision matrix: Compare at least three concepts for a real training task using agreed criteria, explain your scores, and identify the trade-off that most influenced your final choice.
- Prototype: Build a low-cost safe mock-up of a non-hazardous workplace aid, photograph its development, collect feedback from two users, and document one evidence-based improvement.
- Technical drawing: Create a dimensioned sketch or CAD drawing of a simple component and add the information another learner would need to reproduce it accurately.
Advanced
- Design review: Conduct a formal peer review of a vocational design, assign roles such as designer, operator, maintainer, and quality reviewer, and produce a record of actions and unresolved questions.
- Test plan: Develop and carry out a supervised test for a safe prototype, define the acceptance criterion before testing, collect repeat measurements where appropriate, and present the results in a table or graph.
- Life-cycle assessment: Compare two design alternatives by considering material use, manufacture, energy use, maintenance, repairability, transport, and end of life, then defend a recommendation with evidence.
- Engineering communication: Produce a three-minute video or narrated presentation that shows the complete design journey from problem definition to final recommendation, including one failed or weak version and what you learned from it.
Learning Assessment
- Design justification: Given a workplace design brief, propose two different concepts and justify a final choice by connecting stakeholder needs, criteria, constraints, evidence, and trade-offs.
- Requirement quality: Review a set of vague requirements, rewrite them into testable form, and explain how poor requirements could cause manufacturing, testing, or customer problems.
- Failure analysis: Study a failed prototype case, separate observations from interpretations, identify plausible causes, and propose the next test that would provide the most useful evidence.
- Transfer to workplace: Choose a process from your own vocational field and show where problem definition, concept selection, prototyping, verification, validation, revision control, and handover appear in real practice.
- Sustainable redesign: Redesign a familiar product or fixture to improve repairability or reduce waste while maintaining its essential function, and explain which new trade-offs your redesign creates.
- Technical handover: Prepare a concise handover package for a completed design that includes the current revision, requirements status, essential drawings or sketches, test evidence, operating limits, and recommended next actions.
Evidence of Learning
Important evidence of learning includes your ability to explain the purpose of each design stage without treating the process as rigid; identify the real need behind a proposed solution; distinguish criteria, constraints, and requirements; generate alternative concepts; use transparent methods to compare options; create understandable sketches, drawings, CAD models, or specifications; plan safe and meaningful tests; use measuring tools appropriately; interpret data against acceptance criteria; distinguish verification from validation; document iterations and revisions; recognize trade-offs; consider manufacture, assembly, maintenance, quality, and sustainability; and communicate decisions to technical and non-technical stakeholders.
Useful products that demonstrate this learning include a design notebook, stakeholder map, design brief, requirement list, concept portfolio, decision matrix, prototype, technical drawing, bill of materials, test plan, measurement record, graph, change log, risk-related design notes, design review record, final presentation, and handover package.
Strong transfer evidence appears when you can apply the same reasoning in a new vocational context. For example, a mechatronics learner may use the process for a sensor mount, a construction trainee for a temporary layout aid, an electrical apprentice for an enclosure arrangement, a manufacturing trainee for a fixture, and an IT trainee for a digital workflow. The tools differ, but the logic of defining needs, testing assumptions, and improving from evidence remains transferable.
OERs on the Topic
Linked Learning Areas
