id	author	title	date	pages	extension	mime	words	sentences	flesch	summary	cache	txt
work_en2rpj3s6rhivnhyoexbnb5mbq	Kimio Kuramitsu	Continuously revised assurance cases with stakeholders' cross-validation: a DEOS experience	2016	17	.pdf	application/pdf	6069	686	53	stakeholders to share dependability problems across software life cycle stages, which Keywords Assurance cases, GSN, DEOS process, Experience report, Service dependability How to cite this article Kuramitsu (2016), Continuously revised assurance cases with stakeholders' cross-validation: a DEOS experience. assurance cases written in Goal-Structuring Notation (GSN) (Kelly & Weaver, 2004), a How assurance cases to be developed for improved software without regulators This section describes our ideas on how to use assurance cases in software-based IT systems Our aim in the use of assurance cases is to share dependability arguments among The Aspen project includes not only the development of assurance cases across different organizations but also Aspen's software development and service operation with DEOS The developer started the argument with the claim ''Aspen is dependable'' and decomposed failures imply faulty arguments, the operator or the developer needs to revise the assurance Is the development of assurance cases useful in software?	./cache/work_en2rpj3s6rhivnhyoexbnb5mbq.pdf	./txt/work_en2rpj3s6rhivnhyoexbnb5mbq.txt