Dependability Cases

Many large software systems display fragility or a lack of dependability caused by inattention to details at various stages of development (e.g., missing data, undocumented assumptions, lack of testing), resulting in a failure to catch errors. This technical note explains how to create a dependability case for a system that helps identify and keep track of such details. A dependability case is defined here as a structured argument providing evidence that a system meets its specified dependability requirements. The technical note describes how to structure the argument and present evidence to support it. A sample problem is presented, as well as issues raised by that problem and future goals.

View Complete Report

Authors

Charles B. Weinstock

John B. Goodenough

John J. Hudak

This report is related to the following area(s) of work:

Performance and Dependability

Technical Note
CMU/SEI-2004-TN-016
May 2004

For more information

Contact Us

info@sei.cmu.edu

412-268-5800