By Topic

Assurance Cases for Software-Intensive Systems (ASSURE), 2013 1st International Workshop on

Date 19-19 May 2013

Filter Results

Displaying Results 1 - 11 of 11
  • [Front matter]

    Publication Year: 2013 , Page(s): 1 - 2
    Save to Project icon | Request Permissions | PDF file iconPDF (41 KB)  
    Freely Available from IEEE
  • Contents

    Publication Year: 2013 , Page(s): 1
    Save to Project icon | Request Permissions | PDF file iconPDF (46 KB)  
    Freely Available from IEEE
  • Foreword

    Publication Year: 2013 , Page(s): iii - iv
    Save to Project icon | Request Permissions | PDF file iconPDF (95 KB) |  | HTML iconHTML  
    Freely Available from IEEE
  • Safety cases: A review of challenges

    Publication Year: 2013 , Page(s): 1 - 6
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (125 KB) |  | HTML iconHTML  

    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 followed by a review of challenges for the assessment of safety cases by regulators. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Measuring assurance case confidence using Baconian probabilities

    Publication Year: 2013 , Page(s): 7 - 11
    Cited by:  Papers (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (213 KB) |  | HTML iconHTML  

    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. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An evaluation of argument patterns to reduce pitfalls of applying assurance case

    Publication Year: 2013 , Page(s): 12 - 17
    Cited by:  Papers (2)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (470 KB) |  | HTML iconHTML  

    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 assurance cases by reusing those patterns. It is also shown an evaluation result of assurance case pattern application to develop an assurance case for a LAN device management system. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Nuanced term-matching to assist in compositional safety assurance

    Publication Year: 2013 , Page(s): 18 - 23
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (369 KB) |  | HTML iconHTML  

    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 used to describe and share assurance data. Linguistic mismatches highlight various problems for the composition of peer modules and their integration into an overall case. In this paper, we propose the application of a linguistic model of understanding to identify mismatches and to provide guidance on composition and integration. The approach is illustrated using a simple example. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An implementation of GSN community standard

    Publication Year: 2013 , Page(s): 24 - 28
    Cited by:  Papers (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1039 KB) |  | HTML iconHTML  

    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 for module and patterns have been defined in GSN Community Standard. In this paper we report our preliminary implementation partly satisfying the standard. The prototype implementation has been done on D-Case Editor, an Eclipse based GSN editor. Among syntax defined in the standard, we have implemented “away goal” and “module node” as the basis for the module system, together with parameters with scope and pattern instantiation function which are extensions of our previous works. Due to some ambiguity in the GSN community standard, several design choices may exist. In this paper we report our design choices. We also report further a few issues for implementing the full syntax of the GSN community standard. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Architecting and generalizing a safety case for critical condition detection software an experience report

    Publication Year: 2013 , Page(s): 29 - 33
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (396 KB) |  | HTML iconHTML  

    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) system. This paper relates our experience applying the safety case concept to AFDNR, particularly from the perspective of generalizing the safety issues to similar fault management systems. We also provide lessons learned, including a discussion of issues that led to our current refactoring of our initial safety case. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Creating safety assurance cases for rebreather systems

    Publication Year: 2013 , Page(s): 34 - 39
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (376 KB) |  | HTML iconHTML  

    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 presents our experience in the process of developing a safety assurance case for a rebreather sub-system, thus providing guidance on this process to other rebreather manufacturers. We used the Goal Structuring Notation (GSN) to develop a safety argument that compelled us to re-evaluate our safety goals, and that provided a basis for productive discussion between embedded systems engineers, systems safety consultants, and reviewers. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Constructing safety assurance cases for medical devices

    Publication Year: 2013 , Page(s): 40 - 45
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (132 KB) |  | HTML iconHTML  

    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 authority like the Food and Drug Administration. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.