| Name |
Description |
Abstract |
Status |
Publication date |
Edition |
Number of pages |
Technical committee |
ICS |
| ISO/IEC/IEEE 24748-8:2019 |
Systems and software engineering — Life cycle management — Part 8: Technical reviews and audits on defense programs |
This document establishes the requirements for technical reviews and audits to be performed throughout the acquisition life cycle for the US Department of Defense (DoD) and other defense agencies. This document provides the definition, description, and intent, as well as the entry, exit and success criteria, for each technical review and audit. It is to be used to establish agreement between acquirers and suppliers on the technical reviews and audits that are needed for the project, as well as the focus and expectations of each technical review and audit.
|
Published |
2019-02 |
Edition : 1 |
Number of pages : 154 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE FDIS 24748-9 |
Systems and software engineering — Life cycle management — Part 9: Application of system and software life cycle processes in epidemic prevention and control systems |
|
Under development |
|
Edition : 1 |
Number of pages : 44 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 24748-7000:2022 |
Systems and software engineering — Life cycle management — Part 7000: Standard model process for addressing ethical concerns during system design |
The standard establishes a set of processes by which engineers and technologists can include consideration of ethical values throughout the stages of concept exploration and development, which encompass system initiation, analysis, and design. This standard provides engineers and technologists with an implementable process aligning innovation management processes, system design approaches, and software engineering methods to help address ethical concerns or risks during system design.
IEEE Std 7000™ does not give specific guidance on the design of algorithms to apply ethical values such as fairness and privacy.
|
Published |
2022-11 |
Edition : 1 |
Number of pages : 69 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 24765:2010 |
Systems and software engineering — Vocabulary |
ISO/IEC/IEEE 24765:2010 provides a common vocabulary applicable to all systems and software engineering work. It was prepared to collect and standardize terminology. ISO/IEC/IEEE 24765:2010 is intended to serve as a useful reference for those in the information technology field, and to encourage the use of systems and software engineering standards prepared by ISO and liaison organizations IEEE Computer Society and Project Management Institute. ISO/IEC/IEEE 24765:2010 includes references to the active source standards for each definition so that the use of the term can be further explored.
|
Withdrawn |
2010-12 |
Edition : 1 |
Number of pages : 410 |
Technical Committee |
35.080
Software
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC/IEEE 24765:2017 |
Systems and software engineering — Vocabulary |
ISO/IEC/IEEE 24765:2017 provides a common vocabulary applicable to all systems and software engineering work. It was prepared to collect and standardize terminology. ISO/IEC/IEEE 24765:2017 is intended to serve as a useful reference for those in the information technology field, and to encourage the use of systems and software engineering standards prepared by ISO and liaison organizations IEEE Computer Society and Project Management Institute. ISO/IEC/IEEE 24765:2017 includes references to the active source standards for definitions so that systems and software engineering concepts and requirements can be further explored.
|
Published |
2017-09 |
Edition : 2 |
Number of pages : 522 |
Technical Committee |
35.080
Software
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC TR 24766:2009 |
Information technology — Systems and software engineering — Guide for requirements engineering tool capabilities |
Requirements engineering (RE) is an essential process of the systems and software engineering life cycles. RE has been established as an ISO/IEC standard life cycle process in both ISO/IEC 15288:2008, Systems and software engineering — System life cycle processes and ISO/IEC 12207:2008, Systems and software engineering — Software life cycle processes.
This Technical Report provides guidance on desirable capabilities of RE tools. It supplements ISO/IEC 14102:2008, Information technology — Guideline for the evaluation and selection of CASE tools, which details a set of evaluation criteria for CASE tools without referencing a specific activity or service area.
|
Published |
2009-12 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
35.080
Software
|
| ISO/IEC 24773-1:2019 |
Software and systems engineering — Certification of software and systems engineering professionals — Part 1: General requirements |
This document is part one of the ISO/IEC 24773 series. It contains the requirements which will be common to all other parts of the ISO/IEC 24773 series, for certifications (schemes and bodies) in the domain of software and systems engineering.
|
Published |
2019-03 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
35.080
Software
|
| ISO/IEC DIS 24773-2 |
Software and systems engineering — Certification of software and systems engineering professionals — Part 2: Guidance regarding description of knowledge, skills, and competencies contained in schemes |
|
Under development |
|
Edition : 1 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO/IEC 24773-3:2021 |
Software and systems engineering — Certification of software and systems engineering professionals — Part 3: Systems engineering |
This document elaborates requirements and recommendations for certifications schemes based on ISO/IEC 24773-1, which are specific to the domain of systems engineering.
|
Published |
2021-09 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.080
Software
|
| ISO/IEC 24773:2008 |
Software engineering — Certification of software engineering professionals — Comparison framework |
ISO/IEC 24773:2008 establishes a framework for comparison of schemes for certifying software engineering professionals. A certification scheme is a set of certification requirements for software engineering professionals. ISO/IEC 24773:2008 specifies the items that a scheme is required to contain and indicates what should be defined for each item.
ISO/IEC 24773:2008 will facilitate the portability of software engineering professional certifications between different countries or organizations. At present, different countries and organizations have adopted different approaches on the topic that are implemented by means of regulations and bylaws. The intention of ISO/IEC 24773:2008 is to be open to these individual approaches by providing a framework for expressing them in a common scheme that can lead to understanding.
|
Withdrawn |
2008-09 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 24774:2021 |
Systems and software engineering — Life cycle management — Specification for process description |
This document provides an explanation of considerations involved in defining a process. This document gives requirements and recommendations for the description of processes by identifying elements and rules for their formulation.
This document also describes the use of process views.
This document explains how conformance to a process can be defined, when the process is described in accordance with this document.
This document does not describe how processes are composed or otherwise aggregated into larger frameworks or life cycle models. Nor does the document cover how to assess or evaluate the performance of a process, or the output (products) of a process.
NOTE Two prominent International Standards in process description for software and system engineering are ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288. These two standards have very similar process models. The information items associated with their process definitions are given in ISO/IEC/IEEE 15289. Other International Standards provide further characterization of a single life cycle process by elaborating the process elements and levying specific requirements on the execution of the process.
This document is applicable when processes are described for various process definitions in any party, organization or standard relating to systems and software engineering processes.
|
Published |
2021-05 |
Edition : 1 |
Number of pages : 28 |
Technical Committee |
35.080
Software
;
35.080
Software
|
| ISO/IEC TR 24774:2007 |
Software and systems engineering — Life cycle management — Guidelines for process description |
An increasing number of international, national and industry standards describe process models. These models are developed for a range of purposes including process implementation and assessment. The terms and descriptions used in such models vary in format, content and level of prescription. ISO/IEC TR 24774:2007 presents guidelines for the elements used most frequently in describing a process: the title, purpose statement, outcomes, activities and tasks. Whilst the primary purpose of ISO/IEC TR 24774:2007 is to encourage consistency in standard process reference models, the guidelines it provides may be applied to any process model developed for any purpose.
|
Withdrawn |
2007-09 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 24774:2010 |
Systems and software engineering — Life cycle management — Guidelines for process description |
An increasing number of international, national and industry standards describe process models. These models are developed for a range of purposes including process implementation and assessment. The terms and descriptions used in such models vary in format, content and level of prescription. ISO/IEC TR 24774:2010 presents guidelines for the elements used most frequently in describing a process: the title, purpose, outcomes, activities, task and information item. Whilst the primary purpose of ISO/IEC TR 24774:2010 is to encourage consistency in standard process reference models, the guidelines it provides can be applied to any process model developed for any purpose.
|
Withdrawn |
2010-09 |
Edition : 2 |
Number of pages : 15 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25000:2005 |
Software Engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Guide to SQuaRE |
ISO/IEC 25000:2005 provides guidance for the use of the new series of International Standards named Software product Quality Requirements and Evaluation (SQuaRE). The purpose of this guide is to provide a general overview of SQuaRE contents, common reference models and definitions, as well as the relationship among the documents, allowing users of this guide a good understanding of those series of International Standards, according to their purpose of use. This document contains an explanation of the transition process between the old ISO/IEC 9126 and the 14598 series and SQuaRE, and also presents information on how to use the ISO/IEC 9126 and 14598 series in their previous form.
SQuaRE provides:
Terms and definitions,Reference models,General guide,Individual division guides, andStandards for requirements specification, planning and management, measurement and evaluation purposes.
|
Withdrawn |
2005-08 |
Edition : 1 |
Number of pages : 41 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25000:2014 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Guide to SQuaRE |
ISO/IEC 25000:2014 provides guidance for the use of the new series of International Standards named Systems and software Quality Requirements and Evaluation (SQuaRE). The purpose of ISO/IEC 25000:2014 is to provide a general overview of SQuaRE contents, common reference models and definitions, as well as the relationship among the documents, allowing users of the Guide a good understanding of those series of standards, according to their purpose of use. It also contains an explanation of the transition process between the old ISO/IEC 9126 and the ISO/IEC 14598 series and SQuaRE.
|
Published |
2014-03 |
Edition : 2 |
Number of pages : 27 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25001:2007 |
Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Planning and management |
ISO/IEC 25001:2007 provides details about the planning and management requirements associated with software product quality requirements and evaluation.
While it is mainly concerned with product quality requirements and evaluation, wherever it is relevant the corresponding process requirements and evaluation activities are also discussed.
ISO/IEC 25001:2007 aims to clarify the requirements which should be identified by the organization in order to ensure the success of specifying quality requirements and executing the evaluation.
ISO/IEC 25001:2007 is intended to be used in conjunction with the other parts of the SQuaRE series (ISO/IEC 25000-ISO/IEC 25051) of International Standards, and with ISO/IEC 14598 and ISO/IEC 9126-1 until superseded by the ISO/IEC 25000 series of International Standards.
ISO/IEC 25001:2007 complies with the technical processes identified in ISO/IEC 15288 related to quality requirements definition and analysis.
|
Withdrawn |
2007-02 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25001:2014 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Planning and management |
ISO/IEC 25001:2014 provides requirements and recommendations for an organization responsible for implementing and managing the systems and software product quality requirements specification and evaluation activities through the provision of technology, tools, experiences, and management skills.
The role of the evaluation group includes motivating employees and training them for the requirements specification and the evaluation activities, preparing appropriate documents, identification or development of required methods, and responding to queries on relevant technologies.
Technology management is related to the planning and management of a systems and software quality requirements specification and evaluation process, measurements and tools. This includes the management of development, acquisition, standardisation, control, transfer and feedback of requirements specification and evaluation technology experiences within the organisation.
The intended users of ISO/IEC 25001:2014 are those responsible for:
managing technologies used for requirements specification and evaluation execution,
specifying systems and software product quality requirements,
supporting systems and software product quality evaluation,
managing systems and software development organisations,
as well as those in a quality assurance function. However, it is also applicable to managers involved in other systems or software related activities.
|
Published |
2014-03 |
Edition : 2 |
Number of pages : 13 |
Technical Committee |
35.080
Software
|
| ISO/IEC DIS 25002 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality models overview and usage |
|
Under development |
|
Edition : 1 |
Number of pages : 18 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25010:2011 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — System and software quality models |
ISO/IEC 25010:2011 defines:
A quality in use model composed of five characteristics (some of which are further subdivided into subcharacteristics) that relate to the outcome of interaction when a product is used in a particular context of use. This system model is applicable to the complete human-computer system, including both computer systems in use and software products in use.
A product quality model composed of eight characteristics (which are further subdivided into subcharacteristics) that relate to static properties of software and dynamic properties of the computer system. The model is applicable to both computer systems and software products.
The characteristics defined by both models are relevant to all software products and computer systems. The characteristics and subcharacteristics provide consistent terminology for specifying, measuring and evaluating system and software product quality. They also provide a set of quality characteristics against which stated quality requirements can be compared for completeness.
Although the scope of the product quality model is intended to be software and computer systems, many of the characteristics are also relevant to wider systems and services.
ISO/IEC 25012 contains a model for data quality that is complementary to this model.
The scope of the models excludes purely functional properties, but it does include functional suitability.
The scope of application of the quality models includes supporting specification and evaluation of software and software-intensive computer systems from different perspectives by those associated with their acquisition, requirements, development, use, evaluation, support, maintenance, quality assurance and control, and audit. The models can, for example, be used by developers, acquirers, quality assurance and control staff and independent evaluators, particularly those responsible for specifying and evaluating software product quality. Activities during product development that can benefit from the use of the quality models include:
identifying software and system requirements;
validating the comprehensiveness of a requirements definition;
identifying software and system design objectives;
identifying software and system testing objectives;
identifying quality control criteria as part of quality assurance;
identifying acceptance criteria for a software product and/or software-intensive computer system;
establishing measures of quality characteristics in support of these activities.
|
Published |
2011-03 |
Edition : 1 |
Number of pages : 34 |
Technical Committee |
35.080
Software
|
| ISO/IEC DIS 25010 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Product quality model |
|
Under development |
|
Edition : 2 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 25011:2017 |
Information technology — Systems and software Quality Requirements and Evaluation (SQuaRE) — Service quality models |
ISO/IEC TS 25011:2017 is applicable to IT services that support the needs of an individual user or a business. IT services can be delivered personally or remotely by people, or by an IT application that could be in a local or remote location (see Annex A).
These include two types of IT services:
a) services completely automated provided by an IT system;
b) services provided by a human using an IT system.
ISO/IEC TS 25011:2017 describes the use of two quality models for IT services.
a) ISO/IEC TS 25011:2017 defines an IT service quality model composed of eight characteristics (which are further subdivided into sub-characteristics) that relate to properties of the IT service made up from a combination of elements including people, processes, technology, facilities and information.
b) ISO/IEC TS 25011:2017 describes how the quality in use model in ISO/IEC 25010 which is composed of five characteristics (some of them are further subdivided into sub-characteristics) can be applied to the outcome when an IT service is used in a particular context of use. This model is applicable to the complete service provision system composed of people, processes, technology, facilities and information.
The characteristics and sub-characteristics provide consistent terminologies and check lists for specifying, measuring and evaluating IT service quality.
The use of the IT service quality models can help:
- IT service providers to identify service quality requirements, and evaluate and improve the quality of the service provided;
- customers to specify their requirements for the quality of service, define the acceptance criteria for service, and evaluate the quality of an IT service; and
- a third party to evaluate the quality of an IT service.
|
Published |
2017-06 |
Edition : 1 |
Number of pages : 21 |
Technical Committee |
35.080
Software
|
| ISO/IEC 2382-25:1992 |
Information technology — Vocabulary — Part 25: Local area networks |
Defines different types of local area networks, concepts relating to devices, to transmissions and the problems that can appear, and also protocols that govern exchanges, in total 75 terms in English and French. Includes alphabetic indices of the terms in English and French.
|
Withdrawn |
1992-04 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.110
Networking
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 25012:2008 |
Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Data quality model |
ISO/IEC 25012:2008 defines a general data quality model for data retained in a structured format within a computer system.
ISO/IEC 25012:2008 can be used to establish data quality requirements, define data quality measures, or plan and perform data quality evaluations. It could be used, for example,
to define and evaluate data quality requirements in data production, acquisition and integration processes,
to identify data quality assurance criteria, also useful for re-engineering, assessment and improvement of data,
to evaluate the compliance of data with legislation and/or requirements.
ISO/IEC 25012:2008 categorizes quality attributes into fifteen characteristics considered by two points of view: inherent and system dependent. Data quality characteristics will be of varying importance and priority to different stakeholders.
ISO/IEC 25012:2008 is intended to be used in conjunction with the other parts of the SQuaRE series of International Standards, and with ISO/IEC 9126-1 until superseded by ISO/IEC 25010.
|
Published |
2008-12 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
35.080
Software
|
| ISO/IEC DIS 25019 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality-in-use model |
|
Under development |
|
Edition : 1 |
Number of pages : 31 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25020:2007 |
Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Measurement reference model and guide |
ISO/IEC 25020:2007 provides a measurement reference model and guide for measuring the quality characteristics defined in ISO/IEC 2501n, Quality Model Division. ISO/IEC 25020:2007 sets requirements for the selection and construction of quality measures. It also contains informative annexes addressing the following topics: criteria for selecting software quality measures and quality measure elements, demonstrating predictive validity and assessing measurement reliability, and an example format for documenting software quality measures.
The Quality Measurement Division, of which ISO/IEC 25020 is a member, also offers examples of quality measures that can be used across the product development life cycle. These measures are defined in the other documents in the division and correspond to the quality characteristics in a software product quality model such as that described in ISO/IEC 25010. ISO/IEC 25020:2007 and the quality measures are designed to be used, in particular, with other standards in the SQuaRE series that address quality requirements (ISO/IEC 25030) and product quality evaluation (ISO/IEC 25040).
|
Withdrawn |
2007-05 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25020:2019 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality measurement framework |
This document provides a framework for developing quality measurement.
The contents of this document are as follows:
— quality measurement reference model;
— relationships among different types of quality measures;
— guidelines for selecting quality measures;
— guidelines for constructing quality measures;
— guidelines for planning and performing measurements;
— guidelines for the application of measurement results.
It includes considerations for selecting quality measures and quality measure elements (Annex A), assessing the reliability of measurement and the validity of quality measures (Annex B), elements for documenting quality measures (Annex C), normalized measurement function for quality measures (Annex D) and the measurement information model in ISO/IEC/IEEE 15939 (Annex E).
This document can be applied for designing, identifying, evaluating and executing the measurement model of system and software product quality, quality in use, data quality and IT service quality. This reference model can be used by developers, acquirers, quality assurance staff and independent evaluators—essentially by people responsible for specifying and evaluating the quality of information and communication technology (ICT) systems and services.
|
Published |
2019-07 |
Edition : 2 |
Number of pages : 27 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25021:2012 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality measure elements |
ISO/IEC 25021:2012 provides guides to specify Quality Measure Elements (QME) and initial set of QME as examples. QME is a measure defined in terms of a property and the measurement method for quantifying it, including optionally the transformation by a mathematical function.
ISO/IEC 25021:2012 is intended to be used throughout the system and software product life cycle used with other documents of the ISO/IEC 250nn SQuaRE series, especially ISO/IEC 25022, ISO/IEC 25023 and ISO/IEC 25024.
|
Published |
2012-11 |
Edition : 1 |
Number of pages : 37 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 25025:2021 |
Information technology — Systems and software Quality Requirements and Evaluation (SQuaRE) — Measurement of IT service quality |
This document defines quality measures useful for requirements and evaluation of IT service quality in terms of characteristics and sub-characteristics defined in ISO/IEC TS 25011.
This document contains a basic set of quality measures for each characteristic and sub-characteristic.
This document does not assign ranges of values of the quality measures to rated levels or to grades of compliance. Such values are defined based on the nature of the IT service, and so depends on factors such as category of the IT service or users' needs. Some attributes can have a desirable range of values, which does not depend on specific user needs but generic factors, for example, service downtime. This document includes, in Annex A, considerations for the selection and application of quality measures.
The quality measures in this document are primarily intended to be used for quality evaluation and improvement of IT services during or after the development life cycle.
The main users of this document are people carrying out quality requirements specification and evaluation activities for IT services as part of the following:
— development: including requirements analysis, design, implementation, testing and deployment during the development life cycle;
— quality management: monitoring activities of quality assurance and performing quality control of an IT service;
— supply: making a contract with the user for supplying an IT service under the terms of a contract;
— acquisition: including IT service selection, when acquiring or procuring an IT service from a service provider;
— maintenance: improvement of an IT service based on quality measurement.
The relationship of this document to domain-specific IT service quality model and its precedence over this document is determined by the user in a specific context of use.
|
Published |
2021-03 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 25021:2007 |
Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Quality measure elements |
ISO/IEC TR 25021:2007 defines the set of quality measure elements to be used throughout the software product life cycle for the purpose of Software Product Quality Requirement and Evaluation (SQuaRE). While some quality measure elements can be used as standalone quality measures, their main purpose is to be the building blocks for other SQuaRE measurements as described in ISO/IEC TR 9126-2, ISO/IEC TR 9126-3 and ISO/IEC TR 9126-4. ISO/IEC TR 25021:2007 constitutes the link between ISO/IEC 9126 and the subsequent SQuaRE series of standards.
ISO/IEC TR 25021:2007 contains informative annexes documenting the cross-reference relationship between the quality measure elements and quality measures, characteristics and subcharacteristics defined in ISO/IEC 9126.
The Quality Measurement Division, of which ISO/IEC TR 25021:2007 is a member, also offers examples of quality measures that can be used across the product development life-cycle. These measures are defined in the other documents in the division and correspond to the quality characteristics in a software product quality model such as that described in the future International Standard ISO/IEC 25010 (replacing ISO/IEC 9126-1). ISO/IEC TR 25021:2007 is designed to be used, in particular, with other standards in the SQuaRE series that address quality requirements (ISO/IEC 25030) and product quality evaluation (the future International Standard ISO/IEC 25040).
|
Withdrawn |
2007-10 |
Edition : 1 |
Number of pages : 59 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25022:2016 |
Systems and software engineering — Systems and software quality requirements and evaluation (SQuaRE) — Measurement of quality in use |
ISO/IEC 25022:2016 defines quality in use measures for the characteristics defined in ISO/IEC 25010, and is intended to be used together with ISO/IEC 25010. It can be used in conjunction with the ISO/IEC 2503n and the ISO/IEC 2504n standards or to more generally meet user needs with regard to product or system quality.
ISO/IEC 25022:2016 contains the following:
- a basic set of measures for each quality in use characteristic;
- an explanation of how quality in use is measured.
It provides a suggested set of quality in use measures to be used with the quality in use model in ISO/IEC 25010. They are not intended to be an exhaustive set.
It includes as informative annexes examples of how to measure context coverage (Annex A), options for normalising quality in use measures (Annex B), use of ISO/IEC 25022 for measuring usability in ISO 9241‑11 (Annex C), a quality in use evaluation process (Annex D), the relationship between different quality models (Annex E), and quality measurement concepts (Annex F).
The measures are applicable to the use of any human-computer system, including both computer systems in use and software products that form part of the system.
It does not assign ranges of values of the measures to rated levels or to grades of compliance because these values are defined for each system or product depending, on the context of use and users' needs.
Some attributes could have a desirable range of values, which does not depend on specific user needs but depends on generic factors, for example, human cognitive factors.
The proposed quality in use measures are primarily intended to be used for quality assurance and management of systems and software products based on their effects when actually used. The main users of the measurement results are people managing development, acquisition, evaluation, or maintenance of software and systems.
The main users of ISO/IEC 25022:2016 are people carrying out specification and evaluation activities as part of the following:
- development: including requirements analysis, design, and testing through acceptance during the life cycle process;
- quality management: systematic examination of the product or computer system, for example, when evaluating quality in use as part of quality assurance and quality control;
- supply: a contract with the acquirer for the supply of a system, software product, or software service under the terms of a contract, for example, when validating quality at qualification test;
- acquisition: including product selection and acceptance testing, when acquiring or procuring a system, software product, or software service from a supplier;
- maintenance: improvement of the product based on quality in use measures.
|
Published |
2016-06 |
Edition : 1 |
Number of pages : 41 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25023:2016 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Measurement of system and software product quality |
ISO/IEC 25023:2016 defines quality measures for quantitatively evaluating system and software product quality in terms of characteristics and subcharacteristics defined in ISO/IEC 25010 and is intended to be used together with ISO/IEC 25010. It can be used in conjunction with the ISO/IEC 2503n and the ISO/IEC 2504n standards or to more generally meet user needs with regard to software product or system quality.
ISO/IEC 25023:2016 contains the following:
- a basic set of quality measures for each characteristic and subcharacteristics;
- an explanation of how to apply software product and system quality measures.
It includes, as informative annexes, considerations for the use of quality measures (Annex A), QMEs used to define product or system quality measures (Annex B), and detailed explanation of measurement types (Annex C).
ISO/IEC 25023:2016 does not assign ranges of values of the measures to rated levels or to grades of compliance because these values are defined based on the nature of the system, product or a part of the product, and depending on factors such as category of the software, integrity level, and users' needs. Some attributes could have a desirable range of values, which does not depend on specific user needs but depends on generic factors; for example, human cognitive factors.
The proposed quality measures are primarily intended to be used for quality assurance and improvement of system and software products during or post the development life cycle process.
The main users of ISO/IEC 25023:2016 are people carrying out quality requirement specification and evaluation activities as part of the following:
- development: including requirements analysis, design specification, coding and testing through acceptance during the life cycle process;
- quality management: systematic examination of the software product or computer system, for example, when evaluating system or software product quality as part of quality assurance, quality control and quality certification;
- supply: a contract with the acquirer for the supply of a system, software product or software service under the terms of a contract, for example, when validating quality at qualification test;
- acquisition: including product selection and acceptance testing, when acquiring or procuring a system, software product or software service from a supplier;
- maintenance: improvement of the software product or system based on quality measurement.
|
Published |
2016-06 |
Edition : 1 |
Number of pages : 45 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25024:2015 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Measurement of data quality |
ISO/IEC 25024:2015 defines data quality measures for quantitatively measuring the data quality in terms of characteristics defined in ISO/IEC 25012.
ISO/IEC 25024:2015 contains the following:
- a basic set of data quality measures for each characteristic;
- a basic set of target entities to which the quality measures are applied during the data-life-cycle;
- an explanation of how to apply data quality measures;
- a guidance for organizations defining their own measures for data quality requirements and evaluation.
It includes, as informative annexes, a synoptic table of quality measure elements defined in this International standard (Annex A), a table of quality measures associated to each quality measure element and target entitiy (Annex B), considerations about specific quality measure elements (Annex C), a list of quality measures in alphabetic order (Annex D), and a table of quality measures grouped by characteristics and target entities (Annex E).
This International Standard does not define ranges of values of these quality measures to rate levels or grades because these values are defined for each system by its nature depending on the system context and users' needs.
This International Standard can be applied to any kind of data retained in a structured format within a computer system used for any kinds of applications.
People managing data and services including data are the primary beneficiaries of the quality measures.
This International Standard is intended to be used by people who need to produce and/or use data quality measures while pursuing their responsibilities.
- Acquirer (an individual or organization that acquires or procures data from a supplier).
- Evaluator (an individual or organization that performs an evaluation, which can, for example, be a testing laboratory, the quality department of an organization, a government organization, or a user).
- Developer (an individual or organization that performs development activities including requirements, analysis, design, implementation, and testing data during the data-life-cycle).
- Maintainer (an individual or organization that performs operation and maintenance activities of data).
- Supplier (an individual or organization that enters into a contract with the acquirer for the supply of data or service under the terms of the contract).
- User (an individual or organization that uses data to perform a specific function).
- Quality manager (an individual or organization that performs a systematic examination of the data).
- Owner (an individual or organization that takes responsibility for the management and financial value of the data with the legal authority and responsibility to establish for them evaluation, collections, access, dissemination, storage, security, and cancellation).
ISO/IEC 25024:2015 takes into account a large range of data of target entities.
It can be applied in many types of information systems, for example, such as follows:
- legacy information system;
- data warehouse;
- distributed information system;
- cooperative information system;
- world wide web.
The scope does not include the following:
- knowledge representation;
- data mining techniques;
- statistical significance for random sample.
|
Published |
2015-10 |
Edition : 1 |
Number of pages : 45 |
Technical Committee |
35.080
Software
|
| ISO/IEC PRF 5021-1 |
Telecommunications and information exchange between systems — Wireless LAN Access Control — Part 1: Networking architecture specification |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.110
Networking
|
| ISO/IEC 25030:2007 |
Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Quality requirements |
ISO/IEC 25030:2007 provides requirements and recommendations for the specification of software quality requirements. It applies to both acquirers and suppliers. It focuses on software quality requirements, but takes a system perspective since software is normally developed and applied as part of a larger system.
Software product quality requirements are needed for:
specification (including contractual agreement and call for tender);planning (including feasibility analysis);development (including early identification of potential quality problems during development); andevaluation (including objective assessment and certification of software product quality).
If software quality requirements are not stated clearly, they may be viewed, interpreted, implemented and evaluated differently by different people. This may result in: software which is inconsistent with user expectations and of poor quality; users, clients and developers who are unsatisfied; and time and cost overruns to rework software.
ISO/IEC 25030:2007 helps to improve the quality of software quality requirements. It does this by providing requirements and recommendations for quality requirements, and guidance for the processes used to define and analyse quality requirements. It applies the quality model defined in ISO/IEC 9126-1 [ISO/IEC 25010] and it complies with the requirement processes defined in ISO/IEC 15288.
ISO/IEC 25030 is part of the SQuaRE series of International Standards.
|
Withdrawn |
2007-06 |
Edition : 1 |
Number of pages : 36 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25030:2019 |
Systems and software engineering — Systems and software quality requirements and evaluation (SQuaRE) — Quality requirements framework |
This document provides the framework for quality requirements for systems, software products and data, which includes concept of the quality requirements, and requirements and recommendations for the processes and methods to elicit, define, use and govern them. Intended readers of this document include, but are not limited to:
— acquirers: evaluate if the system/software products/data fulfills their value proposition, i.e., meets the expected quality,
— developers: design, implement and test the system/software products/data to ensure that it meets the expected quality,
— testers: verify and validate that the system/software products/data meets the expected quality,
— project managers: plan, monitor and control the achievement of the expected quality, and
— independent evaluators: evaluate the system/software products/data with the objective criteria.
This document complies with the technical processes defined in ISO/IEC/IEEE 15288, which are relevant for elicitation of stakeholders' quality needs and for defining, analyzing and maintaining quality requirements. In this document, the quality models in ISO/IEC 25010 and ISO/IEC 25012 are used to categorize quality requirements and to provide a basis for quantifying them in terms of quality measures in the quality measure division of ISO/IEC 2502n.
This document does not cover specification of the other requirements (such as functional requirements, process requirements, etc.), and prescribes neither any specific quality measure nor any specific development process.
|
Published |
2019-08 |
Edition : 2 |
Number of pages : 46 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25040:2011 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Evaluation process |
ISO/IEC 25040:2011 contains requirements and recommendations for the evaluation of software product quality and clarifies the general concepts. It provides a process description for evaluating software product quality and states the requirements for the application of this process. The evaluation process can be used for different purposes and approaches. The process can be used for the evaluation of the quality of pre-developed software, commercial-off-the-shelf software or custom software and can be used during or after the development process.
ISO/IEC 25040:2011 establishes the relationship of the evaluation reference model to the SQuaRE documents as well as shows how each SQuaRE document should be used during the activities of the evaluation process.
It is intended for those responsible for software product evaluation and is appropriate for developers, acquirers and independent evaluators of software products. These three different approaches are detailed in ISO/IEC 14598-3, ISO/IEC 14598-4, and ISO/IEC 14598-5.
It is not intended for evaluation of other aspects of software products (such as functional requirements, process requirements, business requirements, etc.).
|
Published |
2011-03 |
Edition : 1 |
Number of pages : 45 |
Technical Committee |
35.080
Software
|
| ISO/IEC CD 25040.2 |
Systems and software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – Quality evaluation framework |
This document provides the concepts relating to the quality evaluation of the ICT products, IT service, and data, and requirements for its planning. It intends to be used by those who need to perform quality evaluations on target entities, including development organization (integrators, developers, and quality assurance group), acquirers, and independent evaluators. It does not cover any conformance assessment by a certification body.
|
Under development |
|
Edition : 2 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC 25041:2012 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Evaluation guide for developers, acquirers and independent evaluators |
ISO/IEC 25041:2012 provides requirements, recommendations and guidelines for system and software product quality evaluation, for the application of ISO/IEC 25040. Intended audiences of ISO/IEC 25041:2012 are developers, acquirers and independent evaluators of the system and software product. ISO/IEC 25041:2012 is part of ISO/IEC 250nn SQuaRE series of International Standards. It is not limited to any specific application area, and can be used for quality evaluation of any type of system and software product.
|
Published |
2012-10 |
Edition : 1 |
Number of pages : 52 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26560:2019 |
Software and systems engineering — Tools and methods for product line product management |
This document, within the context of methods and tools for product line product management:
— defines product line-specific processes and their subprocesses for product management of software and systems product lines. Those processes are described in terms of purpose, inputs, tasks and outcomes;
— defines method capabilities to support the defined tasks of each process;
— defines tool capabilities to automate/semi-automate tasks or defined method capabilities.
This document does not concern processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.
|
Published |
2019-05 |
Edition : 1 |
Number of pages : 48 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25045:2010 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Evaluation module for recoverability |
ISO/IEC 25045:2010 is one of the SQuaRE series of International Standards, which provides a framework for software products quality requirements and evaluation including the requirements for methods of software product measurement and evaluation.
ISO/IEC 25045:2010 uses a methodology involving two types of evaluation for recoverability. One part of the method makes use of the disturbance injection methodology and a list of disturbances based on common categories of operational faults and events to evaluate the quality measure of resiliency. The second quality measure is based on a set of questions that is defined for each disturbance to evaluate the quality measure of autonomic recovery index by assessing how well the system detects, analyses, and resolves the disturbance without human intervention.
ISO/IEC 25045:2010 is applicable to information systems executing transactions in a system supporting single or multiple concurrent users, where speedy recovery and ease of managing recovery is important to the acquirer, owner/operator, and the developer.
|
Published |
2010-09 |
Edition : 1 |
Number of pages : 37 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25051:2006 |
Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Requirements for quality of Commercial Off-The-Shelf (COTS) software product and instructions for testing |
ISO/IEC 25051:2005 defines quality requirements for COTS software products. A COTS software product includes the product description, the user documentation, and the software contained on a computer sensible media. The quality requirements, functionality, reliability, usability, efficiency, maintainability, portability, and quality in use are consistent with the definitions of SQuaRE.
In addition to the quality requirements, ISO/IEC 25051:2005 also defines requirements for test documentation. The test documentation purpose is to demonstrate the conformity of the software with the requirements. The documentation contains a test plan, the description of the tests cases, and the tests results.
ISO/IEC 25051:2005 can be used by suppliers, certification bodies, testing laboratories, accreditation bodies, regulatory authorities and acquirers.
|
Withdrawn |
2006-04 |
Edition : 1 |
Number of pages : 27 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25051:2006/Cor 1:2007 |
Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Requirements for quality of Commercial Off-The-Shelf (COTS) software product and instructions for testing — Technical Corrigendum 1 |
|
Withdrawn |
2007-07 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25051:2014 |
Software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing |
ISO/IEC 25051:2014 establishes:
quality requirements for Ready to Use Software Product (RUSP);
requirements for test documentation for the testing of RUSP, including test plan, test description, and test results;
instructions for conformity evaluation of RUSP.
It includes also recommendations for safety or business critical RUSP.
ISO/IEC 25051:2014 deals only with providing the user with confidence that the RUSP will perform as offered and delivered. It does not deal with the production realization (including activities and intermediate products, e.g. specifications). The quality system of a supplier is outside the scope of ISO/IEC 25051:2014.
|
Published |
2014-02 |
Edition : 2 |
Number of pages : 33 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 25052-1:2022 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE): cloud services — Part 1: Quality model |
This document defines the quality model of cloud services.
The quality model of cloud services is composed of nine characteristics (some of which are further subdivided into subcharacteristics), which provide consistent terminology for specifying, measuring and evaluating cloud services so that the stakeholders, cloud service customer (CSC), cloud service provider (CSP) and cloud service partner (CSN) have a common understanding.
Since the quality model in this document is the extension to the existing quality models defined in ISO/IEC 2501n, it can be used with the product quality model, IT service quality model, data quality model, and quality-in-use model according to evaluation purposes. As there are several cloud service categories, this document focuses on the quality model of SaaS (Software as a Service).
NOTE Future documents are intended to address PaaS (Platform as a Service) and IaaS (Infrastructure as a Service).
|
Published |
2022-07 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.080
Software
|
| ISO/IEC PRF 25059 |
Software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality model for AI systems |
|
Under development |
2023-06 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25064:2013 |
Systems and software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Common Industry Format (CIF) for usability: User needs report |
ISO/IEC 25064:2013 describes the Common Industry Format (CIF) for user needs reports, and provides specifications for their contents and format, including the content elements to be provided. User needs reports include both the collection and documentation of information from various sources relevant to user needs, and the analysis and integration of this information into consolidated user needs.
User needs reports are applicable to software and hardware systems, products or services (excluding generic products, such as a display screen or keyboard). The content elements are intended to be used as part of system-level documentation resulting from development processes such as those in ISO 9241-210 and ISO/IEC JTC 1/SC 7 process standards. User needs are a major input into the establishment of user requirements.
User needs reports are intended to be used as part of system-level documentation resulting from development processes such as those in ISO 9241-210 and ISO/IEC JTC 1/SC 7 process standards.
|
Published |
2013-09 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO/TR 25060:2023 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — General framework for Common Industry Format (CIF) for usability-related information |
This document describes information items enabling systematic human-centred design for interactive systems.
Some of these information items are elaborated by separate International Standards, named the Common Industry Format (CIF) for usability-related information.
This document provides the framework of information items, including definitions and the content for each information item.
This document includes the following:
— the intended users of the information items;
— consistent terminology;
— the high-level content structure to be used for documenting each information item.
The information items are intended to be used as part of system-level documentation resulting from development processes such as those in ISO 9241-210, ISO 9241-220 and ISO/IEC JTC 1/SC 7 process standards (e.g. ISO/IEC/IEEE 15288, ISO/IEC/IEEE 29148).
This document focuses on those information items needed for design, development and evaluation of usable systems, rather than prescribing a specific process. It is intended to be used in conjunction with existing International Standards, including the standards of the ISO 9241 series and the SQuaRE documents.
This document does not prescribe any kind of method, life cycle or process.
NOTE The information items produced by human-centred design activities can be incorporated in design approaches as diverse as object-oriented, waterfall, HFI (human factors integration), agile and rapid development.
|
Published |
2023-04 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 25060:2010 |
Systems and software engineering — Systems and software product Quality Requirements and Evaluation (SQuaRE) — Common Industry Format (CIF) for usability: General framework for usability-related information |
ISO/IEC TR 25060:2010 describes a potential family of International Standards, named the Common Industry Formats (CIF), that document the specification and evaluation of the usability of interactive systems. It provides a general overview of the CIF framework and contents, definitions, and the relationship of the framework elements. The intended users of the framework are identified, as well as the situations in which the framework may be applied. The assumptions and constraints of the framework are also enumerated.
The framework content includes the following:
consistent terminology and classification of specification, evaluation and reporting;
a definition of the type and scope of formats and the high-level structure to be used for documenting required information and the results of evaluation.
ISO/IEC TR 25060:2010 is applicable to software and hardware products used for predefined tasks. The information items are intended to be used as part of system-level documentation resulting from development processes such as those in ISO 9241-210, and ISO/IEC JTC 1/SC 7 process standards.
ISO/IEC TR 25060:2010 focuses on documenting those elements needed for design and development of usable systems, rather than prescribing a specific process. It is intended to be used in conjunction with existing International Standards, including ISO 9241, ISO 20282, ISO/IEC 9126 and the SQuaRE series (ISO/IEC 25000 to ISO/IEC 25099).
ISO/IEC TR 25060:2010 does not prescribe any kind of method, life cycle or process.
|
Withdrawn |
2010-07 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO/DIS 25062 |
Systems and software engineering — Systems and Software Quality Requirements and Evaluation (SQuaRE) — Common Industry Format (CIF) for usability: Reporting usability evaluations |
ISO/IEC 25062:2006 provides a standard method for reporting usability test findings. The format is designed for reporting results of formal usability tests in which quantitative measurements were collected, and is particularly appropriate for summative/comparative testing. The CIF does not indicate how to perform a usability test but provides guidance on how to report the results of a usability test. The CIF targets two audiences: usability professionals and stakeholders in an organization. Stakeholders can use the usability data to help make informed decisions concerning the release of software products or the procurement of such products.
The format includes the following elements:
the description of the product,the goals of the test,the test participantsthe tasks the users were asked to perform,the experimental design of the test,the method or process by which the test was conducted,the usability measures and data collection methods, andthe numerical results.
|
Under development |
|
Edition : 1 |
Number of pages : 23 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25062:2006 |
Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Common Industry Format (CIF) for usability test reports |
ISO/IEC 25062:2006 provides a standard method for reporting usability test findings. The format is designed for reporting results of formal usability tests in which quantitative measurements were collected, and is particularly appropriate for summative/comparative testing. The CIF does not indicate how to perform a usability test but provides guidance on how to report the results of a usability test. The CIF targets two audiences: usability professionals and stakeholders in an organization. Stakeholders can use the usability data to help make informed decisions concerning the release of software products or the procurement of such products.
The format includes the following elements:
the description of the product,the goals of the test,the test participantsthe tasks the users were asked to perform,the experimental design of the test,the method or process by which the test was conducted,the usability measures and data collection methods, andthe numerical results.
|
Published |
2006-04 |
Edition : 1 |
Number of pages : 46 |
Technical Committee |
35.080
Software
|
| ISO/IEC 25063:2014 |
Systems and software engineering — Systems and software product Quality Requirements and Evaluation (SQuaRE) — Common Industry Format (CIF) for usability: Context of use description |
ISO/IEC 25063:2014 describes the Common Industry Format (CIF) for context of use descriptions and specifies the contents of both high-level and detailed descriptions of the context of use for an existing, intended, implemented or deployed system. A context-of-use description includes information about the users and other stakeholder groups, the characteristics of each user group, the goals of the users, the tasks of the users, and the environment(s) in which the system is used.
The context of use description is applicable to software and hardware systems, products or services (excluding generic products, such as a display screen or keyboard). It is important to gather and analyse information on the current context in order to understand and then describe the context that will apply in the future system. The context of use description provides a collection of data relevant for analysis, specification, design and evaluation of an interactive system from the perspective of the various user groups and other stakeholders.
|
Published |
2014-03 |
Edition : 1 |
Number of pages : 33 |
Technical Committee |
35.080
Software
|
| ISO 25065:2019 |
Systems and software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Common Industry Format (CIF) for Usability: User requirements specification |
This document provides a framework and consistent terminology for specifying user requirements. It specifies the common industry format (CIF) for a user requirement specification including the content elements and the format for stating those requirements.
NOTE 1 A user requirements specification is the formal documentation of a set of user requirements, which aids in the development and evaluation of usable interactive systems.
In this document, user requirements refers to:
a) user-system interaction requirements for achieving intended outcomes (including requirements for system outputs and their attributes);
b) use-related quality requirements that specify the quality criteria associated with the outcomes of users interacting with the interactive system and can be used as criteria for system acceptance.
NOTE 2 ISO/IEC 25030 introduces the concept of quality requirements. The use-related quality requirements in this document are a particular type of quality requirement.
The content elements of a user requirements specification are intended to be used as part of documentation resulting from the activities specified in ISO 9241-210, and from human centred design processes, such as those in ISO 9241-220.
This document is intended to be used by requirements engineers, business analysts, product managers, product owners, and people acquiring systems from third parties.
The CIF series of standards addresses usability-related information (as described in ISO 9241-11 and ISO/IEC TR 25060).
NOTE 3 In addition to usability, user requirements can include other perspectives, such as human-centred quality introduced in ISO 9241-220, and other quality perspectives presented in ISO/IEC 25010, ISO/IEC TS 25011, and ISO/IEC 25030.
NOTE 4 While this document was developed for interactive systems, the guidance can also be applied in other domains.
This document does not prescribe any kind of method, lifecycle or process. The content elements of a user requirements specification can be used in iterative development which includes the elaboration and evolution of requirements (e.g. as in agile development).
|
Published |
2019-05 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
13.180
Ergonomics
;
35.080
Software
|
| ISO/IEC 25066:2016 |
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Common Industry Format (CIF) for Usability — Evaluation Report |
ISO/IEC 25066:2016 describes the Common Industry Format (CIF) for reporting usability evaluations. It provides a classification of evaluation approaches and the specifications for the content items (content elements) to be included in an evaluation report based on the selected evaluation approach(es). The intended users of the usability evaluation reports are identified, as well as the situations in which the usability evaluation report can be applied.
The usability evaluation reports in ISO/IEC 25066:2016 are applicable to software and hardware systems, products or services used for predefined tasks (excluding generic products, such as a display screen or a keyboard). The content elements are intended to be used as part of system-level documentation resulting from development processes such as those in ISO 9241‑210 and ISO/IEC JTC 1/SC 7 process standards.
The content elements for documenting evaluations can be integrated in any type of process model.
NOTE For the purpose of establishing process models, ISO/IEC TR 24774 and ISO/IEC 33020 specify the format and conformance requirements for process models, respectively. In addition, ISO/IEC 15289 defines the types and content of information items developed and used in process models for system and software lifecycle management. ISO/IEC 15504‑5 and ISO/IEC 15504‑6 (to be replaced by ISO/IEC 33060) define work products, including information items, for the purpose of process capability assessment. Process models and associated information items for human-centred design of interactive systems are contained in ISO/TR 18529 and ISO/TS 18152.
|
Published |
2016-06 |
Edition : 1 |
Number of pages : 37 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 26511:2011 |
Systems and software engineering — Requirements for managers of user documentation |
ISO/IEC 26511:2011 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply. It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC 26511:2011 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.
|
Withdrawn |
2011-12 |
Edition : 1 |
Number of pages : 45 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 26511:2018 |
Systems and software engineering — Requirements for managers of information for users of systems, software, and services |
This document supports the needs of users for consistent, complete, accurate, and usable information. It provides requirements for strategy, planning, managing, staffing, translation, production, and quality and process-maturity assessment for managers of information for users. It specifies processes and procedures for managing information for users throughout the product- or systems-development life cycle. It also includes requirements for key documents produced for managing information for users, including strategic and project plans.
This document provides an overview of the information-management processes that are specific for the management of information for users. It addresses the following activities:
— developing a comprehensive strategy for information development;
— assessing user information needs;
— planning and managing an information-development project;
— staffing and forming information-development teams;
— reviewing and testing information for users;
— managing the translation process;
— publishing and delivering information for users;
— evaluating customer satisfaction and information quality;
— measuring productivity, efficiency, and costs; and
— evaluating organizational maturity.
The guidance in this document applies to multiple project management approaches, including both agile and traditional practices. Traditional practices can encompass predictive, waterfall, or other top-down management methods. Where certain practices are common in agile project management, they are noted.
This document is applicable for use by managers of information for users or organizations with information developers. This document can also be consulted by those with other roles and interests in the process of developing information for users:
— managers of the product and system development process;
— acquirers of information for users prepared by suppliers;
— experienced information developers who prepare information for users;
— human-factors experts who identify principles for making information for users more accessible and easily used; and
— user interface designers and ergonomics experts working together to design the presentation of information.
This document can be applied to manage the following types of information for users, although it does not cover all aspects of them:
— information for user assistance, training, marketing, and systems documentation for product design and development, based on reuse of user information topics;
— multimedia marketing presentations using animation, video, and sound;
— information developed for virtual and augmented reality presentations;
— computer-based training (CBT) packages and course materials intended primarily for use in formal training programs; and
— information describing the internal operation of products.
|
Published |
2018-12 |
Edition : 2 |
Number of pages : 77 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26561:2019 |
Software and systems engineering — Methods and tools for product line technical probe |
This document, within the context of methods and tools for supporting the diagnosis of the organization's capability to adopt or improve software and systems product line engineering:
— defines processes for product line technical probe; those processes are described in terms of purpose, inputs, tasks and outcomes;
— defines method capabilities to support the defined tasks of each process; and
— defines tool capabilities that automate or semi-automate tasks and methods.
This document does not concern processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.
|
Published |
2019-11 |
Edition : 1 |
Number of pages : 39 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 26512:2011 |
Systems and software engineering — Requirements for acquirers and suppliers of user documentation |
ISO/IEC/IEEE 26512:2011 was developed to assist users of ISO/IEC 15288:2008 or ISO/IEC 12207:2008 to acquire or supply software user documentation as part of the software life cycle processes. It defines the documentation process from the acquirer's standpoint and the supplier's standpoint. ISO/IEC/IEEE 26512:2011 covers the requirements for information items used in the acquisition of user documentation products: the Acquisition Plan, Document Specification, Statement of Work, Request for Proposals, and the proposal. It provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work. It includes requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services. It also discusses the use of a Documentation Management Plan and a Document Plan as they arise in the acquisition and supply processes. ISO/IEC/IEEE 26512:2011 is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.
|
Withdrawn |
2011-06 |
Edition : 1 |
Number of pages : 37 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 26512:2018 |
Systems and software engineering — Requirements for acquirers and suppliers of information for users |
This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.
As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:
- information management;
- information design and development;
- information editing and review coordination;
- information testing, particularly usability testing;
- information production and packaging;
- information distribution and delivery;
- advice on the selection and implementation of information development tools and supporting systems; and
- information development process improvement.
This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information. These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
This document is intended for use in acquiring or supplying any type of information for users and is independent of information development or management tools or methodologies.
This document might be helpful for acquiring and supplying the following types of information, although it does not cover all aspects of them:
- multimedia systems using animation, video, and sound;
- computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;
- maintenance documentation describing the internal operation of systems software;
- collaboratively generated, often known as "wiki", documentation, which will usually need to be curated periodically; and
- information for users incorporated into the user interface.
This document is applicable to acquirers and suppliers of information for users, including a variety of specialists:
- analysts (e.g., business analysts, human factors engineers) who identify the tasks that the intended users will perform with the system;
- managers of the software or system development process or the information management process;
- managers of the acquisition process, and those who authorize and approve acquisitions; and
- managers and authors involved in proposal preparation.
It can also be consulted by those with other roles and interests in the information development process:
- information designers and architects who plan the structure, format, and content requirements of information products;
- experienced authors and editors who develop the written content for information for users;
- graphic designers with expertise in electronic media;
- user interface designers and ergonomics experts working together to design the presentation of the information on the screen;
- usability testers, information development reviewers, technical contacts;
- developers of tools for creating on-screen information for users.
|
Published |
2018-06 |
Edition : 2 |
Number of pages : 37 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26513:2009 |
Systems and software engineering - Requirements for testers and reviewers of user documentation |
ISO/IEC 26513:2009 supports the interest of software users in receiving consistent, complete, accurate, and usable documentation. It defines the process in which user documentation products are tested.
ISO/IEC 26513:2009 is intended neither to encourage nor discourage the use of either printed or electronic (on-screen) media for documentation, or of any particular documentation testing or management tools or methodologies.
ISO/IEC 26513:2009 specifies processes for use in testing and reviewing of user documentation. It is not limited to the test and review phase of the life cycle, but includes activities throughout the Information Management and Documentation Management processes.
ISO/IEC 26513:2009 provides the minimum requirements for the testing and reviewing of user documentation, including both printed and on-screen documents used in the work environment by the users of systems software. It applies to printed user manuals, online help, tutorials, and user reference documentation.
The order of clauses in ISO/IEC 26513:2009 does not imply that the software user documentation should be tested in this order.
In each clause, the requirements are media-independent, as far as possible. The informative checklists found in Annexes A and B may be used at each phase of the documentation process to verify that the appropriate steps have been carried out, and that the finished product has acceptable quality.
ISO/IEC 26513:2009 can be helpful for testing and reviewing the following types of documentation:
documentation of products other than software, for example, hardware or devices;
multimedia systems using animation, video, and sound;
computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;
documentation produced for installers, computer operators, or system administrators who are not end users;
maintenance documentation describing the internal operation of systems software.
ISO/IEC 26513:2009 is applicable to testers, reviewers, and other related roles, including a variety of specialists:
usability testers, documentation reviewers, and subject-matter experts;
information designers and architects who plan the structure and format of products in a documentation set;
usability specialists and business analysts who identify the tasks the intended users will perform with the software.
It can also be consulted by those with other roles and interests in the documentation process.
Managers of the software development process or the documentation process should consider the testing of documentation as part of their planning and management activities. Project managers, in particular, have an important role in planning the testing and reviewing of documentation.
Testing of the documentation is likely to highlight any defects or nonconformances in tools that are used to create or display on-screen documentation. Similarly, usability testing of the documentation is likely to highlight defects or nonconformances with the presentation or layout of documentation and associated graphics and other media. As a result, there are a number of roles that should be involved in the testing of documentation because their work affects the content, display or presentation of documentation for the user, for example, developers of tools for creating on-screen documentation, graphic designers producing material displayed as part of the documentation, and human-factors experts who identify principles for making documentation more accessible and easily used, also user interface designers and ergonomics experts working together to design the presentation of the documentation on-screen. In some organizations these roles may have different titles, or an individual may perform more than one of these roles.
There are other roles that need to understand the test processes for the documentation, for example authors should understand the test processed for the documentation that they have produced, and acquirers of documentation prepared by another department or organization, might want to know what testing has been performed and the processes followed for the documentation that they are acquiring from a supplier.
ISO/IEC 26513:2009 is intended for use in all types of organizations, whether or not a dedicated documentation department is present. In all cases, it may be used as a basis for local standards and procedures. Readers are assumed to have experience or general knowledge of testing or reviewing processes.
ISO/IEC 26513:2009 deals with the evaluation of documentation only, and not with the evaluation of the software it supports. Documentation is also included in evaluation of the software product, as in the ISO/IEC 25000 series of standards, in particular, ISO/IEC 25051:2006 Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Requirements for quality of Commercial-Off-The-Shelf (COTS) software product and instructions for testing.
|
Withdrawn |
2009-10 |
Edition : 1 |
Number of pages : 54 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 26513:2017 |
Systems and software engineering — Requirements for testers and reviewers of information for users |
|
Published |
2017-10 |
Edition : 1 |
Number of pages : 40 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26514:2008 |
Systems and software engineering — Requirements for designers and developers of user documentation |
ISO/IEC 26514:2008 provides requirements for the design and development of software user documentation as part of the life cycle processes. It defines the documentation process from the viewpoint of the documentation developer. ISO/IEC 26514:2008 also covers the documentation product. It specifies the structure, content, and format for user documentation, and also provides informative guidance for user documentation style. It is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of ISO/IEC 26514:2008 is also applicable to user documentation for systems including hardware.
|
Withdrawn |
2008-06 |
Edition : 1 |
Number of pages : 143 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 26514:2022 |
Systems and software engineering — Design and development of information for users |
This document covers the development process for designers and developers of information for users of software. It describes how to establish what information users need, how to determine the way in which that information should be presented, and how to prepare the information and make it available. It is not limited to the design and development stage of the life cycle, but includes information on design throughout the life cycle, such as design strategy and maintaining a design.
This document provides requirements for the structure, information content, and format of information for users of software.
This document can be applied to developing the following types of information, although it does not cover all aspects of them:
— information for users of products other than software;
— multimedia systems using animation, video, and sound;
— computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;
— maintenance information describing the internal operation of systems software;
— information for users incorporated into the user interface itself.
This document is applicable to information architects and information developers, including a variety of specialists:
— information architects who plan the structure and format of information products;
— usability specialists and business analysts who identify the tasks that the intended users can perform with the software;
— developers and editors of the written content of information for users;
— graphic designers with expertise in electronic media;
— user interface designers and ergonomics experts working together to design the presentation of the information on the screen.
This document is also a reference for those with other roles and interests in the process of developing information for users:
— managers of the software development process or the information-development process;
— acquirers of information for users prepared by suppliers;
— usability testers, reviewers of information for users, subject-matter experts;
— developers of tools for creating information for users;
— human-factors experts who identify principles for making information for users more accessible and easily used.
|
Published |
2022-01 |
Edition : 1 |
Number of pages : 64 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 26515:2011 |
Systems and software engineering — Developing user documentation in an agile environment |
ISO/IEC 26515:2011 specifies the way in which user documentation can be developed in agile development projects. It is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. ISO/IEC 26515:2011 addresses the relationship between the user documentation process and the life cycle documentation process in agile development. It describes how the information developer or project manager may plan and manage the user documentation development in an agile environment. It is intended neither to encourage nor to discourage the use of any particular agile development tools or methods.
|
Withdrawn |
2011-12 |
Edition : 1 |
Number of pages : 27 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29110-3-2:2018 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 3-2: Conformity certification scheme |
This document:
- defines the rules applicable for certification of the implementation of systems engineering, software engineering and service delivery processes complying with the requirements given in ISO/IEC 29110‑4-m, Profile specifications; and
- provides the necessary information and confidence to customers about the way certification of their suppliers has been granted.
Certification of the implementation of systems and software engineering processes (named "certification" in this document) is a third-party conformity assessment activity (see ISO/IEC 17000:2004, 5.5). Bodies performing this activity are therefore third-party conformity assessment bodies (named "certification body/bodies" in this document).
NOTE This document is primarily intended to be used as a criteria document for the accreditation or peer assessment of certification bodies which seek to be recognized as being competent to certify that a Very Small Entity (VSE) complies with ISO/IEC 29110‑4-m, Profile Specifications. Some of its requirements could also be found useful by any other parties involved in the conformity assessment of such certification bodies.
Systems and software engineering processes certification does not attest the fitness of the systems and or software products offered by a VSE.
It is important to note that certification of the implementation of systems and software engineering processes according to ISO/IEC 29110‑4-m, Profile Specifications, is a process certification and not a management systems certification neither a product certification.
Certification of the implementation of systems and software engineering processes (SEP) of a very small entity (VSE) is one means of providing assurance that the VSE has implemented systems and software engineering processes to the development or maintenance of systems and or software.
Requirements for the implementation of SEP can originate from a number of sources, and this International Standard has been developed to assist in the certification of SEP that fulfil the requirements of ISO/IEC 29110‑4-m, Profile Specifications. The contents of this document can also be used to support certification of SEP that are based on other sets of specified SEP requirements.
This document is intended for use by bodies that carry out audit and certification of SEP for VSEs. It gives generic requirements for such certification bodies performing audit and certification in the field of SEP for VSEs. Such bodies are referred to as certification bodies. This wording is not intended to be an obstacle to the use of this document by bodies with other designations that undertake activities covered by the scope of this document. Indeed, this document is intended to be usable by anyone involved in the assessment of SEP for VSEs.
Certification activities involve the audit of a VSE's SEP. The form of attestation of conformity of a VSE's SEP to a specific lifecycle profile standard setting the applicable SEP (for example ISO/IEC 29110‑4-1 or ISO/IEC 29110‑4-3) or other specified requirements are normally a certification document or a certificate.
This certification is outside the scope of ISO/IEC 29169 to the assessment to process quality characteristics and organizational maturity, and does not cover the results of process assessment. ISO/IEC 29110-3-3 describes such a scheme.
It is for the VSE being certified to develop its own processes (including ISO/IEC 29110‑4-m SEP), other sets of specified SEP requirements, other processes and it is for the VSE to decide how the various components of these will be arranged. It is therefore for certification bodies that operate in accordance with this document to take into account the culture and practices of their clients with respect to the implementation of SEP, including, if applicable, within the wider organization.
|
Published |
2018-04 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO/IEC PRF 5021-2 |
Telecommunications and information exchange between systems — Wireless LAN Access Control — Part 2: Technical specification for dispatching platform |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.110
Networking
|
| ISO/IEC/IEEE 26515:2018 |
Systems and software engineering — Developing information for users in an agile environment |
This document supports the interest of information developers and associated roles responsible for producing information for users of software and systems developed within an agile environment. This document takes a process standard approach to specify the way in which information for users can be developed in agile development projects.
This document provides requirements of information management and information development processes appropriate for software projects that are using agile development methods.
Clause 5 covers the overall requirements for information in agile software development.
Clause 6 covers requirements for the information development lead or project manager to plan an agile information development project and manage the information development activities in an agile environment.
Clause 7 covers requirements for designing, developing, and providing information for users in an agile environment.
Annex A describes agile development practices and methods.
This document is intended neither to encourage nor to discourage the use of any particular agile development tools or methods.
This document provides guidance on processes appropriate for information developers of information for users in software and systems projects that are using agile development methodologies. It is not limited to the development phase of the life cycle of information for users, but includes activities throughout the whole life cycle.
This document is intended for use in all organizations that are using agile development or are considering implementing their projects using these techniques. It is assumed that users of this document have experience or general knowledge of information for users (traditionally called "user documentation") and agile processes.
|
Published |
2018-12 |
Edition : 2 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 26531:2015 |
Systems and software engineering — Content management for product life-cycle, user and service management documentation |
ISO/IEC/IEEE 26531:2015 states requirements for efficient development and management of content produced
throughout the life-cycle of a system and software product;
for the provision of user documentation for systems and software;
for the management of IT services.
ISO/IEC/IEEE 26531:2015 is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets.
The content to be managed with this standard includes
user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product;
product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports;
service management items such as service-level agreements, records, policies, procedures, and other documents.
The purpose of ISO/IEC/IEEE 26531:2015 is to define a process for content management and the requirements of a component content management system through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents.
|
Withdrawn |
2015-05 |
Edition : 1 |
Number of pages : 49 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 26531:2023 |
Systems and software engineering — Content management for product life cycle, user and service management information for users |
This document specifies requirements for efficient development and management of information produced
— throughout the life cycle of a system and software product;
— for the provision of information for users of systems and software;
— for the management of IT and support services.
This document is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets.
The content management process presented in Clauses 6 to 10 is a specialization (lower-level process) of the information management process specified in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207.
|
Published |
2023-03 |
Edition : 2 |
Number of pages : 53 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26550:2013 |
Software and systems engineering — Reference model for product line engineering and management |
ISO/IEC 26550:2013 provides a reference model consisting of an abstract representation of the key processes of software and systems product line engineering and management, and the relationships between the processes.
In the product line there are two development lifecycles (domain engineering and application engineering), the involvement of variabilities, and two process groups (organizational management and technical management).
Domain Engineering lifecycle processes define and implement domain assets commonly used by member products within a product line, while Application Engineering lifecycle processes develop applications by exploiting the domain assets including common and variable assets. During domain engineering, product line variability, which reflects the specific needs of different markets and market segments, are explicitly defined. Variabilities are embedded in domain assets and during application engineering they are selected based on the defined variability models.
Organizational Management process group helps organizations to establish and improve capabilities for nurturing their product lines from conception to retirement and for establishing and managing relationships with customers, providers, and other key stakeholders. Meanwhile, Technical Management process group provides actual means used to support, monitor, and control the activities of both domain engineering and application engineering of a product line.
The reference model for software and systems product line engineering and management of ISO/IEC 26550:2013 can be used in subsequent standardization efforts to create appropriate standards for requirements engineering and management, design, realization, verification and validation, and organizational and technical management processes, tools, and methods of software and systems product line engineering.
|
Withdrawn |
2013-09 |
Edition : 1 |
Number of pages : 34 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26550:2015 |
Software and systems engineering — Reference model for product line engineering and management |
ISO/IEC 26550:2015 is the entry point of the whole suite of International Standards for software and systems product line engineering and management.
The scope of this International Standard is to
? provide the terms and definitions specific to software and systems product line engineering and management,
? define a reference model for the overall structure and processes of software and systems product line engineering and management and describe how the components of the product line reference model fit together, and
? define interrelationships between the components of the product line reference model.
ISO/IEC 26550:2015 does not describe any methods and tools associated with software and systems product line engineering and management. Descriptions of such methods and tools will appear in the consecutive International Standards (ISO/IEC 26551[1] to ISO/IEC 26556[2]). This International Standard does not deal with terms and definitions addressed by ISO/IEC/IEEE 24765:2010 that provides a common vocabulary applicable to all systems and software engineering work.
Whenever this International Standard refers to "products", it means "system-level products" consisting of software systems or both hardware and software systems. It may be useful for the engineering and management of product lines that consist of only hardware systems but it has not been explicitly created to support such hardware product lines. This International Standard is not intended to help the engineering, production, warehousing, logistics, and management of physical items that, possibly combined with software, comprise the products. These processes belong to other disciplines (e.g. mechanics, electronics).
NOTE Annex A provides further information on products.
ISO/IEC 26550:2015, including the product line reference model and the terms and definitions, has been produced starting from References [6], [7], and [8] which finally resulted in a broad consensus from National Member Bodies at the time of publication. In addition to this background process, structures from ISO/IEC 12207:2008, ISO/IEC/IEEE 15288:2015, ISO/IEC 15940:2006 and ISO/IEC 14102:2008 have been used as a baseline.
[1] Second edition to be published.
[2] Under development.
|
Published |
2015-12 |
Edition : 2 |
Number of pages : 35 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-3-4:2015 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 3-4: Autonomy-based improvement method |
ISO/IEC TR 29110-3-4:2015 provides a guide for an autonomy-based improvement method for Very Small Entities (VSEs) developing systems or software products.
|
Published |
2015-10 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO 925:1980 |
Solid mineral fuels — Determination of carbon dioxide content — Gravimetric method |
|
Withdrawn |
1980-08 |
Edition : 2 |
Number of pages : 3 |
Technical Committee |
75.160.10
Solid fuels
|
| ISO/IEC 26551:2012 |
Software and systems engineering — Tools and methods for product line requirements engineering |
ISO/IEC 26551:2012 provides the capabilities of tools and methods that support Software and Systems Product Line (SSPL) requirements engineering. In SSPL requirements engineering, there are three core processes: Product Line scoping, Domain Requirements Engineering, and Application Requirements Engineering.
The major purpose of Product Line Scoping estimates the costs and benefits of a product line, and thereby lets an organization make a go/no-go decision.The costs and benefits estimation results play a pivotal role as an indicator for assessing the effectiveness and efficiency of a product line.
The major purpose of the Domain Requirements Engineering is to analyze commonality and variability for the product line based on the initial features defined in Product Line Scoping, where the major purpose of the Application Requirements Engineering is to define application requirements based on domain requirements assets by reusing, selecting, or newly adding application specific requirements.
For producing multiple products in a product line, the above processes need to be adequately integrated centered around core assets, which is causing the management of domain/application requirements complexities. Thus, the proper supports of methods and tools are essential, and the product line specific capabilities of methods and tools have to be defined.
ISO/IEC 26551:2012 can be used in the following modes:
- By the users: to benefit people who develop, operate, and manage requirements engineering for software and systems product lines.
- By a product line organization: to provide guidance in the evaluation and selection for tools and methods for product line requirements engineering.
- By providers of tools and methods: to provide guidance in implementing or developing tools and methods by providing a comprehensive set of the capabilities of tools and methods for product line requirements engineering.
|
Withdrawn |
2012-12 |
Edition : 1 |
Number of pages : 52 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26551:2016 |
Software and systems engineering — Tools and methods for product line requirements engineering |
ISO/IEC 26551:2016, within the context of tools and methods of requirements engineering for software and systems product lines:
- provides the terms and definitions specific to requirements engineering for software and systems product lines and associated member products;
- defines process groups and their processes performed during product line requirements engineering (those processes are described in terms of purpose, inputs, tasks, and outcomes);
- defines method capabilities to support the defined tasks of each process;
- defines tool capabilities to automate/semi-automate tasks or defined method capabilities.
ISO/IEC 26551:2016 concerns processes and capabilities of requirements tools and methods for a family of products, not for a single system.
This International Standard is not applicable to physical artefacts. Instead, system-level artefacts and software lifecycle artefacts such as requirements documents, architectural data, validation plans, behavioural models, etc. are produced using methods and tools in this International Standard. In the case of the software components of a system, this International Standard can apply twice: once to handle the system elements of the product line and a second time to handle the software elements of the product line, if any. The product line processes are recursive within the different levels of products.
NOTE The requirements in this International Standard apply to the family of systems, software or services.
|
Published |
2016-05 |
Edition : 2 |
Number of pages : 64 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26552:2019 |
Software and systems engineering — Tools and methods for product line architecture design |
This document, within the context of methods and tools for architecture design for software and systems product lines:
— defines processes and their subprocesses performed during domain and application architecture design. Those processes are described in terms of purpose, inputs, tasks and outcomes;
— defines method capabilities to support the defined tasks of each process;
— defines tool capabilities to automate/semi-automate tasks or defined method capabilities.
This document does not concern processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.
|
Published |
2019-05 |
Edition : 1 |
Number of pages : 61 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26553:2018 |
Information technology — Software and systems engineering — Tools and methods for product line realization |
This document, within the context of tools and methods of detailed design and implementation for software and system product lines:
— provides the terms and definitions specific to realization for software and systems product lines;
— defines processes performed during product line realization (those processes are described in terms of purpose, inputs, tasks and outcomes);
— defines method capabilities to support the defined tasks of each process; and
— defines tool capabilities to automate/semi-automate tasks or defined method capabilities.
This document concerns processes and capabilities of realization tools and methods for a family of products, not for a single system.
|
Published |
2018-11 |
Edition : 1 |
Number of pages : 61 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26554:2018 |
Information technology — Software and systems engineering — Tools and methods for product line testing |
This document, within the methods and tools of testing for software and systems product lines:
— provides the terms and definitions specific to testing for software and systems product lines;
— defines processes performed during product line testing (those processes are described in terms of purpose, inputs, tasks and outcomes);
— defines method capabilities to support the defined tasks of each process; and
— defines tool capabilities to automate/semi-automate tasks or defined method capabilities.
This document concerns processes and capabilities of testing methods and tools for a family of products, not for a single system.
|
Published |
2018-11 |
Edition : 1 |
Number of pages : 55 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26559:2017 |
Software and systems engineering — Methods and tools for variability traceability in software and systems product line |
ISO/IEC 26559:2017, within the context of the tools and methods of variability traceability for software and system product lines:
- provides the terms and definitions specific to variability traceability for software and systems product lines;
- defines process groups and their processes for establishing and managing variability traceability at product line lifecycle processes. Those processes are described in terms of purpose, inputs, tasks, and outcomes;
- defines method capabilities to support the defined tasks of each process;
- defines tool capabilities to automate/semi-automate tasks or defined method capabilities.
ISO/IEC 26559:2017 does not concern processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.
|
Published |
2017-07 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26555:2013 |
Software and systems engineering — Tools and methods for product line technical management |
ISO/IEC 26555:2013 deals with the capabilities of tools and methods of Software and Systems Product Line (SSPL) Technical Management. Since product lines deal with multiple products that have similarities, product lines have an unprecedented level of technical management complexities.
In the product line there are inherent differences in technical considerations due to the parallel development processes, domain and application engineering. The two processes are tightly related with each other centered around assets, and the close relationships among domain engineering, application engineering, and assets require highly matured managerial capabilities.
Technical management provides management support for a timely and proper deployment of product line in balance with pre-defined product line objectives such as reusability, reducing cost, and improving quality, as well as its planned cost, schedule, and resources. Technical management addresses actual means used to support, monitor, and control the activities of both domain engineering and application engineering of a product line.
There are needs for defining product line specific technical management processes that integrate the involved product line disciplines with those for a single product. Furthermore, support of tools and methods are required so that a product line organization can perform technical management under the systematic control of complexities.
ISO/IEC 26555:2013 addresses the product line specific processes in technical management by dividing those into Process Management, Variability Management, Asset Management, and Support Management areas with the guidance of a set of tools and methods capabilities for supporting tasks for product line technical management.
ISO/IEC 26555:2013 is intended to benefit people who acquire, supply, develop, operate, and maintain tools and methods for product line technical management. ISO/IEC 26555:2013 can be used in one or more of the following modes:
1) By an organization intended to implement product lines, to understand, adopt, and enact the processes, tools, and methods for product line technical management. This also helps the organization to evaluate and select relevant tools and methods based on business and user-related criteria.
2) By a tool vendor who facilitates or leverages product line engineering practices, to provide a set of tool capabilities that should be embodied in a tool for supporting product line technical management.
|
Withdrawn |
2013-03 |
Edition : 1 |
Number of pages : 56 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26555:2015 |
Software and systems engineering — Tools and methods for product line technical management |
ISO/IEC 26555:2015 deals with the tools and methods of technical management for software products, software services, software-intensive systems (including System Architecture and excluding hardware) within a product line. The scope of this International Standard is as follows:
? Enable the users of this standard to holistically understand, adopt, and enact the processes, tools, and methods for product line technical management. In addition, this International Standard helps the users evaluate and select relevant tools and methods based on business and user-related criteria.
? Help product line engineers, developers, and tool vendors become informed about capabilities of tools and methods that are required for supporting product line implementation from technical aspects.
? Provide product line-specific processes and capabilities of tools and methods in technical management.
ISO/IEC 26555:2015 does not concern processes and capabilities of tools and methods for technical management for a one-of-a-kind system but rather deals with those belonging to a family of systems.
NOTE: System Architecture is a set of logical and physical principles used to achieve a mission within a given environment. From System Architecture are derived components that can be subsystems, software products, human-based products like crew or operators or hardware product like mechanical structures, electronic boards, chemicals, etc. The scope of the International Standard spans from the system, to sub-systems, and software products. Other types of components and especially those related to human beings and to hardware parts are not within the scope of this International Standard.
|
Published |
2015-12 |
Edition : 2 |
Number of pages : 61 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26556:2018 |
Information technology — Software and systems engineering — Tools and methods for product line organizational management |
This document, within the methods and tools of organizational management for software and systems product lines:
— enables the users of this document to holistically understand, adopt and enact the processes, tools and methods for product line organizational management;
— helps the users evaluate and select relevant tools and methods based on business and user-related criteria;
— helps make product line engineers, developers and tool vendors informed about capabilities of tools and methods that are required for supporting product line implementation from organizational aspects; and
— provides product line-specific processes and capabilities of tools and methods in organizational management.
This document concerns processes and capabilities of methods and tools for organizational management for a family of products, not for a single system.
NOTE System Architecture is a set of logical and physical principles used to achieve a mission within a given environment. Components that can be subsystems derived from System Architecture are: software products, human-based products such as crew or operators, or hardware products like mechanical structures, electronic boards and chemicals. The scope of this document spans from the system to subsystems and components. Both hardware-intensive and software-intensive systems are included, if they are part of a product family.
|
Published |
2018-11 |
Edition : 1 |
Number of pages : 65 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26557:2016 |
Software and systems engineering — Methods and tools for variability mechanisms in software and systems product line |
ISO/IEC 26557:2016, within the context of tools and methods of variability mechanisms for software and system product lines:
- provides the terms and definitions related to variability mechanisms for software and systems product lines;
- defines processes and their subprocesses for operating variability mechanisms at each product line life cycle stages and those for providing managerial supports. Those processes are described in terms of purpose, inputs, tasks and outcomes;
- defines method capabilities to support the defined tasks of each process;
- defines tool capabilities to automate/semi-automate tasks or defined method capabilities.
ISO/IEC 26557:2016 does not concern processes and capabilities of tools and methods for a single system, but rather deals with those for a family of products.
|
Published |
2016-12 |
Edition : 1 |
Number of pages : 50 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26558:2017 |
Software and systems engineering — Methods and tools for variability modelling in software and systems product line |
ISO/IEC 26558:2017, within the context of methods and tools for supporting explicit and/or separate variability modelling, variability model management and variability model support in software and systems product lines:
- provides the terms and definitions specific to variability modelling for software and systems product line;
- defines processes for variability modelling, variability model management and variability model support throughout the product line lifecycle. Those processes are described in terms of purpose, inputs, tasks and outcomes;
- defines method capabilities to support the defined tasks of each process;
- defines tool capabilities that automate or semi-automate tasks and methods.
ISO/IEC 26558:2017 does not concern processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.
|
Published |
2017-07 |
Edition : 1 |
Number of pages : 38 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26562:2019 |
Software and systems engineering — Methods and tools for product line transition management |
This document, within the context of methods and tools for supporting the transitioning the organization's current development approach to software and systems product line engineering:
— defines processes for product line transition management. Those processes are described in terms of purpose, inputs, tasks and outcomes;
— defines method capabilities to support the defined tasks of each process;
— defines tool capabilities that automate or semi-automate tasks and methods.
This document does not concern processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.
|
Published |
2019-11 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26563:2022 |
Software and systems engineering — Methods and tools for product line configuration management |
This document, within the context of methods and tools that support the configuration management (CM) capability of software and systems product line engineering:
— specifies processes for product line CM (the processes are described in terms of purpose, inputs, tasks, and outcomes);
— specifies method capabilities to support the defined tasks of each process;
— specifies tool capabilities that automate or semi-automate tasks and methods.
This document does not concern the processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.
|
Published |
2022-12 |
Edition : 1 |
Number of pages : 34 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26564:2022 |
Software and systems engineering — Methods and tools for product line measurement |
This document, within the context of methods and tools that support the product line measurement and management and that demonstrate the quality of the products and a product line:
— specifies processes for product line measurement (the processes are described in terms of purpose, inputs, tasks and outcomes);
— specifies method capabilities to support the defined tasks of each process;
— specifies tool capabilities that automate or semi-automate tasks and methods.
This document does not concern the processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.
|
Published |
2022-12 |
Edition : 1 |
Number of pages : 39 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26580:2021 |
Software and systems engineering — Methods and tools for the feature-based approach to software and systems product line engineering |
This document is a specialization of the more general reference model for software and systems product line engineering and management described in ISO/IEC 26550. The specialization defined herein addresses a class of methods and tools referred to as feature-based software and systems product line engineering, or feature-based PLE, which has emerged as a proven and repeatable product line engineering and management (PLE) practice supported by commercial tool providers.
This document:
— provides the terms and definitions specific to feature-based PLE;
— defines how feature-based PLE is a specialization within the general ISO/IEC 26550 reference model for product line engineering and management;
— defines a reference model for the overall structure and processes of feature-based PLE and describes how the elements of the reference model fit together;
— defines interrelationships and methods for applying the elements and tools of the product line reference model;
— defines required and supporting tool capabilities.
In this document, products of feature-based PLE include digital work products that support the engineering of a system. Some of the artefacts are actually part of the delivered products, while other artefacts can be non-deliverable, such as physical or digital design models.
The intended audience for this document comprises:
— technology providers who wish to provide automated tool support for the reference model and processes described in this document;
— champions within an organization who wish to introduce feature-based PLE throughout that organization;
— IT staff within a PLE organization who will introduce and maintain the necessary technology to support feature-based PLE;
— practitioner stakeholders who will use the provided technology to practice feature-based PLE;
— technical and business managers who will sponsor and direct the methods necessary to practice feature-based PLE;
— university professors, researchers, corporate trainers, and other educators who will create and share pedagogical materials about feature-based PLE and its benefits.
|
Published |
2021-04 |
Edition : 1 |
Number of pages : 51 |
Technical Committee |
35.080
Software
|
| ISO/IEC 26702:2007 |
Systems engineering — Application and management of the systems engineering process |
ISO/IEC 26702:2007 defines the interdisciplinary tasks which are required throughout a system's life cycle to transform customer needs, requirements and constraints into a system solution. In addition, it specifies the requirements for the systems engineering process and its application throughout the product life cycle. ISO/IEC 26702:2007 focuses on engineering activities necessary to guide product development, while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain and eventually dispose of without undue risk to health or the environment.
|
Withdrawn |
2007-07 |
Edition : 1 |
Number of pages : 87 |
Technical Committee |
35.080
Software
|
| ISO/IEC CD 29110-1 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 1: Overview |
This part of ISO/IEC 29110 introduces the major concepts required to understand and use the ISO/IEC 29110 series. It introduces the characteristics and requirements of a VSE and clarifies the rationale for VSE-specific profiles, documents, standards and guides.
This part of ISO/IEC 29110 also introduces process, lifecycle, standardization concepts and defines the organizational terms common to the VSE Profile Set of Documents.
This part of ISO/IEC 29110 is applicable to a VSE. A VSE is an entity (enterprise, organization, department or project) having up to 25 people. The lifecycle processes described in the ISO/IEC 29110 series, Standardized Profiles and Technical Reports are not intended to preclude nor discourage their use by an entity that is larger than a VSE.
|
Deleted |
|
Edition : 1 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-1:2011 |
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 1: Overview |
ISO/IEC TR 29110-1:2011 introduces the major concepts required to understand and use the ISO/IEC 29110 series. It introduces the characteristics and requirements of a Very Small Entity (VSE), and clarifies the rationale for VSE-specific profiles, documents, standards and guides.
It also introduces process, lifecycle and standardization concepts and defines the business terms common to the ISO/IEC 29110 series.
ISO/IEC TR 29110-1:2011 is applicable to VSEs. The lifecycle processes described in ISO/IEC 29110 are not intended to preclude or discourage their use by an entity that is larger than a VSE.
|
Withdrawn |
2011-09 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-1:2016 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 1: Overview |
ISO/IEC TR 29110-1:2016 introduces the major concepts required to understand and use the ISO/IEC 29110 series. It introduces the characteristics and requirements of a VSE and clarifies the rationale for VSE-specific profiles, documents, standards and guides.
It also introduces process, lifecycle, standardization concepts and defines the organizational terms common to the VSE Profile Set of Documents.
It is applicable to a VSE. A VSE is an entity (enterprise, organization, department or project) having up to 25 people. The lifecycle processes described in the ISO/IEC 29110 series, Standardized Profiles and Technical Reports are not intended to preclude nor discourage their use by an entity that is larger than a VSE.
It is targeted both at the general audience wishing to understand the series of documents and, more specifically, at users of the ISO/IEC 29110 series. It should be read first when initially exploring VSE Profile documents. While there is no specific prerequisite to read this part of ISO/IEC 29110, it will be helpful to the user in understanding the other parts.
The lifecycle processes defined in the set of Standardized Profiles and Technical Reports can be used by a VSE when developing, acquiring and using, as well as when creating and supplying systems having hardware and software elements and software. They can be applied at any level in a systems development, software system's structure and at any stage in the lifecycle. They are not intended to preclude or discourage the use of additional processes that a VSE finds useful.
|
Published |
2016-06 |
Edition : 2 |
Number of pages : 23 |
Technical Committee |
35.080
Software
|
| ISO/IEC 29110-2:2011 |
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 2: Framework and taxonomy |
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-2:2011 is targeted for standards producers, tool vendors and methodology vendors. It is not intended for VSEs. It introduces the concepts for software engineering International Standardized Profiles for VSEs, and defines the terms common to ISO/IEC 29110. It establishes the logic behind the definition and application of standardized profiles. It specifies the elements common to all standardized profiles (structure, conformance, assessment) and introduces the taxonomy (catalogue) of ISO/IEC 29110 profiles.
|
Withdrawn |
2011-01 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 29110-3:2011 |
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 3: Assessment guide |
ISO/IEC TR 29110-3:2011 defines the process assessment guidelines and conformance requirements needed to meet the purpose of defined VSE Profiles. It is applicable to all VSE Profiles and is compatible with ISO/IEC 15504-2.
The possible uses of ISO/IEC TR 29110-3:2011 are as follows.
Assessment to evaluate the process capabilities. This is when an organization wants an assessment execution in order to obtain a process profile of the implemented processes.
Provider's capability assessment. This is when a customer asks for a third party to conduct an assessment in order to obtain a process profile of the implemented process by the software development and maintenance provider. The customer chooses the processes to be assessed depending on the services to be contracted.
The target audience of ISO/IEC TR 29110-3:2011 is primarily those who perform process assessments for VSEs. ISO/IEC TR 29110-3:2011 also contains information that can be useful to developers of assessment methods and assessment tools.
ISO/IEC TR 29110-3:2011 is addressed to people who have a direct relation with the assessment process based on the VSE Profiles, e.g. the assessor and the sponsor of the assessment, who need guidance on ensuring that the requirements for performing an assessment have been met.
|
Withdrawn |
2011-09 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.080
Software
|
| ISO/IEC CD 29110-1-2 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 1-2: Vocabulary |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.080
Software
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC CD 29110-5-1-1 |
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-1-1: Management and engineering guide: Generic profile group: Entry profile |
This part of ISO/IEC 29110 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.
The scope of these projects is the conversion of documents published or approved as Technical Reports (TR) to International Standards (IS).
There will be no changes to the original and actual scope of the original project as documented in SC7N3288, which is an update version of the original NWIP ISO/IEC JTC1/SC7 N3288 New Work Item Proposal – Software Life Cycles for Very Small Enterprises - Dated 2005-06-21, N3215, Resolution 847.
The guidelines are informative, and contain no requirements (profile requirements corresponding to each guideline can be found in parts 29110-4-n).
Each guideline will also be revised to accommodate changes in the profile base documents; to process a backlog of minor changes detected by the users and authors of the documents; and as a result of processing ballot comments.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 8802-1Q:2016/Amd 2:2018 |
Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Specific requirements — Part 1Q: Bridges and bridged networks — Amendment 2: Application virtual local area network (VLAN) type, length, value (TLV) |
|
Withdrawn |
2018-01 |
Edition : 1 |
Number of pages : 89 |
Technical Committee |
35.110
Networking
|
| ISO/IEC CD 29110-5-1-2 |
Software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-1-2: Management and engineering guide: Generic profile group: Basic profile |
This part of ISO/IEC 29110 is applicable to Very Small Entities (VSEs). VSEs are enterprises, organizations, departments or projects of up to 25 people. The lifecycle processes described in ISO/IEC 29110 are not intended to preclude or discourage their use by organizations bigger than VSEs.
This part of ISO/IEC 29110 provides the management and engineering guide to the Basic VSE Profile specified in ISO/IEC 29110-4-1 through project management and software implementation 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 this part of ISO/IEC 29110.
This part of ISO/IEC 29110 applies for software development projects, which can be to fulfil an external or internal contract. The internal contract need not be explicit between the project team and their Customer. Using this part of ISO/IEC 29110, a VSE can obtain the following benefits.
⎯ An agreed set of project requirements and expected products is delivered to the Customer.
⎯ A disciplined management process that provides project visibility and corrective actions of project
problems and deviations is performed.
⎯ A systematic software implementation process that satisfies Customer needs and ensures quality
products is followed.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC CD 29110-5-4 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 5-4: Agile software development guidelines |
This document provides guidelines for VSEs that want to reinforce their agile environment to develop software using an agile approach based on Scrum and XP.
This document also provides guidelines that facilitates the implementation of an agile approach for VSEs that are already using the software Basic profile of the ISO/IEC 29110 series.
This document is targeting VSEs that do not develop business or safety critical products.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC CD 29110-5-6-4 |
Systems and software engineering — Systems engineering lifecycle profiles for Very Small Entities (VSEs) — Part 5-6-4: Management and engineering guidelines: Generic profile group: Advanced profile |
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 applies for the development of non safety critical products.
The ISO/IEC 29110–4-6 will identify the requirements applicable to the tasks and work products described in this document.
This document is targeted for VSEs that do not develop safety critical products and have little or no experience with systems engineering (SE) process planning and implementation using the ISO/IEC/IEEE 15288. This document is also targeted for VSEs which are familiar with the management and engineering guide of the systems engineering Intermediate profile (ISO/IEC TR 29110 5-6-3) 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 process, technique and method that enhances the VSE’s stakeholder satisfaction and productivity.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC CD 29110-7-1 |
Systems and software engineering — Lifecycle profiles for Very Small Entities (VSEs) — Part 7-1: Specific space profile guidelines |
This guideline and its associated standard ISO/IEC 29110-6-1 will establish a common framework for very small entities (Space-VSEs – Very Small Entities) entering the space domain. They will provide processes that will be applied during the development of software.
The purpose of this guideline and its associated standard is to provide a set of processes to facilitate a starting point to enter into the space domain within an improvement path towards the fulfilment of all applicable requirements in projects for space.
The processes will not presume specific organizational structures, management philosophies, life cycle models or development methods. In relation to process-related risk determination, the proposed standard and its associated guideline are applicable within any customer– supplier relationship of the space domain and to any organization wishing to enter into the space domain.
The proposed guideline is targeting VSEs that develop low-level critical software development in space domain as in ASIL A level defined in ISO 26262.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.080
Software
|