stpa-step1-define-purpose

To define losses and hazards for STPA, identify unacceptable losses across software, physical, and AI systems, then map system states to those losses using structured templates to produce traceable hazards.

The best way to identify safety constraints from hazards is to generate system-level policies that directly mitigate each identified hazard, ensuring traceability between the constraint and the hazard it addresses.

Yes, STPA hazard analysis applies to AI and autonomous vehicle systems by capturing critical losses, unsafe behaviors, and safety policies during the initial purpose-definition phase of the assessment.

Trace safety constraints to specific losses in STPA by linking constraints to hazards and hazards to losses, maintaining a clear traceability chain throughout the structured markdown templates.

You need to define the purpose of analysis before starting STPA to establish a solid safety foundation, ensuring unacceptable losses and associated hazards are systematically recorded prior to deeper analysis.

STPA step 1 focuses solely on the initial purpose-definition phase, identifying losses, hazards, and constraints, and does not cover the downstream control structure design or detailed causal analysis.