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
Keywords assist with retrieval of results and provide a means to discovering other relevant content. Learn more.
- IEEE Keywords
- Index Terms
- Software Engineering ,
- Software Assurance ,
- Levels Of Use ,
- Risk Analysis ,
- Levels Of Achievement ,
- Design Level ,
- Software Product ,
- Life Cycle Processes ,
- System Life Cycle ,
- Adverse Events ,
- Systemic Conditions ,
- Risk Evaluation ,
- Property Values ,
- System Architecture ,
- Product Design ,
- Elements Of System ,
- Scope Of Application ,
- Time Behavior ,
- Dangerous Effects ,
- Risk Criteria ,
- Dangerous Conditions ,
- External Elements ,
- Definition Of Levels ,
- Authorization For Use ,
- Authority Approval ,
- Dangerous Behaviors ,
- Internal Elements ,
- External Interface ,
- Product Architecture
- Author Keywords
Keywords assist with retrieval of results and provide a means to discovering other relevant content. Learn more.
- IEEE Keywords
- Index Terms
- Software Engineering ,
- Software Assurance ,
- Levels Of Use ,
- Risk Analysis ,
- Levels Of Achievement ,
- Design Level ,
- Software Product ,
- Life Cycle Processes ,
- System Life Cycle ,
- Adverse Events ,
- Systemic Conditions ,
- Risk Evaluation ,
- Property Values ,
- System Architecture ,
- Product Design ,
- Elements Of System ,
- Scope Of Application ,
- Time Behavior ,
- Dangerous Effects ,
- Risk Criteria ,
- Dangerous Conditions ,
- External Elements ,
- Definition Of Levels ,
- Authorization For Use ,
- Authority Approval ,
- Dangerous Behaviors ,
- Internal Elements ,
- External Interface ,
- Product Architecture
- Author Keywords