The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
This paper lays out a approach for safety assurance case argumentation. The approach links together in a principled manner a device's highest-level safety claims, operating environments and hazards; and its safety requirements, final implementation, and test and other validation results. This approach is intended for the creation of safety assurance cases for pre-market submissions to a regulatory...
The creation of safety assurance cases is a new requirement for rebreather manufacturers, where a rebreather is simply understood as a self-contained underwater breathing apparatus. The two main potential benefits to creating safety assurance cases for rebreather systems are: ensuring that the system is sufficiently safe in a given context and showing compliance to a regulatory framework. This paper...
Increased complexity in the design, technology and supply chains for software-intensive safety-critical systems has resulted in a growing demand for a compositional approach to safety assurance. Assurance data relating to independently-derived components must be melded together into a compelling case for overall system safety. One of the barriers to composition is the lack of consistency in the terminology...
The basis for assessing the validity of an assurance case is an active area of study. In this paper, we discuss how to assess confidence in a case by considering the doubts eliminated by the claims and evidence in a case. This is an application of eliminative induction and the notion of Baconian probability as put forward by L. Jonathan Cohen.
In this paper, we will introduce some of the problem areas that Japanese software engineers are susceptible to during the creation of assurance cases, based on the author's educational experience with assurance cases. In addition, methods for dealing with these problem areas will also be explained. To mitigate these problems, it is expected to apply assurance case patterns that help engineers develop...
Safety cases and, specifically, software safety cases, have had virtually no presence in engineering practice in the US. Recent interest, in addition to an early attempt to introduce them into practice in the NASA Constellation Program, motivated us to develop a partial safety case for a safety critical subsystem for the Ares I vehicle, namely the abort detection, notification and response (AFDNR)...
GSN (Goal Structuring Notation) is a graphical notation widely used to construct assurance cases, which are required for the system assurance of safety critical systems specially in Europe, and now worldwide as the importance of system assurance has been growing and several safety standard such as ISO 26262 mandate the use of safety case (assurance case for system safety). The syntax and extensions...
In this article, we address safety cases as special cases of the more general class of assurance cases, which were developed as an extension to the concept of safety case. Related to the development and use of safety cases, there remain challenges, such as their size, readability, and identifying fallacious reasoning used in arguments. Some of these challenges are reviewed in the current article and...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.