Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7310
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039567 {#7274
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39969
        #name: "IEEE/ISO/IEC 15289:2015"
        #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. 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). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), 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.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control 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 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” 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. This International Standard does not establish a service management system. The scope of this International Standard 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 system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n
          b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#7292
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 95
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#93054
  +product: App\Entity\Product\Product {#7310
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039567 {#7274
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39969
        #name: "IEEE/ISO/IEC 15289:2015"
        #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. 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). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), 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.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control 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 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” 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. This International Standard does not establish a service management system. The scope of this International Standard 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 system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n
          b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#7292
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 95
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039567 {#7274
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39969
        #name: "IEEE/ISO/IEC 15289:2015"
        #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. 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). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), 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.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control 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 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” 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. This International Standard does not establish a service management system. The scope of this International Standard 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 system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n
          b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#7292
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 95
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductType {#93234
  +product: App\Entity\Product\Product {#7310
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039567 {#7274
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39969
        #name: "IEEE/ISO/IEC 15289:2015"
        #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. 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). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), 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.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control 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 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” 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. This International Standard does not establish a service management system. The scope of this International Standard 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 system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n
          b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#7292
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 95
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039567 {#7274
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39969
        #name: "IEEE/ISO/IEC 15289:2015"
        #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. 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). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), 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.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control 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 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” 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. This International Standard does not establish a service management system. The scope of this International Standard 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 system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n
          b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#7292
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 95
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#93309
  +product: App\Entity\Product\Product {#7310
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039567 {#7274
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39969
        #name: "IEEE/ISO/IEC 15289:2015"
        #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. 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). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), 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.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control 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 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” 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. This International Standard does not establish a service management system. The scope of this International Standard 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 system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n
          b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#7292
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 95
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106892
    #id: 10917
    #code: "IEEE00005287"
    #attributes: Doctrine\ORM\PersistentCollection {#106875 …}
    #variants: Doctrine\ORM\PersistentCollection {#106872 …}
    #options: Doctrine\ORM\PersistentCollection {#106868 …}
    #associations: Doctrine\ORM\PersistentCollection {#106870 …}
    #createdAt: DateTime @1751039364 {#106900
      date: 2025-06-27 17:49:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#106873
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106925
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106892}
        #id: 38677
        #name: "IEEE/ISO/IEC 15289:2011"
        #slug: "ieee-iso-iec-15289-2011-ieee00005287-242569"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 15289:2011 provides requirements for identifying and planning the specific information items (information products, documentation) to be developed and revised during systems and software life cycles and service processes. It specifies the purpose and content of all identified systems and software data records and life cycle information items, as well as records and information items for information technology service management. The information item contents are<br />\n
          defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. For simplicity of reference, each information item is described as if it were published as a separate document. However, information items may be unpublished but available in a repository for reference, divided into separate documents or volumes, or combined with other information items into one document. ISO/IEC/IEEE 15289:2011 is based on the life cycle processes specified in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and the service management processes specified in ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard (IS) assumes an organization is implementing life cycle processes in conformance with ISO/IEC/IEEE 15288:2008, Systems and software engineering - System life cycle processes, or ISO/IEC/IEEE 12207:2008, Systems and software engineering - Software life cycle processes, or practicing Service Management in conformance with in ISO/IEC 20000-1:2005, Information technology -- Service management -- Part 1: Specification; and ISO/IEC 20000-2:2005, Information technology -- Service management -- Part 2: Code of practice. ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008 define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do &quot;not detail documentation in terms of name, format, explicit content, and recording media&quot; (ISO/IEC/IEEE 15288:2008, clause 1.4). ISO/IEC/IEEE 12207:2008 establishes a common framework for software life cycle processes and in passing identifies or requires a number of documentation items. The Process Reference Model does not represent a particular process implementation approach nor does it prescribe a system/software life cycle model, methodology, or technique. ISO 20000-1:2005 establishes general requirements for documents and records (3.2). ISO/IEC/IEEE 12207:2008 does not always specify when software information items are to be prepared, nor does it identify information item contents. This International Standard provides a mapping of ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008 clauses with a set of information items. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC/IEEE 15288:2008 agreement, enterprise, project, and technical processes; the ISO/IEC/IEEE 12207:2008, primary, supporting, and organizational life cycle processes, or the ISO/IEC 20000-1:2005 Service Management processes. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2008, ISO/IEC/IEEE 12207:2008, and ISO/IEC 20000-1:2005 and 20000-2:2005, 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 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 the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 15288:2008 or ISO/IEC/IEEE 12207:2008. As ISO/IEC/IEEE 15288:2008 points out (1.4), &quot;This International Standard does not detail the life cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.&quot; 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.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008<br />\n
          (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2005 for<br />\n
          identifying and planning the specific information items (information products) to be developed and revised<br />\n
          during systems and software life cycles and service processes. This International Standard is intended for use<br />\n
          as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008<br />\n
          (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes. b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005. The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Content of life-cycle information products (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106883 …}
    #channels: Doctrine\ORM\PersistentCollection {#106877 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106881 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106879 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106893 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106860
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106899
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1320102000 {#106898
      date: 2011-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#106890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106888 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106908
  +product: App\Entity\Product\Product {#106892
    #id: 10917
    #code: "IEEE00005287"
    #attributes: Doctrine\ORM\PersistentCollection {#106875 …}
    #variants: Doctrine\ORM\PersistentCollection {#106872 …}
    #options: Doctrine\ORM\PersistentCollection {#106868 …}
    #associations: Doctrine\ORM\PersistentCollection {#106870 …}
    #createdAt: DateTime @1751039364 {#106900
      date: 2025-06-27 17:49:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#106873
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106925
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106892}
        #id: 38677
        #name: "IEEE/ISO/IEC 15289:2011"
        #slug: "ieee-iso-iec-15289-2011-ieee00005287-242569"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 15289:2011 provides requirements for identifying and planning the specific information items (information products, documentation) to be developed and revised during systems and software life cycles and service processes. It specifies the purpose and content of all identified systems and software data records and life cycle information items, as well as records and information items for information technology service management. The information item contents are<br />\n
          defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. For simplicity of reference, each information item is described as if it were published as a separate document. However, information items may be unpublished but available in a repository for reference, divided into separate documents or volumes, or combined with other information items into one document. ISO/IEC/IEEE 15289:2011 is based on the life cycle processes specified in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and the service management processes specified in ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard (IS) assumes an organization is implementing life cycle processes in conformance with ISO/IEC/IEEE 15288:2008, Systems and software engineering - System life cycle processes, or ISO/IEC/IEEE 12207:2008, Systems and software engineering - Software life cycle processes, or practicing Service Management in conformance with in ISO/IEC 20000-1:2005, Information technology -- Service management -- Part 1: Specification; and ISO/IEC 20000-2:2005, Information technology -- Service management -- Part 2: Code of practice. ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008 define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do &quot;not detail documentation in terms of name, format, explicit content, and recording media&quot; (ISO/IEC/IEEE 15288:2008, clause 1.4). ISO/IEC/IEEE 12207:2008 establishes a common framework for software life cycle processes and in passing identifies or requires a number of documentation items. The Process Reference Model does not represent a particular process implementation approach nor does it prescribe a system/software life cycle model, methodology, or technique. ISO 20000-1:2005 establishes general requirements for documents and records (3.2). ISO/IEC/IEEE 12207:2008 does not always specify when software information items are to be prepared, nor does it identify information item contents. This International Standard provides a mapping of ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008 clauses with a set of information items. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC/IEEE 15288:2008 agreement, enterprise, project, and technical processes; the ISO/IEC/IEEE 12207:2008, primary, supporting, and organizational life cycle processes, or the ISO/IEC 20000-1:2005 Service Management processes. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2008, ISO/IEC/IEEE 12207:2008, and ISO/IEC 20000-1:2005 and 20000-2:2005, 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 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 the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 15288:2008 or ISO/IEC/IEEE 12207:2008. As ISO/IEC/IEEE 15288:2008 points out (1.4), &quot;This International Standard does not detail the life cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.&quot; 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.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008<br />\n
          (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2005 for<br />\n
          identifying and planning the specific information items (information products) to be developed and revised<br />\n
          during systems and software life cycles and service processes. This International Standard is intended for use<br />\n
          as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008<br />\n
          (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes. b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005. The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Content of life-cycle information products (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106883 …}
    #channels: Doctrine\ORM\PersistentCollection {#106877 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106881 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106879 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106893 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106860
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106899
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1320102000 {#106898
      date: 2011-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#106890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106888 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106892
    #id: 10917
    #code: "IEEE00005287"
    #attributes: Doctrine\ORM\PersistentCollection {#106875 …}
    #variants: Doctrine\ORM\PersistentCollection {#106872 …}
    #options: Doctrine\ORM\PersistentCollection {#106868 …}
    #associations: Doctrine\ORM\PersistentCollection {#106870 …}
    #createdAt: DateTime @1751039364 {#106900
      date: 2025-06-27 17:49:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#106873
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106925
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106892}
        #id: 38677
        #name: "IEEE/ISO/IEC 15289:2011"
        #slug: "ieee-iso-iec-15289-2011-ieee00005287-242569"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 15289:2011 provides requirements for identifying and planning the specific information items (information products, documentation) to be developed and revised during systems and software life cycles and service processes. It specifies the purpose and content of all identified systems and software data records and life cycle information items, as well as records and information items for information technology service management. The information item contents are<br />\n
          defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. For simplicity of reference, each information item is described as if it were published as a separate document. However, information items may be unpublished but available in a repository for reference, divided into separate documents or volumes, or combined with other information items into one document. ISO/IEC/IEEE 15289:2011 is based on the life cycle processes specified in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and the service management processes specified in ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard (IS) assumes an organization is implementing life cycle processes in conformance with ISO/IEC/IEEE 15288:2008, Systems and software engineering - System life cycle processes, or ISO/IEC/IEEE 12207:2008, Systems and software engineering - Software life cycle processes, or practicing Service Management in conformance with in ISO/IEC 20000-1:2005, Information technology -- Service management -- Part 1: Specification; and ISO/IEC 20000-2:2005, Information technology -- Service management -- Part 2: Code of practice. ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008 define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do &quot;not detail documentation in terms of name, format, explicit content, and recording media&quot; (ISO/IEC/IEEE 15288:2008, clause 1.4). ISO/IEC/IEEE 12207:2008 establishes a common framework for software life cycle processes and in passing identifies or requires a number of documentation items. The Process Reference Model does not represent a particular process implementation approach nor does it prescribe a system/software life cycle model, methodology, or technique. ISO 20000-1:2005 establishes general requirements for documents and records (3.2). ISO/IEC/IEEE 12207:2008 does not always specify when software information items are to be prepared, nor does it identify information item contents. This International Standard provides a mapping of ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008 clauses with a set of information items. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC/IEEE 15288:2008 agreement, enterprise, project, and technical processes; the ISO/IEC/IEEE 12207:2008, primary, supporting, and organizational life cycle processes, or the ISO/IEC 20000-1:2005 Service Management processes. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2008, ISO/IEC/IEEE 12207:2008, and ISO/IEC 20000-1:2005 and 20000-2:2005, 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 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 the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 15288:2008 or ISO/IEC/IEEE 12207:2008. As ISO/IEC/IEEE 15288:2008 points out (1.4), &quot;This International Standard does not detail the life cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.&quot; 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.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008<br />\n
          (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2005 for<br />\n
          identifying and planning the specific information items (information products) to be developed and revised<br />\n
          during systems and software life cycles and service processes. This International Standard is intended for use<br />\n
          as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008<br />\n
          (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes. b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005. The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Content of life-cycle information products (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106883 …}
    #channels: Doctrine\ORM\PersistentCollection {#106877 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106881 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106879 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106893 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106860
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106899
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1320102000 {#106898
      date: 2011-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#106890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106888 …}
  }
]

App\Twig\Components\ProductMostRecent {#107007
  +product: App\Entity\Product\Product {#106892
    #id: 10917
    #code: "IEEE00005287"
    #attributes: Doctrine\ORM\PersistentCollection {#106875 …}
    #variants: Doctrine\ORM\PersistentCollection {#106872 …}
    #options: Doctrine\ORM\PersistentCollection {#106868 …}
    #associations: Doctrine\ORM\PersistentCollection {#106870 …}
    #createdAt: DateTime @1751039364 {#106900
      date: 2025-06-27 17:49:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#106873
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106925
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106892}
        #id: 38677
        #name: "IEEE/ISO/IEC 15289:2011"
        #slug: "ieee-iso-iec-15289-2011-ieee00005287-242569"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 15289:2011 provides requirements for identifying and planning the specific information items (information products, documentation) to be developed and revised during systems and software life cycles and service processes. It specifies the purpose and content of all identified systems and software data records and life cycle information items, as well as records and information items for information technology service management. The information item contents are<br />\n
          defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. For simplicity of reference, each information item is described as if it were published as a separate document. However, information items may be unpublished but available in a repository for reference, divided into separate documents or volumes, or combined with other information items into one document. ISO/IEC/IEEE 15289:2011 is based on the life cycle processes specified in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and the service management processes specified in ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard (IS) assumes an organization is implementing life cycle processes in conformance with ISO/IEC/IEEE 15288:2008, Systems and software engineering - System life cycle processes, or ISO/IEC/IEEE 12207:2008, Systems and software engineering - Software life cycle processes, or practicing Service Management in conformance with in ISO/IEC 20000-1:2005, Information technology -- Service management -- Part 1: Specification; and ISO/IEC 20000-2:2005, Information technology -- Service management -- Part 2: Code of practice. ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008 define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do &quot;not detail documentation in terms of name, format, explicit content, and recording media&quot; (ISO/IEC/IEEE 15288:2008, clause 1.4). ISO/IEC/IEEE 12207:2008 establishes a common framework for software life cycle processes and in passing identifies or requires a number of documentation items. The Process Reference Model does not represent a particular process implementation approach nor does it prescribe a system/software life cycle model, methodology, or technique. ISO 20000-1:2005 establishes general requirements for documents and records (3.2). ISO/IEC/IEEE 12207:2008 does not always specify when software information items are to be prepared, nor does it identify information item contents. This International Standard provides a mapping of ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008 clauses with a set of information items. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC/IEEE 15288:2008 agreement, enterprise, project, and technical processes; the ISO/IEC/IEEE 12207:2008, primary, supporting, and organizational life cycle processes, or the ISO/IEC 20000-1:2005 Service Management processes. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2008, ISO/IEC/IEEE 12207:2008, and ISO/IEC 20000-1:2005 and 20000-2:2005, 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 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 the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 15288:2008 or ISO/IEC/IEEE 12207:2008. As ISO/IEC/IEEE 15288:2008 points out (1.4), &quot;This International Standard does not detail the life cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.&quot; 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.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008<br />\n
          (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2005 for<br />\n
          identifying and planning the specific information items (information products) to be developed and revised<br />\n
          during systems and software life cycles and service processes. This International Standard is intended for use<br />\n
          as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008<br />\n
          (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes. b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005. The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Content of life-cycle information products (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106883 …}
    #channels: Doctrine\ORM\PersistentCollection {#106877 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106881 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106879 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106893 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106860
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106899
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1320102000 {#106898
      date: 2011-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#106890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106888 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93750
    #id: 12170
    #code: "IEEE00007196"
    #attributes: Doctrine\ORM\PersistentCollection {#93732 …}
    #variants: Doctrine\ORM\PersistentCollection {#93729 …}
    #options: Doctrine\ORM\PersistentCollection {#93725 …}
    #associations: Doctrine\ORM\PersistentCollection {#93727 …}
    #createdAt: DateTime @1751040247 {#93758
      date: 2025-06-27 18:04:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#93737
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93743 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93750}
        #id: 43689
        #name: "IEEE/ISO/IEC 15289:2019"
        #slug: "ieee-iso-iec-15289-2019-ieee00007196-243823"
        #description: """
          Revision Standard - Active.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this document. The information item contents are defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. This document provides a mapping of ISO/IEC/IEEE 15288:2015 and ISO/IEC/IEEE 12207:2017 clauses with a set of information items. This document identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2015 and ISO/IEC/IEEE 12207:2017, which in some cases provide partial or complete outlines for the content of specific documents. Information items may be combined or<br />\n
          subdivided as needed for project or organizational purposes.<br />\n
          \t\t\t\t<br />\n
          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; 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.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard -- Systems and software engineering - Content of life-cycle information items (documentation)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93741 …}
    #channels: Doctrine\ORM\PersistentCollection {#93734 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93739 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93736 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93751 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93721
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93757
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1563487200 {#93756
      date: 2019-07-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#93747 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93745 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113658
  +product: App\Entity\Product\Product {#93750
    #id: 12170
    #code: "IEEE00007196"
    #attributes: Doctrine\ORM\PersistentCollection {#93732 …}
    #variants: Doctrine\ORM\PersistentCollection {#93729 …}
    #options: Doctrine\ORM\PersistentCollection {#93725 …}
    #associations: Doctrine\ORM\PersistentCollection {#93727 …}
    #createdAt: DateTime @1751040247 {#93758
      date: 2025-06-27 18:04:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#93737
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93743 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93750}
        #id: 43689
        #name: "IEEE/ISO/IEC 15289:2019"
        #slug: "ieee-iso-iec-15289-2019-ieee00007196-243823"
        #description: """
          Revision Standard - Active.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this document. The information item contents are defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. This document provides a mapping of ISO/IEC/IEEE 15288:2015 and ISO/IEC/IEEE 12207:2017 clauses with a set of information items. This document identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2015 and ISO/IEC/IEEE 12207:2017, which in some cases provide partial or complete outlines for the content of specific documents. Information items may be combined or<br />\n
          subdivided as needed for project or organizational purposes.<br />\n
          \t\t\t\t<br />\n
          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; 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.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard -- Systems and software engineering - Content of life-cycle information items (documentation)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93741 …}
    #channels: Doctrine\ORM\PersistentCollection {#93734 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93739 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93736 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93751 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93721
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93757
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1563487200 {#93756
      date: 2019-07-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#93747 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93745 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93750
    #id: 12170
    #code: "IEEE00007196"
    #attributes: Doctrine\ORM\PersistentCollection {#93732 …}
    #variants: Doctrine\ORM\PersistentCollection {#93729 …}
    #options: Doctrine\ORM\PersistentCollection {#93725 …}
    #associations: Doctrine\ORM\PersistentCollection {#93727 …}
    #createdAt: DateTime @1751040247 {#93758
      date: 2025-06-27 18:04:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#93737
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93743 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93750}
        #id: 43689
        #name: "IEEE/ISO/IEC 15289:2019"
        #slug: "ieee-iso-iec-15289-2019-ieee00007196-243823"
        #description: """
          Revision Standard - Active.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this document. The information item contents are defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. This document provides a mapping of ISO/IEC/IEEE 15288:2015 and ISO/IEC/IEEE 12207:2017 clauses with a set of information items. This document identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2015 and ISO/IEC/IEEE 12207:2017, which in some cases provide partial or complete outlines for the content of specific documents. Information items may be combined or<br />\n
          subdivided as needed for project or organizational purposes.<br />\n
          \t\t\t\t<br />\n
          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; 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.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard -- Systems and software engineering - Content of life-cycle information items (documentation)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93741 …}
    #channels: Doctrine\ORM\PersistentCollection {#93734 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93739 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93736 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93751 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93721
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93757
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1563487200 {#93756
      date: 2019-07-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#93747 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93745 …}
  }
]

App\Twig\Components\ProductMostRecent {#113725
  +product: App\Entity\Product\Product {#93750
    #id: 12170
    #code: "IEEE00007196"
    #attributes: Doctrine\ORM\PersistentCollection {#93732 …}
    #variants: Doctrine\ORM\PersistentCollection {#93729 …}
    #options: Doctrine\ORM\PersistentCollection {#93725 …}
    #associations: Doctrine\ORM\PersistentCollection {#93727 …}
    #createdAt: DateTime @1751040247 {#93758
      date: 2025-06-27 18:04:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#93737
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93743 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93750}
        #id: 43689
        #name: "IEEE/ISO/IEC 15289:2019"
        #slug: "ieee-iso-iec-15289-2019-ieee00007196-243823"
        #description: """
          Revision Standard - Active.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this document. The information item contents are defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. This document provides a mapping of ISO/IEC/IEEE 15288:2015 and ISO/IEC/IEEE 12207:2017 clauses with a set of information items. This document identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2015 and ISO/IEC/IEEE 12207:2017, which in some cases provide partial or complete outlines for the content of specific documents. Information items may be combined or<br />\n
          subdivided as needed for project or organizational purposes.<br />\n
          \t\t\t\t<br />\n
          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; 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.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard -- Systems and software engineering - Content of life-cycle information items (documentation)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93741 …}
    #channels: Doctrine\ORM\PersistentCollection {#93734 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93739 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93736 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93751 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93721
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93757
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1563487200 {#93756
      date: 2019-07-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#93747 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93745 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#113591
    #id: 11921
    #code: "IEEE00006782"
    #attributes: Doctrine\ORM\PersistentCollection {#113607 …}
    #variants: Doctrine\ORM\PersistentCollection {#113609 …}
    #options: Doctrine\ORM\PersistentCollection {#113613 …}
    #associations: Doctrine\ORM\PersistentCollection {#113611 …}
    #createdAt: DateTime @1751040078 {#113582
      date: 2025-06-27 18:01:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#113580
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113597 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113792
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113591}
        #id: 42693
        #name: "IEEE/ISO/IEC 15289:2017"
        #slug: "ieee-iso-iec-15289-2017-ieee00006782-243573"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this document.<br />\n
          The information item contents are defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. This document provides a mapping of ISO/IEC/IEEE 15288:2015, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This document identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2015, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. Information items may be combined or subdivided as needed for project or organizational purposes.<br />\n
          \t\t\t\t<br />\n
          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 (Clause 10). This document assumes an organization is performing life-cycle processes, or practicing service management,<br />\n
          using one or more of the following: ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle<br />\n
          processes; ISO/IEC/IEEE 15288:2015, Systems and software engineering -- System life cycle processes; ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), Information technology -- Service management -- Part 1:Service management system requirements; and ISO/IEC 20000-2 (IEEE Std 20000-2:2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems. 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 IT service management. This document does not establish a service management system. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC/IEEE 15288:2015 define a set of processes for managing and performing the stages of a software or system life cycle. They define an Information Management process, but do not “detail information items in terms of name, format, explicit content, and recording media”. ISO/IEC/IEEE 15288:2015 and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for system and software life-cycle processes. They identify or require a number of documentation items. Their process reference model does not represent a particular process implementation approach, nor prescribe a system/software life-cycle model, methodology or technique. ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2:2013), provides guidance on the use of ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013).<br />\n
          The generic document types defined in this document are used to identify the information necessary to support the following: the ISO/IEC/IEEE 15288:2015 agreement; organizational project-enabling; technical management and processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; and the ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) service management system (SMS), service delivery, relationship, resolution, and control processes. The generic document types (which can be referred to as information item types) are used to identify the information necessary to support the ISO/IEC/IEEE 15288:2015 agreement, organizational project-enabling,<br />\n
          technical management, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as<br />\n
          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 15288:2015 or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC/IEEE 15288:2015 points out (1.4), “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<br />\n
          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, Applicability, and Clause 5, Conformance.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC/IEEE 15288:2015, and ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113599 …}
    #channels: Doctrine\ORM\PersistentCollection {#113605 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113601 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113603 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113590 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113583
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113576
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1496613600 {#113573
      date: 2017-06-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 97
    -documents: Doctrine\ORM\PersistentCollection {#113593 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113595 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113807
  +product: App\Entity\Product\Product {#113591
    #id: 11921
    #code: "IEEE00006782"
    #attributes: Doctrine\ORM\PersistentCollection {#113607 …}
    #variants: Doctrine\ORM\PersistentCollection {#113609 …}
    #options: Doctrine\ORM\PersistentCollection {#113613 …}
    #associations: Doctrine\ORM\PersistentCollection {#113611 …}
    #createdAt: DateTime @1751040078 {#113582
      date: 2025-06-27 18:01:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#113580
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113597 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113792
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113591}
        #id: 42693
        #name: "IEEE/ISO/IEC 15289:2017"
        #slug: "ieee-iso-iec-15289-2017-ieee00006782-243573"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this document.<br />\n
          The information item contents are defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. This document provides a mapping of ISO/IEC/IEEE 15288:2015, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This document identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2015, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. Information items may be combined or subdivided as needed for project or organizational purposes.<br />\n
          \t\t\t\t<br />\n
          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 (Clause 10). This document assumes an organization is performing life-cycle processes, or practicing service management,<br />\n
          using one or more of the following: ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle<br />\n
          processes; ISO/IEC/IEEE 15288:2015, Systems and software engineering -- System life cycle processes; ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), Information technology -- Service management -- Part 1:Service management system requirements; and ISO/IEC 20000-2 (IEEE Std 20000-2:2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems. 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 IT service management. This document does not establish a service management system. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC/IEEE 15288:2015 define a set of processes for managing and performing the stages of a software or system life cycle. They define an Information Management process, but do not “detail information items in terms of name, format, explicit content, and recording media”. ISO/IEC/IEEE 15288:2015 and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for system and software life-cycle processes. They identify or require a number of documentation items. Their process reference model does not represent a particular process implementation approach, nor prescribe a system/software life-cycle model, methodology or technique. ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2:2013), provides guidance on the use of ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013).<br />\n
          The generic document types defined in this document are used to identify the information necessary to support the following: the ISO/IEC/IEEE 15288:2015 agreement; organizational project-enabling; technical management and processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; and the ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) service management system (SMS), service delivery, relationship, resolution, and control processes. The generic document types (which can be referred to as information item types) are used to identify the information necessary to support the ISO/IEC/IEEE 15288:2015 agreement, organizational project-enabling,<br />\n
          technical management, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as<br />\n
          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 15288:2015 or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC/IEEE 15288:2015 points out (1.4), “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<br />\n
          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, Applicability, and Clause 5, Conformance.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC/IEEE 15288:2015, and ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113599 …}
    #channels: Doctrine\ORM\PersistentCollection {#113605 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113601 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113603 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113590 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113583
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113576
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1496613600 {#113573
      date: 2017-06-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 97
    -documents: Doctrine\ORM\PersistentCollection {#113593 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113595 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#113591
    #id: 11921
    #code: "IEEE00006782"
    #attributes: Doctrine\ORM\PersistentCollection {#113607 …}
    #variants: Doctrine\ORM\PersistentCollection {#113609 …}
    #options: Doctrine\ORM\PersistentCollection {#113613 …}
    #associations: Doctrine\ORM\PersistentCollection {#113611 …}
    #createdAt: DateTime @1751040078 {#113582
      date: 2025-06-27 18:01:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#113580
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113597 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113792
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113591}
        #id: 42693
        #name: "IEEE/ISO/IEC 15289:2017"
        #slug: "ieee-iso-iec-15289-2017-ieee00006782-243573"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this document.<br />\n
          The information item contents are defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. This document provides a mapping of ISO/IEC/IEEE 15288:2015, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This document identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2015, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. Information items may be combined or subdivided as needed for project or organizational purposes.<br />\n
          \t\t\t\t<br />\n
          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 (Clause 10). This document assumes an organization is performing life-cycle processes, or practicing service management,<br />\n
          using one or more of the following: ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle<br />\n
          processes; ISO/IEC/IEEE 15288:2015, Systems and software engineering -- System life cycle processes; ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), Information technology -- Service management -- Part 1:Service management system requirements; and ISO/IEC 20000-2 (IEEE Std 20000-2:2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems. 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 IT service management. This document does not establish a service management system. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC/IEEE 15288:2015 define a set of processes for managing and performing the stages of a software or system life cycle. They define an Information Management process, but do not “detail information items in terms of name, format, explicit content, and recording media”. ISO/IEC/IEEE 15288:2015 and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for system and software life-cycle processes. They identify or require a number of documentation items. Their process reference model does not represent a particular process implementation approach, nor prescribe a system/software life-cycle model, methodology or technique. ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2:2013), provides guidance on the use of ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013).<br />\n
          The generic document types defined in this document are used to identify the information necessary to support the following: the ISO/IEC/IEEE 15288:2015 agreement; organizational project-enabling; technical management and processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; and the ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) service management system (SMS), service delivery, relationship, resolution, and control processes. The generic document types (which can be referred to as information item types) are used to identify the information necessary to support the ISO/IEC/IEEE 15288:2015 agreement, organizational project-enabling,<br />\n
          technical management, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as<br />\n
          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 15288:2015 or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC/IEEE 15288:2015 points out (1.4), “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<br />\n
          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, Applicability, and Clause 5, Conformance.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC/IEEE 15288:2015, and ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113599 …}
    #channels: Doctrine\ORM\PersistentCollection {#113605 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113601 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113603 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113590 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113583
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113576
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1496613600 {#113573
      date: 2017-06-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 97
    -documents: Doctrine\ORM\PersistentCollection {#113593 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113595 …}
  }
]

App\Twig\Components\ProductMostRecent {#113859
  +product: App\Entity\Product\Product {#113591
    #id: 11921
    #code: "IEEE00006782"
    #attributes: Doctrine\ORM\PersistentCollection {#113607 …}
    #variants: Doctrine\ORM\PersistentCollection {#113609 …}
    #options: Doctrine\ORM\PersistentCollection {#113613 …}
    #associations: Doctrine\ORM\PersistentCollection {#113611 …}
    #createdAt: DateTime @1751040078 {#113582
      date: 2025-06-27 18:01:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#113580
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113597 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113792
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113591}
        #id: 42693
        #name: "IEEE/ISO/IEC 15289:2017"
        #slug: "ieee-iso-iec-15289-2017-ieee00006782-243573"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this document.<br />\n
          The information item contents are defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. This document provides a mapping of ISO/IEC/IEEE 15288:2015, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This document identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2015, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. Information items may be combined or subdivided as needed for project or organizational purposes.<br />\n
          \t\t\t\t<br />\n
          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 (Clause 10). This document assumes an organization is performing life-cycle processes, or practicing service management,<br />\n
          using one or more of the following: ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle<br />\n
          processes; ISO/IEC/IEEE 15288:2015, Systems and software engineering -- System life cycle processes; ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), Information technology -- Service management -- Part 1:Service management system requirements; and ISO/IEC 20000-2 (IEEE Std 20000-2:2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems. 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 IT service management. This document does not establish a service management system. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC/IEEE 15288:2015 define a set of processes for managing and performing the stages of a software or system life cycle. They define an Information Management process, but do not “detail information items in terms of name, format, explicit content, and recording media”. ISO/IEC/IEEE 15288:2015 and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for system and software life-cycle processes. They identify or require a number of documentation items. Their process reference model does not represent a particular process implementation approach, nor prescribe a system/software life-cycle model, methodology or technique. ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2:2013), provides guidance on the use of ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013).<br />\n
          The generic document types defined in this document are used to identify the information necessary to support the following: the ISO/IEC/IEEE 15288:2015 agreement; organizational project-enabling; technical management and processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; and the ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) service management system (SMS), service delivery, relationship, resolution, and control processes. The generic document types (which can be referred to as information item types) are used to identify the information necessary to support the ISO/IEC/IEEE 15288:2015 agreement, organizational project-enabling,<br />\n
          technical management, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as<br />\n
          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 15288:2015 or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC/IEEE 15288:2015 points out (1.4), “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<br />\n
          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, Applicability, and Clause 5, Conformance.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC/IEEE 15288:2015, and ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113599 …}
    #channels: Doctrine\ORM\PersistentCollection {#113605 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113601 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113603 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113590 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113583
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113576
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1496613600 {#113573
      date: 2017-06-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 97
    -documents: Doctrine\ORM\PersistentCollection {#113593 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113595 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039567 {#7274
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39969
        #name: "IEEE/ISO/IEC 15289:2015"
        #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. 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). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), 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.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control 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 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” 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. This International Standard does not establish a service management system. The scope of this International Standard 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 system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n
          b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#7292
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 95
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113923
  +product: App\Entity\Product\Product {#7310
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039567 {#7274
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39969
        #name: "IEEE/ISO/IEC 15289:2015"
        #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. 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). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), 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.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control 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 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” 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. This International Standard does not establish a service management system. The scope of this International Standard 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 system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n
          b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#7292
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 95
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039567 {#7274
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39969
        #name: "IEEE/ISO/IEC 15289:2015"
        #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. 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). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), 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.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control 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 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” 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. This International Standard does not establish a service management system. The scope of this International Standard 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 system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n
          b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#7292
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 95
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#113950
  +product: App\Entity\Product\Product {#7310
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039567 {#7274
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39969
        #name: "IEEE/ISO/IEC 15289:2015"
        #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892"
        #description: """
          Revision Standard - Superseded.<br />\n
          The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. 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). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), 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.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control 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 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” 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. This International Standard does not establish a service management system. The scope of this International Standard 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 system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n
          b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#7292
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 95
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106892
    #id: 10917
    #code: "IEEE00005287"
    #attributes: Doctrine\ORM\PersistentCollection {#106875 …}
    #variants: Doctrine\ORM\PersistentCollection {#106872 …}
    #options: Doctrine\ORM\PersistentCollection {#106868 …}
    #associations: Doctrine\ORM\PersistentCollection {#106870 …}
    #createdAt: DateTime @1751039364 {#106900
      date: 2025-06-27 17:49:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#106873
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106925
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106892}
        #id: 38677
        #name: "IEEE/ISO/IEC 15289:2011"
        #slug: "ieee-iso-iec-15289-2011-ieee00005287-242569"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 15289:2011 provides requirements for identifying and planning the specific information items (information products, documentation) to be developed and revised during systems and software life cycles and service processes. It specifies the purpose and content of all identified systems and software data records and life cycle information items, as well as records and information items for information technology service management. The information item contents are<br />\n
          defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. For simplicity of reference, each information item is described as if it were published as a separate document. However, information items may be unpublished but available in a repository for reference, divided into separate documents or volumes, or combined with other information items into one document. ISO/IEC/IEEE 15289:2011 is based on the life cycle processes specified in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and the service management processes specified in ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard (IS) assumes an organization is implementing life cycle processes in conformance with ISO/IEC/IEEE 15288:2008, Systems and software engineering - System life cycle processes, or ISO/IEC/IEEE 12207:2008, Systems and software engineering - Software life cycle processes, or practicing Service Management in conformance with in ISO/IEC 20000-1:2005, Information technology -- Service management -- Part 1: Specification; and ISO/IEC 20000-2:2005, Information technology -- Service management -- Part 2: Code of practice. ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008 define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do &quot;not detail documentation in terms of name, format, explicit content, and recording media&quot; (ISO/IEC/IEEE 15288:2008, clause 1.4). ISO/IEC/IEEE 12207:2008 establishes a common framework for software life cycle processes and in passing identifies or requires a number of documentation items. The Process Reference Model does not represent a particular process implementation approach nor does it prescribe a system/software life cycle model, methodology, or technique. ISO 20000-1:2005 establishes general requirements for documents and records (3.2). ISO/IEC/IEEE 12207:2008 does not always specify when software information items are to be prepared, nor does it identify information item contents. This International Standard provides a mapping of ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008 clauses with a set of information items. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC/IEEE 15288:2008 agreement, enterprise, project, and technical processes; the ISO/IEC/IEEE 12207:2008, primary, supporting, and organizational life cycle processes, or the ISO/IEC 20000-1:2005 Service Management processes. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2008, ISO/IEC/IEEE 12207:2008, and ISO/IEC 20000-1:2005 and 20000-2:2005, 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 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 the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 15288:2008 or ISO/IEC/IEEE 12207:2008. As ISO/IEC/IEEE 15288:2008 points out (1.4), &quot;This International Standard does not detail the life cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.&quot; 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.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008<br />\n
          (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2005 for<br />\n
          identifying and planning the specific information items (information products) to be developed and revised<br />\n
          during systems and software life cycles and service processes. This International Standard is intended for use<br />\n
          as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008<br />\n
          (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes. b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005. The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Content of life-cycle information products (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106883 …}
    #channels: Doctrine\ORM\PersistentCollection {#106877 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106881 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106879 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106893 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106860
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106899
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1320102000 {#106898
      date: 2011-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#106890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106888 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#114014
  +product: App\Entity\Product\Product {#106892
    #id: 10917
    #code: "IEEE00005287"
    #attributes: Doctrine\ORM\PersistentCollection {#106875 …}
    #variants: Doctrine\ORM\PersistentCollection {#106872 …}
    #options: Doctrine\ORM\PersistentCollection {#106868 …}
    #associations: Doctrine\ORM\PersistentCollection {#106870 …}
    #createdAt: DateTime @1751039364 {#106900
      date: 2025-06-27 17:49:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#106873
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106925
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106892}
        #id: 38677
        #name: "IEEE/ISO/IEC 15289:2011"
        #slug: "ieee-iso-iec-15289-2011-ieee00005287-242569"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 15289:2011 provides requirements for identifying and planning the specific information items (information products, documentation) to be developed and revised during systems and software life cycles and service processes. It specifies the purpose and content of all identified systems and software data records and life cycle information items, as well as records and information items for information technology service management. The information item contents are<br />\n
          defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. For simplicity of reference, each information item is described as if it were published as a separate document. However, information items may be unpublished but available in a repository for reference, divided into separate documents or volumes, or combined with other information items into one document. ISO/IEC/IEEE 15289:2011 is based on the life cycle processes specified in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and the service management processes specified in ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard (IS) assumes an organization is implementing life cycle processes in conformance with ISO/IEC/IEEE 15288:2008, Systems and software engineering - System life cycle processes, or ISO/IEC/IEEE 12207:2008, Systems and software engineering - Software life cycle processes, or practicing Service Management in conformance with in ISO/IEC 20000-1:2005, Information technology -- Service management -- Part 1: Specification; and ISO/IEC 20000-2:2005, Information technology -- Service management -- Part 2: Code of practice. ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008 define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do &quot;not detail documentation in terms of name, format, explicit content, and recording media&quot; (ISO/IEC/IEEE 15288:2008, clause 1.4). ISO/IEC/IEEE 12207:2008 establishes a common framework for software life cycle processes and in passing identifies or requires a number of documentation items. The Process Reference Model does not represent a particular process implementation approach nor does it prescribe a system/software life cycle model, methodology, or technique. ISO 20000-1:2005 establishes general requirements for documents and records (3.2). ISO/IEC/IEEE 12207:2008 does not always specify when software information items are to be prepared, nor does it identify information item contents. This International Standard provides a mapping of ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008 clauses with a set of information items. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC/IEEE 15288:2008 agreement, enterprise, project, and technical processes; the ISO/IEC/IEEE 12207:2008, primary, supporting, and organizational life cycle processes, or the ISO/IEC 20000-1:2005 Service Management processes. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2008, ISO/IEC/IEEE 12207:2008, and ISO/IEC 20000-1:2005 and 20000-2:2005, 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 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 the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 15288:2008 or ISO/IEC/IEEE 12207:2008. As ISO/IEC/IEEE 15288:2008 points out (1.4), &quot;This International Standard does not detail the life cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.&quot; 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.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008<br />\n
          (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2005 for<br />\n
          identifying and planning the specific information items (information products) to be developed and revised<br />\n
          during systems and software life cycles and service processes. This International Standard is intended for use<br />\n
          as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008<br />\n
          (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes. b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005. The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Content of life-cycle information products (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106883 …}
    #channels: Doctrine\ORM\PersistentCollection {#106877 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106881 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106879 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106893 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106860
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106899
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1320102000 {#106898
      date: 2011-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#106890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106888 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106892
    #id: 10917
    #code: "IEEE00005287"
    #attributes: Doctrine\ORM\PersistentCollection {#106875 …}
    #variants: Doctrine\ORM\PersistentCollection {#106872 …}
    #options: Doctrine\ORM\PersistentCollection {#106868 …}
    #associations: Doctrine\ORM\PersistentCollection {#106870 …}
    #createdAt: DateTime @1751039364 {#106900
      date: 2025-06-27 17:49:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#106873
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106925
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106892}
        #id: 38677
        #name: "IEEE/ISO/IEC 15289:2011"
        #slug: "ieee-iso-iec-15289-2011-ieee00005287-242569"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 15289:2011 provides requirements for identifying and planning the specific information items (information products, documentation) to be developed and revised during systems and software life cycles and service processes. It specifies the purpose and content of all identified systems and software data records and life cycle information items, as well as records and information items for information technology service management. The information item contents are<br />\n
          defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. For simplicity of reference, each information item is described as if it were published as a separate document. However, information items may be unpublished but available in a repository for reference, divided into separate documents or volumes, or combined with other information items into one document. ISO/IEC/IEEE 15289:2011 is based on the life cycle processes specified in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and the service management processes specified in ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard (IS) assumes an organization is implementing life cycle processes in conformance with ISO/IEC/IEEE 15288:2008, Systems and software engineering - System life cycle processes, or ISO/IEC/IEEE 12207:2008, Systems and software engineering - Software life cycle processes, or practicing Service Management in conformance with in ISO/IEC 20000-1:2005, Information technology -- Service management -- Part 1: Specification; and ISO/IEC 20000-2:2005, Information technology -- Service management -- Part 2: Code of practice. ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008 define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do &quot;not detail documentation in terms of name, format, explicit content, and recording media&quot; (ISO/IEC/IEEE 15288:2008, clause 1.4). ISO/IEC/IEEE 12207:2008 establishes a common framework for software life cycle processes and in passing identifies or requires a number of documentation items. The Process Reference Model does not represent a particular process implementation approach nor does it prescribe a system/software life cycle model, methodology, or technique. ISO 20000-1:2005 establishes general requirements for documents and records (3.2). ISO/IEC/IEEE 12207:2008 does not always specify when software information items are to be prepared, nor does it identify information item contents. This International Standard provides a mapping of ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008 clauses with a set of information items. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC/IEEE 15288:2008 agreement, enterprise, project, and technical processes; the ISO/IEC/IEEE 12207:2008, primary, supporting, and organizational life cycle processes, or the ISO/IEC 20000-1:2005 Service Management processes. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2008, ISO/IEC/IEEE 12207:2008, and ISO/IEC 20000-1:2005 and 20000-2:2005, 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 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 the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 15288:2008 or ISO/IEC/IEEE 12207:2008. As ISO/IEC/IEEE 15288:2008 points out (1.4), &quot;This International Standard does not detail the life cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.&quot; 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.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008<br />\n
          (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2005 for<br />\n
          identifying and planning the specific information items (information products) to be developed and revised<br />\n
          during systems and software life cycles and service processes. This International Standard is intended for use<br />\n
          as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008<br />\n
          (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes. b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005. The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Content of life-cycle information products (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106883 …}
    #channels: Doctrine\ORM\PersistentCollection {#106877 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106881 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106879 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106893 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106860
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106899
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1320102000 {#106898
      date: 2011-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#106890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106888 …}
  }
]

App\Twig\Components\ProductMostRecent {#114041
  +product: App\Entity\Product\Product {#106892
    #id: 10917
    #code: "IEEE00005287"
    #attributes: Doctrine\ORM\PersistentCollection {#106875 …}
    #variants: Doctrine\ORM\PersistentCollection {#106872 …}
    #options: Doctrine\ORM\PersistentCollection {#106868 …}
    #associations: Doctrine\ORM\PersistentCollection {#106870 …}
    #createdAt: DateTime @1751039364 {#106900
      date: 2025-06-27 17:49:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#106873
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106925
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106892}
        #id: 38677
        #name: "IEEE/ISO/IEC 15289:2011"
        #slug: "ieee-iso-iec-15289-2011-ieee00005287-242569"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 15289:2011 provides requirements for identifying and planning the specific information items (information products, documentation) to be developed and revised during systems and software life cycles and service processes. It specifies the purpose and content of all identified systems and software data records and life cycle information items, as well as records and information items for information technology service management. The information item contents are<br />\n
          defined according to generic document types (description, plan, policy, procedure, report, request, and specification) and the specific purpose of the document. For simplicity of reference, each information item is described as if it were published as a separate document. However, information items may be unpublished but available in a repository for reference, divided into separate documents or volumes, or combined with other information items into one document. ISO/IEC/IEEE 15289:2011 is based on the life cycle processes specified in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and the service management processes specified in ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005.<br />\n
          \t\t\t\t<br />\n
          This International Standard 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 (Clause 10). This International Standard (IS) assumes an organization is implementing life cycle processes in conformance with ISO/IEC/IEEE 15288:2008, Systems and software engineering - System life cycle processes, or ISO/IEC/IEEE 12207:2008, Systems and software engineering - Software life cycle processes, or practicing Service Management in conformance with in ISO/IEC 20000-1:2005, Information technology -- Service management -- Part 1: Specification; and ISO/IEC 20000-2:2005, Information technology -- Service management -- Part 2: Code of practice. ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008 define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do &quot;not detail documentation in terms of name, format, explicit content, and recording media&quot; (ISO/IEC/IEEE 15288:2008, clause 1.4). ISO/IEC/IEEE 12207:2008 establishes a common framework for software life cycle processes and in passing identifies or requires a number of documentation items. The Process Reference Model does not represent a particular process implementation approach nor does it prescribe a system/software life cycle model, methodology, or technique. ISO 20000-1:2005 establishes general requirements for documents and records (3.2). ISO/IEC/IEEE 12207:2008 does not always specify when software information items are to be prepared, nor does it identify information item contents. This International Standard provides a mapping of ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008 clauses with a set of information items. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC/IEEE 15288:2008 agreement, enterprise, project, and technical processes; the ISO/IEC/IEEE 12207:2008, primary, supporting, and organizational life cycle processes, or the ISO/IEC 20000-1:2005 Service Management processes. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288:2008, ISO/IEC/IEEE 12207:2008, and ISO/IEC 20000-1:2005 and 20000-2:2005, 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 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 the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 15288:2008 or ISO/IEC/IEEE 12207:2008. As ISO/IEC/IEEE 15288:2008 points out (1.4), &quot;This International Standard does not detail the life cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.&quot; 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.<br />\n
          The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008<br />\n
          (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2005 for<br />\n
          identifying and planning the specific information items (information products) to be developed and revised<br />\n
          during systems and software life cycles and service processes. This International Standard is intended for use<br />\n
          as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008<br />\n
          (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes. b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2005 and ISO/IEC 20000-2:2005. The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Content of life-cycle information products (documentation)"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106883 …}
    #channels: Doctrine\ORM\PersistentCollection {#106877 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106881 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106879 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106893 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106860
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106899
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1320102000 {#106898
      date: 2011-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15289"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#106890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106888 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#135395
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135419 …}
    #variants: Doctrine\ORM\PersistentCollection {#135417 …}
    #options: Doctrine\ORM\PersistentCollection {#135412 …}
    #associations: Doctrine\ORM\PersistentCollection {#135415 …}
    #createdAt: DateTime @1751039021 {#135408
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135401
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135430 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135526
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135395}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135428 …}
    #channels: Doctrine\ORM\PersistentCollection {#135421 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135425 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135423 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135435 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135394
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135443
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135414
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135434 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135432 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#135487
  +product: App\Entity\Product\Product {#135395
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135419 …}
    #variants: Doctrine\ORM\PersistentCollection {#135417 …}
    #options: Doctrine\ORM\PersistentCollection {#135412 …}
    #associations: Doctrine\ORM\PersistentCollection {#135415 …}
    #createdAt: DateTime @1751039021 {#135408
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135401
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135430 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135526
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135395}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135428 …}
    #channels: Doctrine\ORM\PersistentCollection {#135421 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135425 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135423 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135435 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135394
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135443
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135414
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135434 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135432 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}

[
  "product" => App\Entity\Product\Product {#135395
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135419 …}
    #variants: Doctrine\ORM\PersistentCollection {#135417 …}
    #options: Doctrine\ORM\PersistentCollection {#135412 …}
    #associations: Doctrine\ORM\PersistentCollection {#135415 …}
    #createdAt: DateTime @1751039021 {#135408
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135401
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135430 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135526
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135395}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135428 …}
    #channels: Doctrine\ORM\PersistentCollection {#135421 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135425 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135423 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135435 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135394
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135443
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135414
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135434 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135432 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#135528
  +product: App\Entity\Product\Product {#135395
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135419 …}
    #variants: Doctrine\ORM\PersistentCollection {#135417 …}
    #options: Doctrine\ORM\PersistentCollection {#135412 …}
    #associations: Doctrine\ORM\PersistentCollection {#135415 …}
    #createdAt: DateTime @1751039021 {#135408
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135401
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135430 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135526
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135395}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135428 …}
    #channels: Doctrine\ORM\PersistentCollection {#135421 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135425 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135423 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135435 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135394
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135443
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135414
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135434 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135432 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#135395
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135419 …}
    #variants: Doctrine\ORM\PersistentCollection {#135417 …}
    #options: Doctrine\ORM\PersistentCollection {#135412 …}
    #associations: Doctrine\ORM\PersistentCollection {#135415 …}
    #createdAt: DateTime @1751039021 {#135408
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135401
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135430 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135526
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135395}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135428 …}
    #channels: Doctrine\ORM\PersistentCollection {#135421 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135425 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135423 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135435 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135394
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135443
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135414
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135434 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135432 …}
  }
]

App\Twig\Components\ProductMostRecent {#135605
  +product: App\Entity\Product\Product {#135395
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135419 …}
    #variants: Doctrine\ORM\PersistentCollection {#135417 …}
    #options: Doctrine\ORM\PersistentCollection {#135412 …}
    #associations: Doctrine\ORM\PersistentCollection {#135415 …}
    #createdAt: DateTime @1751039021 {#135408
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135401
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135430 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135526
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135395}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135428 …}
    #channels: Doctrine\ORM\PersistentCollection {#135421 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135425 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135423 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135435 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135394
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135443
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135414
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135434 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135432 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}