This International Standard assumes an organization is implementing life cycle processes in conformance with
ISO/IEC 15288:2002 or ISO/IEC 12207:1995, with Amendments 1 and 2. ISO/IEC 15288:2002 defines a set
of processes for managing and performing the stages of a systems life cycle. It defines an Information
Management process, but “does not detail documentation in terms of name, format, explicit content, and
recording media” (1.3). ISO/IEC 12207:1995 with AMD 1 and 2, establishes a common framework for software
life cycle processes, and in passing identifies or requires a number of documentation items.
The purpose of this International Standard is to guide users of ISO/IEC 12207:1995 (with Amendments 1 and 2)
and ISO/IEC 15288:2002 in identifying and planning the specific information items to be produced during
systems and software life cycles. As stated in G.5 of IEEE/EIA 12207.0:1996.
This International Standard identifies the purpose and content of all identified Systems and Software Life
Cycle information items. The information item contents are defined according to generic document types, as
presented in Clause 7, and the specific purpose of the document (Clause 10). The generic document types
(which may be referred to as information item types to conform to [3]) are to be used to identify the information
necessary to support the ISO/IEC 15288:2002 agreement, enterprise, project, and technical processes; and
the ISO/IEC 12207:1995, primary, supporting, and organizational life cycle processes.
This International Standard identifies records and information items based on analysis of references in
ISO/IEC 15288:2002 and ISO/IEC 12207:1995, which in some cases provide partial or complete outlines for
the content of specific documents. However, the requirements for the life-cycle processes do not uniquely and
unambiguously state the requirements for the information items contents or the information needed by a user
of an information item. Moreover, the information from the life-cycle processes may overlap or may be created
and revised at different times. In short, the analyzed references do not result in a logically complete list of
information items. For example, for each life-cycle process, it would be possible to prepare a plan, procedures,
and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of a documentation schema would be more rigorous than specified by either ISO/IEC 15288:2002 or
ISO/IEC 12207:1995. Thus, information items may be combined or subdivided as needed for project or
organizational purposes, as further defined in Clause 2, Applicability, and Clause 3, Conformance.