Lesson 2 of 6 · Engineers and designers
Understand how engineers compare possible designs
8 minute lesson · 3 checks along the way
Your goal for this lessonConnect requirements, interfaces and evidence-based disagreement.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Follow a linked name to explore its archive card. “Back to your lesson” brings you to the same part of the reading.
Words with a dotted underline open a short definition right here in the lesson.
Read & understand
Engineering turns goals into working arrangements
Engineers translate an intended task into systems that can perform it under stated conditions. They compare options for mass, power, reliability, thermal behavior, communications and cost. A design that optimizes one component can still fail the complete mission if its interfaces or operating assumptions do not fit the rest.
For a fictional camera, a larger detector may improve one measurement while increasing power use and data volume. The engineering decision must include battery capacity, heat removal, storage and downlink. Tradeoffs are relationships among requirements, not simply a search for the biggest specification.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Historical design choices involved argument and evidence
John Houbolt advocated lunar-orbit rendezvous during Apollo planning, helping make the case for a separate lunar landing vehicle and a meeting in lunar orbit. The approach offered system-level advantages but required confidence in rendezvous and docking. Its adoption depended on analysis and organizational debate, not one unexplained flash of inspiration.
Mary W. Jackson’s career at Langley included experimental aeronautical engineering and efforts to widen opportunities for others. Her path also reflects the barriers faced by Black women in segregated institutions. Technical histories should preserve both the work and the conditions under which people were permitted to do it.
Compare the complete system
Original teaching diagram. Local design choice. Mass, power and performance. Interfaces with other hardware. Mission consequences. Operations and failure cases. Evidence behind the tradeoff. A simpler component can create a more demanding operation; state the boundary of the comparison.
Open full-size diagram in a new tab: Compare the complete systemCheck 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
A design claim must survive review
In a fictional , option A uses less propellant but introduces a new docking operation. The team should compare the complete mission sequence, failure cases and evidence supporting each assumption. Calling one option simpler without specifying the system boundary can hide where complexity moved.
Engineers document decisions, test models against measurements and revise designs when evidence changes. Productive disagreement requires traceable reasoning and a route for unresolved concerns to reach the people with authority. The final hardware embodies a series of choices made by many contributors rather than an inevitable answer.
Check 3 of 3
10 pointsUse the reading above. You can try again without losing points.
Put it together
Your lesson progress
Each check connects to a part of the story. Complete all 3 to earn your 25-point lesson bonus.
Explore further · Optional
Go to the source
Explore the evidence behind this lesson. These optional readings and videos open in a new tab.
- Read: NASA: John C. Houbolt and lunar-orbit rendezvousCompare the explanation and its assumptions with the worked example in this lesson.
- Read: NASA: Mary W. JacksonCompare the explanation and its assumptions with the worked example in this lesson.
- Read: NASA: system design processesCompare the explanation and its assumptions with the worked example in this lesson.