The intent of this pattern is to argue that an individual software hazard, which is of the type Value, is absent within a certain component of software functionality in a system.
Resources
Posted by GSNAdmin
on December 07, 2011
GSN Patterns / Comments Off on Absence of Value Hazardous Failure Mode
GSN Patterns / Comments Off on Absence of Value Hazardous Failure Mode
Posted by GSNAdmin
on December 07, 2011
GSN Patterns / Comments Off on Absence of Late Hazardous Failure Mode
GSN Patterns / Comments Off on Absence of Late Hazardous Failure Mode
The intent of this pattern is to argue that an individual software hazard, which is of the type Late, is absent within a certain component of software functionality in a system.
Posted by GSNAdmin
on December 07, 2011
GSN Patterns / Comments Off on Absence of Early Hazardous Failure Mode
GSN Patterns / Comments Off on Absence of Early Hazardous Failure Mode
The intent of this pattern is to argue that an individual software hazard, which is of the type Early, is absent within a certain component of software functionality in a system.
Posted by GSNAdmin
on December 07, 2011
GSN Patterns / Comments Off on Absence of Commission Hazardous Failure Mode
GSN Patterns / Comments Off on Absence of Commission Hazardous Failure Mode
The intent of this pattern is to argue that an individual hazardous software failure mode, which is of the type Commission, is absent within a certain component of software functionality in a system.
Posted by GSNAdmin
on December 07, 2011
GSN Patterns / Comments Off on Absence of Omission Hazardous Failure Mode
GSN Patterns / Comments Off on Absence of Omission Hazardous Failure Mode
The intent of this pattern is to argue that an individual hazardous software failure mode, which is of the type Omission, is absent within a certain component of software functionality in a system.
The intent of this pattern is to identify the argument approach used for demonstrating the acceptability of the hazardous software failure mode. The argument can be made by showing Absence and/or Handling of the failure mode.
Posted by GSNAdmin
on December 07, 2011
GSN Patterns / Comments Off on Hazardous Software Failure Mode Classification
GSN Patterns / Comments Off on Hazardous Software Failure Mode Classification
The intent of this pattern is to provide a type classification for the hazardous failure mode that is the subject of the argument. The failure mode can be classified as one of Omission, Commission, Early, Late or Value.
Posted by GSNAdmin
on December 07, 2011
GSN Patterns / Comments Off on Hazardous Software Failure Mode Decomposition
GSN Patterns / Comments Off on Hazardous Software Failure Mode Decomposition
The intent of this pattern is to provide a decomposition for the acceptability of software with respect to system level hazards. The pattern identifies the primary claims for developing a software safety argument from a hazard control perspective.
Posted by GSNAdmin
on December 07, 2011
GSN Patterns / Comments Off on Component Contributions to System Hazards
GSN Patterns / Comments Off on Component Contributions to System Hazards
The intent of this pattern is to provide a top level decomposition for the safety argument of a system. In particular, the pattern provides the context for a software safety argument constructed from the Software Safety Pattern Catalogue. The focus for the argument is the identification of hazards and the assessment of the associated risks.
Posted by GSNAdmin
on December 07, 2011
GSN Patterns / Comments Off on Safety Principle 6 (Defence in Depth) Compliance
GSN Patterns / Comments Off on Safety Principle 6 (Defence in Depth) Compliance
The purpose of this pattern is to argue compliance with Safety Principle 6 (Defence in Depth) of the Nuclear Naval Programme Safety Principles and Safety Criteria document.
