本文档为软件生命周期过程建立了一个通用框架，其中包含定义良好的术语，可供软件行业参考。它包含在软件系统、产品和服务的获取、供应、开发、操作、维护或处置过程中适用的过程、活动和任务。这些生命周期过程是通过利益相关者的参与来完成的，最终目标是实现客户满意度。本文件适用于软件系统、产品和服务的获取、供应、开发、运行、维护和处置（无论是在组织内部还是外部执行），以及任何系统的软件部分，软件包括固件的软件部分。包括为软件产品和服务提供上下文所需的系统定义的那些方面。 定义一个组织的生命周期，或提供一个软件生命周期的控制过程。本文件中的过程、活动和任务也可在包含软件的系统的采购过程中应用，可以单独使用，也可以与ISO/IEC/IEEE 15288:2015《系统和软件工程-系统生命周期过程》结合使用。在本文件和ISO/IEC/IEEE 15288的背景下，有一系列人造系统，从很少使用或不使用软件的系统到主要关注软件的系统。很少会遇到没有软件的复杂系统，所有软件系统都需要物理系统组件（硬件）来运行，无论是作为感兴趣的软件系统的一部分，还是作为使能系统或基础设施。因此，选择是否将本文件应用于软件生命周期过程，或ISO/IEC/IEEE 15288: 2015年，系统和软件工程系统生命周期过程取决于感兴趣的系统。两个文档中的过程具有相同的过程目的和过程结果，但分别在执行软件工程或系统工程的活动和任务上有所不同。1.2目的本文件的目的是提供一套定义的过程，以促进软件系统生命周期内收单机构、供应商和其他利益相关者之间的沟通。本文档面向软件系统、产品和服务的收单机构、供应商、开发人员、集成商、运营商、维护人员、经理、质量保证经理和用户。它可以由单个组织以自我强加的方式或在多方情况下使用。当事人可以来自同一个组织，也可以来自不同的组织，情况可以是非正式协议，也可以是正式合同。 本文档中的流程可作为建立业务环境的基础，例如方法、程序、技术、工具和经过培训的人员。附录A提供了有关这些软件生命周期过程裁剪的规范性指导。 1.3应用领域本文件适用于软件系统、产品和服务的整个生命周期，包括概念、开发、生产、使用、支持和退役，以及它们的获取和供应，无论是在组织内部还是外部执行。本文档的生命周期过程可以并发、迭代和递归地应用于软件系统，并增量应用于其元素。软件系统的用途、应用领域、复杂性、规模、新颖性、适应性、数量、位置、寿命和进化等方面都有很多种。 本文档描述了构成人造软件系统生命周期的过程。因此，一种定制的软件适用于一种通用的软件系统。它还适用于完整的独立软件系统，以及嵌入并集成到更大、更复杂和完整系统中的软件系统。本文件提供了一个流程参考模型，以流程目的和成功执行活动任务所产生的流程结果为特征。附录B列出了可能与各种过程相关的工件和信息项的示例。因此，本文件可用作参考模型，以支持ISO/IEC 33002:2015中规定的过程评估。附录C提供了有关使用软件生命周期过程作为过程参考模型的信息。 附录D描述了过程参考模型中使用的过程结构。附录I提供了本文件与ISO/IEC/IEEE 12207:2008在过程名称和过程结果层面的对应关系。1.4限制本文件未规定特定的软件生命周期模型、开发方法、方法、建模方法或技术。本文档的用户负责为项目选择生命周期模型，并将本文档中的流程、活动和任务映射到该模型中。双方还负责选择和应用适用于本项目的适当方法、方法、模型和技术。本文件未建立管理体系或要求使用任何管理体系标准。然而，它旨在与ISO 9001规定的质量管理体系、ISO/IEC 20000规定的服务管理体系兼容- 1（IEEE Std 20000-1），以及ISO/IEC 27000规定的信息安全管理系统。本文件不详细说明信息项的名称、格式、明确内容和记录介质。ISO/IEC/IEEE 15289规定了生命周期过程信息项（文件）的内容。

This document 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 applicable during the acquisition, supply, development, operation, maintenance or disposal of software systems, products, and services. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction.This document applies to the acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of software systems, products and services, and the software portion of any system, Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software products and services are included.This document 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.1.2 PurposeThe purpose of this document is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software system.This document is written for acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations and the situation can range from an informal agreement to a formal contract.The processes in this document can be used as a basis for establishing business environments, e.g., methods, procedures, techniques, tools and trained personnel. Annex A provides normative direction regarding the tailoring of these software life cycle processes. 1.3 Field of applicationThis document applies to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support and retirement, and to their acquisition and supply, whether performed internally or externally to an organization. The life cycle processes of this document can be applied concurrently, iteratively and recursively to a software system and incrementally to its elements.There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans and evolution. This document describes the processes that comprise the life cycle of man-made software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex and complete systems.This document provides a process reference model characterized in terms of the process purpose and the process outcomes that result from the successful execution of the activity tasks. Annex B lists examples of artifacts and information items that may be associated with various processes. This document can therefore be used as a reference model to support process assessment as specified in ISO/IEC 33002:2015. Annex C provides information regarding the use of the software life cycle processes as a process reference model. Annex D describes the process constructs for use in the process reference model. Annex I provides the correspondence between this document and ISO/IEC/IEEE 12207:2008 at the level of process name and process outcome.1.4 LimitationsThis document does not prescribe a specific software life cycle model, development methodology, method, modelling approach, or technique. The users of this document are responsible for selecting a life cycle model for the project and mapping the processes, activities, and tasks in this document into that model. The parties are also responsible for selecting and applying appropriate methodologies, methods, models and techniques suitable for the project.This document does not establish a management system or require 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 (IEEE Std 20000-1), and the information security management system specified by ISO/IEC 27000.This document does not detail information items in terms of name, format, explicit content and recording media. ISO/IEC/IEEE 15289 addresses the content for life cycle process information items (documentation).