Abstract We provide an operational scenario-based assurance method for assuring the safety of a software product. Software safety is usually demonstrated by assessing the software development process in what is called a process-based approach. Because the process-based approach indirectly explains safety of software product, it cannot explicate safety boundary: Software product is safe or unsafe in what context of use. In this paper, we focus on operational scenario and unusual events which can occur in the scenario. The proposed method provides an operational scenario-based safety case which explains tolerable and not-tolerable abnormal scenarios including unusual events as the boundary. The method promotes domain experts identifying unusual events from a normal scenario. Furthermore, it constructs scenario-based safety case by using Event Sequence Diagram. To evaluate the method, we applied it to a ground system for artificial satellite, and engine control system of the rocket system. As a result, we conclude that the method can construct a valid operational scenario-based safety case.
[1]
John A. McDermid,et al.
Safety Case Construction and Reuse Using Patterns
,
1997,
SAFECOMP.
[2]
Yasushi Ueda,et al.
IV&V Case: Empirical Study of Software Independent Verification and Validation Based on Safety Case
,
2017,
2017 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW).
[3]
Philip Koopman.
Software Quality, Dependability and Safety in Embedded Systems
,
2014
.
[4]
T. S. E. Maibaum,et al.
Safety cases: A review of challenges
,
2013,
2013 1st International Workshop on Assurance Cases for Software-Intensive Systems (ASSURE).
[5]
T. S. E. Maibaum,et al.
On Software Certification: We Need Product-Focused Approaches
,
2008,
Monterey Workshop.
[6]
T. S. E. Maibaum,et al.
A Product-Focused Approach to Software Certification
,
2008,
Computer.
[7]
John A. McDermid,et al.
Assurance cases and prescriptive software safety certification: A comparative study
,
2013
.