ISO/IEC/IEEE 15289:2019本文件规定了所有已识别系统、软件生命周期和服务管理信息项（文件）的目的和内容。信息项内容根据通用文件类型（如第7条所示）和文件的具体用途（如第10条所示）进行定义
本文档假设一个组织正在执行生命周期流程，或提供系统或软件工程服务，使用以下任一项或两项:
-ISO/IEC/IEEE 12207:2017软件生命周期过程
-ISO/IEC/IEEE 15288:2015系统生命周期过程
ISO/IEC/IEEE 12207:2017和ISO/IEC/IEEE 15288:2015定义了一个信息管理过程，但没有“在名称、格式、明确内容和记录媒体方面详细说明信息项”（ISO/IEC/IEEE 12207:2017，1.4）。这些标准确定、建议或要求许多文件项目。本文件提供了从上述标准到一组信息项的流程映射。 它提供了一种一致的方法来满足系统和软件工程以及工程服务管理的信息和文档需求
本文件中定义的通用文件类型用于识别支持ISO/IEC/IEEE 12207:2017和ISO/IEC/IEEE 15288:2015要求的过程所需的信息。通用文档类型（可称为信息项类型）用于识别支持流程所需的信息
对于每个生命周期流程或服务，可以准备政策、计划、程序和报告，以及大量记录、请求、说明和规范。这种文档模式的详细说明将比ISO/IEC/IEEE 12207:2017或ISO/IEC/IEEE 15288:2015规定的更严格。正如ISO/IEC/IEEE 15288:2015第1.4节所指出的，“本文件的用户负责为项目选择生命周期模型，并将本文件中的过程、活动和任务映射到该模型中。 双方还负责选择和应用适用于本项目的适当方法、方法、模型和技术。“因此，根据项目或组织目的的需要，按照生命周期模型对信息项进行组合或细分，如第4条和第5条中的进一步定义。
本文件不是管理体系标准，也没有建立服务管理体系、质量管理体系或资产管理体系。本文件的范围不包括以下内容:
a） 建议输入数据或输入信息项的格式或内容，但也属于输出信息项的输入项的内容除外
b） 关于合并或细分信息项和类似性质的信息项内容的说明
c） 为系统或软件生命周期数据、记录、信息项或文档（如电子出版系统、内容管理系统或数据存储库）选择适当的演示格式、交付媒体和维护技术的指南；
注ISO/IEC/IEEE 26531规定了内容管理和组件内容管理系统的要求。ISO/IEC 26514提供了用户文档格式指南（用户信息）
d） 与一般业务、合同、组织和财务管理相关的信息项的详细内容，不特定于系统和软件工程以及工程服务管理，例如业务战略、合同变更通知（协议变更报告）、人力资源和投资政策、人员选择标准、，财务预算、会计政策和程序、成本报告或工资数据
e） 仅显示ISO/IEC/IEEE 12207:2017或ISO/IEC/IEEE 15288:2015子条款批准的信息项，如ISO/IEC/IEEE 12207:2017，6.4.10.3 c）3）
f） 任何ISO/IEC/IEEE 15288:2015或ISO/IEC/IEEE 12207:2017子条款未明确或隐含地标识有关过程、活动或任务的信息记录，例如ISO/IEC/IEEE 12207: 2017年6.2.4.3 c）
g） 非信息项或信息项中使用的记录的工作产品、模型、软件和生命周期产品和服务的其他工件。

ISO/IEC/IEEE 15289:2019 This document specifies the purpose and content of all identified systems and software life‐cycle and service management information items (documentation). The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document, as presented in Clause 10.
This document assumes an organization is performing life‐cycle processes, or delivering system or software engineering services, using either or both of the following:
- ISO/IEC/IEEE 12207:2017 software life cycle processes;
- ISO/IEC/IEEE 15288:2015 system life cycle processes.
ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015 define an Information Management process, but do not "detail information items in terms of name, format, explicit content, and recording media" (ISO/IEC/IEEE 12207:2017, 1.4). These standards identify, recommend or require a number of documentation items. This document provides a mapping of processes from the above standards to a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and engineering service management.
The generic document types defined in this document are used to identify the information necessary to support the processes required by ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015. The generic document types (which can be referred to as information item types) are used to identify the information necessary to support the processes.
For each life‐cycle process or service, it would be possible to prepare a policy, plan, procedures and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 12207:2017 or ISO/IEC/IEEE 15288:2015. As ISO/IEC/IEEE 15288:2015, 1.4 points out, "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." Thus, information items are combined or subdivided consistent with the life cycle model, as needed for project or organizational purposes, as further defined in Clause 4 and Clause 5.
This document is not a management system standard and does not establish a service management system, quality management system, or asset management system. The scope of this document does not include the following:
a) the format or content of recommended input data or input information items, except for the content of those input items that are also output information items;
b) instructions on combining or subdividing information items and information item contents of a similar nature;
c) guidance on selecting an appropriate presentation format, delivery media and maintenance technology for systems or software life‐cycle data, records, information items or documentation, such as electronic publishing systems, content management systems or data repositories;
NOTE ISO/IEC/IEEE 26531 provides requirements for content management and component content management systems. ISO/IEC 26514 provides guidance on formats for user documentation (information for users).
d) detailed content for information items related to general business, contractual, organizational and financial management that is not specific to systems and software engineering and engineering service management, such as business strategies, contract change notices (agreement change report), human resources and investment policies, personnel selection criteria, financial budgeting and accounting policies and procedures, cost reports, or payroll data;
e) information items showing only approval of an ISO/IEC/IEEE 12207:2017 or ISO/IEC/IEEE 15288:2015 subclause, such as ISO/IEC/IEEE 12207:2017, 6.4.10.3 c) 3);
f) any ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207:2017 subclause not explicitly or implicitly identifying the recording of information about a process, activity or task, for example, ISO/IEC/IEEE 12207:2017, 6.2.4.3 c);
g) work products, models, software, and other artifacts of life‐cycle products and services that are not information items or records used in information items.