BS ISO/IEC 15026-2:2011
Superseded
A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.
View Superseded by
Systems and software engineering. Systems and software assurance Assurance case
11-15-2022
03-31-2011
Foreword
Introduction
1 Scope
2 Conformance
3 Normative references
4 Terms and definitions
5 Use of this part of ISO/IEC 15026
6 Structure and contents of an assurance case
7 Required outcomes of using Part 2 assurance case
Bibliography
Describes minimum requirements for the structure and contents of an assurance case. 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.
Committee |
IST/15
|
DevelopmentNote |
Supersedes 10/30215541 DC. (03/2011) Together with BS PD ISO/IEC TR 15026-1, BS ISO/IEC 15026-3 and BS ISO/IEC 15026-4, it supersedes BS ISO/IEC 15026. (05/2013)
|
DocumentType |
Standard
|
PublisherName |
British Standards Institution
|
Status |
Superseded
|
SupersededBy | |
Supersedes |
This part of ISO/IEC15026 specifies minimum requirements for the structure and contents of an assurance case. 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.
This part of ISO/IEC15026 does not place requirements on the quality of the contents of an assurance case. Rather, it places requirements on the existence of the contents and structure of an assurance case. While several notations and slightly varying terminologies are currently used in practice, this part of ISO/IEC15026 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.
Standards | Relationship |
ISO/IEC 15026-2:2011 | Identical |
ISO/IEC 26702:2007 | Systems engineering — Application and management of the systems engineering process |
ISO/IEC 25020:2007 | Software engineering Software product Quality Requirements and Evaluation (SQuaRE) Measurement reference model and guide |
ISO/IEC 25010:2011 | Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — System and software quality models |
CAA CAP 760 : 2006 AMD 1 2010 | GUIDANCE ON THE CONDUCT OF HAZARD IDENTIFICATION, RISK ASSESSMENT AND THE PRODUCTION OF SAFETY CASES: FOR AERODROME OPERATORS AND AIR TRAFFIC SERVICE PROVIDERS |
DEFSTAN 00-56(PT2)/4(2007) : 2007 | SAFETY MANAGEMENT REQUIREMENTS FOR DEFENCE SYSTEMS - PART 2: GUIDANCE ON ESTABLISHING A MEANS OF COMPLYING WITH PART 1 |
ISO/IEC 25051:2014 | Software engineering Systems and software Quality Requirements and Evaluation (SQuaRE) Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing |
ISO/IEC 15289:2006 | Systems and software engineering Content of systems and software life cycle process information products (Documentation) |
ISO/TR 18529:2000 | Ergonomics Ergonomics of human-system interaction Human-centred lifecycle process descriptions |
ISO/IEC 25040:2011 | Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Evaluation process |
ISO/IEC TR 15026-1:2010 | Systems and software engineering Systems and software assurance Part 1: Concepts and vocabulary |
ISO/IEC 25012:2008 | Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Data quality model |
ISO/IEC 21827:2008 | Information technology Security techniques Systems Security Engineering Capability Maturity Model (SSE-CMM) |
ISO/IEC 15288:2008 | Systems and software engineering — System life cycle processes |
ISO/IEC 16085:2006 | Systems and software engineering — Life cycle processes — Risk management |
ISO/IEC 27005:2011 | Information technology Security techniques Information security risk management |
ISO/IEC 12207:2008 | Systems and software engineering — Software life cycle processes |
DEFSTAN 00-55(PT2)/2(1997) : 1997 ERRATUM 1997 | REQUIREMENTS FOR SAFETY RELATED SOFTWARE IN DEFENCE EQUIPMENT - PART 2: GUIDANCE |
DEFSTAN 00-55(PT1)/2(1997) : 1997 | REQUIREMENTS FOR SAFETY RELATED SOFTWARE IN DEFENCE EQUIPMENT - PART 1: REQUIREMENTS |
ISO/IEC 25030:2007 | Software engineering Software product Quality Requirements and Evaluation (SQuaRE) Quality requirements |
DEFSTAN 00-56(PT1)/4(2007) : 2007 | SAFETY MANAGEMENT REQUIREMENTS FOR DEFENCE SYSTEMS - PART 1: REQUIREMENTS |
DEFSTAN 00-42(PT3)/3(2008) : 2008 | RELIABILITY AND MAINTAINABILITY (R&M) ASSURANCE GUIDE - PART 3: R&M CASE |
CAA CAP 670 : 2013 + A1 2014 | ATS SAFETY REQUIREMENTS |
Access your standards online with a subscription
Features
-
Simple online access to standards, technical information and regulations.
-
Critical updates of standards and customisable alerts and notifications.
-
Multi-user online standards collection: secure, flexible and cost effective.