2015/07/31 by Kimio Kuramitsu, Kuramitsu, Kimio
Computer Science · Decision Sciences · Engineering · #Business #Computer science #Computer security #Dependability #Engineering #Engineering management #Environmental resource management #Environmental science #FOS: Computer and information sciences #Marketing #Operations management #Process management #Risk and Safety Analysis #Safety Systems Engineering in Autonomy #Service (business) #Software Engineering (cs.SE) #Software Reliability and Analysis Research #Software engineering #cs.SE
paper · pdf · doi:10.48550/arxiv.1507.08888
Submitted to Journal of Information Processing
arxiv created 2015/07/31 · openalex publication_date 2015/07/31 · arxiv updated 2015/08/03 · openalex created_date 2016/06/24 · openalex updated_date 2026/07/28
Recently, assurance cases have received much attentions in the field of software-based computer systems and IT services. However, software very often changes and there are no strong regulations for software. These facts are main two challenges to be addressed in software assurance cases. We propose a development method of assurance cases by means of continuous revision at every stage of the system lifecycle, including in-operation and service recovery in failure cases. The quality of dependability arguments are improved by multiple stakeholders who check with each other. This paper reported our experience of the proposed method in a case of the ASPEN education service. The case study demonstrate that the continuos updates create a significant amount of active risk communications between stakeholders. This gives us a promising perspective for the long-term improvement of service dependability with the lifecycle assurance cases.