ISO/IEC TR 15026-1:2010
Withdrawn
Withdrawn
View Superseded by
Systems and software engineering — Systems and software assurance — Part 1: Concepts and vocabulary
Amended by
Available format(s)
Hardcopy , PDF
Published date
07-30-2010
Withdrawn date
03-26-2019
Superseded by
US$96.00
Excluding Tax where applicable
ISO/IEC TR 15026-1:2010 defines 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. It provides information to users of the subsequent parts of ISO/IEC 15026, including the use of each part and the combined use of multiple parts.
Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in ISO/IEC 15026.
| Committee |
ISO/IEC JTC 1/SC 7
|
| DocumentType |
Standard
|
| Pages |
95
|
| PublisherName |
International Organization for Standardization
|
| Status |
Withdrawn
|
| SupersededBy |
| Standards | Relationship |
| SA/SNZ TR 15026.1:2013 | Identical |
| PD ISO/IEC/TR 15026-1:2010 | Identical |
| NEN NPR ISO/IEC TR 15026-1 : 2010 C1 2012 | Identical |
| PD ISO/IEC TR 19759:2016 | Software Engineering. Guide to the software engineering body of knowledge (SWEBOK) |
| 12/30248997 DC : 0 | BS ISO/IEC 15026-4 - SYSTEMS AND SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE ASSURANCE - PART 4: ASSURANCE IN THE LIFE CYCLE |
| ISO/IEC TR 29110-2-2:2016 | Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 2-2: Guide for the development of domain-specific profiles |
| BS ISO/IEC 15026-4:2012 | Systems and software engineering. Systems and software assurance Assurance in the life cycle |
| PD ISO/IEC TR 15443-1:2012 | Information technology. Security techniques. Security assurance framework Introduction and concepts |
| AAMI TIR38 : 2015 | MEDICAL DEVICE SAFETY ASSURANCE CASE REPORT GUIDANCE |
| IEEE 15026-3-2013 | IEEE Standard Adoption of ISO/IEC 15026-3 -- Systems and Software Engineering -- Systems and Software Assurance -- Part 3: System Integrity Levels |
| ISO/IEC 15026-2:2011 | Systems and software engineering — Systems and software assurance — Part 2: Assurance case |
| 14/30289476 DC : 0 | BS ISO/IEC 15026-3 - SYSTEMS AND SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE ASSURANCE - PART 3: SYSTEM INTEGRITY LEVELS |
| ISO/IEC TR 15443-1:2012 | Information technology — Security techniques — Security assurance framework — Part 1: Introduction and concepts |
| ISO/IEC 15026-4:2012 | Systems and software engineering — Systems and software assurance — Part 4: Assurance in the life cycle |
| 10/30230297 DC : 0 | BS ISO/IEC 15026-3 - SYSTEMS AND SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE ASSURANCE - PART 3: SYSTEM INTEGRITY LEVELS |
| BS ISO/IEC 15026-2:2011 | Systems and software engineering. Systems and software assurance Assurance case |
| 10/30215541 DC : 0 | BS ISO/IEC 15026-2 - SYSTEMS AND SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE ASSURANCE - PART 2: ASSURANCE CASE |
| IEEE 15026-4-2013 | IEEE Standard Adoption of ISO/IEC 15026-4--Systems and Software Engineering--Systems and Software Assurance--Part 4: Assurance in the Life Cycle |
| IEEE 15026-2-2011 | IEEE Standard--Adoption of ISO/IEC 15026-2:2011 Systems and Software Engineering--Systems and Software Assurance--Part 2: Assurance Case |
| IEEE 1012-2012 | IEEE Standard for System and Software Verification and Validation |
| ISO/IEC TR 19759:2015 | Software Engineering — Guide to the software engineering body of knowledge (SWEBOK) |
| 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 human—system interaction — Part 400: Principles and requirements for physical input devices |
| DEFSTAN 00-42(PT3)/2(2003) : 2003 | RELIABILITY AND MAINTAINABILITY (R&M) ASSURANCE GUIDANCE - PART 3: R&M CASE |
| 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 |
| 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 |
| 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 |
| 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®) |
| DEFSTAN 00-56(PT2)/3(2004) : INTERIM | SAFETY MANAGEMENT REQUIREMENTS FOR DEFENCE SYSTEMS - PART 2: GUIDANCE ON ESTABLISHING A MEANS OF COMPLYING WITH PART 1 |
| ISO/IEC 15288:2008 | Systems and software engineering — System life cycle processes |
| 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 |
| DEFSTAN 00-56(PT1)/3(2004) : INTERIM | SAFETY MANAGEMENT REQUIREMENTS FOR DEFENCE SYSTEMS - PART 1: REQUIREMENTS |
| 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 |
| ISO/IEC 25030:2007 | Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Quality requirements |
| ISO/TS 25238:2007 | Health informatics — Classification of safety risks from health software |
| CAA CAP 670 : 2013 + A1 2014 | ATS SAFETY REQUIREMENTS |
| 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 |
Summarise
US$96.00
Excluding Tax where applicable
Please Login or Create an Account so you can add users to your Multi user PDF Later.
Important note : All end users must be registered with an Account prior to user licenses being assigned.
Users cannot be edited or removed once added to your Multi user PDF.