Welcome to the InfoSci Platform
A New Method for Writing Assurance Cases

A New Method for Writing Assurance Cases

Yutaka Matsuno, Shuichiro Yamamoto
Copyright: © 2015 |Pages: 19
ISBN13: 9781466684737|ISBN10: 1466684739|EISBN13: 9781466684744
DOI: 10.4018/978-1-4666-8473-7.ch077
Cite Chapter Cite Chapter

MLA

Matsuno, Yutaka, and Shuichiro Yamamoto. "A New Method for Writing Assurance Cases." Transportation Systems and Engineering: Concepts, Methodologies, Tools, and Applications, edited by Information Resources Management Association, IGI Global, 2015, pp. 1614-1632. https://doi.org/10.4018/978-1-4666-8473-7.ch077

APA

Matsuno, Y. & Yamamoto, S. (2015). A New Method for Writing Assurance Cases. In I. Management Association (Ed.), Transportation Systems and Engineering: Concepts, Methodologies, Tools, and Applications (pp. 1614-1632). IGI Global. https://doi.org/10.4018/978-1-4666-8473-7.ch077

Chicago

Matsuno, Yutaka, and Shuichiro Yamamoto. "A New Method for Writing Assurance Cases." In Transportation Systems and Engineering: Concepts, Methodologies, Tools, and Applications, edited by Information Resources Management Association, 1614-1632. Hershey, PA: IGI Global, 2015. https://doi.org/10.4018/978-1-4666-8473-7.ch077

Export Reference

Mendeley
Favorite

Abstract

In this paper, the authors present a new method for writing assurance cases. Assurance cases are documented bodies of evidence that provide a convincing and valid argument that a system is adequately dependable for a given application in a given environment. Assurance cases have been used mostly in the safety field, but are now beginning to be widely applied in other areas. Cyber security is one such area, and recently, assuring security of cyber systems has become crucial. Several methods and various guidelines for writing assurance cases have been used. Unfortunately, only experts are currently able to write assurance cases, and it is still difficult for ordinary engineers to write them. This paper presents a new method for writing assurance cases. The main ideas are that (1) documents generated and used during the system lifecycle must be either used by the assurance cases or must be referred to in the assurance cases, and (2) typical patterns exist for assurance cases, and these patterns have not yet been well discussed. This paper presents the preliminary steps in developing a method for writing assurance cases. The authors also report on a preliminary experiment carried out on a web server demo system.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.