3.6.28 · D3Spacecraft Structures & Systems Engineering

Worked examples — Verification methods — analysis, test, inspection, demonstration

3,963 words18 min readBack to topic

This page is the practice arena for the four verification methods. The parent note told you what analysis, test, inspection, and demonstration are. Here we throw every kind of case at you — every method, the edge cases where a method fails, the degenerate "zero" inputs, the limiting values, a real word problem, and a nasty exam twist — and work each one from the ground up.

Before we compute anything, two words that will appear over and over must be earned:

Figure — Verification methods — analysis, test, inspection, demonstration

Walk through the figure (s01) concretely. The mint green bar on top is the allowable — say a material can take units of stress before it yields. The coral bar below it is the applied — the launch only produces units. Because the mint bar is longer, its tip pokes out past the coral tip; that stick-out piece is drawn as the lavender double arrow labelled "margin". The dashed vertical line sits exactly at the coral (applied) tip — that is the "MoS zero line". Read the picture like this: if the mint tip lands to the right of the dashed line, you PASS; if it lands exactly on it, MoS ; if the coral bar ever grows past the mint bar, applied overshoots and you FAIL. Every example below is just this same picture with different bar lengths.

Why subtract 1? Because alone is a ratio: it equals 1 when the two are equal. Subtracting 1 shifts that "just barely equal" point to zero, so the sign of MoS instantly tells you pass/fail. That shift is why the dashed zero line in the figure sits right at the applied tip.


Building the beam-stress tool from scratch

Several examples below need the bending stress of a beam. The parent note quoted the collapsed formula ; let us earn every symbol so no example makes an unexplained leap.

Figure — Verification methods — analysis, test, inspection, demonstration

Walk through figure s02. The slate rectangle is the beam's cross-section (width across, height up). The dashed horizontal line through its middle is the neutral axis — the fibres there are neither stretched nor squashed. The lavender arrow points from that middle line up to the top edge; its length is , the farthest fibre. The little coral tick marks stacked up the height remind you that each sliver of area contributes to — the higher up (bigger ), the more it counts, which is why grows like .


The scenario matrix

Every problem this topic can throw at you falls into one of these cells. Each worked example below is tagged with the cell it hits, and together they cover the whole grid. The flow-schema below (figure s03) shows how the cells fan out from a single starting question, so you can see that we cover the whole space, not just a list.

Figure — Verification methods — analysis, test, inspection, demonstration

Walk through figure s03. The butter box on the left is the single root question every verification starts from: "Which verification scenario am I in?" Eight arrows fan out from it to the right, one per row of the table below — the arrow colour just groups related cells (mint = passes, coral = fails/wrong-method, lavender = degenerate/limit, butter = statistical). Reading top-to-bottom the leaf boxes are cells A through H; each box names the case class and its one-line "trick". The point of the picture is coverage: no matter which node you land on, an example below works it out, so the fan has no missing branch.

# Cell (case class) What makes it tricky Example
A Analysis, positive margin Straight number-crunch, PASS Ex 1
B Analysis, negative margin (FAIL) Sign flips negative → redesign Ex 2
C Zero / degenerate input Divide-by-zero, undefined MoS Ex 3
D Limiting value (MoS = 0) Exactly on the boundary Ex 4
E Test, qualification vs acceptance Two different levels, same unit Ex 5
F Wrong method chosen Requirement can't be tested → must inspect Ex 6
G Real-world word problem Extract numbers from prose Ex 7
H Exam twist: combined + statistical Two uncertainties combine, then verify Ex 8

We link the physics tools as they enter: Margin Philosophy, Finite Element Analysis, Thermal Math Modeling, Vibration Testing, Acceptance Testing, Traceability Matrix.


Cell A — Analysis, positive margin

Forecast: guess before computing — will a 2 kg mass on a 1 cm-thick aluminium bar at 8g pass, or is it too thin? Write down PASS or FAIL now.

  1. Inertial force. . Why this step? During launch the acceleration feels like extra gravity (a quasi-static load); Newton's second law converts the load factor "" into a real force the bracket must carry.
  2. Bending moment. . Why this step? A force at a distance from the fixed root bends the bar. The moment (defined above) measures that bending leverage — the farther out the mass, the harder the twist at the root.
  3. Bending stress using the transparent form (derived above, with the bending moment from step 2): Why this step? Stress is bending effort concentrated at the farthest fibre (distance from the neutral axis); the top fibre stretches most, so we check there — if the worst fibre survives, all do.
  4. Margin. . Why this step? This is the pass/fail verdict. Positive and large → the bracket is way over-strong.

Verify: Units — Pa = N/m². is far below (only about one-sixth of the allowable), so MoS PASS. In the s01 picture, the coral "applied" bar is tiny and the mint "allowable" bar towers over it. Sanity: a chunky 1 cm bar carrying only 2 kg should be easily strong, matching a big positive margin.


Cell B — Analysis, negative margin (FAIL)

Forecast: thinner and higher g — do you think it still passes? Guess.

  1. New force. . Why this step? Higher load factor means more inertial force — same Newton's-law conversion, now with .
  2. New bending moment then stress. , so Why this step? Notice appears squared in the denominator — shrinking from 10 mm to 4 mm ( thinner) blows up stress by . This is why thickness matters so much.
  3. Margin. . Why this step? Negative! In the s01 picture the coral "applied" bar has now grown past the mint "allowable" bar — the tip lands left of the mint tip — so the part yields.

Verify: is larger than → MoS FAIL. The Finite Element Analysis would flag this region red. Fix: thicken , add ribs, or pick a stronger alloy. Sanity check: ratio — the 1.5 is the load-factor increase (), the 6.25 is the thickness effect. The physics is self-consistent.


Cell C — Zero / degenerate input

Forecast: MoS . Plug in … what happens? Guess the trap.

  1. Try the formula directly. . Why this step? Dividing by zero is mathematically undefined — it is not a real number, and calling it "infinity" is only informal shorthand for "grows without bound as the denominator shrinks". You cannot write a finite margin here.
  2. Interpret physically. The stress being exactly zero means the member is not loaded at all in this case. Why this step? A picture: the coral "applied" bar in figure s01 has zero length, so the mint "allowable" bar sticks out past it with no upper limit. The ratio has no finite value — it just keeps rising as approaches zero.
  3. Correct engineering statement. Report: "MoS not applicable (denominator zero — undefined); member unloaded in this load case; verification satisfied by inspection of the load path, not by margin computation." Why this step? Never write a literal "" or a made-up big number on a Traceability Matrix. Zero applied load is a different verification story — you inspect that the load path genuinely bypasses this member.

Verify: Limit check — as , the ratio increases without bound (no finite limit exists). The formula therefore confirms the trap: MoS is undefined at , hence the special reporting rule. Never a finite lie, and never a literal in the paperwork.


Cell D — Limiting value (MoS exactly zero)

Forecast: applied equals allowable exactly. Pass or fail? Think about the "" in the requirement.

  1. Compute MoS. . Why this step? In figure s01 the coral and mint bars are now identical length; the lavender extra-length arrow has zero length; the mint tip lands exactly on the dashed zero line.
  2. Read the requirement carefully. It said MoS (strictly greater), not . Why this step? The boundary case turns on one inequality symbol. means the part yields at precisely the design load — zero protection against any manufacturing scatter, temperature effect, or model error.
  3. Verdict: MoS does not satisfy "MoS ". FAIL (marginal). Why this step? This is exactly why Margin Philosophy demands positive margin — reality always has scatter, and a zero-margin part is a coin flip.

Verify: exactly; is false → correctly fails the strict requirement. Limiting behaviour confirmed: this is the razor's edge between Ex 1 (positive) and Ex 2 (negative).


Cell E — Test: qualification vs acceptance levels

Forecast: which level is higher, and why would you ever test a flight unit at a lower level than the design proof? Guess before reading.

  1. Qualification level RMS. Why this step? Qualification proves the design survives worse-than-flight, covering all future units built to that design. The buys margin against manufacturing + environment scatter.
  2. Acceptance level RMS. Why this step? Acceptance Testing confirms this specific unit has no build defects (cold solder, loose fastener) without over-stressing flight hardware — you already proved the design at 10 g on the qual unit, so you never re-punish the flight unit to 10 g.
  3. What each verifies. Qual → the design margin. Acceptance → workmanship of one article. Why this step? Same requirement, two questions: "is the design good?" vs "is this copy built right?" Different levels answer different questions.

Verify: ; . Qual () Acceptance () and Acceptance equals Flight () — the correct ordering. Ratio qual/acceptance , matching the design margin factor.


Cell F — Wrong method chosen (method-selection twist)

Forecast: can you test a mass? What does testing even mean here? Guess the right method.

  1. Reject the wrong method. Mass is a static property — it doesn't emerge from operation or environment. A mission simulation is a demonstration and reveals nothing about mass. Why this step? The parent note's intuition: you can't "test" a mass — you just weigh it, and weighing is inspection, not test.
  2. Apply the correct method — inspection. Place the assembled, dry spacecraft on a calibrated scale: it reads . Why this step? Inspection directly observes the physical property against the limit — no model, no environment needed. Weighing is the textbook example of inspection.
  3. Verify against the limit. Is ? Yes. For mass we report the remaining allocation rather than a stress-style MoS: spare , which is under budget. Why this step? Mass margin is tracked in kilograms of spare allocation, which flows straight into mass budget tracking — not as the ratio-minus-one MoS used for stress.
  4. State the verdict. PASS by inspection, with () of margin remaining. Why this step? The requirement is met and the method is now the correct one; both the number and the method must be right for a valid verification entry.

Verify: → PASS. Method-fit check: static scalar property → inspection ✓ (not test, not analysis, not demonstration). Spare kg; . Both the numeric answer and the method selection are confirmed.


Cell G — Real-world word problem

Forecast: which limit is the battery closer to violating — the hot ceiling or the cold floor? Guess.

  1. Extract the numbers from the prose. Allowable band ; predicted band . Why this step? A word problem hides the numbers in sentences; the first job is always to name the applied values (predicted extremes) and the allowable values (the two limits).
  2. Hot-side margin. Distance to the ceiling of headroom. Why this step? For a two-sided limit you must check both ends; a temperature can fail high or low. The hot case tests the ceiling.
  3. Cold-side margin. Distance to the floor of headroom. Why this step? The cold case tests the floor. Both margins must be positive for the requirement to hold across the whole orbit.
  4. Overall verdict. Both and are PASS by analysis. The tighter margin is the hot side (). Why this step? Reporting the tightest margin tells the model-validation team where a small model error would matter most — the hot ceiling is the risk driver.

Verify: ✓ and ✓. Predicted band → requirement met. Tighter margin correctly identified as the hot side ().


Cell H — Exam twist: combine uncertainties, then verify

Forecast: two 10% scatters — do they add to 20%? Guess before you combine them.

  1. Combine independent uncertainties in quadrature. Why this step? Independent random errors do not add directly (that would be ); they add as squares under a root — the Pythagorean rule for uncertainties. Picture two perpendicular arrows of length 0.10; their resultant is , not 0.20.
  2. Go out to for high () coverage. Why this step? A band on a normal distribution captures of all units — testing to this level means almost every real flight unit is bounded by your test.
  3. Compare to the practical factor. Why this step? The pure statistics demands , but the industry standard is (Ex 5). So is less conservative than full — a deliberate cost/risk compromise, accepting slightly under coverage to avoid over-testing and over-building hardware. This is Margin Philosophy in one number.

Verify: ; . And , confirming the practical factor is the less-conservative compromise. Not : quadrature ≠ linear sum ✓.


Recall Quick self-test

Ex 1 bracket MoS (2 kg, 10 mm, 8g) ::: → PASS Ex 2 bracket MoS (4 mm, 12g) ::: → FAIL (stress 441 MPa > 270) MoS when applied stress is exactly zero ::: undefined (division by zero) — report "member unloaded", verify by inspection Does MoS satisfy "MoS "? ::: No — strict inequality, marginal FAIL Qual vs acceptance level for 8g flight limit ::: 10g (design) vs 8g (workmanship) Right method to verify a mass requirement ::: Inspection (weigh it), not test Combine two independent 10% scatters ::: , not 0.20 statistical test level vs industry ::: (statistics) vs (practical, less conservative) What does the load factor mean? ::: a plain dimensionless number of "g's" — the acceleration feels like times ordinary gravity How does become ? ::: put , ; the algebra collapses to