Systems and software engineering — Content of life-cycle information items (documentation)
Introduction: The purpose of this document is to provide requirements for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service processes. This document specifies the purpose and content of all identified systems and software life‐cycle information items, as well as information items for information technology service management. The information item contents are defined according to generic document types and the specific purpose of the document. Information items are combined or subdivided as needed for project or organizational purposes. This document is based on the life‐cycle processes specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015. ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015 establish a common framework for system and software life‐cycle processes. These standards define an identical process model for the process purposes and outcomes, though their tasks and activities differ. Their process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life‐cycle model, methodology or technique. Their processes are grouped in four categories: agreement, organizational project‐enabling, technical management and technical. ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015 establish a common Information Management process as part of a framework for systems and software life‐cycle processes, and iden
Scope: 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 fo