This document is not a management system standard and does not establish a service management system, quality management system, or asset management system. 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. 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. 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. The generic document types (which can be referred to as information item types) are used to identify the information necessary to support the processes.įor 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. 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. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and engineering service management. This document provides a mapping of processes from the above standards to a set of information items. These standards identify, recommend or require a number of documentation items.
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).
ISO/IEC/IEEE 15288:2015 system life cycle processes. ISO/IEC/IEEE 12207:2017 software life cycle processes This document assumes an organization is performing life‐cycle processes, or delivering system or software engineering services, using either or both of the following: 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 specifies the purpose and content of all identified systems and software life‐cycle and service management information items (documentation).
0 kommentar(er)
