CSA ISO/IEC TR 15026-1 : 2013
Withdrawn
A Withdrawn Standard is one, which is removed from sale, and its unique number can no longer be used. The Standard can be withdrawn and not replaced, or it can be withdrawn and replaced by a Standard with a different number.
SYSTEMS AND SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE ASSURANCE - PART 1: CONCEPTS AND VOCABULARY
Hardcopy , PDF
28-07-2021
English
01-01-2013
Foreword
Introduction
1 Scope
2 Terms and definitions
3 Document purpose and audience
4 Organization of report
5 Basic concepts
6 How to use multiple parts of ISO/IEC 15026
7 Assurance Case
8 ISO/IEC 15026 and integrity levels
9 ISO/IEC 15026 and life cycle processes: 15288/12207
10 Summary
Annex A (informative) - Frequently asked questions
Annex B (informative) - Difficulties with terms and concepts
Annex C (informative) - ISO/IEC 15026 relationships to
standards
Annex D (informative) - Phenomena
Annex E (informative) - Security
Annex F (informative) - Selected Related Standards
Bibliography
Specifies terms and establishes an extensive and organized set of concepts and their relationships, thereby establishing a basis for shared understanding of the concepts and principles central to ISO/IEC 15026 across its user communities.
DocumentType |
Standard
|
Pages |
114
|
PublisherName |
Canadian Standards Association
|
Status |
Withdrawn
|
Standards | Relationship |
ISO/IEC TR 15026-1:2010 | Identical |
IEC 61025:2006 | Fault tree analysis (FTA) |
ISO/IEC 26702:2007 | Systems engineering — Application and management of the systems engineering process |
ISO 9241-400:2007 | Ergonomics of humansystem interaction Part 400: Principles and requirements for physical input devices |
ISO/IEC/IEEE 16326:2009 | Systems and software engineering Life cycle processes Project management |
ISO/IEC TR 24748-1:2010 | Systems and software engineering Life cycle management Part 1: Guide for life cycle management |
ISO 14625:2007 | Space systems — Ground support equipment for use at launch, landing or retrieval sites — General requirements |
ISO/TR 27809:2007 | Health informatics Measures for ensuring patient safety of health software |
ISO/IEC 27001:2013 | Information technology — Security techniques — Information security management systems — Requirements |
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 |
IEC 60812:2006 | Analysis techniques for system reliability - Procedure for failure mode and effects analysis (FMEA) |
ISO/IEC 27004:2016 | Information technology — Security techniques — Information security management — Monitoring, measurement, analysis and evaluation |
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 27006:2015 | Information technology — Security techniques — Requirements for bodies providing audit and certification of information security management systems |
ISO 2394:2015 | General principles on reliability for structures |
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/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 25000:2014 | Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Guide to SQuaRE |
IEC 61078:2016 | Reliability block diagrams |
ISO/IEC 27002:2013 | Information technology Security techniques Code of practice for information security controls |
ISO 28003:2007 | Security management systems for the supply chain Requirements for bodies providing audit and certification of supply chain security management systems |
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 |
DEFSTAN 00-42(PT3)/4(2011) : 2011 | RELIABILITY AND MAINTAINABILITY ASSURANCE GUIDE - PART 3: R&M CASE |
IEC 60300-3-2:2004 | Dependability management - Part 3-2: Application guide - Collection of dependability data from the field |
ISO/IEC 27011:2016 | Information technology — Security techniques — Code of practice for Information security controls based on ISO/IEC 27002 for telecommunications organizations |
ISO/IEC TR 19791:2010 | Information technology Security techniques Security assessment of operational systems |
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 |
ISO 12100-2:2003 | Safety of machinery Basic concepts, general principles for design Part 2: Technical principles |
ISO/IEC TR 15446:2017 | Information technology Security techniques Guidance for the production of protection profiles and security targets |
ISO/TR 17944:2002 | Banking Security and other financial services Framework for security in financial systems |
ISO 12100-1:2003 | Safety of machinery Basic concepts, general principles for design Part 1: Basic terminology, methodology |
DEFSTAN 00-55(PT2)/2(1997) : 1997 ERRATUM 1997 | REQUIREMENTS FOR SAFETY RELATED SOFTWARE IN DEFENCE EQUIPMENT - PART 2: GUIDANCE |
ISO/IEC 2382-14:1997 | Information technology Vocabulary Part 14: Reliability, maintainability and availability |
ISO 19706:2011 | Guidelines for assessing the fire threat to people |
DEFSTAN 00-55(PT1)/2(1997) : 1997 | REQUIREMENTS FOR SAFETY RELATED SOFTWARE IN DEFENCE EQUIPMENT - PART 1: REQUIREMENTS |
IEC 60300-3-15:2009 | Dependability management - Part 3-15: Application guide - Engineering of system dependability |
IEC 60300:1984 | Reliability and maintainability management |
ISO/IEC 90003:2014 | Software engineering Guidelines for the application of ISO 9001:2008 to computer software |
IEC 61508-7:2010 | Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 7: Overview of techniques and measures (see Functional Safety and IEC 61508) |
ISO/IEC 27000:2016 | Information technology Security techniques Information security management systems Overview and vocabulary |
SAE JA 1000 : 2012 | RELIABILITY PROGRAM STANDARD |
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 |
ISO/TS 25238:2007 | Health informatics Classification of safety risks from health software |
ISO/IEC 42010:2007 | Systems and software engineering Recommended practice for architectural description of software-intensive systems |
ISO/TR 16982:2002 | Ergonomics of human-system interaction Usability methods supporting human-centred design |
ISO/IEC 15939:2007 | Systems and software engineering Measurement process |
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.