Systems and software engineering — Systems and software assurance — Part 2: Assurance case
Introduction: The purpose of this document is to define assurance case structure terminology, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases. This document does not place requirements on the quality of the contents but describes the structure and meaning of assurance cases with the necessary level of precision and detail so as to avoid inconsistent and subjective use of the terms. Existing standards addressing different application areas and topics related to assurance cases possibly uses differing terminology and concepts when addressing common themes. This document is based on experience drawn from these specialized standards and guidelines. While several notations and slightly varying terminologies are currently used in practice, this document does not require the use of any particular concrete representation including graphical representation. Likewise, it places no requirements on physical implementation of the data; in particular, it includes no requirements for redundancy or co-location. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security. They are applicable to any property of a system. These assurance cases are often called by more specific names, e.g. safety case or dependability case. ISO/IEC/IEEE 15026-1 provides concepts, terminology, backgr
Scope: This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.