ISO/IEC 15026-2:2011 is adopted by this standard. 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.
- Sponsor Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
Learn More About C/S2ESC - Software & Systems Engineering Standards Committee - Status
- Inactive-Reserved Standard
- PAR Approval
- 2011-06-16
- Superseded by
- 15026-2-2022
- Board Approval
- 2011-09-10
- History
-
- ANSI Approved:
- 2013-01-24
- Published:
- 2011-10-11
- Inactivated Date:
- 2022-03-24
Working Group Details
- Society
- IEEE Computer Society
Learn More About IEEE Computer Society - Sponsor Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
Learn More About C/S2ESC - Software & Systems Engineering Standards Committee - Working Group
-
WG_LCP - Working Group for Life Cycle Processes
- IEEE Program Manager
- Patricia Roder
Contact Patricia Roder - Working Group Chair
- Teresa Doran
Other Activities From This Working Group
Current projects that have been authorized by the IEEE SA Standards Board to develop a standard.
P12207
Systems and software engineering -- Software life cycle processes
This document establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. Software includes the software portion of firmware. This document includes those aspects of system definition needed to provide the context for software systems and services. This document also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project.
P24748-4
Systems and Software Engineering -- Life Cycle Management -- Part 4: Systems Engineering Management Planning
This part of ISO/IEC/IEEE 24748 n - specifies the processes from ISO/IEC/IEEE 15288 that implement systems engineering management for the life cycles of technical solutions, n - describes a required information item, termed the Systems Engineering Management Plan (SEMP) for the technical management and execution of the systems engineering of technical solutions, n - provides requirements and guidance for the content of the required information item.
Standards approved by the IEEE SA Standards Board that are within the 10-year lifecycle.
No Active Standards
These standards have been replaced with a revised version of the standard, or by a compilation of the original active standard and all its existing amendments, corrigenda, and errata.
No Superseded Standards
These standards have been removed from active status through a ballot where the standard is made inactive as a consensus decision of a balloting group.
No Inactive-Withdrawn Standards
These standards are removed from active status through an administrative process for standards that have not undergone a revision process within 10 years.
No Inactive-Reserved Standards