AS/NZS 15026:1999
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
Information technology - System and software integrity levels
Hardcopy , PDF 1 User , PDF 3 Users , PDF 5 Users , PDF 9 Users
24-06-2021
English
05-05-1999
Specifies requirements for the determination of system and software integrity levels for software products and systems that use software. The Standard also defines the concepts associated with integrity levels, defines the processes for determining integrity levels and software integrity requirements, and places requirements on each process. This Standard is identical with and has been reproduced from ISO/IEC 15026:1998
Committee |
IT-015
|
DocumentType |
Standard
|
ISBN |
0 7337 2660 7
|
Pages |
12
|
PublisherName |
Standards Australia
|
Status |
Superseded
|
SupersededBy | |
Supersedes | |
UnderRevision |
This International Standard introduces the concepts of software integrity levels and software integrity requirements. It defines the concepts associated with integrity levels, defines the processes for determining integrity levels and software integrity requirements, and places requirements on each process. This International Standard does not prescribe a specific set of integrity levels or software integrity requirements. These must be established either on a project by project basis, or for a specific sector and/or country. This International Standard is applicable to software only. The system integrity level and the integrity levels of the non-software components are only required in this International Standard to determine the integrity levels of the software components.This International Standard is intended for use by developers, users, procurers, and assessors of software products or systems containing software for the administrative and technical support of those products and systems.A software integrity level denotes a range of values of a software property necessary to maintain system risks within tolerable limits. For software that performs a mitigating function, the property is the reliability with which the software must perform the mitigating function. For software whose failure can lead to a system threat, the property is the limit on the frequency or probability of that failure.Software integrity requirements are requirements that must be met by the software engineering process used to develop the software, requirements that must be met by the software engineering products, and/or requirements that must be true of the software's performance over time in order to provide a degree of confidence in the software that is commensurate with the software's integrity level.This International Standard does not prescribe the way in which integrity level determination is integrated with the overall system engineering life cycle processes.
Standards | Relationship |
ISO/IEC 15026:1998 | Identical |
First published as AS/NZS 15026:1999.
AS 1189.1-1991 | Data processing - Vocabulary - Fundamental terms |
AS 1189.20-1991 | Data processing - Vocabulary System development |
AS/NZS ISO 8402:1994 | Quality management and quality assurance - Vocabulary |
AS/NZS ISO/IEC 12207:1997 | Information technology - Software life cycle processes |
AS IEC 60300.2-2005 | Dependability management - Guidance for dependability programme management |
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.