@@ -524,8 +524,6 @@ It is up to the software design to tolerate these interruptions.
Modern design is often distributed, but depending on the implementation and runtime context, a singular process can also provide the targetted service availability if implemented correctly and self healing system can launch a replacement within the given time window.
When evaluating the applicability of these requirements, the highest of following risk factors define the category to follow: [SRU], [Complexity], [Segment], [CENT]
For low risk:
***[REQ-HA-0]** Expected availability shall be defined for each relevant system component.
@@ -533,7 +531,8 @@ For low risk:
For medium risk:
***[REQ-HA-2]** System shall tolerate loss of resources within the limits of the defined availability.
***[REQ-HA-2]** The product shall tolerate loss of resources within the limits of the defined availability.
***[REQ-HA-6]** The product shall minimise the impact to other systems when anomalies occur.
***[REQ-HA-3]** Recovery capabilities shall be sufficiently implemented to match the expected availability targets.
<mark>REQ-HA-3 needs documentation trick for: "made available in the technical documentation"</mark>
