Space RHA short course · Chapter 3 of 12 · about 60 minutes
RHA requirements
Turning an environment and a mission into requirements a project can verify: the trade space, flowdown, cumulative and single-event criteria, margins and verification.
Status: this chapter is the earlier material rewritten into the lesson flow. The worked examples with computed numbers that chapters 1 and 6 to 12 have are still to be written here; where a lesson has an exercise instead, that is why.
Lessons
- 01RHA choices are connected10 minThe mission needs a function to keep working. Which parts are used, how the architecture is built around them, what test evidence exists and what resources are available …
- 02Flowdown in both directions10 minA requirement runs from the mission intent down to a function, then to a circuit or a part, and the evidence has to run back up the same path. Requirements flow down; tes…
- 03Writing a TID and DDD requirement10 minA TID requirement is more than a dose. Behind the number are a choice of solar-particle model and statistical case, a local dose calculation, a margin with a reason, and …
- 04Writing the SEE criteria10 minThe environment sets how often particles arrive. The mission duration and the number of susceptible parts set how many opportunities for an event accumulate. The applicat…
- 05Margin needs a reason10 minA design margin provides headroom against named uncertainties and against design choices. The value of the margin does not by itself express a survival probability or a c…
- 06A requirement someone can verify10 minA requirement that can be verified names the hardware or function that must perform, the exposure and conditions it must perform under, the measurable limit, and how the …