software

Software Contribution Safety Argument Pattern with Grouping

Posted by GSNAdmin on December 09, 2011
Tiered Safety Argument Patterns / Comments Off on Software Contribution Safety Argument Pattern with Grouping

This pattern is an extension of the Software Contribution Safety Argument Pattern. It provides the option of grouping the argument to reflect natural requirements groupings in the software design. For example, for an instantiation of the Software Contribution Safety Argument Pattern at the software architecture level, it may be desirable to create groupings in the argument which reflect each of the individual architectural design elements.

Continue reading…

Tags: , ,

Hazardous Contribution Software Safety Argument Pattern

Posted by GSNAdmin on December 09, 2011
Tiered Safety Argument Patterns / Comments Off on Hazardous Contribution Software Safety Argument Pattern

This pattern provides the structure for arguments that potential hazardous failures that may arise at {tier n} are acceptably managed.

Continue reading…

Tags: , ,

SSR Identification Software Safety Argument Pattern

Posted by GSNAdmin on December 09, 2011
Tiered Safety Argument Patterns / Comments Off on SSR Identification Software Safety Argument Pattern

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.

Continue reading…

Tags: , ,

Software Contribution Safety Argument Pattern

Posted by GSNAdmin on December 09, 2011
Tiered Safety Argument Patterns / Comments Off on Software Contribution Safety Argument Pattern

This pattern provides the structure for arguments that the contributions made by software to system hazards are acceptably managed.

Continue reading…

Tags: , ,

High-Level Software Safety Argument Pattern

Posted by GSNAdmin on December 09, 2011
Tiered Safety Argument Patterns / Comments Off on High-Level Software Safety Argument Pattern

This pattern provides the high-level structure for a software safety argument. The pattern can either be used to create the high level structure of a ‘stand alone’ software safety argument considering just the software aspects of the system, or alternatively can be used to support claims relating to software aspects within a broader system safety argument.

Continue reading…

Tags: ,

Handling of Software Failure Mode

Posted by GSNAdmin on December 07, 2011
GSN Patterns / Comments Off on Handling of Software Failure Mode

The intent of this pattern is to develop an argument that a software failure mode can be handled by other components (software, hardware or other).

Continue reading…

Tags: ,

Software Argument Approach

Posted by GSNAdmin on December 07, 2011
GSN Patterns / Comments Off on Software Argument Approach

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.

Continue reading…

Tags: ,

Hazardous Software Failure Mode Classification

Posted by GSNAdmin on December 07, 2011
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.

Continue reading…

Tags: ,

Hazardous Software Failure Mode Decomposition

Posted by GSNAdmin on December 07, 2011
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.

Continue reading…

Tags: , ,