系统与软件工程.系统与软件保证.第2部分:保证实例

[中文适用范围]： ISO/IEC 15026 的这一部分规定了保证案例的结构和内容的最低要求。 保证案例包括对系统或产品（或一组声明）的属性的顶级声明、关于该声明的系统论证以及该论证背后的证据和明确假设。 这种结构化论证通过多个层次的从属主张进行论证，将顶层主张与证据和假设联系起来。 ISO/IEC 15026 的这一部分并未对保证案例内容的质量提出要求。 相反，它对保证案例的内容和结构的存在提出了要求。 虽然目前在实践中使用了多种符号和略有不同的术语，但 ISO/IEC 15026 的这一部分并不要求使用特定的术语或图形表示。 同样，它对数据的物理实现方式没有要求，包括对冗余或共置的要求。 [外文原描述]： ISO/IEC 15026-2:2011 specifies minimum requirements for the structure and contents of an assurance case to improve the consistency and comparability of assurance cases and to facilitate stakeholder communications, engineering decisions, and other uses of assurance cases. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R&M) case. ISO/IEC 15026-2:2011 does not place requirements on the quality of the contents of an assurance case and does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.