Continuously revised assurance cases with stakeholders' cross-validation: A DEOS experience

1Citations
Citations of this article
9Readers
Mendeley users who have this article in their library.

Abstract

Recently, assurance cases have received much attention in the field of software-based computer systems and IT services. However, software changes very often, and there are no strong regulations for software. These facts are two main challenges to be addressed in the development of software assurance cases. We propose a method of developing assurance cases by means of continuous revision at every stage of the system life cycle, including in operation and service recovery in failure cases. Instead of a regulator, dependability arguments are validated by multiple stakeholders competing with each other. This paper reported our experience with the proposed method in the case of Aspen education service. The case study demonstrates that continuous revisions enable stakeholders to share dependability problems across software life cycle stages, which will lead to the long-term improvement of service dependability.

Cite

CITATION STYLE

APA

Kuramitsu, K. (2016). Continuously revised assurance cases with stakeholders’ cross-validation: A DEOS experience. PeerJ Computer Science, 2016(12). https://doi.org/10.7717/peerj-cs.101

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free