Lesson 2 of 6 · Development and integration
Make the parts work as one spacecraft
8 minute lesson · 3 checks along the way
Your goal for this lessonDistinguish component evidence, interface evidence and tests after a design change.
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
Development makes assumptions concrete
Once a design advances, teams turn requirements into hardware, software and operational procedures. Components arrive with specifications, configuration records and their own test evidence. combines them into larger assemblies. At each step, previously abstract interfaces become real cables, messages, mechanical connections and timing relationships.
Two parts can each meet their own specification yet fail together if their interface definitions disagree. Imagine an instrument that reports temperature in kelvin while receiving software interprets the numbers as degrees Celsius. Both might pass isolated tests built around different assumptions; an integrated test must examine what crosses the boundary.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Test the behavior that matters
Verification asks whether the system meets specified requirements. Validation asks whether it serves the intended use. These questions overlap but differ. A file can have the required format and still omit information that scientists need to interpret a measurement. A mission must connect technical compliance with the actual investigation.
For a fictional camera, a component test confirms that the detector records light. An integrated sequence then checks pointing, exposure, time labels, storage and eventual ground decoding. That sequence examines a chain of behavior. It does not prove survival of launch vibration; environmental evidence addresses a different requirement.
Mars Observer is integrated with the Transfer Orbit Stage during ground preparation before encapsulation. The photograph shows connected hardware; records of interface and sequence tests supply the evidence about how the assembly behaves.
Look closely
Which claim requires more than this photograph?
See what to notice
That the combined hardware and software communicate correctly and execute the required sequence needs test results. Visible assembly alone does not establish integrated performance.
Check 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
A change has a reach
Suppose an instrument’s data packet grows from 2 to 3 megabytes while the recorder allocation stays at 30 megabytes. Ignoring overhead, capacity falls from fifteen packets to ten. A “small” software change has altered the observing plan even if the detector itself works exactly as before.
Record the configuration tested, assess the affected interfaces and repeat the relevant checks. Repeating every historical test may be wasteful, but assuming that old results automatically cover the changed system is unsafe reasoning. Reviews should identify what evidence still applies and what new evidence is needed before the next mission phase.
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.