系统和软件工程.生命周期信息项目(文件)的内容

[中文适用范围]： 本文件规定了所有已识别系统和软件生命周期以及服务管理信息项（文档）的目的和内容。信息项内容是根据第 7 条中提出的通用文档类型@以及第 10 条中提出的文档的具体目的@来定义的。本文档假设组织正在执行生命周期流程@或交付系统或软件工程services@ 使用以下一项或两项： ?? 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.3c); g) 工作产品@模型@软件@以及生命周期产品和服务的其他工件，它们不是信息项或信息项中使用的记录。 [外文原描述]： 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.