ISO/IEC JTC 1/SC 7/WG 7 - Life cycle management

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

This document provides guidance for the maintenance of software, based on the maintenance process and its activities and tasks defined in ISO/IEC/IEEE 12207:2017, 6.4.13. Moreover, this document describes the maintenance process in greater detail and establishes definitions for the various types of maintenance. This includes maintenance for multiple software products with the same maintenance resources. “Maintenance” in this document means software maintenance unless otherwise stated. The document does not address the operation of software and the operational functions, e.g. backup, recovery, system administration, which are normally performed by those who operate the software. However, it does include the related disposal process defined in ISO/IEC/IEEE 12207:2017, 6.4.14. This document is written primarily for managers, maintenance organizations, quality managers, users and acquirers of systems containing software. Many of the activities and tasks discussed in this document apply equally to maintenance services, as well as to maintained software products. For example, in a COTS intensive system, maintenance services are performed to sustain the product in operations. While the scope of this document is software maintenance, hardware and hardware costs are important considerations for maintenance.

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.

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.

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.

This document is a guideline for the application of 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. This document 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. This document applies to the acquisition, supply, design and development, transition, operation, maintenance, and disposal (whether performed internally or externally to an organization) of software systems, products, and services (including software as a service (SaaS)), and the software portion of any system. Software includes the software portion of firmware. The guidance on processes, activities, and tasks in this document can also be applied during the acquisition of a system that contains software. The guidance in this document can also be used as a basis for selecting, establishing, and improving organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. In the context of this document, 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 (SoI) or as an enabling system or infrastructure. Thus, the choice of whether to apply this document for guidance to the software life cycle processes, or ISO/IEC/IEEE 24748-2, depends on the SoI. At a high level, both documents have the same life cycle process framework, but differ in guidance for activities and tasks to perform software engineering or systems engineering, respectively. The processes and process groups in this document are identical in their purpose and outcomes with those in ISO/IEC/IEEE 12207:2017 and in ISO/IEC/IEEE 15288:2015, with one exception: the System/Software Requirements Definition process of ISO/IEC/IEEE 12207:2017 and this document has a different name from the System Requirements Definition process of ISO/IEC/IEEE 15288:2015. Use of the guidance in this document is appropriate regardless of software system size or complexity or organizational size. The process outcomes from the ISO/IEC/IEEE 12207:2017 life cycle processes are meant to be generic and applicable to the engineering of any software system in any size organization. This document does not prescribe nor detail a specific software life cycle model, development methodology, method, modelling approach, or technique and method. The variety of ways for implementing software (e.g., development of new code, integration of existing open source components and commercial products, or modifications to existing software, including transition to new platforms) make it impossible to detail specific procedures. This document does not establish a management system or provide guidance on the use of any management system standard. However, it is intended to be compatible with the quality management system specified by ISO 9001, the service management system specified by ISO/IEC 20000-1, the IT asset management system specified by ISO/IEC 19770 (all parts), and the information security management system specified by ISO/IEC 27000. Clause 6 provides guidance on aspects of purposes, outcomes, activities, and tasks in ISO/IEC/IEEE 12207:2017. However, this document does not repeat the detailed requirements and recommendations for purposes, outcomes, activities, and tasks for each life cycle process found in ISO/IEC/IEEE 12207:2017. Clause 6 also pr

This document provides the mapping expressing corresponding relations between software life cycle processes in ISO/IEC/IEEE 12207:2017 and the processes in ISO/IEC 12207:2008. These relations are demonstrated by means of mapping tables that show relationships between activities and tasks, and process outcomes. This mapping assists users of ISO/IEC 12207:2008 to transition to using ISO/IEC/IEEE 12207:2017. This document will help users understand the differences between the reference processes and requirements of the two editions of ISO/IEC/IEEE 12207, and any potential gaps or process enhancements that can be needed in seeking conformance to and/or using ISO/IEC/IEEE 12207:2017. Also, this document provides to such users the mapping which helps to identify corresponding process outcomes, activities and tasks of processes for software systems in ISO/IEC/IEEE 12207:2017. The mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008 in this document can be used as a basis to continuously conduct, improve and extend current process assets including software specific process assets based on ISO/IEC 12207:2008 for effective implementation of ISO/IEC/IEEE 12207:2017. These process activities and tasks can be applied iteratively.

1.1 Purpose This document is intended to aid project managers in managing to successful conclusion those projects concerned with systems, including software systems. This document specifies the required content of the project management plan (PMP). This document also quotes the extracted purpose and outcome statements from the technical management processes of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, and adds detailed guidance for managing projects that use these processes for systems, including software systems. 1.2 Field of application This document is written for those who use or plan to use ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 on projects dealing with systems, including software systems, regardless of project scope, products, methodology, size or complexity. The field of application of this document spans the whole system or software life cycle and addresses all project management roles, specifically: — those responsible for establishing and continuously improving their organization's policies for implementing ISO/IEC/IEEE 15288 system life cycle processes and ISO/IEC/IEEE 12207 software life cycle processes; — those responsible for executing any ISO/IEC/IEEE 15288 system life cycle process or ISO/IEC/IEEE 12207 software life cycle process at a project level. — organizations or individuals subcontracting a project management effort. In many organizations, the various responsibilities of project management are assigned to more than one person. Where the term "project manager" is used in this document, the guidance, advice or normative requirement is taken as applying to the applicable role within the organization. This document is intended to provide guidance for two-party situations and can be equally applied where the two parties are from the same organization. This document can also be used by a single party as self-imposed tasks. This document can also serve as guidance in multi-party situations, where high risks are inherent in the supply and integration of complex software-based systems, and procurement can involve several vendors, organizations or contracting parties. 1.3 Limitations The normative content specifications for PMPs and the guidance for application of the technical management processes have general application across the scope of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, but are developed with a focus on projects dealing with systems with a significant software element, and software systems.

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. NOTE 1 Throughout the document, there is mixed use of "system of systems" and "systems of systems". "SoS" could refer to a system of systems or systems of systems. Similarly, "CS" could refer to a constituent system or constituent systems. 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. NOTE 2 In many cases, this document notes that ISO/IEC/IEEE 15288 processes or process outcomes "? applies as stated to SoS." Some interpretation within the context of SoS can still be needed.

This document provides guidance on the relationship between ISO/IEC 16350:2015 and a commonly used application management framework, ASL. It can be used by any organization or person wishing to understand how ASL can be used with ISO/IEC 16350:2015, including: a) an internal or external application management organization that has demonstrated or intends to demonstrate conformity to the requirements specified in ISO/IEC 16350:2015 and is seeking guidance on the use of ASL to establish and improve an AMS and the processes; b) an application management organization that already uses ASL and is seeking guidance on how ASL can be used to support efforts to demonstrate conformity to the requirements specified in ISO/IEC 16350:2015; c) an assessor or auditor who wishes to understand the use of ASL as support to achieve the requirements specified in ISO/IEC 16350:2015. The correlations provided in this document relate to the 2nd version of ASL® (ASL2). Clause 4 describes how ASL® can support the demonstration of conformity to ISO/IEC 16350:2015. Clause 5 relates chapters in ASL® to clauses in ISO/IEC 16350:2015.

1.1 Purpose This document provides a set of critical system of systems (SoS) considerations to be addressed at key points in the life cycle of the system of interest (SoI). This document refers to considerations that apply to an SoI that is a constituent system that interacts in an SoS. The considerations and life cycle model align with those which are already defined in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 24748-1. Selected subsets of these considerations can be applied throughout the life of systems through the involvement of stakeholders. The ultimate goal is to achieve customer satisfaction, so that when delivered, the SoI will operate effectively in the operational or business environment which is typically 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. 1.2 Field of application This document addresses SoS considerations that apply to systems at each stage of their respective life cycles. There is a wide variety of systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans and evolution. This document is concerned with describing the system of systems considerations that apply to a system that is the SoI; that is a constituent system within a system of systems. It applies to one-of-a-kind systems, mass produced systems or customized, adaptable systems. 1.3 Limitations This document does not detail the approach to addressing system of systems considerations in terms of methods or procedures. This document does not detail the described documentation in terms of name, format, explicit content and recording media of documentation.

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.

This document defines assurance-related terms and establishes an organized set of concepts and relationships to form a basis for shared understanding across user communities for assurance. It provides information to users of the other parts of ISO/IEC/IEEE 15026 including the combined use of multiple parts. The essential concept introduced by ISO/IEC/IEEE 15026 (all parts) 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 ISO/IEC/IEEE 15026 (all parts). A variety of potential users of ISO/IEC/IEEE 15026 (all parts) exists including developers and maintainers of assurance cases and those who wish to develop, sustain, evaluate or acquire a system that possesses requirements for specific properties in such a way as to be more certain of those properties and their requirements. ISO/IEC/IEEE 15026 (all parts) uses concepts and terms consistent with ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and generally consistent with the ISO/IEC 25000 series, but the potential users of ISO/IEC/IEEE 15026 (all parts) need to understand the differences from concepts and terms to which they may be accustomed. This document attempts to clarify these differences. The primary purpose of this document is to aid users of the other parts of ISO/IEC/IEEE 15026 by providing context, concepts and explanations for assurance, assurance cases and integrity levels. While essential to assurance practice, details regarding exactly how to measure, demonstrate or analyse particular properties are not covered. These are the subjects of more specialized standards of which a number are referenced and included in the Bibliography.

This document is a guideline for the application of ISO/IEC/IEEE 15288:2015. It addresses system, life cycle, organizational, project, and process, concept application, principally through reference to ISO/IEC/IEEE 24748‑1 and ISO/IEC/IEEE 15288:2015. It gives guidance on applying ISO/IEC/IEEE 15288:2015 from the aspects of strategy, planning, application in organizations, and application on projects. It also provides comparison of the differences between ISO/IEC/IEEE 15288:2015 and the prior versions, ISO/IEC 15288:2008. This document is intended to be consistent with both ISO/IEC/IEEE 24748‑1 and ISO/IEC/IEEE 15288:2015 in its treatment of life-cycle concepts and systems engineering processes. NOTE Systems engineering for defense programs is addressed in IEEE Std 15288.1, Application of Systems Engineering on Defense Programs.

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. It does not add to or otherwise change the requirements of ISO 9001:2015. Annex A provides a table pointing to additional guidance on the implementation of ISO 9001:2015, available in ISO/IEC JTC 1/SC 7, ISO/IEC JTC 1/SC 27 and ISO/TC 176 International Standards. The guidelines provided in this document are not intended to be used as assessment criteria in quality management system registration/certification. However, some organizations can consider it useful to implement the guidelines proposed in this document and can be interested in knowing whether the resultant quality management system is compliant or not with this document. In this case, an organization can use both this document and ISO 9001 as assessment criteria for quality management systems in the software domain.

This document: — specifies the required processes implemented in the engineering activities that result in requirements for systems and software products (including services) throughout the life cycle; — provides guidelines for applying the requirements and requirements-related processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207; — specifies the required information items produced through the implementation of the requirements processes; — specifies the required contents of the required information items; — provides guidelines for the format of the required and related information items. This document is applicable to: — those who use or plan to use ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity; — anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC/IEEE 15288 and/or ISO/IEC/IEEE12207; — those who use or plan to use ISO/IEC/IEEE 15289 on projects dealing with man-made systems, software-intensive systems, software and hardware products and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity; — anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conforms to ISO/IEC/IEEE 15289.

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.

ISO/IEC/IEEE 12207:2017 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 document can also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288:2015, Systems and software engineering?System life cycle processes. In the context of this document and ISO/IEC/IEEE 15288, 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 document 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 documents have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.

ISO/IEC/IEEE 24748-5:2017 provides a common framework for planning and controlling the technical processes and activities to produce and sustain software products. The complete life cycle is covered by this document, from idea conception to the retirement of a software product. The framework described by this document provides for best practices in communication and cooperation among parties that plan for, develop, utilize, and manage modern software. ISO/IEC/IEEE 24748-5:2017: - specifies the required information items to be produced through the implementation of the required planning and control processes; - specifies the required content of the required information items; - gives guidelines for the format and content of the required and related information items; and - details the processes necessary to develop and implement a software plan. ISO/IEC/IEEE 24748-5:2017 is intended to provide guidance for parties involved in the planning of software engineering at all stages of the software life cycle. It is intended to provide a common framework for two-party and multi-party collaborations and can be applied where the parties are from the same organization. This document can also be used by a single party. ISO/IEC/IEEE 24748-5:2017 is applicable to: - those who use ISO/IEC/IEEE FDIS 12207 on projects dealing with software products and services related to those products; - those who are responsible for the technical management of the development of software systems; - organizations and individuals performing software development activities; and - organizations and individuals developing information items during the development of software.

ISO/IEC/IEEE 15939:2017 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. ISO/IEC/IEEE 15939:2017 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.

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).

ISO/IEC 15026-3:2015 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 dependences. This part of ISO/IEC 15026 is applicable to systems and software and is intended for use by the following: a) definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies; b) users of integrity levels such as developers and maintainers, suppliers and acquirers, system or software users, assessors of systems or software and administrative and technical support staff of systems and/or software products. One important use of integrity levels is by suppliers and acquirers in agreements; for example, to aid in assuring safety, financial, or security characteristics of a delivered system or product. ISO/IEC 15026-3:2015 does not prescribe a specific set of integrity levels or their integrity level requirements. In addition, it does not prescribe the way in which integrity level use is integrated with the overall system or software engineering life cycle processes. It does, however, provide an example of use of this part of ISO/IEC 15026 in Annex A.

The scope of ISO/TS 30103:2015 is to indicate how to apply the life cycle processes in ISO/IEC/IEEE 15288:2008 to achieve quality in the context of a specific product. It is independent of any tailoring that may be made to modify the generic process descriptions to suit the needs of a particular context. Even after any applicable tailoring, there is a need to apply the resulting process guidance and determine the specific detailed activities, tasks and associated success criteria for each of the process instances needed to deliver the target system. That is the focus of the framework described in ISO/TS 30103:2015. ISO/TS 30103:2015 is applicable to those who use or plan to use ISO/IEC/IEEE 15288:2008 on projects dealing with man-made systems, software-intensive systems, software products, and services related to those systems and products, regardless of project scope, product(s), service(s), methodology, size or complexity, those who use or plan to use ISO/IEC/IEEE 15289 on projects dealing with man-made systems, software-intensive systems, software products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, anyone performing technical processes and tasks, those who are responsible for the technical management of projects concerned with the development of systems, those responsible for performing ISO/IEC/IEEE 15288:2008 life cycle processes at a project level, organizations and individuals subcontracting a project management effort, anyone developing systems engineering management documentation to complete technical planning aspects of their project processes, anyone performing systems engineering activities, project managers responsible for staffing projects and identifying competency development needs, anyone developing information items during the application of project and technical processes, and anyone performing project and technical processes to aid in ensuring that the information items developed during these processes conform to ISO/IEC/IEEE 15289.

ISO 16350:2015 establishes a common framework for application management processes with well-defined terminology that can be referenced by the software industry. It contains processes, activities, and tasks that apply during the stage of operation and use from the point of view of the supplier organization that enhances, maintains, and renews the application software and the software-related products such as data-structures, architecture, designs, and other documentation. It applies to the supply, maintenance, and renewal of applications, whether performed internally or externally with respect to the organization that uses the applications.

ISO/IEC TS 24748-6:2016 - specifies activities and processes to be implemented for engineering the integration of systems-of-interest throughout the life cycle (systems made of products and/or services; see Note 1), - provides guidance for the integration process and its relationships to other system life cycle processes as described in ISO/IEC/IEEE 15288, - specifies the information items to be produced through the implementation of the integration engineering (integration process and its relationships to other system life cycle processes), - specifies the contents of the information items, and - provides guidelines for the format of the information items. ISO/IEC TS 24748-6:2016 can be applied to - those who use or plan to use ISO/IEC/IEEE 15288 on projects dealing with man-made systems, software-intensive systems, products and services related to those systems, regardless of project scope, methodology, size or complexity, and - anyone performing integration engineering activities to aid in ensuring that the application of the integration process and its relationships to other system life cycle processes conform to ISO/IEC/IEEE 15288.

ISO/IEC TS 24748-1:2016 provides guidelines for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC 12207. This Technical Specification: - 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 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.

ISO/IEC/IEEE 15288:2015 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. ISO/IEC/IEEE 15288:2015 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. ISO/IEC/IEEE 15288:2015 concerns those systems that are man-made 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.

ISO/IEC 90003:2014 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. ISO/IEC 90003:2014 does not add to or otherwise change the requirements of ISO 9001:2008. The guidelines provided in ISO/IEC 90003:2014 are not intended to be used as assessment criteria in quality management system registration/certification. The application of ISO/IEC 90003:2014 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. ISO/IEC 90003:2014 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:2008, in particular ISO/IEC 12207:2008.

ISO/IEC 15026-1:2013 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 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.

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

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.

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.

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.

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.

ISO/IEC TR 24748-1:2010 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.

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.

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

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.

ISO/IEC 12207:2008 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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware. ISO/IEC 12207:2008 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. ISO/IEC 12207:2008 also provides a process that can be employed for defining, controlling, and improving software life cycle processes. The processes, activities and tasks of ISO/IEC 12207:2008 - either alone or in conjunction with ISO/IEC 15288 - may also be applied during the acquisition of a system that contains software.

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.

ISO/IEC 14764:2006 describes in greater detail management of the Maintenance Process described in ISO/IEC 12207, including Amendments. It also establishes definitions for the various types of maintenance. ISO/IEC 14764:2006 provides guidance that applies to planning, execution and control, review and evaluation, and closure of the Maintenance Process. The scope of ISO/IEC 14764:2006 includes maintenance for multiple software products with the same maintenance resources. "Maintenance" in ISO/IEC 14764:2006 means software maintenance unless otherwise stated. ISO/IEC 14764:2006 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. It provides the framework, precise terminology and processes to allow the consistent application of technology (tools, techniques and methods) to software maintenance. ISO/IEC 14764:2006 provides guidance for the maintenance of software. The basis for the Maintenance Process and its activities comes from the definitions of ISO/IEC 12207. It 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 and system administration, which are normally performed by those who operate the software. ISO/IEC 14764:2006 is written primarily for maintainers of software and additionally for those responsible for development and quality assurance. It may also be used by acquirers and users of systems containing software who may provide inputs to the maintenance plan.

ISO/IEC 90003:2004 provides guidance for organizations in the application of ISO 9001:2000 to the acquisition, supply, development, operation and maintenance of computer software and related support services. ISO/IEC 90003:2004 does not add to or otherwise change the requirements of ISO 9001:2000. The guidelines provided in ISO/IEC 90003:2004 are not intended to be used as assessment criteria in quality management system registration/certification. The application of ISO/IEC 90003:2004 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. ISO/IEC 90003:2004 identifies the issues which 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:2000: in particular ISO/IEC 12207, ISO/IEC TR 9126, ISO/IEC 14598, ISO/IEC 15939 and ISO/IEC TR 15504.

ISO/IEC TR 19760:2003 is a Technical Report that provides guidance for application of the International Standard ISO/IEC 15288 Systems Engineering - System life cycle processes in regard to systems and projects irrespective of size and type. ISO/IEC TR 19760:2003 can be used as a companion document to the International Standard by those who: apply the International Standard within their organization; use the International Standard in regard to a specific system; prepare organizational and domain specific standards based on the International Standard. ISO/IEC TR 19760:2003 elaborates on factors that should be considered when applying the International Standard. It does this in the context of the various ways in which ISO/IEC 15288 may be applied. ISO/IEC TR 19760:2003 provides example application concerns lists for user consideration. However, ISO/IEC TR 19760:2003 is not intended to provide how-to guidance for each application area of the International Standard. Guidance is provided for appropriate tailoring of the International Standard for application to specific systems or projects. ISO/IEC TR 19760:2003 also provides appropriate links to other ISO documents for supporting application of the International Standard and to aid in assessing the effectiveness of the application of the International Standard.

Establishes a system for software life cycle processes with well-defined terminology. Contains processes, activities and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product and software services.