This pattern provides the structure for arguments that software safety requirements (SSRs) from a previous tier of development have been adequately captured at the next tier of development through the allocation, decomposition, apportionment or interpretation of the SSRs from the previous tier. This is achieved either through making design decisions which mitigate the SSR, or through the definition of additional SSRs.
requirements
Posted by GSNAdmin
on December 09, 2011
Tiered Safety Argument Patterns / Comments Off on SSR Identification Software Safety Argument Pattern
Tiered Safety Argument Patterns / Comments Off on SSR Identification Software Safety Argument Pattern
The intent of this pattern is to create arguments that instil a high degree of confidence in the satisfaction of a goal and are resilient to change and criticism.
