On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
constructed to be as flexible as possible such that they are applicable to a wide range of systems. There are a wide
range of different development processes used on different projects, and it is important that the argument pattern
may be instantiated no matter what development process is used. The structure of the pattern is therefore based upon
a generalized ‘tier’ model of development such as that proposed in reference 10. Each tier corresponds to one level
of decomposition of the design. The number of tiers of development may be different for different software systems,
but the general safety considerations at each tier are unchanged. In addition, different parts of the design of any
software system may be decomposed over a different number of tiers. Note that the term ‘tier’ is used principally to
avoid the potential confusion of overloading the term ‘level’.
R. Hawkins et al A Systematic Approach for Developing Software Safety Arguments,
Figure 4 - The structure of the software contribution safety argument pattern