mil-std-882

Assign a severity category (I–IV) and probability level (A–F) to each hazard, combine them into a Risk Assessment Code such as 2C, then map it via Table III to a High, Serious, Medium, or Low risk level. The skill's cheatsheet contains the full matrix and quantitative probability thresholds.

The standard defines Task 100 management tasks (SSPP, HTS), Task 200 analysis tasks (PHL, PHA, SRHA, SSHA, SHA, O&SHA, HHA, FHA, SoSHA, EHA), Task 300 evaluation tasks (SAR, HMAR, T&E), and Task 400 verification tasks. Each must be individually invoked in the contract.

Software uses a criticality framework instead of probability: a Software Control Category (1–5) crossed with severity produces a Software Criticality Index (SwCI 1–5), which drives required Level of Rigor analysis and testing tasks. Incomplete LOR tasks default to defined risk levels.

No. The pack covers MIL-STD-882E only and explicitly excludes DO-178C, ARP 4761, ISO/IEC 61508, and FAA/OSHA/EPA regulations, though it notes conceptual cross-walks such as DALs roughly corresponding to SwCI levels.

No. Probability F (Eliminated) requires the hazard to be physically incapable of occurrence. The standard states that no amount of doctrine, training, warnings, cautions, or PPE can move a mishap probability to level F.