Active Standard

IEEE/ISO/IEC 21841-2019

ISO/IEC/IEEE International Standard - Systems and software engineering -- Taxonomy of systems of systems

This document defines a normalized taxonomy for systems of systems (SoS) to facilitate communications among stakeholders. It also briefly explains what a taxonomy is and how it applies to the SoS to aid in understanding and communication. Taxonomies provide a means in many fields to classify and describe the relationships between the relevant elements being studied. The elements of the taxonomy, or taxa, form a partitioning or means of classification within that body of knowledge. In the context of systems of systems (SoS), the relevant elements are, by definition, systems themselves. Using essential characteristics to partition the various types of SoS provides an abbreviated nomenclature for thinking about SoS. Based on the taxonomies, different approaches to the engineering of systems of systems are possible, improving the efficiency and effectiveness of systems of systems engineering.

Sponsor Committee
C/S2ESC - Software & Systems Engineering Standards Committee
Learn More
Status
Active Standard
PAR Approval
2017-12-06
Board Approval
2019-06-13
History
Published:
2019-07-19

Working Group Details

Society
IEEE Computer Society
Learn More
Sponsor Committee
C/S2ESC - Software & Systems Engineering Standards Committee
Learn More
Working Group
WG_LCP - Working Group for Life Cycle Processes
Learn More
IEEE Program Manager
Patricia Roder
Contact
Working Group Chair
Teresa Doran

P15026-3

IEEE/ISO/IEC Draft International Standard - Systems and Software Engineering - Systems and Software Assurance - Part 3: System Integrity Levels

This part of ISO/IEC 15026 specifies the concept of integrity levels with corresponding integrity level requirements that are required to be met in order to show the achievement of the integrity level. It places requirements on and recommends methods for defining and using integrity levels and their corresponding integrity level requirements. It covers systems, software products, and their elements, as well as relevant external dependencies.

Learn More

P15288

ISO/IEC/IEEE Draft Standard - Systems and Software engineering -- System Life Cycle Processes

This International Standard establishes a common framework of process descriptions for describing the life cycle of systems created by humans. It defines a set of processes and associated terminology from an engineering viewpoint. These processes can be applied at any level in the hierarchy of a system's structure. Selected sets of these processes can be applied throughout the life cycle for managing and performing the stages of a system's life cycle. This is accomplished through the involvement of all stakeholders, with the ultimate goal of achieving customer satisfaction. This International Standard also provides processes that support the definition, control and improvement of the system life cycle processes used within an organization or a project. Organizations and projects can use these processes when acquiring and supplying systems. This International Standard concerns those systems that are made by humans and may be configured with one or more of the following system elements: hardware, software, data, humans, processes (e.g., processes for providing service to users), procedures (e.g., operator instructions), facilities, materials and naturally occurring entities.

Learn More

P24748-1

ISO/IEC/IEEE Draft International Standard - Systems and software engineering - Life cycle management - Part 1: Guidelines for life cycle management

This document provides guidelines for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document: - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines; - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide, or acquire either products or services; - defines the concept and terminology of a life cycle; - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services; - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle; - describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software aspects); - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects; and - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management.

Learn More

P24748-2

ISO/IEC/IEEE Draft International Standard - Systems and software engineering -Life cycle management - Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (System life cycle processes)

ISO/IEC/IEEE 15288 establishes a common framework for system life cycle processes, with well-defined terminology, that can be referenced by any party, particularly those having any involvement or interest in the system life cycle or performance of systems engineering activities. It applies to the acquisition of systems, which can be comprised of products, services, or both, as well as to the supply, development, operation, maintenance, and disposal of systems, whether performed internally or externally to an organization. ISO/IEC/IEEE 15288 may be used stand-alone or jointly with other International Standards, such as ISO/IEC/IEEE 12207, and supplies a process reference model that supports process capability assessment according to ISO/IEC 33002.

Learn More

P24748-6

ISO/IEC/IEEE Draft Standard - Systems and Software Engineering -- Life Cycle Management -- Part 6: Systems and Software Integration

This standard: u2022provides requirements and guidance for use of the integration process and its relationships to other system and software life cycle processes as described in ISO/IEC/IEEE 15288:2015 and ISO/IEC/IEEE 12207:2017, u2022specifies information items to be produced as a result of using the integration process, including the content and format of the information items. This standard provides a detailed presentation of system and software integration, considering: u2022the related concepts of integration, such as interface, verification, and validation; u2022the possible composition of a system comprised of any mix of products and services that can include hardware, software, humans, data, processes (e.g. review process), procedures (e.g. operator instructions), facilities and naturally occurring entities (e.g. water, organisms, minerals), u2022the life cycle stages of a system at which integration may occur, and u2022the context of the domain in which the system functions.

Learn More

P24748-9

ISO/IEC/IEEE Draft Standard - Systems and software engineering -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems

Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.

Learn More

12207-2017

ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes

This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. This International Standard applies to the acquisition of software systems, products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of any system, whether performed internally or externally to an organization. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software products and services are included. This International Standard also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project. The processes, activities and tasks of this International Standard may also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288, Systems and software engineering–System life cycle processes. In the context of this International Standard and ISO/IEC/IEEE 15288, it is recognized that there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system of interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this International Standard for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering-System life cycle processes, depends on the system of interest. Processes in both standards have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.

Learn More

12207-2-2020

ISO/IEC/IEEE International Standard - Systems and software engineering--Software life cycle processes--Part 2: Relation and mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008

ISO/IEC/IEEE 12207-2 provides the mapping expressing corresponding relations between software life cycle processes in ISO/IEC/IEEE 12207:2017 and the processes in the previous edition ISO/IEC 12207:2008. These relations are demonstrated by means of mapping tables that show relationships between Process Outcomes, and Activities and Tasks in these both editions of ISO/IEC/IEEE 12207. This mapping assists users of the ISO/IEC 12207:2008 edition to transition to using the ISO/IEC/IEEE 12207:2017 edition. This document will help users understand the differences between the reference processes and requirements of the two editions of ISO/IEC/IEEE 12207, and help the user to understand any potential gaps or process enhancements might be needed in seeking conformance to, and/or use of ISO/IEC/IEEE 12207:2017. Also, this document provides to such users the mapping which helps to identify corresponding and compatible process outcomes, activities and tasks of processes for software systems in the ISO/IEC/IEEE 12207:2017.

Learn More

14764-2021

ISO/IEC/IEEE International Standard - Software engineering - Software life cycle processes - Maintenance

This standard describes an iterative process for managing and executing software maintenance activities. Use of this standard is not restricted by size, complexity, criticality, or application of the software product. This standard uses a process model to discuss and depict aspects of software maintenance. The criteria established apply to both the planning of maintenance for software while under development, as well as the planning and execution of software maintenance activities for existing software products. Ideally, maintenance planning should begin during planning for software development. This International Standard provides the framework within which generic and specific software maintenance plans may be executed, evaluated, and tailored to the maintenance scope and magnitude of given software products. This International Standard provides the framework, precise terminology, and processes to allow the consistent application of technology (tools, techniques, and methods) to software maintenance. This International Standard provides requirements and guidance for the maintenance of software. The basis for the Maintenance Process and its activities is consistent with ISO/IEC/IEEE 12207:2017, Systems and software engineering -- Software life cycle processes. This standard defines the activities and tasks of software maintenance, and provides maintenance planning requirements. It does not address the operation of software and the operational functions, e.g., backup, recovery, or system administration, which are normally performed by those who operate the software.

Learn More

15026-1-2019

ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance --Part 1:Concepts and vocabulary

This document defines assurance-related terms and establishes an organized set of concepts and their relationships, thereby establishing a basis for shared understanding of the concepts and principles central to all parts of ISO/IEC/IEEE 15026 across its user communities. It provides information to users of the subsequent parts of ISO/IEC/IEEE 15026, including the use of each part and the combined use of multiple parts. Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in the ISO/IEC/IEEE 15026 series.

Learn More

15026-2-2022

ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case

This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.

Learn More

15026-3-2013

IEEE Standard Adoption of ISO/IEC 15026-3 -- Systems and Software Engineering -- Systems and Software Assurance -- Part 3: System Integrity Levels

The concept of integrity levels with corresponding integrity level requirements that are required to be met in order to show the achievement of the integrity level are specified in this adoption of ISO/IEC 15026-3:2011. It places requirements on and recommends methods for defining and using integrity levels and their integrity level requirements, including the assignment of integrity levels to systems, software products, their elements, and relevant external dependencies.

Learn More

15026-4-2021

ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance -- Part 4: Assurance in the life cycle

This document provides guidance and recommendations for assurance of a selected claim about the system-of-interest by achieving the claim and showing the achievement. The guidance and recommendations are given in a System Assurance process view on top of ISO/IEC/IEEE 15288 and a Software Assurance process view on top of ISO/IEC/IEEE 12207.

Learn More

15288-2015

ISO/IEC/IEEE International Standard - Systems and software engineering -- System life cycle processes

This International Standard establishes a common process framework for describing the life cycle of man-made systems. It defines a set of processes and associated terminology for the full life cycle, including conception, development, production, utilization, support and retirement. This standard also supports the definition, control, assessment, and improvement of these processes. These processes can be applied concurrently, iteratively, and recursively to a system and its elements throughout the life cycle of a system.

Learn More

15939-2017

ISO/IEC/IEEE International Standard - Systems and software engineering--Measurement process

This document provides an elaboration of the measurement process from ISO/IEC 15288 and ISO/IEC 12207. The measurement process is applicable to system and software engineering and management disciplines. The process is described through a model that defines the activities of the measurement process that are required to adequately specify what measurement information is required, how the measures and analysis results are to be applied, and how to determine if the analysis results are valid. The measurement process is flexible, tailorable, and adaptable to the needs of different users. This document identifies a process that supports defining a suitable set of measures that address specific information needs. It identifies the activities and tasks that are necessary to successfully identify, define, select, apply, and improve measurement within an overall project or organizational measurement structure. It also provides definitions for commonly used measurement terms.

Learn More

16085-2020

ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes -- Risk management

This document: – provides risk management elaborations for the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, – provides the users of ISO/IEC/IEEE 15288, ISO/IEC/IEEE 12207 and their associated elaboration standards with common terminology and specialized guidance for performing risk management within the context of systems and software engineering projects, – specifies the required information items that are to be produced through the implementation of risk management process for claiming conformance, and – specifies the required contents of the information items. This document provides a universally applicable standard for practitioners responsible for managing risks associated with systems and software over their life cycle. This document is suitable for the management of all risks encountered in any organization or project appropriate to the systems or software projects regardless of context, type of industry, technologies utilized, or organizational structures involved. This document does not provide detailed information about risk management practices, techniques, or tools which are widely available in other publications. Instead this document focuses on providing a comprehensive reference for integrating the large and wide variety of processes, practices, techniques, and tools encountered in systems and software engineering projects and other lifecycle activities into a unified approach for risk management, with the purpose of providing effective and efficient risk management while meeting the expectations and requirements of organization and project stakeholders.

Learn More

21839-2019

ISO/IEC/IEEE International Standard -- Systems and software engineering -- System of systems (SoS) considerations in life cycle stages of a system

This document provides a set of critical considerations to be addressed at key points in the life cycle of systems created by humans. This document refers to a constituent system that will interact in a system of systems as the system of interest (SOI). These considerations are aligned with ISO/IEC/IEEE 15288 and the ISO/IEC/IEEE 24748 framework for system life cycle stages and associated terminology. Selected subsets of these considerations may be applied throughout the life of systems. This is accomplished through the involvement of all stakeholders with the ultimate goal of achieving customer satisfaction by ensuring that when delivered, the system will operate effectively in the operational or business environment which will typically be characterized as one or more systems of systems. This document concerns those systems that are man-made and are configured with one or more of the following: hardware, software, humans, procedures and facilities.

Learn More

21840-2019

ISO/IEC/IEEE International Standard - Systems and software engineering -- Guidelines for the utilization of ISO/IEC/IEEE 15288 in the context of system of systems (S0S)

This document provides guidance on the application of processes in ISO/IEC/IEEE 15288 to systems of systems (SoS). The scope of this document is the same as ISO/IEC/IEEE 15288, which addresses more than systems engineering activities. This document provides general guidance for each ISO/IEC/IEEE 15288 process and process outcome in the context of SoS, but it does not address specific activities, tasks, methods, or procedures. Additional processes and process outcomes unique to SoS can still be needed and are not covered by this document. This document explores the similarities and differences between systems and SoS and, by extension, the similarities and differences between engineering of systems and SoS. The guidance contained in this document is expected to evolve as the discipline matures.

Learn More

24748-1-2018

ISO/IEC/IEEE International Standard - Systems and software engineering - Life cycle management - Part 1:Guidelines for life cycle management

The purpose of this document is to facilitate the joint usage of the process content of the latest revisions of both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, by providing unified and consolidated guidance on life cycle management of systems and software. This is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains as the two International Standards are used in combination. That will in turn help a project team design a life cycle model for managing the progress of their project. Hence, ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 are the documents that apply the concepts found in this document to specific processes.

Learn More

24748-2-2018

ISO/IEC/IEEE International Standard - Systems and Software Engineering-- Life Cycle Management-- Part 2: Guidelines for the Application of ISO/IEC/IEEE 15288 (System Life Cycle Processes)

This document specifies requirements and procedures for managing information for users throughout the software-, services-, and systems-development life cycle. It applies to people or organizations producing suites of information, to those undertaking a single information-development project, and to information produced internally, as well as to information contracted to outside service organizations. It provides details of the information-development and project-management processes and also presents aspects of strategic planning and translation management that managers apply. It covers management activities related to starting a project, building a team, and managing information through the translation and localization process. It addresses productivity and quality measurements needed for management control. This document is independent of the software tools that may be used to produce or manage information for users and applies to both printed, embedded, and mobile information. Much of its guidance is applicable to information for users of systems of hardware as well as software, systems, and services.

Learn More

24748-3-2020

ISO/IEC/IEEE International Standard - Systems and software engineering--Life cycle management--Part 3: Guidelines for the application of ISO/IEC/IEEE 12207 (software life cycle processes)

ISO/IEC/IEEE 24748-3 provides guidance on the application of the software life cycle processes standard, ISO/IEC/IEEE 12207:2017. This document establishes guidance to implement a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. This document provides guidance on defining, controlling, and improving software life cycle processes within an organization or a project. It recommends methods and approaches suitable for a variety of life cycle models. The guidance emphasizes the importance of establishing a strategy, planning, and the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. Its purpose is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains. This document concentrates on specific guidance for the Technical processes and how they can be effectively used during the software life cycle. It is intended to be useful in a variety of software life cycle situations, including the use of agile methods.

Learn More

24748-4-2016

ISO/IEC/IEEE International Standard for Systems and Software Engineering -- Life Cycle Management -- Part 4: Systems Engineering Planning

The evolution of the harmonized set of ISO/IEC/IEEE 15288-12207 related standards and technical reports that are discussed in this International Standard provides detailed requirements and guidance on the application of system life cycle processes. This International Standard unifies technical and management requirements and guidance from several of these sources to specify the requirements for the content of a SEMP and to provide a common SEMP format. This International Standard also identifies the processes as defined in ISO/IEC/IEEE 15288 to perform the necessary project planning activities to accomplish the project's technical effort and to develop the project's SEMP. Due to close alignment with the content of ISO/IEC 24748, ISO/IEC 26702 is now Part 4 of the multi-part International Standard, ISO/IEC 24748 (Systems and software engineering -- Life cycle management).

Learn More

24748-5-2017

ISO/IEC/IEEE International Standard - Systems and Software Engineering--Life Cycle Management--Part 5: Software Development Planning

ISO/IEC/IEEE 24748 provides unified and consolidated guidance on the life cycle management of systems and software. This document focuses on the processes required for successful planning and management of the project's software development effort and for development of the software development plan (SDP) as a vehicle for representing a project's application of software life cycle processes. The SDP is a top level technical planning document for a project which addresses technical management processes established by three principal sources (the project's contract, applicable organizational and technical management processes, and the software development project team) as necessary to successfully accomplish the software development related tasks of the project.

Learn More

24774-2021

ISO/IEC/IEEE International Standard -Systems and software engineering - Life cycle management--Specification for process description

A number of international, national and industry standards describe processes and process models. Process models are developed for a range of purposes including process implementation and assessment. In order for users of standards to select the appropriate forms of process description and apply them in a consistent fashion, it is desirable to develop a common characterization of all of these forms of process description. This document presents requirements for the description of processes in terms of their format, content and level of prescription. Because of the wide usage of process descriptions, process elements are categorized as u201cRequiredu201d or u201cOptionalu201d. Although developed within ISO/IEC/JTC1/SC7 u2013 Systems and software engineering, the requirements of this document can be applied to any process model or description developed for any purpose.

Learn More

29148-2018

ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes -- Requirements engineering

This document contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. This document provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288. Information items applicable to the engineering of requirements and their content are defined. The content of this document can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288, or can be used independently.

Learn More

90003-2018

ISO/IEC/IEEE International Standard - Software engineering -- Guidelines for the application of ISO 9001:2015 to computer software

This document provides guidance for organizations in the application of ISO 9001:2015 to the acquisition, supply, development, operation and maintenance of computer software and related support services. This document does not add to or otherwise change the requirements of ISO 9001:2015. The guidelines provided in this document are not intended to be used as assessment criteria in quality management system registration/certification. The application of this document is appropriate to software that is: part of a commercial contract with another organization, a product available for a market sector, used to support the processes of an organization, embedded in a hardware product, or related to software services. Some organizations may be involved in all the above activities; others may specialize in one area. Whatever the situation, the organization's quality management system should cover all aspects (software related and non-software related) of the business. This document identifies the issues that should be addressed and is independent of the technology, life cycle models, development processes, sequence of activities and organizational structure used by an organization. Additional guidance and frequent references to the ISO/IEC JTC 1/SC 7 software engineering standards are provided to assist in the application of ISO 9001:2015, in particular ISO/IEC/IEEE 12207:2017.

Learn More

1008-1987

IEEE Standard for Software Unit Testing

An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.

Learn More

1220-2005

IEEE Standard for Application and Management of the Systems Engineering Process

The interdisciplinary tasks that are required throughout a system's life cycle to transform stakeholder needs, requirements, and constraints into a system solution are defined. This standard is intended to guide the development of systems for commercial, government, military, and space applications. The information applies to a project within an enterprise that is responsible for developing a product design and establishing the life cycle infrastructure needed to provide for life cycle sustainment.

Learn More

12207-1996

ISO/IEC International Standard - Information Technology - Software Life Cycle Processes

ISO/IEC 12207 provides a common framework for developing and managing software. IEEE/EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Alliance (EIA) as formulated by a joint project of the two organizations. IEEE/EIA 12207.0 contains concepts and guidelines to foster better understanding and application of the standard. Thus this standard provides industry a basis for software practices that would be usable for both national and international business.

Learn More

12207-2008

ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes

Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.

Learn More

12207.2-1997

IEEE/EIA Guide - Industry Implementation of International Standard ISO/IEC 12207 : 1995 (ISO/IEC 12207) Standard for Information Technology- Software Life Cycle Processes - Implementation considerations

Superseded by 12207:2008(E) (IEEE Std 12207-2008). ISO/IEC 12207 provides a common framework for developing and managing software. IEEE/EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Association (EIA) as formulated by a joint project of the two organizations. IEEE/EIA 12207.2 provides implementation consideration guidance for the normative clauses of IEEE/EIA 12207.0. The guidance is based on software industry experience with the life cycle processes presented in IEEE/EIA 12207.0.

Learn More

14764-2006

ISO/IEC/IEEE International Standard for Software Engineering - Software Life Cycle Processes - Maintenance

This International Standard describes in greater detail management of the Maintenance Process described in ISO/IEC 12207, including Amendments. This International Standard also establishes definitions for the various types of maintenance. This International Standard provides guidance that applies to planning, execution and control, review and evaluation, and closure of the Maintenance Process. The scope of this International Standard includes maintenance for multiple software products with the same maintenance resources. u201cMaintenanceu201d in this International Standard means software maintenance unless other wise stated.

Learn More

15026-1-2014

IEEE Standard Adoption of ISO/IEC 15026-1--Systems and Software Engineering--Systems and Software Assurance--Part 1: Concepts and Vocabulary

Assurance-related terms are defined and an organized set of concepts and relationships to establish a basis for shared understanding across user communities for assurance are established in this adoption of ISO/IEC 15026-1. It provides information to users of the other parts of this International Standard including the combined use of multiple parts. The essential concept introduced by ISO/IEC 15026 is the statement of claims in an assurance case and the support of those claims through argumentation and evidence. These claims are in the context of assurance for properties of systems and software within life cycle processes for the system or software product. Assurance for a service being operated and managed on an ongoing basis is not covered in this International Standard.

Learn More

15026-4-2013

IEEE Standard Adoption of ISO/IEC 15026-4--Systems and Software Engineering--Systems and Software Assurance--Part 4: Assurance in the Life Cycle

Guidance and recommendations for conducting selected processes, activities, and tasks for systems and software products requiring assurance claims for properties selected for special attention (called critical properties) are given in this adoption of ISO/IEC 15026-4:2012. IEEE Std 15026-4-2013 specifies a property-independent list of processes, activities and tasks to achieve the claim and show the achievement of the claim. IEEE Std 15026-4-2013 establishes the processes, activities, tasks, guidance, and recommendations in the context of a defined life cycle model and set of life cycle processes for system and/or software life cycle management.

Learn More

15288-2004

Adoption of ISO/IEC 15288:2002 Systems Engineering-System Life Cycle Processes

Superseded by ISO/IEC/15288:2008(E) (IEEE Std 15288-2008). IEEE adoption of ISO/IEC Std 15288-2002. This standard establishes a common framework for describing the life cycle of systems created by humans. It defines a set of processes and associated terminology. These processes can be applied at any level in the hierarchy of a system's structure. Selected sets of these processes can be applied throughout the life cycle for managing and performing the stages of a system's life cycle. This is accomplished through the involvement of all interested parties with the ultimate goal of achieving customer satisfaction. This standard is identical with ISO/IEC 15288: 2002 but contains an additional informative annex, Annex E, explaining the relationship of this standard to other IEEE standards.

Learn More

15288-2008

ISO/IEC/IEEE International Standard - Systems and software engineering System life cycle processes

Revision of ISO/IEC 15288-2004. This International Standard was jointly developed by ISO/IEC and IEEE. This International Standard establishes a common process framework for describing the life cycle of man-made systems. It defines a set of processes and associated terminology for the full life cycle, including conception, development, production, utilization, support and retirement. This standard also supports the definition, control, assessment, and improvement of these processes. These processes can be applied concurrently, iteratively, and recursively to a system and its elements throughout the life cycle of a system.

Learn More

15939-2008

IEEE Standard Adoption of ISO/IEC 15939:2007--Systems and Software Engineering--Measurement Process

This International Standard defines a measurement process applicable to system and software engineering and management disciplines. The process is described through a model that defines the activities of the measurement process that are required to adequately specify what measurement information is required, how the measures and analysis results are to be applied, and how to determine if the analysis results are valid. The measurement process is flexible, tailorable, and adaptable to the needs of different users. This International Standard identifies a process that supports defining a suitable set of measures that address specific information needs. It identifies the activities and tasks that are necessary to successfully identify, define, select, apply, and improve measurement within an overall project or organizational measurement structure. It also provides definitions for commonly used measurement terms. This international standard provides an elaboration of the measurement process from ISO/IEC 15288:2008 and IEEE Std 15288-2008, as well as ISO/IEC 12207:2008 and IEEE Std 12207-2008.

Learn More

16085-2006

ISO/IEC/IEEE International Standard - Systems and Software Engineering - Life Cycle Processes - Risk Management

A process for the management of risk in the life cycle is defined. It can be added to the existing set of software life cycle processes defined by the ISO/IEC 12207 or ISO/IEC 15288 series of standards, or it can be used independently.

Learn More

16326-2009

ISO/IEC/IEEE International Standard - Systems and Software Engineering--Life Cycle Processes--Project Management

ISO/IEC/IEEE 16326:2009 provides normative content specifications for project management plans covering software projects, and software-intensive system projects. It also provides detailed discussion and advice on applying a set of project processes that are common to both the software and system life cycle as covered by ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288- 2008), respectively. The discussion and advice are intended to aid in the preparation of the normative content of project management plans. ISO/IEC/IEEE 16326:2009 is the result of the harmonization of ISO/IEC TR 16326:1999 and IEEE Std 1058-1998.

Learn More

24748-1-2011

IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management

This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties. ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.

Learn More

24748-2-2012

IEEE Guide--Adoption of ISO/IEC TR 24748-2:2011 Systems and Software Engineering-- Life Cycle Management-- Part 2: Guide to the Application of ISO/IEC 15288 (System Life Cycle Processes)

ISO/IEC TR 24748-2:2011 is adopted by this standard. ISO/IEC TR 24748-2:2011 is a guide for the application of ISO/IEC 15288:2008. It addresses system, life cycle, process, organizational, project, and adaptation concepts, principally through reference to ISO/IEC TR 24748-1 and ISO/IEC 15288:2008. It then gives guidance on applying ISO/IEC 15288:2008 from the aspects of strategy, planning, application in organizations, and application on projects. ISO/IEC TR 24748-2:2011 is intentionally aligned with both ISO/IEC TR 24748-1 and ISO/IEC TR 24748-3 (Guide to the application of ISO/IEC 12207) in its terminology, structure and content.

Learn More

24748-3-2012

IEEE Guide--Adoption of ISO/IEC TR 24748-3:2011,Systems and Software Engineering--Life Cycle Management-- Part 3: Guide to the Application of ISO/IEC 12207 (Software Life Cycle Processes)

Adoption of ISO/IEC TR 24748-3:2011. ISO/IEC TR 24748-3:2011 is a guide for the application of ISO/IEC 12207:2008. It addresses system, life cycle, process, organizational, project, and adaptation concepts, principally through reference to ISO/IEC TR 24748-1 and ISO/IEC 12207:2008. It gives guidance on applying ISO/IEC 12207:2008 from the aspects of strategy, planning, application in organizations, and application on projects. ISO/IEC TR 24748-3:2011 is intentionally aligned with both ISO/IEC TR 24748-1 and ISO/IEC TR 24748-2 (Guide to the application of ISO/IEC 15288) in its terminology, structure and content.

Learn More

24774-2012

IEEE Guide--Adoption of ISO/IEC TR 24474:2010 Systems and Software Engineering-- Life Cycle Management--Guidelines for Process Description

ISO/IEC TR 24774:2010 is adopted by this standard. 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.

Learn More

26702-2007

ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process

The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is 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 to dispose of, without undue risk to health or the environment.

Learn More

29148-2011

ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering

This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.

Learn More

90003-2008

IEEE Guide--Adoption of ISO/IEC 90003:2004 Software Engineering--Guidelines for the Application of ISO 9001:2000 to Computer Software

This standard provides guidance to users of IEEE standards as to how to meet the quality management expectations of ISO 9001:2000 clauses and sub-clauses in a software development context by adopting ISO/IEC 90003 (the software development guidance document for ISO 9001) and adding an informative annex to cross-reference IEEE S2ESC standards to relevant ISO 9001 material. This standard is identical to ISO/IEC 90003 but contains an additional informative annex, Annex C, cross-referencing material in ISO 9001 with material in S2ESC standards that could be helpful in meeting the intent of ISO 9001, as well as a second additional annex, Annex D, which is a bibliography of the specific IEEE standards referenced.

Learn More

90003-2015

IEEE Standard Adoption of ISO/IEC 90003:2014, Software Engineering -- Guidelines for the Application of ISO 9001:2008 to Computer Software

This International Standard provides guidance for organizations in the application of ISO 9001:2008 to the acquisition, supply, development, operation, and maintenance of computer software and related support services. It does not add to or other wise change the requirements of ISO 9001:2008.

Learn More

15026-1-2011

IEEE Trial-Use Standard--Adoption of ISO/IEC TR 15026-1:2010 Systems and Software Engineering--Systems and Software Assurance--Part 1: Concepts and Vocabulary

This trial-use standard adopts ISO/IEC TR 15026-1:2010, which defines terms and establishes an extensive and organized set of concepts and their relationships for software and systems assurance, thereby establishing a basis for shared understanding of the concepts and principles central to ISO/IEC 15026 across its user communities. It provides information to users of the subsequent parts of ISO/IEC 15026, including the use of each part and the combined use of multiple parts. Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in ISO/IEC 15026.

Learn More

15026-2-2011

IEEE Standard--Adoption of ISO/IEC 15026-2:2011 Systems and Software Engineering--Systems and Software Assurance--Part 2: Assurance Case

ISO/IEC 15026-2:2011 is adopted by this standard. ISO/IEC 15026-2:2011 specifies minimum requirements for the structure and contents of an assurance case to improve the consistency and comparability of assurance cases and to facilitate stakeholder communications, engineering decisions, and other uses of assurance cases. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R&M) case. ISO/IEC 15026-2:2011 does not place requirements on the quality of the contents of an assurance case and does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.

Learn More

Newswire

Sign up for our monthly newsletter to learn about new developments, including resources, insights and more.