Abstract:
The concept of integrity levels with corresponding integrity level requirements that are required to be met in order to show the achievement of the integrity level are sp...Show MoreMetadata
Abstract:
The concept of integrity levels with corresponding integrity level requirements that are required to be met in order to show the achievement of the integrity level are specified in this adoption of ISO/IEC 15026-3:2011. It places requirements on and recommends methods for defining and using integrity levels and their integrity level requirements, including the assignment of integrity levels to systems, software products, their elements, and relevant external dependences. This standard is applicable to systems and software and is intended for use by the following: Definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies; Users of integrity levels such as developers and maintainers, suppliers and acquirers, users, and assessors of systems or software and for the administrative and technical support of systems and/or software products. One important use of integrity levels is by suppliers and acquirers in agreements; for example, to aid in assuring safety, economic, or security characteristics of a delivered system or product. This standard does not prescribe a specific set of integrity levels or their integrity level requirements. In addition, it does not prescribe the way in which integrity level use is integrated with the overall system or software engineering life cycle processes. This standard can be used alone or with other parts of ISO/IEC 15026. It can be used with a variety of technical and specialized risk analysis and development approaches. ISO/IEC TR 15026-1 provides additional information and references to aid users of IEEE Std 15026-3.
Date of Publication: 12 July 2013
Electronic ISBN:978-0-7381-8436-4
ICS Code: 35.080 - Software
Persistent Link: https://ieeexplore.ieee.org/servlet/opac?punumber=6557403
References is not available for this document.
Select All
1.
IEC 300-3-9, Risk Analysis of Technological Systems
2.
IEC 60300, Dependability management [multiple parts]
3.
IEC 60812:2006, Analysis techniques for system reliability — Procedure for failure mode and effects analysis (FMEA)
4.
IEG 61508, Functional safety of electrical/electronic/programmable electronic safety-related systems [multiple parts]
5.
IEC 61511:2003, Functional safety — Safety instrumented systems for the process industry sector [Three parts]
6.
IEG 61882, Hazard and operability studies (HAZOP studies) — Application guide
7.
IEEE Std 1012-2004, IEEE Standard for Software Verification and Validation
8.
ISO 13849 (all parts), Safety of machinery — Safety-related parts of control systems
9.
ISO 14620 (all parts), Space systems — Safety requirements
10.
ISO/IEC 12207:2008, Systems and software engineering — Software life cycle processes
11.
ISO/IEC 15289:2006, Systems and software engineering — Content of systems and software life cycle process information products (Documentation)
12.
ISO/IEC 15288:2008, Systems and software engineering — System life cycle processes
13.
ISO/IEC 15504 (all parts), Information technology — Process assessment
14.
ISO/IEC 16085:2006, Systems and software engineering — Life cycle processes — Risk management
15.
ISO/TR 18152:2010, Ergonomics of human-system interaction — Specification for the process assessment of human-system issues
16.
ISO 19706:2007, Guidelines for assessing the fire threat to people
17.
ISO/IEC 19770 (all parts), Information technology — Software asset management
18.
ISO/IEC 21827, Information technology — Systems Security Engineering — Capability Maturity Model (SSE-CMIVI®)
19.
ISO/IEC 25010:2011, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — System and software quality models
20.
ISO/TS 25238:2007, Health informatics — Classification of safety risks from health software
21.
ISO/IEC 27005, Information technology — Security techniques — Information security risk management
22.
ISO/IEG 42010:2007, Systems and software engineering — Recommended practice for architectural description of software-intensive systems
