\[ \begin{align}\begin{aligned}\newcommand\blank{~\underline{\hspace{1.2cm}}~}\\% Bold symbols (vectors) \newcommand\bs[1]{\mathbf{#1}}\\% Differential \newcommand\dd[2][]{\mathrm{d}^{#1}{#2}} % use as \dd, \dd{x}, or \dd[2]{x}\\% Poor man's siunitx \newcommand\unit[1]{\mathrm{#1}} \newcommand\num[1]{#1} \newcommand\qty[2]{#1~\unit{#2}}\\\newcommand\per{/} \newcommand\squared{{}^2} \newcommand\cubed{{}^3} % % Scale \newcommand\milli{\unit{m}} \newcommand\centi{\unit{c}} \newcommand\kilo{\unit{k}} \newcommand\mega{\unit{M}} % % Percent \newcommand\percent{\unit{{\kern-4mu}\%}} % % Angle \newcommand\radian{\unit{rad}} \newcommand\degree{\unit{{\kern-4mu}^\circ}} % % Time \newcommand\second{\unit{s}} \newcommand\s{\second} \newcommand\minute{\unit{min}} \newcommand\hour{\unit{h}} % % Distance \newcommand\meter{\unit{m}} \newcommand\m{\meter} \newcommand\inch{\unit{in}} \newcommand\foot{\unit{ft}} % % Force \newcommand\newton{\unit{N}} \newcommand\kip{\unit{kip}} % kilopound in "freedom" units - edit made by Sri % % Mass \newcommand\gram{\unit{g}} \newcommand\g{\gram} \newcommand\kilogram{\unit{kg}} \newcommand\kg{\kilogram} \newcommand\grain{\unit{grain}} \newcommand\ounce{\unit{oz}} % % Temperature \newcommand\kelvin{\unit{K}} \newcommand\K{\kelvin} \newcommand\celsius{\unit{{}^\circ C}} \newcommand\C{\celsius} \newcommand\fahrenheit{\unit{{}^\circ F}} \newcommand\F{\fahrenheit} % % Area \newcommand\sqft{\unit{sq\,\foot}} % square foot % % Volume \newcommand\liter{\unit{L}} \newcommand\gallon{\unit{gal}} % % Frequency \newcommand\hertz{\unit{Hz}} \newcommand\rpm{\unit{rpm}} % % Voltage \newcommand\volt{\unit{V}} \newcommand\V{\volt} \newcommand\millivolt{\milli\volt} \newcommand\mV{\milli\volt} \newcommand\kilovolt{\kilo\volt} \newcommand\kV{\kilo\volt} % % Current \newcommand\ampere{\unit{A}} \newcommand\A{\ampere} \newcommand\milliampereA{\milli\ampere} \newcommand\mA{\milli\ampere} \newcommand\kiloampereA{\kilo\ampere} \newcommand\kA{\kilo\ampere} % % Resistance \newcommand\ohm{\Omega} \newcommand\milliohm{\milli\ohm} \newcommand\kiloohm{\kilo\ohm} % correct SI spelling \newcommand\kilohm{\kilo\ohm} % "American" spelling used in siunitx \newcommand\megaohm{\mega\ohm} % correct SI spelling \newcommand\megohm{\mega\ohm} % "American" spelling used in siunitx % % Capacitance \newcommand\farad{\unit{F}} \newcommand\F{\farad} \newcommand\microfarad{\micro\farad} \newcommand\muF{\micro\farad} % % Inductance \newcommand\henry{\unit{H}} \newcommand\H{\henry} \newcommand\millihenry{\milli\henry} \newcommand\mH{\milli\henry} % % Power \newcommand\watt{\unit{W}} \newcommand\W{\watt} \newcommand\milliwatt{\milli\watt} \newcommand\mW{\milli\watt} \newcommand\kilowatt{\kilo\watt} \newcommand\kW{\kilo\watt} % % Energy \newcommand\joule{\unit{J}} \newcommand\J{\joule} % % Composite units % % Torque \newcommand\ozin{\unit{\ounce}\,\unit{in}} \newcommand\newtonmeter{\unit{\newton\,\meter}} % % Pressure \newcommand\psf{\unit{psf}} % pounds per square foot \newcommand\pcf{\unit{pcf}} % pounds per cubic foot \newcommand\pascal{\unit{Pa}} \newcommand\Pa{\pascal} \newcommand\ksi{\unit{ksi}} % kilopound per square inch % NOTE: do NOT define \bar -- it is the built-in LaTeX accent used by \bar{x}, % \bar{y} (sample means). Redefining it made those render as the word "bar". \newcommand\barunit{\unit{bar}} \end{aligned}\end{align} \]

Nov 16, 2026 | 1439 words | 14 min read

15. The Engineering Design Process#

At a Glance

What you will do: Read how the engineering design process maps onto the five milestones, and which sections of your Design Project Technical Report you build at each one.

What you will submit: Nothing. Return to this page at each milestone.

In engineering, a project starts by defining the problem. Before designing anything, engineers confirm who the solution is for and agree on the criteria it must meet. The engineering design process (EDP) is the sequence of stages that takes a general request, such as “keep our plants alive,” to a tested solution. This project follows the EDP one stage at a time across five milestones.

Milestones M1 to M5 as connected stages left to right, with a curved arrow running back from M4 to M2.

Fig. 15.1 The five milestones as design stages, each with its report checkpoint: M1 scope the problem (TP1), M2 generate ideas (TP2), M3 test and iterate (TP3), M4 develop and optimize (TP4), and M5 deliver and reflect (TP5). The forward arrows show the order of the milestones. The backward arrow shows iteration: results at a later stage send the team back to an earlier decision. The band underneath shows the report growing section by section, from problem scoping to the executive summary.#

15.1. The Technical Report#

Your main deliverable is the Design Project Technical Report. Your team builds it over the whole project. At each milestone you draft new sections and revise earlier ones. By Milestone 5 the report covers the problem, the evidence, the ideas you considered, the design you chose, the data that shows it works, and what your team would do differently.

Each milestone has a report checkpoint, labeled TP1 to TP5. A checkpoint is a graded submission of your report in its current state, together with the other deliverables for that milestone. Examples of those deliverables are your client needs analysis, a regression plot, a flowchart, and the performance plots for your controller. Each checkpoint is graded on the sections that milestone requires. Download the report template and start filling it in at M1.

15.2. The Stages, the Milestones, and Your Report#

Milestone

Design stage (what you do)

Report sections you draft

Sections you revise

M1: Problem Scoping

Analyze the client’s brief, scope the problem, set measurable criteria, research the background, organize the team

II. Team Roles; III. Problem Scoping (problem statement, criteria and constraints, users and stakeholders, problem finding, background, assumptions)

-

M2: Idea Generation and Rapid Prototyping

Learn what the system senses and controls, generate candidate ideas, model the insulation trade-off, evaluate ideas

IV. Idea Generation (functional decomposition, prior art, sketches, AI); V. Thought Experiments

III. Problem Scoping (update with simulation evidence)

M3: Testing and Iteration

Choose a hardware selection and control strategy with a weighted decision matrix, flowchart it, write a first draft, run it, and iterate until the crop survives

VI. Prototyping, Testing and Weighted Decision Matrix (predicted scores); VII. Iteration #1

III. Criteria; IV. Idea Generation (narrow to finalists)

M4: Solution Development

Finish, tune, and optimize the controller; test it against your criteria; exchange peer review

VI.c Test Results for the Chosen Design; VIII. Iteration #2; IX. Overview of Final Design (detailed design and data)

VI.d Weighted Decision Matrix (add measured results); VII. Iteration #1

M5: Communication and Refinement

Deliver a client-ready report, present your work, reflect

I. Executive Summary; IX. Final Design (novel aspects, trade-offs, lessons learned); X. References

All sections (final revision for a reader who was not part of the project)

Later milestones add new sections and also send the team back to earlier ones to review and improve them. This return to earlier work is called iteration.

15.3. Iteration#

Engineering projects do not move strictly from one stage to the next. Test results in M3 and M4 will send you back to earlier design decisions. Simulation evidence from M2 may show that a requirement you wrote in M1 cannot be met as written. When that happens, revise the requirement and record the evidence for the change. Revising a problem statement when new evidence arrives is one of the learning objectives of this course.

PS05:

Problem Revision - Revise the problem statement based on new evidence or insights.

15.4. What Design Means in This Project#

Your team designs three parts of the greenhouse system: the hardware selection (glazing, heater, and battery), the sensor strategy, and the control software. You compare design choices in your report and build the controller in code.

  • In your report: You generate and compare design choices using sketches, a trade-off model, and a weighted decision matrix. The “generate ideas,” “prototype,” and “choose” stages of the EDP happen here.

  • In code: You write the controller and test it in a physics-based simulation of GHU-2, running on the hardware your team selected. For a given seed, the simulation produces the same result on every run, so your results are repeatable.

In the report template, a prototype is a candidate design: a hardware selection paired with a control strategy. To test a prototype, you run it in the simulation.

15.5. The Ideation Toolkit#

In Milestone 2 your team generates a wide range of candidate ideas before choosing any of them. Engineers use several named strategies to generate ideas. Your report’s Idea Generation section requires functional decomposition, at least four AI-assisted ideas, and at least one other strategy: prior art, rapid prototyping, or biomimicry.

Strategy

What you do

Example

Functional decomposition

Break the job of the system into sub-functions and generate ideas for each one separately.

“Keep the crop alive” splits into sense temperature, add heat, add CO2, water the roots, detect a faulty sensor, and survive a storm. “Detect a faulty sensor” alone suggests three ideas: trust the backup, average the two readings, or switch sensors when they disagree.

Prior art

Find how existing systems perform the same function and adapt the best parts.

Commercial greenhouses remove excess heat by venting. GHU-2 cannot vent, so look at how other sealed systems, such as submarines and spacecraft, remove heat.

Sketching

Draw the system: where the sensors sit, what each actuator affects, and how the control loop connects them.

A sketch shows interactions that are easy to miss in a list, such as the LEDs also adding heat and the pump also raising humidity.

Rapid prototyping

Make the simplest version that can be evaluated, such as a rule table or a few lines of pseudocode.

“IF night AND temp below 17: heater 80%” is a complete rule the team can check against the brief before anyone writes code.

Biomimicry

Look at how living things solve the same problem.

The human body holds 37 C by sweating or shivering slightly as soon as its temperature starts to drift.

AI-assisted ideation

Ask an AI tool for candidate approaches you have not considered. Check every suggestion against the brief and the physics, and log each use in your AI Use Log.

Ask how controlled-environment farms keep a crop alive through a power shortage, then check each answer against the hardware in the annex.

Work in two phases. First, generate ideas with these strategies without judging them. Then narrow the list. Your Thought Experiments table (report section V) evaluates about six of the strongest ideas against your criteria, and the weighted decision matrix in Milestone 3 selects one design from the finalists.

15.6. The Learning Objectives This Project Assesses#

This project develops and assesses the course outcomes below. Most of them also appear in earlier parts of the course.

PS:

Problem Scoping - Develop and refine a problem statement based on stakeholder needs and evolving evidence.

IF:

Information Fluency - Generate ideas fluently and explore multiple potential solutions.

EB:

Evidence-Based Decision Making - Use evidence to compare, evaluate, and improve potential solutions.

SQ:

Solution Quality - Design solutions that meet technical requirements and stakeholder needs.

UC:

Universal Concepts - Demonstrate an understanding of foundational engineering concepts, including conservation principles and system modeling, that apply across engineering disciplines.

DV:

Data Visualization - Visually represent data and derive meaningful information from data. Demonstrate ability to accurately describe data sets through foundational descriptive statistics and then perform simple inferential statistics through understanding probability concepts and linear regression.

PR:

Programming - Write professional, well-organized, and error-free code. Store and access data appropriately; perform calculations using built-in functions and operators; and apply selection, repetition, and user-defined functions to solve problems. Translate written descriptions or flowcharts into working code. Students will demonstrate programming objectives using any appropriate programming or computational environment unless otherwise specified. For these objectives, “code” may include scripts, functions, formulas, or structured spreadsheet logic, depending on the tool used.

AI:

Artificial Intelligence

IL:

Information Literacy - Locate, evaluate, and use information appropriately to support engineering problem solving, modeling, and decision-making.

TM:

Teaming - Contribute meaningfully to team projects and discussions. Demonstrate responsibility, collaboration, and mutual learning in group work.

PC:

Professional Communication - Communicate engineering concepts, ideas, and decisions effectively and professionally through written, visual, and oral formats.

EC:

Ethical and Contextual Reasoning - Understand and explain the broader impacts of engineering decisions or recommendations, considering ethics, uncertainty, risk, and stakeholder responsibility.

PA:

Process Awareness - Reflect on individual and team problem-solving or design processes to support continuous improvement.