From 4c3977e3a8e06c45385b5630095217724572dfa6 Mon Sep 17 00:00:00 2001
From: Flancian <0@flancia.org>
Date: Sun, 18 Jul 2021 23:37:54 +0200
Subject: [PATCH] vault backup: 2021-07-18 23:37:54

---
 system theoretic process analysis.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/system theoretic process analysis.md b/system theoretic process analysis.md
index d6b801370..8ea71a9f9 100644
--- a/system theoretic process analysis.md	
+++ b/system theoretic process analysis.md	
@@ -4,15 +4,16 @@
 	- [[pull]] [[stpa handbook]] [[stpa workshop]]
 	- [[push]] [[stpa]]
 		- I love how STPA defers key steps to a later stage so they can be done systemically, once partial but complete initial modeling has taken place.
+	- can be applied recursively
 	- 4 [[steps]]
-		- define the purpose of the analysis, including [[scope]], [[losses]], [[hazards]], [[constraints]] (optionally derived also from [[sub hazards]]).
+		- define the purpose of the analysis, including [[losses]], [[scope]], [[hazards]], [[constraints]] (optionally derived also from [[sub hazards]]).
 		- model the control structure
 	- step one: define the purpose of the analysis
 		- start with the [[losses]], which involve something of value to stakeholders
-		- continue by defining the scope of the system
+		- continue by defining the [[scope]] of the system
 		- find [[hazards]], which are systemic states or conditions to be prevented, and which together with (worst-case) environmental conditions lead to [[losses]].
 			- [[hazards]] + [[environmental conditions]] -> [[losses]]
 		- find [[system level constraints]]. 
 			- they can look like [[hazards]], inverted.
 			- or define how the system must [[minimize losses]] in case the hazards occur.
-	- can be applied recursively
\ No newline at end of file
+		- find [[sub hazards]], which
\ No newline at end of file