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.
- Standard Committee
- 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
- Standard Committee
- 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.
P15026-1
ISO/IEC/IEEE International Standard for Systems and software engineering--Systems and software assurance --Part 1:Concepts and vocabulary
This document defines assurance-related terms and establishes an organized set of concepts and their relationships, thereby establishing a basis for shared understanding of the concepts and principles central to all parts of ISO/IEC/IEEE 15026 across its user communities. It provides information to users of the subsequent parts of ISO/IEC/IEEE 15026, including the use of each part and the combined use of multiple parts. Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in the ISO/IEC/IEEE 15026 series.
P24748-10
ISO/IEC/IEEE Systems and software engineering-- Life cycle management--Part 10: Guidelines for systems engineering agility
This part of ISO/IEC/IEEE 24748 specifies strategic aspects supporting systems engineering agility, and provides guidelines for their selection and application. Strategic aspects included in this document are: adaptable modular architecture, iterative and incremental development, situational awareness and decision-making, common mission teaming, shared knowledge management, continual integration and test, and agile operations.
P24748-4
ISO/IEC/IEEE Draft International Standard - Systems and Software Engineering -- Life Cycle Management -- Part 4: Systems Engineering Management Planning
ISO/IEC/IEEE 15288, Systems and software engineering -- System life cycle processes, provides a common process framework covering the life cycle of human-made systems, from the conception of ideas through to the retirement of a system. It provides the processes for acquiring and supplying systems. In addition, this framework provides for the assessment and improvement of the life cycle processes. This common framework improves communication and cooperation among the parties that create, utilize, and manage modern systems in order that they can work in an integrated, coherent fashion. The acquisition or supply of a system is usually done within a project. A project prepares and implements the technical planning, resources and schedules necessary to guide the project toward accomplishment of its objectives and proper conclusion. The project's authorization and objectives are documented in an information item identified as a Systems Engineering Management Plan (SEMP). This document defines a SEMP as the key vehicle for representing a project's application of systems life cycle processes. In this document, the terms technical planning and systems engineering planning are used interchangeably to emphasize or differentiate technical contributions in the processes under discussion.
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