| Name |
Description |
Abstract |
Status |
Publication date |
Edition |
Number of pages |
Technical committee |
ICS |
| ISO/IEC DIS 29110-1-1 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 1-1: Overview |
|
Under development |
|
Edition : 1 |
Number of pages : 19 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29110-2-1:2015 |
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 2-1: Framework and taxonomy |
1.1 Fields of application ISO/IEC 29110-2-1:2015 is applicable to Very Small Entities (VSEs). The lifecycle processes described in ISO/IEC 29110 are not intended to preclude or discourage their use by organizations bigger than VSEs. However, certain issues faced by large organizations might not be covered by ISO/IEC 29110.
The lifecycle processes defined in ISO/IEC 29110 can be used by VSEs when acquiring and using, as well as when creating and supplying, a software, and systems. They can be applied at any level in a software and systems structure and at any stage in the lifecycle. The processes described in ISO/IEC 29110 are not intended to preclude or discourage the use of additional processes that VSEs find useful.
ISO/IEC 29110-2-1:2015 introduces the major concepts for software and systems engineering profiles for VSEs, and defines the terms common to the set of documents associated with VSE profiles.
It establishes the logic behind the definition and application of profiles. It specifies the elements common to all standardized profiles (structure, conformance, assessment).
ISO/IEC 29110-2-1:2015 is applicable to all profiles.
1.2 Target audience ISO/IEC 29110-2-1:2015 is targeted at authors and reviewers of standardized profiles, authors of other parts, and authors of other VSE profiles.
|
Published |
2015-11 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29110-3-3:2016 |
Systems and software engineering — Lifecycle profiles for Very Small Enterprises (VSEs) — Part 3-3: Certification requirements for conformity assessments of VSE profiles using process assessment and maturity models |
ISO/IEC 29110-3-3:2016 contains the requirements for certification bodies performing conformity assessments, of the requirements contained in VSE profile specifications (e.g. ISO/IEC 29110‑4-1 for VSE software basic profile), using process assessments and maturity models. This document is based on published ISO/IEC standards and guides for
a) certification bodies (see ISO/IEC 17065)
b) the process assessment and organizational process maturity performed according to the requirements of the ISO/IEC 33001 to ISO/IEC 33099 family of process assessment standards, and
c) based on ISO/IEC 29169 to support an environment which encourages worldwide recognition of VSE profiles conformity assessment results.
The overall framework for conformity assessment follows the approach defined in ISO/IEC 17065:2012.
This document has been developed following practical use and in consultation with key stakeholders, national accreditation bodies, and ISO's policy committee for conformity assessment (CASCO).
ISO/IEC 29110-3-3:2016 is addressed to people and certification bodies who have a direct relationship with the assessment process based on the VSE profiles.
It is intended that ISO/IEC/TR 29110‑1, ISO/IEC 29110‑2-1 and ISO/IEC 29110‑4-1 (containing VSE profile specifications) be read first when investigating the possibility of conducting VSE profile certification.
NOTE Any clause with requirements directly copied from other standards has those copied requirements marked up in a box. Other requirements which are also copied but for which information is added are not marked up in a box but their source is clearly referenced in the text.
|
Published |
2016-10 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29110-4-1:2011 |
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 4-1: Profile specifications: Generic profile group |
ISO/IEC 29110-4-1:2011 is applicable to Very Small Entities (VSEs). A Very Small Entity (VSE) is defined as an enterprise, organization, department or project having up to 25 people. A set of standards and guides have been developed according to a set of VSEs' characteristics and needs. The guides are based on subsets of appropriate standards elements, referred to as VSE profiles. The purpose of a VSE profile is to define a subset of International Standards relevant to the VSE context.
ISO/IEC 29110 is targeted by audience. ISO/IEC 29110-4 is targeted for standards producers, tool vendors and methodology vendors. It is not intended for VSEs. ISO/IEC 29110-4-m provides the specification for all the profiles in a profile group that are based on subsets of appropriate standards elements. If a new profile is needed, a Part 4-m can be developed without impacting existing documents.
ISO/IEC 29110-4-1:2011 provides a profile specification for the Basic VSE profile within the Generic profile group. The Generic profile group is applicable to VSEs that do not develop critical software. The Generic profile group does not imply any specific application domain.
The Basic VSE profile selects ISO/IEC 12207 project management and software implementation process elements and ISO/IEC 15289 products from the single project perspective. Its purpose is to provide the normative and informative links to the subset of ISO/IEC 12207 and ISO/IEC 15289.
|
Withdrawn |
2011-01 |
Edition : 1 |
Number of pages : 52 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29110-4-2:2021 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 4-2: Software engineering: Profile specifications: Organizational management profile group |
This document provides a profile specification for the organizational management profile. The organizational management profile applies to VSEs involved in systems engineering and/or software engineering development.
This document provides links to the subset of ISO/IEC/IEEE 12207 and ISO 9001 organizational, resources, processes and project portfolio process elements from the organizational perspective.
|
Published |
2021-03 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29110-4-3:2018 |
Systems and software engineering — Lifecycle profiles for very small entities (VSEs) — Part 4-3: Service delivery — Profile specification |
This document is applicable to Very Small Entities (VSEs). A VSE is an enterprise, an organization, a department or a project having up to 25 people.
The purpose of this document is to provide a set of auditable requirements based on multiple standards (i.e., ISO/IEC/IEEE 15288, ISO/IEC/IEEE 15289, ISO 9000, ISO 9001, ISO 31000, ISO/IEC 38500, ISO 10004, ISO 10007, ISO/IEC 20000, ISO/IEC 27035) that supports the delivery of services by a VSE. Services can be delivered to internal or external customers. This document is not a Management System Standard (MSS), nor does it provide guidance on fulfilling the requirements of an MSS. ISO/IEC 20000-1:2011 is the MSS for service management (see Annex D for information).
This document does not promote uniformity in the approach across all organizations, as specific objectives and initiatives are tailored to suit an individual organization's needs.
|
Published |
2018-09 |
Edition : 1 |
Number of pages : 67 |
Technical Committee |
35.080
Software
|
| ISO/IEC DIS 29110-6-1 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 6-1: Software engineering — Specific Space Profile Specifications |
|
Under development |
|
Edition : 1 |
Number of pages : 33 |
Technical Committee |
35.080
Software
|
| 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 |
ISO/IEC TR 29110-2-2:2016 provides a guide for developing a profile which is domain-specific for VSEs (Very Small Entities) business situation. It may be used by technical advisers, including consultants, to help VSEs on software process problems. It also provides a conceptual framework for standardized profile developers using the ISO/IEC 29110 series concept.
|
Published |
2016-05 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-3-1:2015 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 3-1: Assessment guide |
ISO/IEC TR 29110-3-1:2015 defines the process assessment guidelines needed to meet the purpose of defined Very Small Entity (VSE) profiles. It is applicable to all VSE profiles and is compatible with ISO/IEC 33002.
|
Withdrawn |
2015-10 |
Edition : 1 |
Number of pages : 43 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-5-1-1:2012 |
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-1-1: Management and engineering guide: Generic profile group: Entry profile |
ISO/IEC TR 29110-5-1-1:2012 is applicable to Very Small Entities (VSEs). VSEs are enterprises, organizations, departments or projects up to 25 people. The life cycle processes described in the set of International Standards (IS) Profiles and Technical Reports (TR) are not intended to preclude or discourage their use by organizations bigger than VSEs.
ISO/IEC TR 29110-5-1-1:2012 provides the management and engineering guide to the entry profile described in ISO/IEC 29110-4-1 through project management and software implementation processes. ISO/IEC TR 29110‑5‑1‑1:2012 is a stand-alone guide. It is not intended for a VSE to use the standardized profile to implement ISO/IEC TR 29110-5-1-1:2012.
ISO/IEC TR 29110-5-1-1:2012 applies for software development project. The project may be to fulfil an external or internal contract. The internal contract need not be explicit between the project team and their customer.
Using ISO/IEC TR 29110-5-1-1:2012, a VSE can obtain the following benefits:
1) an agreed set of project requirements and expected products is delivered to the customer;
2) a disciplined management process, that provides project visibility and corrective actions of project problems and deviations, is performed;
3) a systematic software implementation process, that satisfies customer needs and ensures quality products, is followed.
ISO/IEC TR 29110-5-1-1:2012 is targeted at VSEs (a start-up VSE that started the operation less than 3 years ago and/or with a project size less than 6 person-months).
It is intended to be used with any processes, techniques and methods that enhance the VSE's customer satisfaction and productivity.
|
Published |
2012-09 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-5-1-2:2011 |
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-1-2: Management and engineering guide: Generic profile group: Basic profile |
ISO/IEC TR 29110-5-1-2:2011 is applicable to Very Small Entities (VSEs). A VSE is defined as an enterprise, organization, department or project having up to 25 people. A set of standards and guides have been developed according to a set of VSEs' characteristics and needs. The guides are based on subsets of appropriate standards elements, referred to as VSE Profiles. The purpose of a VSE Profile is to define a subset of ISO/IEC International Standards relevant to the VSEs' context.
The ISO/IEC 29110 series is targeted by audience. ISO/IEC TR 29110-5 is targeted to VSEs. ISO/IEC TR 29110-5-1-2:2011 provides the management and engineering guide to the Basic VSE Profile specifed in ISO/IEC 29110-4-1 through project management and software implementation processes. The Basic Profile is one profile of the Generic profile group. The Generic profile group is applicable to VSEs that do not develop critical software. The Generic profile group does not imply any specific application domain.
|
Published |
2011-05 |
Edition : 1 |
Number of pages : 44 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-5-1-3:2017 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-1-3: Software engineering — Management and engineering guide: Generic profile group — Intermediate profile |
ISO/IEC TR 29110-5-1-3:2017 provides management and engineering guide to the intermediate profile described in terms of business management, project management, software implementation and acquisition processes.
ISO/IEC TR 29110-5-1-3:2017 is applicable to Very Small Entities (VSEs). VSEs are enterprises, organizations, departments or projects having up to 25 people. The life cycle processes described in the ISO/IEC 29110 series are not intended to preclude or discourage their use by organizations bigger than VSEs.
ISO/IEC 29110?4-1 identifies the requirements applicable to the tasks and work products described in this document.
ISO/IEC TR 29110-5-1-3:2017 has been developed using the management and engineering guide of the Basic profile and by modifying and adding elements (e.g. process, task, work product, role) for VSEs involved in the development of more than one project in parallel with more than one work team.
ISO/IEC TR 29110-5-1-3:2017 applies for VSEs developing non-critical software.
Using this document, VSEs can obtain the following benefits:
- the management and monitoring of more than one project in parallel with more than one work team;
- reuse existing software components (e.g. code and document) in new projects;
- continuously measure projects and improve processes.
Once the software, developed by a VSE, has been accepted by their customers, the VSE that wants to provide after delivery services can refer to ISO/IEC TR 29110-5-3.[1]
ISO/IEC TR 29110-5-1-3:2017 is targeted to VSEs which are familiar with ISO/IEC TR 29110‑5-1-2 for their software development projects and are involved in the development of more than one project in parallel with more than one work team.
ISO/IEC TR 29110-5-1-3:2017 is intended to be used with any lifecycles, processes, techniques and methods that enhance the VSEs customer satisfaction and productivity.
[1] To be published.
|
Published |
2017-02 |
Edition : 1 |
Number of pages : 78 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-5-1-4:2018 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-1-4: Software engineering: Management and engineering guidelines: Generic profile group: Advanced profile |
This document is applicable to Very Small Entities (VSEs). VSEs are enterprises, organisations, departments or projects having up to 25 people. The life cycle processes described in the set of International Standards (IS) and Technical Reports (TR) are not intended to preclude or discourage their use by organisations bigger than VSEs.
The Advanced profile is the fourth profile of a four-profile software engineering roadmap (i.e. Entry, Basic, Intermediate and Advanced). This document describes processes targeted at VSEs that want to sustain and grow as an independent competitive software development business.
ISO/IEC 29110-4-1 identifies the requirements applicable to the tasks and work products described in this document.
These guidelines apply to VSEs that develop non-critical software.
Using these guidelines, VSEs can obtain the following benefits:
- management and monitoring of more than one project in parallel with more than one work team;
- reuse of existing software components (e.g. code and document) in new projects;
- continuous measurement and evaluation of projects;
- continuous evaluation and improvement processes;
- continuous sustainability and growth; and
- support to customers in the disposal of software and installation of new software.
Once the software, developed by a VSE, has been accepted by their customer, the VSE that wants to provide after-delivery services can refer to ISO/IEC TR 29110-5-3.
|
Published |
2018-04 |
Edition : 1 |
Number of pages : 95 |
Technical Committee |
35.080
Software
|
| ISO/IEC 30130:2016 |
Software engineering — Capabilities of software testing tools |
ISO/IEC 30130:2016 defines the framework to which capabilities of software testing tools are allocated in order to identify the capabilities of products being used by any project for software testing. Software testing processes are identified in ISO/IEC/IEEE 29119‑2 and software verification processes are identified in ISO/IEC 12207. This International Standard is fully harmonized with these existing standards in terms of software testing processes.
ISO/IEC 30130:2016 focuses on the following areas that the existing ISO/IEC standards do not deal with the following:
- categorization of software test entities and software testing tools (Clauses 4 and 5);
- characterization of each software testing tool category (Clauses 5 and 6);
- mapping of software testing tool capabilities and characteristics (Clauses 6 and 7).
|
Published |
2016-02 |
Edition : 1 |
Number of pages : 27 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-5-2-1:2016 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-2-1: Organizational management guidelines |
ISO/IEC 29110-5-2-1:2016 is applicable to Very Small Entities (VSEs). VSEs are enterprises, organizations, departments or projects having up to 25 people. The lifecycle processes described in the ISO/IEC 29110:2016 series are not intended to preclude or discourage their use by organizations bigger than VSEs.
ISO/IEC 29110-5-2-1:2016 is the Organizational management guidance for profiles described in ISO/IEC 29110-4-1 through Organizational Management, Project Portfolio Management, Resource Management and Process Management Processes. It is not intended for a VSE to use the standardized profile to implement ISO/IEC 29110-5-2-1:2016.
Using ISO/IEC 29110-5-2-1:2016, a VSE can obtain benefits in the following aspects:
? multiple project execution and supervision of its performance, making sure all processes are executed according to the organizational strategy;
? continuous monitoring of the customer satisfaction;
? deployment and improvement of the organizational standard processes in all projects;
? controlled provision of required resources.
|
Published |
2016-06 |
Edition : 1 |
Number of pages : 55 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-5-3:2018 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-3: Service delivery guidelines |
1.1 Fields of application These Service Delivery guidelines are applicable to Very Small Entities (VSEs). A VSE is an enterprise, an organization, a department or a project having up to 25 people.
ISO/IEC TR 29110-5-3:2018 provides guidance to manage a set of services delivered to customers. The VSE can act as an internal service provider (providing services internal to the VSE) or as an external service provider (providing services commercially to external customers). These lifecycle processes (Governance, Service Control, Service Relationship and Service Incident) support and enhance the activities of software and system operations (further to development and installation) to create effective and efficient products and services.
ISO/IEC TR 29110-5-3:2018 provides guidance for Service Delivery. This document, when implemented, will assist and guide the VSE in the delivery of services which can benefit customers. This document does not promote uniformity in approach across all organizations as specific objectives and initiatives are tailored to suit an individual organization's needs.
Tasks described in this guideline document (and therefore activities and processes) are related by input/output relationships which imply a logical execution sequence. The order of presentation of the processes or the associated numbering scheme is for identification purposes only, NOT to indicate implementation or execution order. As every VSE is different; tasks can be implemented in an order that is suitable for the organization, while respecting the relationships between tasks.
1.2 Target audience ISO/IEC TR 29110-5-3:2018 is intended to be used by VSEs to establish processes to implement effective and efficient service delivery. This service delivery guidelines document can be used by VSEs that are offering only services to its customers or it can be combined with the information from ISO/IEC 29110 systems and/or software management and engineering guidelines.
|
Published |
2018-01 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-5-6-1:2015 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-6-1: Systems engineering — Management and engineering guide: Generic profile group: Entry profile |
ISO/IEC 29110:2015 is applicable to Very Small Entities (VSEs). VSEs are enterprises, organizations, departments or projects having up to 25 people. The lifecycle processes described in the set of International Standards (IS) and Technical Reports (TR) are not intended to preclude or discourage their use by organizations bigger than VSEs.
ISO/IEC 29110:2015 provides the management and engineering guide to the Entry Profile described in ISO/IEC 29110-4-6 through Project Management and System Definition and realization processes. This part of ISO/IEC 29110 is a standalone guide; it is not intended for a VSE to use the standardized profile to implement ISO/IEC 29110:2015.
ISO/IEC 29110:2015 applies for non-critical systems development projects. The system development should fulfil the project requirements and the system description.
ISO/IEC 29110:2015, a VSE can obtain benefits in the following aspects:
– an agreed set of project requirements (technical part of contract) and expected products are agreed by the Acquirer;
– a disciplined management process, that provides project visibility and corrective actions of project problems and deviations, is performed;
– a systematic System Definition and Realization process, that satisfies Acquirer needs and ensures quality products, is followed.
VSEs developing software that is part of a larger system and for standalone software products and services are encouraged to use the management and engineering guide of the Entry Profile (ISO/IEC TR 29110‑5‑1‑1).
|
Published |
2015-12 |
Edition : 1 |
Number of pages : 50 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-5-6-2:2014 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-6-2: Systems engineering — Management and engineering guide: Generic profile group: Basic profile |
ISO/IEC 29110 is applicable to Very Small Entities (VSEs). VSEs are enterprises, organizations, departments or projects having up to 25 people. The lifecycle processes described in the set of International Standards (IS) and Technical Reports (TR) are not intended to preclude or discourage their use by organizations bigger than VSEs.
ISO/IEC 29110-5-6-2:2014 provides the management and engineering guide to the Basic Profile described in ISO/IEC 29110-4-6 through Project Management and System Definition and realization processes. It is a standalone guide; it is not intended for a VSE to use the standardized profile to implement ISO/IEC 29110-5-6-2:2014.
ISO/IEC 29110-5-6-2:2014 applies for non-critical systems development projects. The system development should fulfil the project requirements and the system description.
ISO/IEC 29110-5-6-2:2014, a VSE can obtain benefits in the following aspects:
An agreed set of project requirements (technical part of contract) and expected products are agreed by the Acquirer.
A disciplined management process, that provides project visibility and corrective actions of project problems and deviations, is performed.
A systematic System Definition and Realization process, that satisfies Acquirer needs and ensures quality products, is followed.
VSEs developing software that is part of a larger system, and for stand-alone software products and services, are encouraged to use the management and engineering guide of the Basic Profile (ISO/IEC 29110 5 1-2).
|
Published |
2014-08 |
Edition : 1 |
Number of pages : 58 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29119-2:2013 |
Software and systems engineering — Software testing — Part 2: Test processes |
The purpose of the ISO/IEC/IEEE 29119 series of software testing standards is to define an internationally-agreed set of standards for software testing that can be used by any organization when performing any form of software testing. ISO/IEC/IEEE 29119-2:2013 comprises test process descriptions that define the software testing processes at the organizational level, test management level and dynamic test levels. It supports dynamic testing, functional and non-functional testing, manual and automated testing, and scripted and unscripted testing. The processes defined in ISO/IEC/IEEE 29119-2:2013 can be used in conjuntion with any software development lifecycle model.
Since testing is a key approach to risk-mitigation in software development, ISO/IEC/IEEE 29119-2:2013 follows a risk-based approach to testing. Risk-based testing is a common industry approach to strategizing and managing testing. Risk-based testing allows testing to be prioritzed and focused on the most important features and functions.
|
Withdrawn |
2013-09 |
Edition : 1 |
Number of pages : 59 |
Technical Committee |
35.080
Software
|
| ISO 14218:1998 |
Aerospace — Airframe ball bearings, single-row, self-aligning, sealed, heavy duty — Inch series |
|
Withdrawn |
1998-05 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
49.035
Components for aerospace construction
|
| ISO/IEC TR 29110-5-6-3:2019 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-6-3: Systems engineering: Management and engineering guide: Generic profile group: Intermediate profile |
1.1 Fields of application This document provides management and engineering guidance within the Intermediate profile for the Business Management, Project Management, System Definition and Realisation and Acquisition Management processes.
This document is applicable to Very Small Entities (VSEs). VSEs are enterprises, organisations, departments or projects having up to 25 people. The lifecycle processes described in the ISO/IEC 29110 series are not intended to preclude or discourage their use by organisations bigger than VSEs.
This document has been developed using the management and engineering guide from the systems engineering Basic profile. Elements were added or modified (e.g. process, task, work product, role) to support VSEs involved in the development of more than one project in parallel with more than one work team.
This guide is oriented towards the management of more than one project in parallel with more than one work team.
This document applies for the development of non-critical systems.
Using this document, a VSE can obtain benefits in the following aspects:
— An agreed set of project requirements (technical part of contract) and expected work products are agreed by the Acquirer.
— A disciplined management process, that provides project visibility and corrective actions of project problems and deviations, is performed.
— A systematic System Definition and Realisation process, that satisfies Acquirer needs and helps ensure quality work products, is followed.
Once the system, developed by a VSE, has been accepted by their customers, the VSE that wants to provide after delivery services can refer to ISO/IEC TR 29110-5-3.
In the context of systems engineering, that is the System Definition and Realisation (SR) process, the group that is part of the VSE responsible for developing software elements that are part of the system are encouraged to use the management and engineering guide of the software engineering Intermediate profile (ISO/IEC TR 29110-5-1-3).
1.2 Target audience This document is targeted at VSEs that do not develop critical systems and have little or no experience with systems engineering (SE) process planning and implementation using ISO/IEC/IEEE 15288.
This document is also targeted to VSEs which are familiar with management and engineering guide of the systems engineering Basic profile (ISO/IEC TR 29110 5-6-2) for their system development projects and are involved in the development of more than one project in parallel with more than one work team.
This document is intended to be used with any processes, techniques and methods that enhance the VSE's Stakeholder satisfaction and productivity.
|
Published |
2019-09 |
Edition : 1 |
Number of pages : 92 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29110-2-1:2015/Amd 1:2022 |
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 2-1: Framework and taxonomy — Amendment 1: Update of references and editorial improvements |
|
Published |
2022-03 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29110-4-1:2018 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 4-1: Software engineering - Profile specifications: Generic profile group |
ISO/IEC 29110-4-1:2018 series is applicable to Very Small Entities (VSEs). VSEs are enterprises, organizations, departments or projects having up to 25 people. The lifecycle processes described in the ISO/IEC 29110 series are not intended to preclude or discourage their use by larger organizations than VSEs.
The lifecycle processes defined in the ISO/IEC 29110 series can be used by VSEs when using, as well as when creating and supplying, a software system. They can be applied at any level in a software system's structure and at any stage in the lifecycle. The processes described in the ISO/IEC 29110 series are not intended to preclude or discourage the use of additional processes that VSEs find useful. This document is not intended to preclude the use of different life cycles such as: waterfall, iterative, incremental, evolutionary or agile.
ISO/IEC 29110-4-1:2018 provides a profile specification for the Basic profile. The Basic profile applies to VSEs involved in software development. It selects ISO/IEC/IEEE 12207 project management and software implementation process elements from the single project perspective.
ISO/IEC 29110-4-1:2018 provides the normative and informative links to the subset of ISO/IEC/IEEE 12207.
|
Published |
2018-04 |
Edition : 2 |
Number of pages : 18 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-3-1:2020 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 3-1: Process assessment guidelines |
This document defines the process assessment guidelines needed to meet the purpose of defined VSE profiles. It is applicable to all VSE profiles and is compatible with ISO/IEC 33002.
The possible uses of this document are as follows.
a) Assessment to evaluate the process capabilities. Use when an organization wants an assessment of profile conformance (basic, etc.) of the implemented processes.
b) Supplier's capability assessment. Use when a customer asks for a third party to conduct an assessment in order to obtain a profile (basic, etc.) of the implemented process by the system or software development and maintenance supplier.
|
Published |
2020-04 |
Edition : 2 |
Number of pages : 99 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29119-1:2013 |
Software and systems engineering — Software testing — Part 1: Concepts and definitions |
The purpose of the ISO/IEC/IEEE 29119 series of software testing standards is to define an internationally-agreed set of standards for software testing that can be used by any organization when performing any form of software testing. ISO/IEC/IEEE 29119-1:2013 facilitates the use of the other ISO/IEC/IEEE 29119 standards by introducing the concepts and vocabulary on which these standards are built, as well as providing examples of its application in practice. ISO/IEC/IEEE 29119-1:2013 is informative, providing a starting point, context, and guidance for the other parts.
|
Withdrawn |
2013-09 |
Edition : 1 |
Number of pages : 56 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29119-1:2022 |
Software and systems engineering — Software testing — Part 1: General concepts |
This document specifies general concepts in software testing and presents key concepts for the ISO/IEC/IEEE 29119 series.
|
Published |
2022-01 |
Edition : 2 |
Number of pages : 47 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29119-2:2021 |
Software and systems engineering — Software testing — Part 2: Test processes |
This document specifies test processes that can be used to govern, manage and implement software testing for any organization, project or testing activity. It comprises generic test process descriptions that define the software testing processes. Supporting informative diagrams describing the processes are also provided.
This document is applicable to testing in all software development lifecycle models.
This document is intended for, but not limited to, testers, test managers, developers and project managers, particularly those responsible for governing, managing and implementing software testing.
|
Published |
2021-10 |
Edition : 2 |
Number of pages : 54 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29119-3:2013 |
Software and systems engineering — Software testing — Part 3: Test documentation |
The purpose of the ISO/IEC/IEEE 29119 series of software testing standards is to define an internationally-agreed set of standards for software testing that can be used by any organization when performing any form of software testing.
ISO/IEC/IEEE 29119-3:2013 includes templates and examples of test documentation. The templates are arranged within clauses reflecting the overall test process description structure in ISO/IEC/IEEE 29119-2, i.e. by the test process in which they are being produced. Annex A contains outlines of the contents of each document. Annex B contains mappings of ISO/IEC/IEEE 29119-2. Annex C contains an overview of the examples. Annexes D to S contain examples of the application of the templates. Annex T provides mappings to existing standards. The Bibliography for ISO/IEC/IEEE 29119-3:2013 is at the end of the document. ISO/IEC/IEEE 29119-3:2013 supports dynamic testing, functional and non-functional testing, manual and automated testing, and scripted and unscripted testing. The documentation templates defined in ISO/IEC/IEEE 29119-3:2013 can be used in conjunction with any software development lifecycle model.
|
Withdrawn |
2013-09 |
Edition : 1 |
Number of pages : 127 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29119-3:2021 |
Software and systems engineering — Software testing — Part 3: Test documentation |
This document specifies software test documentation templates that can be used for any organization, project or testing activity. It describes the test documentation that is an output of the processes specified in ISO/IEC/IEEE 29119-2.
This document is applicable to testing in all software development lifecycle models. This document is intended for, but not limited to, testers, test managers, developers, and project managers, particularly those responsible for governing, managing, and implementing software testing.
|
Published |
2021-10 |
Edition : 2 |
Number of pages : 84 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29119-4:2015 |
Software and systems engineering — Software testing — Part 4: Test techniques |
ISO/IEC/IEEE 29119-4:2015 defines test design techniques that can be used during the test design and implementation process that is defined in ISO/IEC/IEEE 29119‑2.
ISO/IEC/IEEE 29119-4:2015 is intended for, but not limited to, testers, test managers, and developers, particularly those responsible for managing and implementing software testing.
|
Withdrawn |
2015-12 |
Edition : 1 |
Number of pages : 139 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29119-4:2021 |
Software and systems engineering — Software testing — Part 4: Test techniques |
This document defines test design techniques that can be used during the test design and implementation process that is defined in ISO/IEC/IEEE 29119‑2.
Each technique follows the test design and implementation process that is defined in ISO/IEC/IEEE 29119‑2 and shown in Figure 1. This document is intended for, but not limited to, testers, test managers, and developers, particularly those responsible for managing and implementing software testing.
|
Published |
2021-10 |
Edition : 2 |
Number of pages : 135 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29119-5:2016 |
Software and systems engineering — Software testing — Part 5: Keyword-Driven Testing |
ISO/IEC/IEEE 29119-5:2016 defines an efficient and consistent solution for Keyword-Driven Testing by:
giving an introduction to Keyword-Driven Testing;
providing a reference approach to implement Keyword-Driven Testing;
defining requirements on frameworks for Keyword-Driven Testing to enable testers to share their work items, such as test cases, test data, keywords, or complete test specifications;
defining requirements for tools that support Keyword-Driven Testing. These requirements could apply to any tool that supports the Keyword-Driven approach (e.g., test automation, test design and test management tools);
defining interfaces and a common data exchange format to ensure that tools from different vendors can exchange their data (e.g. test cases, test data and test results);
defining levels of hierarchical keywords, and advising use of hierarchical keywords. This includes describing specific types of keywords (e.g. keywords for navigation or for checking a value) and when to use "flat" structured keywords;
providing an initial list of example generic technical (low-level) keywords, such as "inputData" or "checkValue". These keywords can be used to specify test cases on a technical level, and may be combined to create business-level keywords as required.
NOTE This standard is applicable to all those who want to create keyword-driven test specifications, create corresponding frameworks, or build test automation based on keywords.
|
Published |
2016-11 |
Edition : 1 |
Number of pages : 54 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29119-6:2021 |
Software and systems engineering — Software testing — Part 6: Guidelines for the use of ISO/IEC/IEEE 29119 (all parts) in agile projects |
This document provides guidance for the application of ISO/IEC/IEEE 29119 (all parts) in agile life cycles. This document is intended for (and not limited to) testers, test managers, business analysts, product owners, Scrum masters and developers involved in agile projects. The mappings provided in this document are designed to benefit any team or organization that is either moving away from traditional/waterfall life cycles and into agile or vice versa as well as new organizations that are commencing agile as their chosen life cycle. It is designed to be understandable regardless of the reader's familiarity with ISO/IEC/IEEE 29119 (all parts).
|
Published |
2021-07 |
Edition : 1 |
Number of pages : 45 |
Technical Committee |
35.080
Software
|
| ISO/IEC CD TR 29119-8.2 |
Software and systems engineering — Software testing — Part 8: Model-based testing |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC 9995-2:1994/Amd 1:1999 |
Information technology — Keyboard layouts for text and office systems — Part 2: Alphanumeric section — Amendment 1 |
|
Withdrawn |
1999-12 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.180
IT terminal and other peripheral equipment
|
| ISO/IEC TR 29119-11:2020 |
Software and systems engineering — Software testing — Part 11: Guidelines on the testing of AI-based systems |
This document provides an introduction to AI-based systems. These systems are typically complex (e.g. deep neural nets), are sometimes based on big data, can be poorly specified and can be non-deterministic, which creates new challenges and opportunities for testing them.
This document explains those characteristics which are specific to AI-based systems and explains the corresponding difficulties of specifying the acceptance criteria for such systems.
This document presents the challenges of testing AI-based systems, the main challenge being the test oracle problem, whereby testers find it difficult to determine expected results for testing and therefore whether tests have passed or failed. It covers testing of these systems across the life cycle and gives guidelines on how AI-based systems in general can be tested using black-box approaches and introduces white-box testing specifically for neural networks. It describes options for the test environments and test scenarios used for testing AI-based systems.
In this document an AI-based system is a system that includes at least one AI component.
|
Published |
2020-11 |
Edition : 1 |
Number of pages : 52 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29119-13:2022 |
Software and systems engineering — Software testing — Part 13: Using the ISO/IEC/IEEE 29119 series in the testing of biometric systems |
This document:
— gives information for software testers for the systematic, risk-based testing of biometric systems and larger systems which include biometric subsystems;
— establishes the importance of both biometric standards and software testing standards and provides overviews of both areas and their standardization;
— specifies the most important biometric standards for software testers of biometric systems;
— provides information for software testers who wish to conform to both the relevant biometrics standards and the ISO/IEC/IEEE 29119 series of software testing standards by providing mappings between the two sets of standards;
— is not limited to the testing of the technical performance of biometric systems in terms of error rates and throughput rates, but instead covers the testing of the full range of relevant quality characteristics, such as reliability, availability, maintainability, security, conformance, usability, human factors, and privacy regulation compliance;
— gives information on applying a risk-based testing approach to the testing of biometric systems that covers the full range of product and project risks;
— provides testers with an example set of product and project risks associated with biometric systems along with suggestions on how these risks can be treated as part of a risk-based approach to the testing;
— includes mappings between the documentation requirements of ISO/IEC 19795-1, ISO/IEC 19795-2 and ISO/IEC 19795-6 and the software test documentation defined by ISO/IEC/IEEE 29119-3.
|
Published |
2022-11 |
Edition : 1 |
Number of pages : 274 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29148:2011 |
Systems and software engineering — Life cycle processes — Requirements engineering |
ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207:2008 and ISO/IEC 15288:2008. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207:2008 or ISO/IEC 15288:2008, or can be used independently.
|
Withdrawn |
2011-12 |
Edition : 1 |
Number of pages : 83 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 29148:2018 |
Systems and software engineering — Life cycle processes — Requirements engineering |
This document:
— specifies the required processes implemented in the engineering activities that result in requirements for systems and software products (including services) throughout the life cycle;
— provides guidelines for applying the requirements and requirements-related processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207;
— specifies the required information items produced through the implementation of the requirements processes;
— specifies the required contents of the required information items;
— provides guidelines for the format of the required and related information items.
This document is applicable to:
— those who use or plan to use ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity;
— anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC/IEEE 15288 and/or ISO/IEC/IEEE12207;
— those who use or plan to use ISO/IEC/IEEE 15289 on projects dealing with man-made systems, software-intensive systems, software and hardware products and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity;
— anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conforms to ISO/IEC/IEEE 15289.
|
Published |
2018-11 |
Edition : 2 |
Number of pages : 92 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29154:2013 |
Software engineering — Guide for the application of ISO/IEC 24773:2008 (Certification of software engineering professionals — Comparison framework) |
ISO/IEC TR 29154:2013 is a guide for the application of ISO/IEC 24773:2008. It addresses terminology used in ISO/IEC 24773. It also includes interpretive guidance on several clauses of ISO/IEC 24773, as well as a review of potential typical scenarios for use of ISO/IEC 24773.
|
Withdrawn |
2013-08 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29155-1:2011 |
Systems and software engineering — Information technology project performance benchmarking framework — Part 1: Concepts and definitions |
ISO/IEC 29155-1:2011 identifies a framework for information technology (IT) project performance benchmarking (e.g. development or maintenance productivity) and related aspects (e.g. data collection and software classification).
The framework consists of activities and components that are necessary to successfully identify, define, select, apply, and improve benchmarking for IT project performance. It also provides definitions for IT project performance benchmarking terms.
The target audience of ISO/IEC 29155-1:2011 are the stakeholders of IT project performance benchmarking.
ISO/IEC 29155-1:2011 does not prescribe how to organize benchmarking. It is out of the scope of ISO/IEC 29155-1:2011 to prescribe the name, format, or explicit content of the documentation to be produced from the benchmarking process.
|
Withdrawn |
2011-12 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 33060:2020 |
Information technology — Process assessment — Process assessment model for system life cycle processes |
This document defines a process assessment model for system life cycle processes, conformant with the requirements of ISO/IEC 33004, for use in performing a conformant assessment in accordance with the requirements of ISO/IEC 33002.
|
Published |
2020-03 |
Edition : 1 |
Number of pages : 66 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29155-1:2017 |
Systems and software engineering — Information technology project performance benchmarking framework — Part 1: Concepts and definitions |
ISO/IEC 29155-1:2017 identifies a framework for information technology (IT) project performance benchmarking (e.g. development or maintenance productivity) and related aspects (e.g. data collection and software classification).
The framework consists of activities and components that are necessary to successfully identify, define, select, apply, and improve benchmarking for IT project performance. It also provides definitions for IT project performance benchmarking terms, which are also applicable to other parts of the ISO/IEC 29155 series.
The target audience of this document are stakeholders of IT project performance benchmarking.
NOTE The following are examples of how this document can be used:
- by a benchmarking service provider who wants to align their benchmarking process to be consistent with this document;
- by a benchmarking user (or third-party agents) for evaluating the performance of an IT project;
- by an organization internally to answer specific information needs.
ISO/IEC 29155-1:2017 does not cover how to organize benchmarking. It is out of the scope of this document to prescribe the name, format, or explicit content of the documentation to be produced from the benchmarking process.
|
Published |
2017-12 |
Edition : 2 |
Number of pages : 17 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29155-2:2013 |
Systems and software engineering — Information technology project performance benchmarking framework — Part 2: Requirements for benchmarking |
ISO/IEC 29155-2:2013 provides general requirements for processes of "the information technology (IT) project performance benchmarking framework" by prescribing:
the requirements for the processes for individual activities within the benchmarking framework (e.g. conduct benchmarking, maintain repository, submit data),
the tasks necessary to successfully execute activities and equip them with components, both of which are defined in ISO/IEC 29155-1.
ISO/IEC 29155-2:2013 is intended for use by any stakeholder(s) of IT project performance benchmarking (e.g. benchmarking user, benchmark provider, benchmarking service provider, and IT project team).
The following are examples of how ISO/IEC 29155-2:2013 can be used:
by a systems and software supplier to implement a benchmarking process to estimate and/or evaluate performance of an IT project,
by a systems and software acquirer (or a third-party agent) for evaluating the performance of the supplier's IT project,
by a benchmark provider to implement processes to collect and analyse IT project data and provide benchmarks,
by a benchmarking service provider to implement various services (e.g. providing instruments for benchmarking, or conducting an instance of benchmarking for a benchmarking user).
ISO/IEC 29155-2:2013 does not prescribe how to utilize benchmarking results, nor does it prescribe the name, format, or explicit content of the documentation that results from the benchmarking processes.
|
Published |
2013-11 |
Edition : 1 |
Number of pages : 24 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29155-3:2015 |
Systems and software engineering — Information technology project performance benchmarking framework — Part 3: Guidance for reporting |
ISO/IEC 29155-3:2015 provides general requirements and guidance for reporting processes and contents of typical reports within benchmarking activities of "the information technology (IT) project performance benchmarking framework" by prescribing:
- requirements and guidance for the reporting processes within the benchmarking framework;
? requirements and guidance for the contents of reports.
ISO/IEC 29155-3:2015 focuses on three major activities, i.e. "conduct benchmarking", "maintain repository", and "issue benchmarks" activities.
NOTE 1 These activities are selected, not only because the importance of the outcomes of these activities, but also the outcomes of these activities are the direct input for benchmarking users who execute "core benchmarking" activities. In addition, benchmarking users are not usually so deeply involved to these activities even though they need in-deep information to understand the benchmarking results or to select appropriate data (i.e. benchmarking repository and benchmarks).
ISO/IEC 29155-3:2015 also focuses on two types of reports in the benchmarking framework:
a) the benchmarking report, that describes the results of an instance of benchmarking;
b) the explanatory report, that provides complementary information about the released benchmarking repository or benchmark(s).
ISO/IEC 29155-3:2015 is intended for use by stakeholder(s) of IT project performance benchmarking (e.g. benchmarking user, benchmark provider, and benchmarking service provider).
NOTE 2 The following are examples of how this part of ISO/IEC 29155 can be used:
- by a systems and software acquirer (or a third-party agent), to define, order, obtain and evaluate an acceptable and creditable benchmarking report;
- by a benchmarking service provider, to produce a high-quality benchmarking report;
- by a benchmark provider, to provide complementary information about the released benchmarking repository or issued benchmarks.
It is out of the scope of this part of ISO/IEC 29115 to prescribe the particular names, formats, or explicit contents of the reports of the benchmarking activities.
|
Published |
2015-11 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29155-4:2016 |
Systems and software engineering — Information technology project performance benchmarking framework — Part 4: Guidance for data collection and maintenance |
ISO/IEC 29155-4:2016 provides general requirements and guidance for collecting and maintaining data of information technology (IT) projects and for delivering the benchmarking repository within benchmarking activities of "the IT project performance benchmarking framework" by prescribing the following:
a) requirements and guidance for data element definitions;
b) requirements and guidance for the data collection and maintenance processes within the benchmarking framework;
c) requirements and guidance for maintaining benchmarking repository product and issued benchmarks.
ISO/IEC 29155-4:2016 mainly focuses on three major activities, which are "maintain repository", "submit IT project data", and "measure IT project" activities.
ISO/IEC 29155-4:2016 is intended for use by stakeholder(s) of IT project performance benchmarking (e.g. benchmarking user, benchmark provider, benchmarking service provider, and IT project team).
NOTE The following are examples of how this document can be used:
- by a benchmark provider, to define data elements, collect and maintain IT project data, and provide benchmarking repository product or issued benchmarks;
- by a benchmarking analyst, to use benchmarking repository product and/or benchmarks for executing an instance of benchmarking;
- by a benchmarking service provider, to utilize benchmarking repository product and/or benchmarks for providing benchmarking services;
- by an IT service provider, to define data elements to be measured and/or to be submitted to repository owner.
It is out of the scope of this document to prescribe a particular set of data element definitions, formats or contents of the benchmarking repository.
|
Published |
2016-10 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 30103:2015 |
Software and Systems Engineering — Lifecycle Processes — Framework for Product Quality Achievement |
The scope of ISO/TS 30103:2015 is to indicate how to apply the life cycle processes in ISO/IEC/IEEE 15288:2008 to achieve quality in the context of a specific product. It is independent of any tailoring that may be made to modify the generic process descriptions to suit the needs of a particular context. Even after any applicable tailoring, there is a need to apply the resulting process guidance and determine the specific detailed activities, tasks and associated success criteria for each of the process instances needed to deliver the target system. That is the focus of the framework described in ISO/TS 30103:2015.
ISO/TS 30103:2015 is applicable to
those who use or plan to use ISO/IEC/IEEE 15288:2008 on projects dealing with man-made systems, software-intensive systems, software products, and services related to those systems and products, regardless of project scope, product(s), service(s), methodology, size or complexity,
those who use or plan to use ISO/IEC/IEEE 15289 on projects dealing with man-made systems, software-intensive systems, software products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,
anyone performing technical processes and tasks,
those who are responsible for the technical management of projects concerned with the development of systems,
those responsible for performing ISO/IEC/IEEE 15288:2008 life cycle processes at a project level,
organizations and individuals subcontracting a project management effort,
anyone developing systems engineering management documentation to complete technical planning aspects of their project processes,
anyone performing systems engineering activities,
project managers responsible for staffing projects and identifying competency development needs,
anyone developing information items during the application of project and technical processes, and
anyone performing project and technical processes to aid in ensuring that the information items developed during these processes conform to ISO/IEC/IEEE 15289.
|
Published |
2015-09 |
Edition : 1 |
Number of pages : 39 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29168-1:2011 |
Information technology — Open systems interconnection — Part 1: Object identifier resolution system |
ISO/IEC 29168-1:2011 specifies the object identifier (OID) resolution system (ORS), including the overall architecture and a DNS-based resolution mechanism.
It specifies the means for inserting any application-defined information associated with an OID node into the domain name system (DNS) and the means of retrieval of that information using the ORS.
It does not restrict the number of applications it can support.
It specifies the required operation of an ORS client, including the mapping of an OID-IRI (internationalized resource identifier) value by the ORS client into a DNS name to produce a DNS query for the specified application information and the processing of any returned information. The ORS has no role in the allocation or registration of OID nodes.
The required behaviour of an ORS client is specified, but the interfaces to it are specified only in terms of the semantics of the interaction. A bit-level application program interface is platform- and software-dependent, and is not in the scope of ISO/IEC 29168-1:2011.
It does not include a tutorial or complete specification on the management of DNS zone files; it specifies (only) the DNS resource records that need to be inserted in the zone files in order to support ORS access to the information associated with an OID node.
ISO/IEC 29168-1:2011 specifies required DNS zone file resource records, and prohibits the use of other resource records of a similar form but with different semantics (in DNS zone files in the .oid res.org domain). It does not otherwise restrict the general use of DNS zone files.
|
Withdrawn |
2011-09 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29168-2:2011 |
Information technology — Open systems interconnection — Part 2: Procedures for the object identifier resolution system operational agency |
ISO/IEC 29168-2:2011 specifies the mechanisms and criteria for the selection and approval of the object identifier resolution system (ORS) operational agency, and the procedures that the operational agency is required to follow to support the operation of the ORS. It includes the specification of use of DNSSEC (NSEC3) and addresses issues of charging. It also specifies the mechanisms for the appointment of the operational agency as an ISO/IEC Registration Authority.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.080
Software
|
| ISO/IEC FDIS 29168-2 |
Information technology — Open systems interconnection — Part 2: Procedures for the object identifier resolution system operational agency |
|
Under development |
|
Edition : 2 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC 29169:2016 |
Information technology — Process assessment — Application of conformity assessment methodology to the assessment to process quality characteristics and organizational maturity |
ISO/IEC 29169:2016 aims to define the application of a conformity assessment methodology, based on the existing published ISO/IEC standards and guides, to the process assessment of process quality characteristics and organizational process maturity, performed in accordance with the requirements of the ISO/IEC 33001 to ISO/IEC 33099 family of process assessment standards,
Conformity assessment, also known as compliance assessment, is any activity to determine, directly or indirectly, that a process, product, or service meets relevant standards and fulfils relevant requirements. The subject of conformity assessment activities may include testing, inspection or certification.
Conformity assessment in this International Standard can be performed by various types of bodies that meet the requirements of ISO/IEC 17020.
The term "inspection" as used in ISO/IEC 17020 is synonymous with the term "process assessment" as defined in ISO/IEC 33001 and used throughout the ISO/IEC 33001 to ISO/IEC 33099 family of standards.
While a process assessment may be performed solely according to the ISO/IEC 33002 requirements for performing an assessment, performing a process assessment in the context of conformity assessment according to a conformity assessment scheme brings with it additional requirements. Conformity assessment involves a functional approach consisting of a number of stages: selection?determination?review and attestation, plus surveillance when there is a need to provide continuing assurance of conformity.
|
Published |
2016-04 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29881:2008 |
Information technology — Software and systems engineering — FiSMA 1.1 functional size measurement method |
ISO/IEC 29881:2008 specifies the set of definitions, conventions and activities of FiSMA 1.1. The target audience includes anyone who applies FiSMA 1.1 to measure the functional size of a piece of software. FiSMA 1.1 is intended for use by those persons associated with the acquisition, development, use, support, maintenance, and audit of software. FiSMA 1.1 is based on an assessment of the Functional User Requirements. It measures the functional size of a piece of software from the perspective of the users.
|
Withdrawn |
2008-05 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29881:2010 |
Information technology — Systems and software engineering — FiSMA 1.1 functional size measurement method |
ISO/IEC 29881:2010 specifies the set of definitions, conventions and activities of FiSMA 1.1.
The target audience of ISO/IEC 29881:2010 includes anyone who applies FiSMA 1.1 to measure the functional size of a piece of software. FiSMA 1.1 is intended for use by those persons associated with the acquisition, development, use, support, maintenance, and audit of software. FiSMA 1.1 is based on an assessment of the Functional User Requirements. It measures the functional size of a piece of software from the perspective of the users.
|
Published |
2010-08 |
Edition : 2 |
Number of pages : 16 |
Technical Committee |
35.080
Software
|
| ISO/IEC 30121:2015 |
Information technology — Governance of digital forensic risk framework |
ISO/IEC 30121:2015 provides a framework for Governing bodies of organizations (including owners, board members, directors, partners, senior executives, or similar) on the best way to prepare an organization for digital investigations before they occur. This International Standard applies to the development of strategic processes (and decisions) relating to the retention, availability, access, and cost effectiveness of digital evidence disclosure. This International Standard is applicable to all types and sizes of organizations.
|
Published |
2015-03 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.080
Software
|
| ISO 14219:1998 |
Aerospace — Airframe ball bearings, single-row, self-aligning, precision, sealed, heavy duty — Inch series |
|
Withdrawn |
1998-05 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
49.035
Components for aerospace construction
|
| ISO/IEC/IEEE 31320-1:2012 |
Information technology — Modeling Languages — Part 1: Syntax and Semantics for IDEF0 |
ISO/IEC/IEEE 31320-1:2012 identifies the basic components of Integration Definition 0 (IDEF0) syntax (the drawn, visual elements of the language and how they may be used together) and IDEF0 semantics (what it means when the visual elements are used together in specific, allowable ways), specifies the rules that govern the use of these modelling components, and describes the types of diagrams used in an IDEF0 model. ISO/IEC/IEEE 31320-1:2012 identifies and discusses the model pages with which each diagram in an IDEF0 model is associated and discusses specific features found in an IDEF0 diagram. It describes IDEF0 reference expressions and IDEF0 diagram feature references. It also presents an abstract formalization of the IDEF0 language.
|
Published |
2012-09 |
Edition : 1 |
Number of pages : 106 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 31320-2:2012 |
Information technology — Modeling Languages — Part 2: Syntax and Semantics for IDEF1X97 (IDEFobject) |
ISO/IEC/IEEE 31320-2:2012 describes the semantics and syntax of IDEF1X, a language used to represent a conceptual schema. Two styles of IDEF1X model are described.
The key style is used to produce information models that represent the structure and semantics of data within an enterprise and is backward-compatible with the US government's Federal Information Processing Standard (FIPS) PUB 184, Integration Definition for Information Modeling (IDEF1X).
The identity style is used to produce object models that represent the knowledge, behaviour, and rules of the concepts within an enterprise. It can be used as a growth path for key-style models. The identity style can, with suitable automation support, be used to develop a model that is an executable prototype of the target object-oriented system.
|
Published |
2012-09 |
Edition : 1 |
Number of pages : 305 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 32430:2021 |
Software engineering — Trial use standard for software non-functional sizing measurements |
This document defines a method for the sizing of non-functional software requirements. It complements ISO/ IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR).1
This document also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects.
In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use.
This document covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence.
Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.
|
Published |
2021-10 |
Edition : 1 |
Number of pages : 76 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 32675:2022 |
Information technology — DevOps — Building reliable and secure systems including application build, package and deployment |
This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders.
This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements.
This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included.
There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.
|
Published |
2022-08 |
Edition : 1 |
Number of pages : 81 |
Technical Committee |
35.080
Software
|
| ISO/IEC 33001:2015 |
Information technology — Process assessment — Concepts and terminology |
ISO/IEC 33001:2015 provides a repository for key terminology relating to process assessment. It gives overall information on the concepts of process assessment, the application of process assessment for evaluating the achievement of process quality characteristics, and the application of the results of process assessment to the conduct of process management. ISO/IEC 33001:2015 provides an introduction to the ISO/IEC 330xx family of standards for process assessment; it describes how the parts of the family of standards for process assessment fit together and provides guidance for their selection and use. It explains the requirements contained within the suite and their applicability to performing assessments.
|
Published |
2015-03 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
35.080
Software
|
| ISO/IEC 33002:2015 |
Information technology — Process assessment — Requirements for performing process assessment |
ISO/IEC 33002:2015 defines the minimum set of requirements for performing an assessment that will ensure assessment results are objective, consistent, repeatable, and representative of the assessed processes.
The requirements defined in ISO/IEC 33002:2015 can be used by or on behalf of an organization to
a) facilitate self-assessment,
b) provide a basis for improving process performance and mitigating process-related risk,
c) produce a rating of the achievement of the relevant process quality characteristic, and
d) provide an objective benchmark between organizations.
ISO/IEC 33002:2015 is applicable across all application domains and sizes of organization.
|
Published |
2015-03 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
35.080
Software
|
| ISO/IEC 33003:2015 |
Information technology — Process assessment — Requirements for process measurement frameworks |
ISO/IEC 33003:2015 sets out the requirements for process measurement frameworks for use in process assessment. The requirements defined in ISO/IEC 33003:2015 form a structure which
a) establish the requirements for process measurement frameworks in the context of process assessment,
b) establish the requirements for the validation of process measurement frameworks for use in process assessment, and
c) establish requirements that are applicable to any process measurement frameworks to develop composite measures across domains.
ISO/IEC 33003:2015 is applicable to the development of process measurement frameworks for any process quality characteristic across all application domains.
|
Published |
2015-03 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO/IEC 33004:2015 |
Information technology — Process assessment — Requirements for process reference, process assessment and maturity models |
ISO/IEC 33004:2015 sets out the requirements for process reference models, process assessment models, and maturity models. The requirements defined in this International Standard form a structure which specifies
a) the relationship between the classes of process model associated with the performance of process assessment,
b) the relationship between process reference models and prescriptive/normative models of process performance, as constituted by, for example, the activities and tasks defined in ISO/IEC 12207 and ISO/IEC 15288,
c) the integration of process reference models and process measurement frameworks to establish process assessment models,
d) the use of common sets of assessment indicators of process performance and process quality in process assessment models, and
e) the relationship between maturity models and process assessment models and the extent to which a maturity model can be constructed using elements from different process assessment models.
|
Published |
2015-03 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 33010:2023 |
Information technology — Process assessment — Guidance for performing process assessments |
This document provides an overview of process assessment and interprets the requirements of ISO/IEC 33002 and ISO/IEC 33004 through the provision of guidance on the selection and use of assessment models, documented assessment processes, and instruments or tools for assessment.
Process assessment is applicable in the following circumstances:
a) by or on behalf of an organization with the objective of understanding the state of its own processes for process improvement;
b) by or on behalf of an organization with the objective of determining the suitability of its own processes for a particular requirement or class of requirements;
c) by or on behalf of one organization with the objective of determining the suitability of another organization's processes for a particular contract or class of contracts.
|
Published |
2023-04 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 33014:2013 |
Information technology — Process assessment — Guide for process improvement |
ISO/IEC TR 33014:2013 provides informative guidance on using process assessment as part of a complete framework and method for performing process improvement as part of a continual improvement activity. It also provides guidance on how to strengthen and maintain the abilities to ensure success with continual process improvement - improvability. Improvability is addressed both at the organizational perspective and at the project perspective.
In the case of process improvement, the concepts and principles are appropriate for the full range of different business goals, application domains and sizes of organization, so that all types of organizations may use them. It is the same in the case of process improvability.
ISO/IEC TR 33014:2013 deals with process improvement on three levels.
Strategic: what goals to achieve, the motivation and direction.
Tactical: how to achieve the goals of process improvement.
Operational: how to perform the process improvement.
ISO/IEC TR 33014:2013 has three improvement perspectives.
Process perspective: Process improvement as a programme or project.
Organizational perspective: Improvement of organizational improvability in order to ensure success with improvement projects.
Project perspective: Improve a project´s improvability and reach improvement success.
ISO/IEC TR 33014:2013 includes topics such as: utilising the results of a process assessment; principles of continual process improvement; roles in process improvement; principles of enhancing improvability; process improvement support elements; overall change strategies; scope of change;
Although the focus for ISO/IEC TR 33014:2013 is continual process improvement based on using process assessment as part of a complete framework and method for performing and ensuring success with continual process improvement, it can also be used in related areas.
|
Published |
2013-12 |
Edition : 1 |
Number of pages : 41 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 33015:2019 |
Information technology — Process assessment — Guidance for process risk determination |
This document provides guidance on the application of the results of a process assessment for process risk determination.
The guidance provided does not presume specific organizational structures, management philosophies, life cycle models or development methods. In relation to process risk determination, this guidance is applicable within any customer?supplier relationship, and to any organization wishing to perform a process risk determination of its processes.
|
Published |
2019-08 |
Edition : 1 |
Number of pages : 34 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 33017:2021 |
Information technology — Process assessment — Framework for assessor training |
This document provides a framework for assessor training aimed at training providers who design, develop, and/or deliver training courses for assessors conducting assessments conformant with ISO/IEC 33002.
The document defines four training course elements:
— Foundation
— Process assessment model
— Assessor
— Practical assessment performance
Whilst the training is defined as separate training course elements, the elements can be combined into one or more training courses for delivery. Furthermore, training modules and learning objectives can be addressed in training courses in any combination or sequence.
|
Published |
2021-02 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 33018:2019 |
Information technology — Process assessment — Guidance for assessor competency |
This document provides general and specific guidance for the competency of assessors performing assessments in accordance with the ISO/IEC 330xx family of standards.
|
Published |
2019-07 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
35.080
Software
|
| ISO/IEC 33020:2015 |
Information technology — Process assessment — Process measurement framework for assessment of process capability |
ISO/IEC 33020:2015 defines a process measurement framework that supports the assessment of process capability, in accordance with the requirements of ISO/IEC 33003. The process measurement framework provides a schema that can be used to construct a process assessment model conformant with ISO/IEC 33004 which can be used in the performance of assessment of process capability according to the requirements of ISO/IEC 33002. In the context of this and related standards, process capability is a process quality characteristic related to the ability of a process to consistently meet current or projected business goals.
The process measurement frameworks defined in ISO/IEC 33020:2015 form a structure which
a) facilitates self-assessment,
b) provides a basis for use in process improvement and process quality determination,
c) is applicable across all application domains and sizes of organization,
d) produces a set of process (capability) attribute ratings (process profile), and
e) derives a process capability level.
|
Withdrawn |
2015-03 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
35.080
Software
|
| ISO/IEC 33020:2019 |
Information technology — Process assessment — Process measurement framework for assessment of process capability |
This document defines a process measurement framework that supports the assessment of process capability, in accordance with the requirements of ISO/IEC 33003. The process measurement framework provides a schema that can be used to construct a process assessment model conformant with ISO/IEC 33004 which can be used in the performance of assessment of process capability according to the requirements of ISO/IEC 33002. In the context of this document and related standards, process capability is a process quality characteristic related to the ability of a process to consistently meet current or projected business goals.
The process measurement framework defined in this document forms a structure which
a) facilitates self-assessment,
b) provides a basis for use in process improvement and process quality determination,
c) is applicable across all application domains and sizes of organization,
d) produces a set of process (capability) attribute ratings (process profile), and
e) derives a process capability level.
This document also includes as informative annexes a set of assessment indicators of process capability that can be used in the construction of a process assessment model using this process measurement framework, and guidance on the meaning of the process capability levels and the achievement of the process attributes.
|
Published |
2019-11 |
Edition : 2 |
Number of pages : 42 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 33030:2017 |
Information technology — Process assessment — An exemplar documented assessment process |
ISO/IEC TS 33030:2017 contains an exemplar documented assessment process, and serves as guidance on the nature of activities required by this document. The content of this exemplar contains the minimum elements of a documented assessment process applicable for performing all classes of assessments as defined in ISO/IEC 33002. See also Annex B.
ISO/IEC TS 33030:2017 is suitable for all classes of assessments defined in ISO/IEC 33002.
This exemplar includes the activities by describing the tasks, inputs, outputs and the assessment-related roles and responsibilities. This description implicitly contains other elements that could comprise the process, like purpose, initial/end conditions, additional supporting roles/responsibilities or necessary resources.
While this exemplar contains all of the activities that are considered to be required for a process assessment, it is the case that variation exists in individual process assessments, and therefore, some degree of tailoring of this assessment process could be required. Tailoring of the assessment process is permitted, though it is the responsibility of the Lead Assessor and it would need to be conformant to the requirements of ISO/IEC 33002.
ISO/IEC TS 33030:2017 is not intended for use in performing organizational maturity assessments.
|
Published |
2017-04 |
Edition : 1 |
Number of pages : 33 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 33052:2016 |
Information technology — Process reference model (PRM) for information security management |
ISO/IEC TS 33052:2016 defines a process reference model (PRM) for the domain of information security management. The model architecture specifies a process architecture for the domain and comprises a set of processes, with each described in terms of process purpose and outcomes.
|
Published |
2016-06 |
Edition : 1 |
Number of pages : 60 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 33053:2019 |
Information technology — Process assessment — Process Reference Model (PRM) for quality management |
This document defines a process reference model for the domain of quality management.
The model specifies a process architecture for the domain and comprises a set of processes. Each process is described in terms of process purpose and outcomes.
NOTE Users of this document can freely reproduce the detailed descriptions contained in this process reference model as part of any tool or other material to support the performance of process assessments, so that it can be used for its intended purpose.
|
Published |
2019-11 |
Edition : 1 |
Number of pages : 57 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 33054:2020 |
Information technology — Process assessment — Process reference model for service management |
This document defines a process reference model for the domain of service management.
The model specifies a process architecture for the domain and comprises a set of processes. Each process is described in terms of process purpose and outcomes.
The process reference model in this document is directed at assessment sponsors and competent assessors who wish to select a model, and associated documented process method, for assessment (for either capability determination or process improvement).
|
Published |
2020-06 |
Edition : 1 |
Number of pages : 73 |
Technical Committee |
35.080
Software
|
| ISO/IEC 11801-4:2017/Cor 1:2018 |
Information technology — Generic cabling for customer premises — Part 4: Single-tenant homes — Technical Corrigendum 1 |
|
Published |
2018-04 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
35.200
Interface and interconnection equipment
|
| ISO/IEC 33063:2015 |
Information technology — Process assessment — Process assessment model for software testing |
ISO/IEC 33063:2015
- defines a process assessment model that meets the requirements of ISO/IEC 33004 and that supports the performance of an assessment of process capability using the process measurement framework defined in ISO/IEC 33020. The process assessment model provides indicators for guidance on the interpretation of the process purposes and outcomes as defined in ISO/IEC/IEEE 29119‑2 and the process attributes as defined in ISO/IEC 33020, and
- provides guidance, by example, on the definition, selection, and use of assessment indicators.
A process assessment model comprises a set of indicators of process performance and process capability. The indicators are used as a basis for collecting the objective evidence that enables an assessor to assign ratings, following the requirements of ISO/IEC 33002. The set of indicators included in this International Standard is not intended to be an all-inclusive set nor is it intended to be applicable in its entirety. Subsets that are appropriate to the context and scope of the assessment should be selected.
The process assessment model in this International Standard is directed at assessment sponsors and competent assessors who wish to select a model and associated documented process method for assessment (for either capability determination or process improvement).
Any process assessment model for software testing meeting the requirements defined in ISO/IEC 33004 concerning models for process assessment may be used for assessment. Different models and methods might be needed to address differing business and testing needs. This assessment model is provided as an exemplar of a model meeting all the requirements expressed in ISO/IEC 33004.
|
Published |
2015-08 |
Edition : 1 |
Number of pages : 69 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 33072:2016 |
Information technology — Process assessment — Process capability assessment model for information security management |
ISO/IEC TS 33072:2016:
- defines a process assessment model (PAM) that meets the requirements of ISO/IEC 33004 and that supports the performance of an assessment of process capability by providing indicators for guidance on the interpretation of the process purposes and outcomes as defined in ISO/IEC TS 33052 and the process attributes as defined in ISO/IEC 33020;
- provides guidance, by example, on the definition, selection and use of assessment indicators.
|
Published |
2016-07 |
Edition : 1 |
Number of pages : 183 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 33073:2017 |
Information technology — Process assessment — Process capability assessment model for quality management |
ISO/IEC TS 33073:2017:
- defines an integrated PRM and PAM that meets the requirements of ISO/IEC 33004 and that supports the performance of an assessment by providing indicators for guidance on the interpretation of the process purposes and outcomes and the process attributes as defined in ISO/IEC 33020;
- provides guidance, by example, on the definition, selection and use of assessment indicators.
A PAM comprises a set of indicators of process performance and process capability. The indicators are used as a basis for collecting the objective evidence that enables an assessor to assign ratings. The set of indicators included in ISO/IEC TS 33073:2017 is not intended to be an all-inclusive set nor is it intended to be applicable in its entirety.
The PAM in ISO/IEC TS 33073:2017 is directed at assessment sponsors and competent assessors who wish to select a model and associated documented process method for assessment (for either capability determination or process improvement). Additionally, it can be of use to developers of assessment models in the construction of their own model, by providing examples of good service management practices. It can be used by:
a) service providers to assess and improve a Quality Management System (QMS);
b) service providers to demonstrate their capability for the design, development, transition and delivery of services that fulfil Quality Management requirements.
Any PAM meeting the requirements defined in ISO/IEC 33004 concerning models for process assessment may be used for assessment. Different models and methods can be needed to address differing business needs. The assessment model in ISO/IEC TS 33073:2017 is provided as an assessment model meeting all the requirements expressed in ISO/IEC 33004.
NOTE Copyright release for the PAM: Users of ISO/IEC TS 33073:2017 can freely reproduce the detailed descriptions contained in the assessment model as part of any tool or other material to support the performance of process assessments, so that it can be used for its intended purpose.
|
Published |
2017-11 |
Edition : 1 |
Number of pages : 298 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 33074:2020 |
Information technology — Process assessment — Process capability assessment model for service management |
This document:
— defines a process assessment model that relies on the process reference model published as ISO/IEC TS 33054 that meets the requirements of ISO/IEC 33004 and that supports the performance of an assessment by providing indicators for guidance on the interpretation of the process purposes and outcomes and the process attributes as defined in ISO/IEC 33020;
— provides guidance, by example, on the definition, selection and use of assessment indicators.
A process assessment model comprises a set of indicators of process performance and process capability. The indicators are used as a basis for collecting the objective evidence that enables an assessor to assign ratings. The set of indicators included in this document is not intended to be an all-inclusive set.
The process assessment model in this document is directed at assessment sponsors and competent assessors who wish to select a model, and associated documented process method, for assessment (for either capability determination or process improvement). Additionally, it can be of use to developers of assessment models in the construction of their own model, by providing examples of good service management practices. It can be used by:
a) service providers to assess and improve a service management system (SMS);
b) service providers to demonstrate their capability for the planning, design, development, transition and delivery of services that meet agreed service management requirements.
Any process assessment model meeting the requirements defined in ISO/IEC 33004 concerning models for process assessment can be used for assessment. Different models and methods can be needed to address differing business needs. The assessment model in ISO/IEC TS 33074 is provided as an assessment model meeting all the requirements expressed in ISO/IEC 33004.
|
Published |
2020-05 |
Edition : 1 |
Number of pages : 273 |
Technical Committee |
35.080
Software
|
| ISO/IEC CD 33202 |
Software and systems engineering — Core Agile practices |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC 38500:2008 |
Corporate governance of information technology |
ISO/IEC 38500:2008 provides guiding principles for directors of organizations (including owners, board members, directors, partners, senior executives, or similar) on the effective, efficient, and acceptable use of Information Technology (IT) within their organizations.
ISO/IEC 38500:2008 applies to the governance of management processes (and decisions) relating to the information and communication services used by an organization. These processes could be controlled by IT specialists within the organization or external service providers, or by business units within the organization.
It also provides guidance to those advising, informing, or assisting directors.
They include:
senior managers;
members of groups monitoring the resources within the organization;
external business or technical specialists, such as legal or accounting specialists, retail associations, or professional bodies;
vendors of hardware, software, communications and other IT products;
internal and external service providers (including consultants);
IT auditors.
|
Withdrawn |
2008-06 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 8802-1BR:2016 |
Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Specific requirements — Part 1BR: Virtual bridged local area networks — Bridge port extension |
This standard specifies the operation of Bridge Port Extenders, including management, protocols, and algorithms. Bridge Port Extenders operate in support of the MAC Service by Extended Bridges.
|
Published |
2016-10 |
Edition : 1 |
Number of pages : 121 |
Technical Committee |
35.110
Networking
|
| ISO/IEC 40210:2011 |
Information technology — W3C SOAP Version 1.2 Part 1: Messaging Framework (Second Edition) |
SOAP Version 1.2 (SOAP) is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. It uses XML technologies to define an extensible messaging framework providing a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation specific semantics.
ISO/IEC 40210:2011 defines the SOAP messaging framework consisting of:
the SOAP processing model defining the rules for processing a SOAP message;
the SOAP Extensibility model defining the concepts of SOAP features and SOAP modules;
the SOAP underlying protocol binding framework describing the rules for defining a binding to an underlying protocol that can be used for exchanging SOAP messages between SOAP nodes;
the SOAP message construct defining the structure of a SOAP message.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.080
Software
|
| ISO/IEC 40220:2011 |
Information technology — W3C SOAP Version 1.2 Part 2: Adjuncts (Second Edition) |
SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. ISO/IEC 42020:2011 defines a set of adjuncts for use with the SOAP Version 1.2 messaging framework specified in ISO/IEC 42010:2011. ISO/IEC 42020:2011 depends on ISO/IEC 42010:2011.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.080
Software
|
| ISO/IEC 40230:2011 |
Information technology — W3C SOAP Message Transmission Optimization Mechanism |
ISO/IEC 40230:2011 specifies an abstract feature for optimizing the transmission and/or wire format of a SOAP message by selectively encoding portions of the message, while still presenting an XML Infoset to the SOAP application.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
35.080
Software
|
| ISO/IEC 40240:2011 |
Information technology — W3C Web Services Addressing 1.0 — Core |
Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. ISO/IEC 42040:2011 defines a set of abstract properties and an XML Infoset representation thereof to reference Web services and to facilitate end-to-end addressing of endpoints in messages. It enables messaging systems to support message transmission through networks that include processing nodes such as endpoint managers, firewalls, and gateways in a transport-neutral manner.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
35.080
Software
|
| ISO/IEC 40250:2011 |
Information technology — W3C Web Services Addressing 1.0 — SOAP Binding |
Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. ISO/IEC 42050:2011 defines the binding of the abstract properties defined in ISO/IEC 42040 to SOAP Messages.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
35.080
Software
|
| ISO/IEC 40260:2011 |
Information technology — W3C Web Services Addressing 1.0 — Metadata |
Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. ISO/IEC 40260:2011 defines how the abstract properties defined in ISO/IEC 40240 are described using Web Services Description Language (WSDL), how to include WSDL metadata in endpoint references, and how WS-Policy can be used to indicate the support of WS-Addressing by a Web service.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
35.080
Software
|
| ISO/IEC 40270:2011 |
Information technology — W3C Web Services Policy 1.5 — Framework |
ISO/IEC 40270:2011 defines a framework and a model for expressing policies that refer to domain-specific capabilities, requirements, and general characteristics of entities in a Web services-based system.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
35.080
Software
|
| ISO/IEC 40280:2011 |
Information technology — W3C Web Services Policy 1.5 — Attachment |
ISO/IEC 40280:2011 defines two general-purpose mechanisms for associating policies, as defined in ISO/IEC 40270, with the subjects to which they apply. It also defines how these general-purpose mechanisms can be used to associate policies with Web Services Description Language (WSDL) and Universal Description, Discovery and Integration (UDDI) descriptions.
|
Published |
2011-09 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.080
Software
|
| ISO/IEC 40500:2012 |
Information technology — W3C Web Content Accessibility Guidelines (WCAG) 2.0 |
ISO/IEC 40500:2012 [Web Content Accessibility Guidelines (WCAG) 2.0] covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photo-sensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general.
WCAG 2.0 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents.
An overview of WCAG 2.0, the WCAG 2.0 standard, technical and education material supporting implementation of WCAG 2.0, and information on translating WCAG 2.0, are freely available from Web Content Accessibility Guidelines (WCAG) Overview.
|
Published |
2012-10 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 41062:2019 |
Software engineering — Recommended practice for software acquisition |
This recommended practice describes a set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of commercial-off-the-shelf (COTS), custom, or free and open source software (FOSS). Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within the organization's acquisition process. Security will be included as a quality attribute considered during the acquisition.
|
Published |
2019-02 |
Edition : 1 |
Number of pages : 56 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE CD 41062.2 |
Software engineering – Life cycle processes — Software acquisition |
|
Under development |
|
Edition : 2 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC 42010:2007 |
Systems and software engineering — Recommended practice for architectural description of software-intensive systems |
ISO/IEC 42010:2007 addresses the activities of the creation, analysis and sustainment of architectures of software-intensive systems, and the recording of such architectures in terms of architectural descriptions. ISO/IEC 42010:2007 establishes a conceptual framework for architectural description and defines the content of an architectural description. Annexes provide the rationale for key concepts and terminology, the relationships to other standards, and examples of usage.
|
Withdrawn |
2007-07 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 42010:2011 |
Systems and software engineering — Architecture description |
ISO/IEC/IEEE 42010:2011 addresses the creation, analysis and sustainment of architectures of systems through the use of architecture descriptions. A conceptual model of architecture description is established. The required contents of an architecture description are specified. Architecture viewpoints, architecture frameworks and architecture description languages are introduced for codifying conventions and common practices of architecture description. The required content of architecture viewpoints, architecture frameworks and architecture description languages is specified. Annexes provide the motivation and background for key concepts and terminology and examples of applying ISO/IEC/IEEE 42010:2011.
|
Withdrawn |
2011-12 |
Edition : 1 |
Number of pages : 37 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 42010:2022 |
Software, systems and enterprise — Architecture description |
This document specifies requirements for the structure and expression of an architecture description (AD) for various entities, including software, systems, enterprises, systems of systems, families of systems, products (goods or services), product lines, service lines, technologies and business domains.
This document distinguishes the architecture of an entity of interest from an AD expressing that architecture. Architectures are not the subject of this document.
This document specifies requirements for use of the architectural concepts and their relationships as captured in an AD. It does not specify requirements for any entity of interest or its environment.
This document specifies requirements for an architecture description framework (ADF), an architecture description language (ADL), architecture viewpoints and model kinds in order to usefully support the development and use of an AD.
This document specifies conformance to the requirements for an AD, ADF, ADL, architecture viewpoint and model kind.
This document does not specify the processes, architecting methods, models, notations, techniques or tools by which an AD is created, utilized or managed.
This document does not specify any format or media for recording an AD.
|
Published |
2022-11 |
Edition : 2 |
Number of pages : 62 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 42020:2019 |
Software, systems and enterprise — Architecture processes |
This document establishes a set of process descriptions for the governance and management of a collection of architectures and the architecting of entities. This document also establishes an enablement process description that provides support to these other architecture processes.
The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects. These processes are applicable throughout the life of an architecture or a collection of architectures. These processes are applicable for managing and performing the activities within any stage in the life cycle of the architecture entities.
Annex D describes the relationships between this document and other standards.
|
Published |
2019-07 |
Edition : 1 |
Number of pages : 110 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 42030:2019 |
Software, systems and enterprise — Architecture evaluation framework |
This document specifies the means to organize and record architecture evaluations for enterprise, systems and software fields of application.
The aim of this document is to enable architecture evaluations that are used to:
a) validate that architectures address the concerns of stakeholders;
b) assess the quality of architectures with respect to their intended purpose;
c) assess the value of architectures to their stakeholders;
d) determine whether architecture entities address their intended purpose;
e) provide knowledge and information about architecture entities;
f) assess progress towards achieving architecture objectives;
g) clarify understanding of problem space and of stakeholder needs and expectations;
h) identify risks and opportunities associated with architectures; and
i) support decision making where architectures are involved.
NOTE This document addresses the evaluation of an architecture and not an evaluation of the architecture description's suitability. Matters concerning the evaluation of the architecture description fall within the scope of the architecture conceptualization and architecture elaboration processes as defined in ISO/IEC/IEEE 42020. However, it is sometimes the case that the architecture description is evaluated concurrently with the evaluation of the architecture itself.
The entity being evaluated can be of several kinds, as illustrated in the following examples: enterprise, organization, solution, system, subsystem, business, data (as a data element or data structure), application, information technology (as a collection), mission, product, service, software item, hardware item, etc. The kind of entity can also be a product line, family of systems, system of systems, etc. It also spans the variety of applications that utilize digital technology such as mobile, cloud, big data, robotics, Internet of Things (IoT), web, desktop, embedded systems, and so on.
The generic Architecture Evaluation (AE) framework specified in this document can be used in support of the Architecture Evaluation process defined in ISO/IEC/IEEE 42020. Specific frameworks can be derived from this generic framework, which can provide a mapping to the system life cycle processes in ISO/IEC/IEEE 15288 or to the software life cycle processes in ISO/IEC/IEEE 12207.
|
Published |
2019-07 |
Edition : 1 |
Number of pages : 77 |
Technical Committee |
35.080
Software
|
| IEC 81001-5-1:2021 |
Health software and health IT systems safety, effectiveness and security — Part 5-1: Security — Activities in the product life cycle |
This document defines the LIFE CYCLE requirements for development and maintenance of HEALTH SOFTWARE needed to support conformance to IEC 62443-4-1 – taking the specific needs for HEALTH SOFTWARE into account. The set of PROCESSES, ACTIVITIES, and TASKS described in this document establishes a common framework for secure HEALTH SOFTWARE LIFE CYCLE PROCESSES.The purpose is to increase the CYBERSECURITY of HEALTH SOFTWARE by establishing certain ACTIVITIES and TASKS in the HEALTH SOFTWARE LIFE CYCLE PROCESSES and also by increasing the SECURITY of SOFTWARE LIFE CYCLE PROCESSES themselves.It is important to maintain an appropriate balance of the key properties SAFETY, effectiveness and SECURITY as discussed in ISO 81001-1.This document excludes specification of ACCOMPANYING DOCUMENTATION contents.
|
Published |
2021-12 |
Edition : 1 |
|
Technical Committee |
35.080
Software
;
35.240.80
IT applications in health care technology
|
| IEC 82304-1:2016 |
Health software — Part 1: General requirements for product safety |
IEC 82304-1:2016 applies to the safety and security of health software products designed to operate on general computing platforms and intended to be placed on the market without dedicated hardware, and its primary focus is on the requirements for manufacturers. It covers the entire lifecycle including design, development,
validation, installation, maintenance, and disposal of health software products.
|
Published |
2016-10 |
Edition : 1 |
Number of pages : 45 |
Technical Committee |
35.080
Software
;
35.240.80
IT applications in health care technology
|