Symfony Profiler

[
  "paddingClasses" => "p-2 px-lg-5 py-lg-0"
  "searchPlaceholder" => "sylius.ui.search"
  "showSearch" => "true"
  "searchValue" => "IEEE/ISO/IEC 15068-2:1999"
  "title" => "Search results"
]

App\Twig\Components\PageBanner {#94652
  +supTitle: null
  +title: "Search results"
  +subTitle: null
  +backUrl: null
  +backLabel: null
  +customClasses: null
  +backgroundType: null
  +centered: true
  +showSearch: true
  +searchPlaceholder: "sylius.ui.search"
  +searchValue: "IEEE/ISO/IEC 15068-2:1999"
  +paddingClasses: "p-2 px-lg-5 py-lg-0"
}

[
  "product" => App\Entity\Product\Product {#95506
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#95523 …}
    #variants: Doctrine\ORM\PersistentCollection {#95525 …}
    #options: Doctrine\ORM\PersistentCollection {#95529 …}
    #associations: Doctrine\ORM\PersistentCollection {#95527 …}
    #createdAt: DateTime @1751039319 {#95501
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95502
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95513 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95978
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95506}
        #id: 38389
        #name: "IEEE/ISO/IEC 26512:2011"
        #slug: "ieee-iso-iec-26512-2011-ieee00005160-242497"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26512:2011 was developed to assist users of ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008) to acquire or supply software user documentation as part of the software life cycle processes. It defines the documentation process from the acquirer's standpoint and the supplier's standpoint. ISO/IEC/IEEE 26512:2011 covers the requirements for information items used in the acquisition of user documentation products: the Acquisition Plan, Document Specification, Statement of Work, Request for Proposals, and the proposal. It provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work. It includes requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services. It also discusses the use of a Documentation Management Plan and a Document Plan as they arise in the acquisition and supply processes. ISO/IEC/IEEE 26512:2011 is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the interest of software users in having consistent, complete, accurate, and usable documentation. It addresses both available approaches to standardization: a) process standards, which specify the way that documentation products are to be acquired and supplied; and b) documentation product standards, which specify the characteristics and functional requirements of the documentation.<br />\n
          As defined in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), the acquisition and supply activities comprise the agreement processes of the software life cycle. Acquisition and supply of user documentation and user documentation services are specializations of those processes.<br />\n
          User documentation services can be acquired and supplied for any part of the software documentation management or information management process, such as:<br />\n
          * documentation or information management;<br />\n
          * information design and development;<br />\n
          * documentation editing and review coordination;<br />\n
          * documentation testing, particularly usability testing;<br />\n
          * documentation production and packaging;<br />\n
          * documentation distribution and delivery;<br />\n
          * advice on the selection and implementation of documentation tools and supporting systems;<br />\n
          * documentation process improvement.<br />\n
          This International Standard provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It applies the Agreement processes (acquisition and supply) to software user documentation, and addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work discussed in this International Standard. This International Standard also addresses requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services.<br />\n
          This International Standard is intended for use in acquiring or supplying either printed or electronic (on-screen)<br />\n
          documentation. It is independent of documentation development or management tools or methodologies.<br />\n
          This International Standard might be helpful for acquiring and supplying the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation of products other than software;<br />\n
          * multimedia systems using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software;<br />\n
          * documentation incorporated into the user interface.<br />\n
          This International Standard is applicable to acquirers and suppliers of user documentation, including a variety of specialists:<br />\n
          * business analysts who identify the tasks that the intended users will perform with the software;<br />\n
          * managers of the software development process or the documentation process;<br />\n
          * managers of the acquisition process, and those who authorize and approve acquisitions;<br />\n
          * managers and authors involved in proposal preparation.<br />\n
          It can also be consulted by those with other roles and interests in the documentation process:<br />\n
          * information designers and architects who plan the structure, format, and content requirements of<br />\n
          documentation products in a documentation set or web-accessible suite;<br />\n
          * experienced authors and editors who develop the written content for user documentation;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen;<br />\n
          * usability testers, documentation reviewers, subject matter experts;<br />\n
          * developers of tools for creating on-screen documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC Systems and software engineering -- Requirements for acquirers and suppliers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95515 …}
    #channels: Doctrine\ORM\PersistentCollection {#95521 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95517 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95519 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95507 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95503
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95504
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#95505
      date: 2011-06-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95509 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95511 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#95862
  +product: App\Entity\Product\Product {#95506
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#95523 …}
    #variants: Doctrine\ORM\PersistentCollection {#95525 …}
    #options: Doctrine\ORM\PersistentCollection {#95529 …}
    #associations: Doctrine\ORM\PersistentCollection {#95527 …}
    #createdAt: DateTime @1751039319 {#95501
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95502
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95513 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95978
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95506}
        #id: 38389
        #name: "IEEE/ISO/IEC 26512:2011"
        #slug: "ieee-iso-iec-26512-2011-ieee00005160-242497"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26512:2011 was developed to assist users of ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008) to acquire or supply software user documentation as part of the software life cycle processes. It defines the documentation process from the acquirer's standpoint and the supplier's standpoint. ISO/IEC/IEEE 26512:2011 covers the requirements for information items used in the acquisition of user documentation products: the Acquisition Plan, Document Specification, Statement of Work, Request for Proposals, and the proposal. It provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work. It includes requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services. It also discusses the use of a Documentation Management Plan and a Document Plan as they arise in the acquisition and supply processes. ISO/IEC/IEEE 26512:2011 is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the interest of software users in having consistent, complete, accurate, and usable documentation. It addresses both available approaches to standardization: a) process standards, which specify the way that documentation products are to be acquired and supplied; and b) documentation product standards, which specify the characteristics and functional requirements of the documentation.<br />\n
          As defined in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), the acquisition and supply activities comprise the agreement processes of the software life cycle. Acquisition and supply of user documentation and user documentation services are specializations of those processes.<br />\n
          User documentation services can be acquired and supplied for any part of the software documentation management or information management process, such as:<br />\n
          * documentation or information management;<br />\n
          * information design and development;<br />\n
          * documentation editing and review coordination;<br />\n
          * documentation testing, particularly usability testing;<br />\n
          * documentation production and packaging;<br />\n
          * documentation distribution and delivery;<br />\n
          * advice on the selection and implementation of documentation tools and supporting systems;<br />\n
          * documentation process improvement.<br />\n
          This International Standard provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It applies the Agreement processes (acquisition and supply) to software user documentation, and addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work discussed in this International Standard. This International Standard also addresses requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services.<br />\n
          This International Standard is intended for use in acquiring or supplying either printed or electronic (on-screen)<br />\n
          documentation. It is independent of documentation development or management tools or methodologies.<br />\n
          This International Standard might be helpful for acquiring and supplying the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation of products other than software;<br />\n
          * multimedia systems using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software;<br />\n
          * documentation incorporated into the user interface.<br />\n
          This International Standard is applicable to acquirers and suppliers of user documentation, including a variety of specialists:<br />\n
          * business analysts who identify the tasks that the intended users will perform with the software;<br />\n
          * managers of the software development process or the documentation process;<br />\n
          * managers of the acquisition process, and those who authorize and approve acquisitions;<br />\n
          * managers and authors involved in proposal preparation.<br />\n
          It can also be consulted by those with other roles and interests in the documentation process:<br />\n
          * information designers and architects who plan the structure, format, and content requirements of<br />\n
          documentation products in a documentation set or web-accessible suite;<br />\n
          * experienced authors and editors who develop the written content for user documentation;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen;<br />\n
          * usability testers, documentation reviewers, subject matter experts;<br />\n
          * developers of tools for creating on-screen documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC Systems and software engineering -- Requirements for acquirers and suppliers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95515 …}
    #channels: Doctrine\ORM\PersistentCollection {#95521 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95517 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95519 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95507 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95503
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95504
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#95505
      date: 2011-06-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95509 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95511 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95506
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#95523 …}
    #variants: Doctrine\ORM\PersistentCollection {#95525 …}
    #options: Doctrine\ORM\PersistentCollection {#95529 …}
    #associations: Doctrine\ORM\PersistentCollection {#95527 …}
    #createdAt: DateTime @1751039319 {#95501
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95502
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95513 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95978
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95506}
        #id: 38389
        #name: "IEEE/ISO/IEC 26512:2011"
        #slug: "ieee-iso-iec-26512-2011-ieee00005160-242497"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26512:2011 was developed to assist users of ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008) to acquire or supply software user documentation as part of the software life cycle processes. It defines the documentation process from the acquirer's standpoint and the supplier's standpoint. ISO/IEC/IEEE 26512:2011 covers the requirements for information items used in the acquisition of user documentation products: the Acquisition Plan, Document Specification, Statement of Work, Request for Proposals, and the proposal. It provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work. It includes requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services. It also discusses the use of a Documentation Management Plan and a Document Plan as they arise in the acquisition and supply processes. ISO/IEC/IEEE 26512:2011 is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the interest of software users in having consistent, complete, accurate, and usable documentation. It addresses both available approaches to standardization: a) process standards, which specify the way that documentation products are to be acquired and supplied; and b) documentation product standards, which specify the characteristics and functional requirements of the documentation.<br />\n
          As defined in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), the acquisition and supply activities comprise the agreement processes of the software life cycle. Acquisition and supply of user documentation and user documentation services are specializations of those processes.<br />\n
          User documentation services can be acquired and supplied for any part of the software documentation management or information management process, such as:<br />\n
          * documentation or information management;<br />\n
          * information design and development;<br />\n
          * documentation editing and review coordination;<br />\n
          * documentation testing, particularly usability testing;<br />\n
          * documentation production and packaging;<br />\n
          * documentation distribution and delivery;<br />\n
          * advice on the selection and implementation of documentation tools and supporting systems;<br />\n
          * documentation process improvement.<br />\n
          This International Standard provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It applies the Agreement processes (acquisition and supply) to software user documentation, and addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work discussed in this International Standard. This International Standard also addresses requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services.<br />\n
          This International Standard is intended for use in acquiring or supplying either printed or electronic (on-screen)<br />\n
          documentation. It is independent of documentation development or management tools or methodologies.<br />\n
          This International Standard might be helpful for acquiring and supplying the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation of products other than software;<br />\n
          * multimedia systems using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software;<br />\n
          * documentation incorporated into the user interface.<br />\n
          This International Standard is applicable to acquirers and suppliers of user documentation, including a variety of specialists:<br />\n
          * business analysts who identify the tasks that the intended users will perform with the software;<br />\n
          * managers of the software development process or the documentation process;<br />\n
          * managers of the acquisition process, and those who authorize and approve acquisitions;<br />\n
          * managers and authors involved in proposal preparation.<br />\n
          It can also be consulted by those with other roles and interests in the documentation process:<br />\n
          * information designers and architects who plan the structure, format, and content requirements of<br />\n
          documentation products in a documentation set or web-accessible suite;<br />\n
          * experienced authors and editors who develop the written content for user documentation;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen;<br />\n
          * usability testers, documentation reviewers, subject matter experts;<br />\n
          * developers of tools for creating on-screen documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC Systems and software engineering -- Requirements for acquirers and suppliers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95515 …}
    #channels: Doctrine\ORM\PersistentCollection {#95521 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95517 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95519 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95507 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95503
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95504
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#95505
      date: 2011-06-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95509 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95511 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#95985
  +product: App\Entity\Product\Product {#95506
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#95523 …}
    #variants: Doctrine\ORM\PersistentCollection {#95525 …}
    #options: Doctrine\ORM\PersistentCollection {#95529 …}
    #associations: Doctrine\ORM\PersistentCollection {#95527 …}
    #createdAt: DateTime @1751039319 {#95501
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95502
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95513 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95978
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95506}
        #id: 38389
        #name: "IEEE/ISO/IEC 26512:2011"
        #slug: "ieee-iso-iec-26512-2011-ieee00005160-242497"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26512:2011 was developed to assist users of ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008) to acquire or supply software user documentation as part of the software life cycle processes. It defines the documentation process from the acquirer's standpoint and the supplier's standpoint. ISO/IEC/IEEE 26512:2011 covers the requirements for information items used in the acquisition of user documentation products: the Acquisition Plan, Document Specification, Statement of Work, Request for Proposals, and the proposal. It provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work. It includes requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services. It also discusses the use of a Documentation Management Plan and a Document Plan as they arise in the acquisition and supply processes. ISO/IEC/IEEE 26512:2011 is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the interest of software users in having consistent, complete, accurate, and usable documentation. It addresses both available approaches to standardization: a) process standards, which specify the way that documentation products are to be acquired and supplied; and b) documentation product standards, which specify the characteristics and functional requirements of the documentation.<br />\n
          As defined in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), the acquisition and supply activities comprise the agreement processes of the software life cycle. Acquisition and supply of user documentation and user documentation services are specializations of those processes.<br />\n
          User documentation services can be acquired and supplied for any part of the software documentation management or information management process, such as:<br />\n
          * documentation or information management;<br />\n
          * information design and development;<br />\n
          * documentation editing and review coordination;<br />\n
          * documentation testing, particularly usability testing;<br />\n
          * documentation production and packaging;<br />\n
          * documentation distribution and delivery;<br />\n
          * advice on the selection and implementation of documentation tools and supporting systems;<br />\n
          * documentation process improvement.<br />\n
          This International Standard provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It applies the Agreement processes (acquisition and supply) to software user documentation, and addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work discussed in this International Standard. This International Standard also addresses requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services.<br />\n
          This International Standard is intended for use in acquiring or supplying either printed or electronic (on-screen)<br />\n
          documentation. It is independent of documentation development or management tools or methodologies.<br />\n
          This International Standard might be helpful for acquiring and supplying the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation of products other than software;<br />\n
          * multimedia systems using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software;<br />\n
          * documentation incorporated into the user interface.<br />\n
          This International Standard is applicable to acquirers and suppliers of user documentation, including a variety of specialists:<br />\n
          * business analysts who identify the tasks that the intended users will perform with the software;<br />\n
          * managers of the software development process or the documentation process;<br />\n
          * managers of the acquisition process, and those who authorize and approve acquisitions;<br />\n
          * managers and authors involved in proposal preparation.<br />\n
          It can also be consulted by those with other roles and interests in the documentation process:<br />\n
          * information designers and architects who plan the structure, format, and content requirements of<br />\n
          documentation products in a documentation set or web-accessible suite;<br />\n
          * experienced authors and editors who develop the written content for user documentation;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen;<br />\n
          * usability testers, documentation reviewers, subject matter experts;<br />\n
          * developers of tools for creating on-screen documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC Systems and software engineering -- Requirements for acquirers and suppliers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95515 …}
    #channels: Doctrine\ORM\PersistentCollection {#95521 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95517 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95519 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95507 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95503
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95504
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#95505
      date: 2011-06-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95509 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95511 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95506
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#95523 …}
    #variants: Doctrine\ORM\PersistentCollection {#95525 …}
    #options: Doctrine\ORM\PersistentCollection {#95529 …}
    #associations: Doctrine\ORM\PersistentCollection {#95527 …}
    #createdAt: DateTime @1751039319 {#95501
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95502
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95513 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95978
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95506}
        #id: 38389
        #name: "IEEE/ISO/IEC 26512:2011"
        #slug: "ieee-iso-iec-26512-2011-ieee00005160-242497"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26512:2011 was developed to assist users of ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008) to acquire or supply software user documentation as part of the software life cycle processes. It defines the documentation process from the acquirer's standpoint and the supplier's standpoint. ISO/IEC/IEEE 26512:2011 covers the requirements for information items used in the acquisition of user documentation products: the Acquisition Plan, Document Specification, Statement of Work, Request for Proposals, and the proposal. It provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work. It includes requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services. It also discusses the use of a Documentation Management Plan and a Document Plan as they arise in the acquisition and supply processes. ISO/IEC/IEEE 26512:2011 is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the interest of software users in having consistent, complete, accurate, and usable documentation. It addresses both available approaches to standardization: a) process standards, which specify the way that documentation products are to be acquired and supplied; and b) documentation product standards, which specify the characteristics and functional requirements of the documentation.<br />\n
          As defined in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), the acquisition and supply activities comprise the agreement processes of the software life cycle. Acquisition and supply of user documentation and user documentation services are specializations of those processes.<br />\n
          User documentation services can be acquired and supplied for any part of the software documentation management or information management process, such as:<br />\n
          * documentation or information management;<br />\n
          * information design and development;<br />\n
          * documentation editing and review coordination;<br />\n
          * documentation testing, particularly usability testing;<br />\n
          * documentation production and packaging;<br />\n
          * documentation distribution and delivery;<br />\n
          * advice on the selection and implementation of documentation tools and supporting systems;<br />\n
          * documentation process improvement.<br />\n
          This International Standard provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It applies the Agreement processes (acquisition and supply) to software user documentation, and addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work discussed in this International Standard. This International Standard also addresses requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services.<br />\n
          This International Standard is intended for use in acquiring or supplying either printed or electronic (on-screen)<br />\n
          documentation. It is independent of documentation development or management tools or methodologies.<br />\n
          This International Standard might be helpful for acquiring and supplying the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation of products other than software;<br />\n
          * multimedia systems using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software;<br />\n
          * documentation incorporated into the user interface.<br />\n
          This International Standard is applicable to acquirers and suppliers of user documentation, including a variety of specialists:<br />\n
          * business analysts who identify the tasks that the intended users will perform with the software;<br />\n
          * managers of the software development process or the documentation process;<br />\n
          * managers of the acquisition process, and those who authorize and approve acquisitions;<br />\n
          * managers and authors involved in proposal preparation.<br />\n
          It can also be consulted by those with other roles and interests in the documentation process:<br />\n
          * information designers and architects who plan the structure, format, and content requirements of<br />\n
          documentation products in a documentation set or web-accessible suite;<br />\n
          * experienced authors and editors who develop the written content for user documentation;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen;<br />\n
          * usability testers, documentation reviewers, subject matter experts;<br />\n
          * developers of tools for creating on-screen documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC Systems and software engineering -- Requirements for acquirers and suppliers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95515 …}
    #channels: Doctrine\ORM\PersistentCollection {#95521 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95517 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95519 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95507 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95503
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95504
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#95505
      date: 2011-06-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95509 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95511 …}
  }
]

App\Twig\Components\ProductMostRecent {#96079
  +product: App\Entity\Product\Product {#95506
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#95523 …}
    #variants: Doctrine\ORM\PersistentCollection {#95525 …}
    #options: Doctrine\ORM\PersistentCollection {#95529 …}
    #associations: Doctrine\ORM\PersistentCollection {#95527 …}
    #createdAt: DateTime @1751039319 {#95501
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95502
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95513 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95978
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95506}
        #id: 38389
        #name: "IEEE/ISO/IEC 26512:2011"
        #slug: "ieee-iso-iec-26512-2011-ieee00005160-242497"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26512:2011 was developed to assist users of ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008) to acquire or supply software user documentation as part of the software life cycle processes. It defines the documentation process from the acquirer's standpoint and the supplier's standpoint. ISO/IEC/IEEE 26512:2011 covers the requirements for information items used in the acquisition of user documentation products: the Acquisition Plan, Document Specification, Statement of Work, Request for Proposals, and the proposal. It provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work. It includes requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services. It also discusses the use of a Documentation Management Plan and a Document Plan as they arise in the acquisition and supply processes. ISO/IEC/IEEE 26512:2011 is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the interest of software users in having consistent, complete, accurate, and usable documentation. It addresses both available approaches to standardization: a) process standards, which specify the way that documentation products are to be acquired and supplied; and b) documentation product standards, which specify the characteristics and functional requirements of the documentation.<br />\n
          As defined in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), the acquisition and supply activities comprise the agreement processes of the software life cycle. Acquisition and supply of user documentation and user documentation services are specializations of those processes.<br />\n
          User documentation services can be acquired and supplied for any part of the software documentation management or information management process, such as:<br />\n
          * documentation or information management;<br />\n
          * information design and development;<br />\n
          * documentation editing and review coordination;<br />\n
          * documentation testing, particularly usability testing;<br />\n
          * documentation production and packaging;<br />\n
          * documentation distribution and delivery;<br />\n
          * advice on the selection and implementation of documentation tools and supporting systems;<br />\n
          * documentation process improvement.<br />\n
          This International Standard provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It applies the Agreement processes (acquisition and supply) to software user documentation, and addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work discussed in this International Standard. This International Standard also addresses requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services.<br />\n
          This International Standard is intended for use in acquiring or supplying either printed or electronic (on-screen)<br />\n
          documentation. It is independent of documentation development or management tools or methodologies.<br />\n
          This International Standard might be helpful for acquiring and supplying the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation of products other than software;<br />\n
          * multimedia systems using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software;<br />\n
          * documentation incorporated into the user interface.<br />\n
          This International Standard is applicable to acquirers and suppliers of user documentation, including a variety of specialists:<br />\n
          * business analysts who identify the tasks that the intended users will perform with the software;<br />\n
          * managers of the software development process or the documentation process;<br />\n
          * managers of the acquisition process, and those who authorize and approve acquisitions;<br />\n
          * managers and authors involved in proposal preparation.<br />\n
          It can also be consulted by those with other roles and interests in the documentation process:<br />\n
          * information designers and architects who plan the structure, format, and content requirements of<br />\n
          documentation products in a documentation set or web-accessible suite;<br />\n
          * experienced authors and editors who develop the written content for user documentation;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen;<br />\n
          * usability testers, documentation reviewers, subject matter experts;<br />\n
          * developers of tools for creating on-screen documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC Systems and software engineering -- Requirements for acquirers and suppliers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95515 …}
    #channels: Doctrine\ORM\PersistentCollection {#95521 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95517 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95519 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95507 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95503
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95504
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#95505
      date: 2011-06-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95509 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95511 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95536
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#95553 …}
    #variants: Doctrine\ORM\PersistentCollection {#95555 …}
    #options: Doctrine\ORM\PersistentCollection {#95559 …}
    #associations: Doctrine\ORM\PersistentCollection {#95557 …}
    #createdAt: DateTime @1751039414 {#95531
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95532
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95543 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96293
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95536}
        #id: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95545 …}
    #channels: Doctrine\ORM\PersistentCollection {#95551 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95549 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95537 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95533
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95534
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95535
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95541 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96271
  +product: App\Entity\Product\Product {#95536
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#95553 …}
    #variants: Doctrine\ORM\PersistentCollection {#95555 …}
    #options: Doctrine\ORM\PersistentCollection {#95559 …}
    #associations: Doctrine\ORM\PersistentCollection {#95557 …}
    #createdAt: DateTime @1751039414 {#95531
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95532
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95543 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96293
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95536}
        #id: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95545 …}
    #channels: Doctrine\ORM\PersistentCollection {#95551 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95549 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95537 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95533
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95534
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95535
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95541 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95536
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#95553 …}
    #variants: Doctrine\ORM\PersistentCollection {#95555 …}
    #options: Doctrine\ORM\PersistentCollection {#95559 …}
    #associations: Doctrine\ORM\PersistentCollection {#95557 …}
    #createdAt: DateTime @1751039414 {#95531
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95532
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95543 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96293
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95536}
        #id: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95545 …}
    #channels: Doctrine\ORM\PersistentCollection {#95551 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95549 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95537 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95533
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95534
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95535
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95541 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96300
  +product: App\Entity\Product\Product {#95536
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#95553 …}
    #variants: Doctrine\ORM\PersistentCollection {#95555 …}
    #options: Doctrine\ORM\PersistentCollection {#95559 …}
    #associations: Doctrine\ORM\PersistentCollection {#95557 …}
    #createdAt: DateTime @1751039414 {#95531
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95532
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95543 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96293
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95536}
        #id: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95545 …}
    #channels: Doctrine\ORM\PersistentCollection {#95551 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95549 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95537 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95533
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95534
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95535
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95541 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95536
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#95553 …}
    #variants: Doctrine\ORM\PersistentCollection {#95555 …}
    #options: Doctrine\ORM\PersistentCollection {#95559 …}
    #associations: Doctrine\ORM\PersistentCollection {#95557 …}
    #createdAt: DateTime @1751039414 {#95531
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95532
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95543 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96293
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95536}
        #id: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95545 …}
    #channels: Doctrine\ORM\PersistentCollection {#95551 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95549 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95537 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95533
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95534
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95535
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95541 …}
  }
]

App\Twig\Components\ProductMostRecent {#96377
  +product: App\Entity\Product\Product {#95536
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#95553 …}
    #variants: Doctrine\ORM\PersistentCollection {#95555 …}
    #options: Doctrine\ORM\PersistentCollection {#95559 …}
    #associations: Doctrine\ORM\PersistentCollection {#95557 …}
    #createdAt: DateTime @1751039414 {#95531
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95532
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95543 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96293
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95536}
        #id: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95545 …}
    #channels: Doctrine\ORM\PersistentCollection {#95551 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95549 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95537 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95533
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95534
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95535
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95541 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95626
    #id: 11892
    #code: "IEEE00006738"
    #attributes: Doctrine\ORM\PersistentCollection {#95643 …}
    #variants: Doctrine\ORM\PersistentCollection {#95645 …}
    #options: Doctrine\ORM\PersistentCollection {#95649 …}
    #associations: Doctrine\ORM\PersistentCollection {#95647 …}
    #createdAt: DateTime @1751040060 {#95621
      date: 2025-06-27 18:01:00.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95622
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95633 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96502
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95626}
        #id: 42577
        #name: "IEEE/ISO/IEC 18881:2016"
        #slug: "ieee-iso-iec-18881-2016-ieee00006738-243544"
        #description: """
          Adoption Standard - Active.<br />\n
          This standard describes network gateway access, control, and management; specifies control and management requirements; defines the system architecture, communication sequences, and enhanced functions for the protocols defined in IEEE 1888(TM), “Ubiquitous Green Community Control Network Protocol”; and extends the protocols and interfaces based on the requirements. This standard shall provide enhanced protocols, workflows, and message formats for the network gateway under control and management, such as registration, access, control, event handling, configuration, status querying, etc.<br />\n
          \t\t\t\t<br />\n
          Based on the IEEE 1888(TM) protocols, this standard describes network gateway central access control and management policy through the extension of existing interface protocols, message formats, and interactive processing in ubiquitous green community control networks (UGCCNets). This standard extends the definition of the original interface protocols and message formats and mainly specifies the network gateway signal flow for access control, registration management, state querying, event reporting, remote management, etc.<br />\n
          This standard aims to provide open and standardized network gateway management interface protocols for service providers, system integrators, equipment manufacturers, etc., through the extension of the original interface protocol in order to be able to remotely control and monitor the network gateway and other facilities in green communities, such as heating, ventilation, and air conditioning (HVAC); lighting systems; energy equipment; and so on.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard -- Information technology -- Ubiquitous green community control network -- Control and management"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95635 …}
    #channels: Doctrine\ORM\PersistentCollection {#95641 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95637 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95639 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95627 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95623
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95624
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1460671200 {#95625
      date: 2016-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "18881"
    -bookCollection: ""
    -pageCount: 65
    -documents: Doctrine\ORM\PersistentCollection {#95629 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95631 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96482
  +product: App\Entity\Product\Product {#95626
    #id: 11892
    #code: "IEEE00006738"
    #attributes: Doctrine\ORM\PersistentCollection {#95643 …}
    #variants: Doctrine\ORM\PersistentCollection {#95645 …}
    #options: Doctrine\ORM\PersistentCollection {#95649 …}
    #associations: Doctrine\ORM\PersistentCollection {#95647 …}
    #createdAt: DateTime @1751040060 {#95621
      date: 2025-06-27 18:01:00.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95622
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95633 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96502
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95626}
        #id: 42577
        #name: "IEEE/ISO/IEC 18881:2016"
        #slug: "ieee-iso-iec-18881-2016-ieee00006738-243544"
        #description: """
          Adoption Standard - Active.<br />\n
          This standard describes network gateway access, control, and management; specifies control and management requirements; defines the system architecture, communication sequences, and enhanced functions for the protocols defined in IEEE 1888(TM), “Ubiquitous Green Community Control Network Protocol”; and extends the protocols and interfaces based on the requirements. This standard shall provide enhanced protocols, workflows, and message formats for the network gateway under control and management, such as registration, access, control, event handling, configuration, status querying, etc.<br />\n
          \t\t\t\t<br />\n
          Based on the IEEE 1888(TM) protocols, this standard describes network gateway central access control and management policy through the extension of existing interface protocols, message formats, and interactive processing in ubiquitous green community control networks (UGCCNets). This standard extends the definition of the original interface protocols and message formats and mainly specifies the network gateway signal flow for access control, registration management, state querying, event reporting, remote management, etc.<br />\n
          This standard aims to provide open and standardized network gateway management interface protocols for service providers, system integrators, equipment manufacturers, etc., through the extension of the original interface protocol in order to be able to remotely control and monitor the network gateway and other facilities in green communities, such as heating, ventilation, and air conditioning (HVAC); lighting systems; energy equipment; and so on.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard -- Information technology -- Ubiquitous green community control network -- Control and management"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95635 …}
    #channels: Doctrine\ORM\PersistentCollection {#95641 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95637 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95639 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95627 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95623
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95624
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1460671200 {#95625
      date: 2016-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "18881"
    -bookCollection: ""
    -pageCount: 65
    -documents: Doctrine\ORM\PersistentCollection {#95629 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95631 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95626
    #id: 11892
    #code: "IEEE00006738"
    #attributes: Doctrine\ORM\PersistentCollection {#95643 …}
    #variants: Doctrine\ORM\PersistentCollection {#95645 …}
    #options: Doctrine\ORM\PersistentCollection {#95649 …}
    #associations: Doctrine\ORM\PersistentCollection {#95647 …}
    #createdAt: DateTime @1751040060 {#95621
      date: 2025-06-27 18:01:00.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95622
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95633 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96502
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95626}
        #id: 42577
        #name: "IEEE/ISO/IEC 18881:2016"
        #slug: "ieee-iso-iec-18881-2016-ieee00006738-243544"
        #description: """
          Adoption Standard - Active.<br />\n
          This standard describes network gateway access, control, and management; specifies control and management requirements; defines the system architecture, communication sequences, and enhanced functions for the protocols defined in IEEE 1888(TM), “Ubiquitous Green Community Control Network Protocol”; and extends the protocols and interfaces based on the requirements. This standard shall provide enhanced protocols, workflows, and message formats for the network gateway under control and management, such as registration, access, control, event handling, configuration, status querying, etc.<br />\n
          \t\t\t\t<br />\n
          Based on the IEEE 1888(TM) protocols, this standard describes network gateway central access control and management policy through the extension of existing interface protocols, message formats, and interactive processing in ubiquitous green community control networks (UGCCNets). This standard extends the definition of the original interface protocols and message formats and mainly specifies the network gateway signal flow for access control, registration management, state querying, event reporting, remote management, etc.<br />\n
          This standard aims to provide open and standardized network gateway management interface protocols for service providers, system integrators, equipment manufacturers, etc., through the extension of the original interface protocol in order to be able to remotely control and monitor the network gateway and other facilities in green communities, such as heating, ventilation, and air conditioning (HVAC); lighting systems; energy equipment; and so on.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard -- Information technology -- Ubiquitous green community control network -- Control and management"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95635 …}
    #channels: Doctrine\ORM\PersistentCollection {#95641 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95637 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95639 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95627 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95623
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95624
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1460671200 {#95625
      date: 2016-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "18881"
    -bookCollection: ""
    -pageCount: 65
    -documents: Doctrine\ORM\PersistentCollection {#95629 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95631 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96516
  +product: App\Entity\Product\Product {#95626
    #id: 11892
    #code: "IEEE00006738"
    #attributes: Doctrine\ORM\PersistentCollection {#95643 …}
    #variants: Doctrine\ORM\PersistentCollection {#95645 …}
    #options: Doctrine\ORM\PersistentCollection {#95649 …}
    #associations: Doctrine\ORM\PersistentCollection {#95647 …}
    #createdAt: DateTime @1751040060 {#95621
      date: 2025-06-27 18:01:00.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95622
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95633 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96502
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95626}
        #id: 42577
        #name: "IEEE/ISO/IEC 18881:2016"
        #slug: "ieee-iso-iec-18881-2016-ieee00006738-243544"
        #description: """
          Adoption Standard - Active.<br />\n
          This standard describes network gateway access, control, and management; specifies control and management requirements; defines the system architecture, communication sequences, and enhanced functions for the protocols defined in IEEE 1888(TM), “Ubiquitous Green Community Control Network Protocol”; and extends the protocols and interfaces based on the requirements. This standard shall provide enhanced protocols, workflows, and message formats for the network gateway under control and management, such as registration, access, control, event handling, configuration, status querying, etc.<br />\n
          \t\t\t\t<br />\n
          Based on the IEEE 1888(TM) protocols, this standard describes network gateway central access control and management policy through the extension of existing interface protocols, message formats, and interactive processing in ubiquitous green community control networks (UGCCNets). This standard extends the definition of the original interface protocols and message formats and mainly specifies the network gateway signal flow for access control, registration management, state querying, event reporting, remote management, etc.<br />\n
          This standard aims to provide open and standardized network gateway management interface protocols for service providers, system integrators, equipment manufacturers, etc., through the extension of the original interface protocol in order to be able to remotely control and monitor the network gateway and other facilities in green communities, such as heating, ventilation, and air conditioning (HVAC); lighting systems; energy equipment; and so on.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard -- Information technology -- Ubiquitous green community control network -- Control and management"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95635 …}
    #channels: Doctrine\ORM\PersistentCollection {#95641 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95637 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95639 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95627 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95623
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95624
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1460671200 {#95625
      date: 2016-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "18881"
    -bookCollection: ""
    -pageCount: 65
    -documents: Doctrine\ORM\PersistentCollection {#95629 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95631 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95626
    #id: 11892
    #code: "IEEE00006738"
    #attributes: Doctrine\ORM\PersistentCollection {#95643 …}
    #variants: Doctrine\ORM\PersistentCollection {#95645 …}
    #options: Doctrine\ORM\PersistentCollection {#95649 …}
    #associations: Doctrine\ORM\PersistentCollection {#95647 …}
    #createdAt: DateTime @1751040060 {#95621
      date: 2025-06-27 18:01:00.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95622
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95633 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96502
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95626}
        #id: 42577
        #name: "IEEE/ISO/IEC 18881:2016"
        #slug: "ieee-iso-iec-18881-2016-ieee00006738-243544"
        #description: """
          Adoption Standard - Active.<br />\n
          This standard describes network gateway access, control, and management; specifies control and management requirements; defines the system architecture, communication sequences, and enhanced functions for the protocols defined in IEEE 1888(TM), “Ubiquitous Green Community Control Network Protocol”; and extends the protocols and interfaces based on the requirements. This standard shall provide enhanced protocols, workflows, and message formats for the network gateway under control and management, such as registration, access, control, event handling, configuration, status querying, etc.<br />\n
          \t\t\t\t<br />\n
          Based on the IEEE 1888(TM) protocols, this standard describes network gateway central access control and management policy through the extension of existing interface protocols, message formats, and interactive processing in ubiquitous green community control networks (UGCCNets). This standard extends the definition of the original interface protocols and message formats and mainly specifies the network gateway signal flow for access control, registration management, state querying, event reporting, remote management, etc.<br />\n
          This standard aims to provide open and standardized network gateway management interface protocols for service providers, system integrators, equipment manufacturers, etc., through the extension of the original interface protocol in order to be able to remotely control and monitor the network gateway and other facilities in green communities, such as heating, ventilation, and air conditioning (HVAC); lighting systems; energy equipment; and so on.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard -- Information technology -- Ubiquitous green community control network -- Control and management"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95635 …}
    #channels: Doctrine\ORM\PersistentCollection {#95641 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95637 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95639 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95627 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95623
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95624
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1460671200 {#95625
      date: 2016-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "18881"
    -bookCollection: ""
    -pageCount: 65
    -documents: Doctrine\ORM\PersistentCollection {#95629 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95631 …}
  }
]

App\Twig\Components\ProductMostRecent {#96590
  +product: App\Entity\Product\Product {#95626
    #id: 11892
    #code: "IEEE00006738"
    #attributes: Doctrine\ORM\PersistentCollection {#95643 …}
    #variants: Doctrine\ORM\PersistentCollection {#95645 …}
    #options: Doctrine\ORM\PersistentCollection {#95649 …}
    #associations: Doctrine\ORM\PersistentCollection {#95647 …}
    #createdAt: DateTime @1751040060 {#95621
      date: 2025-06-27 18:01:00.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95622
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95633 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96502
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95626}
        #id: 42577
        #name: "IEEE/ISO/IEC 18881:2016"
        #slug: "ieee-iso-iec-18881-2016-ieee00006738-243544"
        #description: """
          Adoption Standard - Active.<br />\n
          This standard describes network gateway access, control, and management; specifies control and management requirements; defines the system architecture, communication sequences, and enhanced functions for the protocols defined in IEEE 1888(TM), “Ubiquitous Green Community Control Network Protocol”; and extends the protocols and interfaces based on the requirements. This standard shall provide enhanced protocols, workflows, and message formats for the network gateway under control and management, such as registration, access, control, event handling, configuration, status querying, etc.<br />\n
          \t\t\t\t<br />\n
          Based on the IEEE 1888(TM) protocols, this standard describes network gateway central access control and management policy through the extension of existing interface protocols, message formats, and interactive processing in ubiquitous green community control networks (UGCCNets). This standard extends the definition of the original interface protocols and message formats and mainly specifies the network gateway signal flow for access control, registration management, state querying, event reporting, remote management, etc.<br />\n
          This standard aims to provide open and standardized network gateway management interface protocols for service providers, system integrators, equipment manufacturers, etc., through the extension of the original interface protocol in order to be able to remotely control and monitor the network gateway and other facilities in green communities, such as heating, ventilation, and air conditioning (HVAC); lighting systems; energy equipment; and so on.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard -- Information technology -- Ubiquitous green community control network -- Control and management"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95635 …}
    #channels: Doctrine\ORM\PersistentCollection {#95641 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95637 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95639 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95627 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95623
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95624
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1460671200 {#95625
      date: 2016-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "18881"
    -bookCollection: ""
    -pageCount: 65
    -documents: Doctrine\ORM\PersistentCollection {#95629 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95631 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95566
    #id: 10996
    #code: "IEEE00005409"
    #attributes: Doctrine\ORM\PersistentCollection {#95583 …}
    #variants: Doctrine\ORM\PersistentCollection {#95585 …}
    #options: Doctrine\ORM\PersistentCollection {#95589 …}
    #associations: Doctrine\ORM\PersistentCollection {#95587 …}
    #createdAt: DateTime @1751039414 {#95561
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95562
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95573 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96740
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95566}
        #id: 38993
        #name: "IEEE/ISO/IEC 26515:2012"
        #slug: "ieee-iso-iec-26515-2012-ieee00005409-242648"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26515:2012 specifies the way in which user documentation can be developed in agile development projects. It is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. ISO/IEC/IEEE 26515:2012 addresses the relationship between the user documentation process and the life cycle documentation process in agile development. It describes how the information developer or project manager may plan and manage the user documentation development in an agile environment. It is intended neither to encourage nor to discourage the use of any particular agile development tools or methods.<br />\n
          \t\t\t\t<br />\n
          This clause presents the scope, purpose, organization, and candidate uses of this International Standard.<br />\n
          This International Standard supports the interest of technical writers and associated roles responsible for producing user documentation for software and systems developed within an agile environment. This<br />\n
          International Standard takes a process standard approach to specify the way in which user documentation can be developed in agile development projects.<br />\n
          This International Standard provides requirements on information management and documentation processes appropriate for software projects that are using agile development methods.<br />\n
          Clause 5 covers the overall requirements for documentation in the software life cycle.<br />\n
          Clause 6 describes how the information development lead or project manager may plan and manage the user documentation development team in an agile environment.<br />\n
          Clause 7 covers the relationship between the user documentation process and life cycle documentation process in agile development.<br />\n
          This International Standard is intended neither to encourage nor to discourage the use of any particular agile development tools or methods. This International Standard provides guidance on processes appropriate for developers of user documentation in software and systems projects that are using agile development methodologies. It will not be limited to the development phase of the life cycle of user documentation, but includes activities throughout the user documentation life cycle.<br />\n
          This International Standard is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It is assumed that users of this International Standard have experience or general knowledge of traditional user documentation processes.<br />\n
          document does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Developing user documentation in an agile environment"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95575 …}
    #channels: Doctrine\ORM\PersistentCollection {#95581 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95577 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95579 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95567 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95563
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95565
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26515"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#95569 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95571 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96720
  +product: App\Entity\Product\Product {#95566
    #id: 10996
    #code: "IEEE00005409"
    #attributes: Doctrine\ORM\PersistentCollection {#95583 …}
    #variants: Doctrine\ORM\PersistentCollection {#95585 …}
    #options: Doctrine\ORM\PersistentCollection {#95589 …}
    #associations: Doctrine\ORM\PersistentCollection {#95587 …}
    #createdAt: DateTime @1751039414 {#95561
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95562
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95573 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96740
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95566}
        #id: 38993
        #name: "IEEE/ISO/IEC 26515:2012"
        #slug: "ieee-iso-iec-26515-2012-ieee00005409-242648"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26515:2012 specifies the way in which user documentation can be developed in agile development projects. It is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. ISO/IEC/IEEE 26515:2012 addresses the relationship between the user documentation process and the life cycle documentation process in agile development. It describes how the information developer or project manager may plan and manage the user documentation development in an agile environment. It is intended neither to encourage nor to discourage the use of any particular agile development tools or methods.<br />\n
          \t\t\t\t<br />\n
          This clause presents the scope, purpose, organization, and candidate uses of this International Standard.<br />\n
          This International Standard supports the interest of technical writers and associated roles responsible for producing user documentation for software and systems developed within an agile environment. This<br />\n
          International Standard takes a process standard approach to specify the way in which user documentation can be developed in agile development projects.<br />\n
          This International Standard provides requirements on information management and documentation processes appropriate for software projects that are using agile development methods.<br />\n
          Clause 5 covers the overall requirements for documentation in the software life cycle.<br />\n
          Clause 6 describes how the information development lead or project manager may plan and manage the user documentation development team in an agile environment.<br />\n
          Clause 7 covers the relationship between the user documentation process and life cycle documentation process in agile development.<br />\n
          This International Standard is intended neither to encourage nor to discourage the use of any particular agile development tools or methods. This International Standard provides guidance on processes appropriate for developers of user documentation in software and systems projects that are using agile development methodologies. It will not be limited to the development phase of the life cycle of user documentation, but includes activities throughout the user documentation life cycle.<br />\n
          This International Standard is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It is assumed that users of this International Standard have experience or general knowledge of traditional user documentation processes.<br />\n
          document does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Developing user documentation in an agile environment"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95575 …}
    #channels: Doctrine\ORM\PersistentCollection {#95581 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95577 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95579 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95567 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95563
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95565
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26515"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#95569 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95571 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95566
    #id: 10996
    #code: "IEEE00005409"
    #attributes: Doctrine\ORM\PersistentCollection {#95583 …}
    #variants: Doctrine\ORM\PersistentCollection {#95585 …}
    #options: Doctrine\ORM\PersistentCollection {#95589 …}
    #associations: Doctrine\ORM\PersistentCollection {#95587 …}
    #createdAt: DateTime @1751039414 {#95561
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95562
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95573 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96740
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95566}
        #id: 38993
        #name: "IEEE/ISO/IEC 26515:2012"
        #slug: "ieee-iso-iec-26515-2012-ieee00005409-242648"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26515:2012 specifies the way in which user documentation can be developed in agile development projects. It is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. ISO/IEC/IEEE 26515:2012 addresses the relationship between the user documentation process and the life cycle documentation process in agile development. It describes how the information developer or project manager may plan and manage the user documentation development in an agile environment. It is intended neither to encourage nor to discourage the use of any particular agile development tools or methods.<br />\n
          \t\t\t\t<br />\n
          This clause presents the scope, purpose, organization, and candidate uses of this International Standard.<br />\n
          This International Standard supports the interest of technical writers and associated roles responsible for producing user documentation for software and systems developed within an agile environment. This<br />\n
          International Standard takes a process standard approach to specify the way in which user documentation can be developed in agile development projects.<br />\n
          This International Standard provides requirements on information management and documentation processes appropriate for software projects that are using agile development methods.<br />\n
          Clause 5 covers the overall requirements for documentation in the software life cycle.<br />\n
          Clause 6 describes how the information development lead or project manager may plan and manage the user documentation development team in an agile environment.<br />\n
          Clause 7 covers the relationship between the user documentation process and life cycle documentation process in agile development.<br />\n
          This International Standard is intended neither to encourage nor to discourage the use of any particular agile development tools or methods. This International Standard provides guidance on processes appropriate for developers of user documentation in software and systems projects that are using agile development methodologies. It will not be limited to the development phase of the life cycle of user documentation, but includes activities throughout the user documentation life cycle.<br />\n
          This International Standard is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It is assumed that users of this International Standard have experience or general knowledge of traditional user documentation processes.<br />\n
          document does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Developing user documentation in an agile environment"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95575 …}
    #channels: Doctrine\ORM\PersistentCollection {#95581 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95577 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95579 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95567 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95563
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95565
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26515"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#95569 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95571 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96747
  +product: App\Entity\Product\Product {#95566
    #id: 10996
    #code: "IEEE00005409"
    #attributes: Doctrine\ORM\PersistentCollection {#95583 …}
    #variants: Doctrine\ORM\PersistentCollection {#95585 …}
    #options: Doctrine\ORM\PersistentCollection {#95589 …}
    #associations: Doctrine\ORM\PersistentCollection {#95587 …}
    #createdAt: DateTime @1751039414 {#95561
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95562
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95573 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96740
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95566}
        #id: 38993
        #name: "IEEE/ISO/IEC 26515:2012"
        #slug: "ieee-iso-iec-26515-2012-ieee00005409-242648"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26515:2012 specifies the way in which user documentation can be developed in agile development projects. It is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. ISO/IEC/IEEE 26515:2012 addresses the relationship between the user documentation process and the life cycle documentation process in agile development. It describes how the information developer or project manager may plan and manage the user documentation development in an agile environment. It is intended neither to encourage nor to discourage the use of any particular agile development tools or methods.<br />\n
          \t\t\t\t<br />\n
          This clause presents the scope, purpose, organization, and candidate uses of this International Standard.<br />\n
          This International Standard supports the interest of technical writers and associated roles responsible for producing user documentation for software and systems developed within an agile environment. This<br />\n
          International Standard takes a process standard approach to specify the way in which user documentation can be developed in agile development projects.<br />\n
          This International Standard provides requirements on information management and documentation processes appropriate for software projects that are using agile development methods.<br />\n
          Clause 5 covers the overall requirements for documentation in the software life cycle.<br />\n
          Clause 6 describes how the information development lead or project manager may plan and manage the user documentation development team in an agile environment.<br />\n
          Clause 7 covers the relationship between the user documentation process and life cycle documentation process in agile development.<br />\n
          This International Standard is intended neither to encourage nor to discourage the use of any particular agile development tools or methods. This International Standard provides guidance on processes appropriate for developers of user documentation in software and systems projects that are using agile development methodologies. It will not be limited to the development phase of the life cycle of user documentation, but includes activities throughout the user documentation life cycle.<br />\n
          This International Standard is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It is assumed that users of this International Standard have experience or general knowledge of traditional user documentation processes.<br />\n
          document does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Developing user documentation in an agile environment"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95575 …}
    #channels: Doctrine\ORM\PersistentCollection {#95581 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95577 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95579 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95567 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95563
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95565
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26515"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#95569 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95571 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95566
    #id: 10996
    #code: "IEEE00005409"
    #attributes: Doctrine\ORM\PersistentCollection {#95583 …}
    #variants: Doctrine\ORM\PersistentCollection {#95585 …}
    #options: Doctrine\ORM\PersistentCollection {#95589 …}
    #associations: Doctrine\ORM\PersistentCollection {#95587 …}
    #createdAt: DateTime @1751039414 {#95561
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95562
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95573 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96740
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95566}
        #id: 38993
        #name: "IEEE/ISO/IEC 26515:2012"
        #slug: "ieee-iso-iec-26515-2012-ieee00005409-242648"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26515:2012 specifies the way in which user documentation can be developed in agile development projects. It is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. ISO/IEC/IEEE 26515:2012 addresses the relationship between the user documentation process and the life cycle documentation process in agile development. It describes how the information developer or project manager may plan and manage the user documentation development in an agile environment. It is intended neither to encourage nor to discourage the use of any particular agile development tools or methods.<br />\n
          \t\t\t\t<br />\n
          This clause presents the scope, purpose, organization, and candidate uses of this International Standard.<br />\n
          This International Standard supports the interest of technical writers and associated roles responsible for producing user documentation for software and systems developed within an agile environment. This<br />\n
          International Standard takes a process standard approach to specify the way in which user documentation can be developed in agile development projects.<br />\n
          This International Standard provides requirements on information management and documentation processes appropriate for software projects that are using agile development methods.<br />\n
          Clause 5 covers the overall requirements for documentation in the software life cycle.<br />\n
          Clause 6 describes how the information development lead or project manager may plan and manage the user documentation development team in an agile environment.<br />\n
          Clause 7 covers the relationship between the user documentation process and life cycle documentation process in agile development.<br />\n
          This International Standard is intended neither to encourage nor to discourage the use of any particular agile development tools or methods. This International Standard provides guidance on processes appropriate for developers of user documentation in software and systems projects that are using agile development methodologies. It will not be limited to the development phase of the life cycle of user documentation, but includes activities throughout the user documentation life cycle.<br />\n
          This International Standard is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It is assumed that users of this International Standard have experience or general knowledge of traditional user documentation processes.<br />\n
          document does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Developing user documentation in an agile environment"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95575 …}
    #channels: Doctrine\ORM\PersistentCollection {#95581 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95577 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95579 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95567 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95563
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95565
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26515"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#95569 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95571 …}
  }
]

App\Twig\Components\ProductMostRecent {#96824
  +product: App\Entity\Product\Product {#95566
    #id: 10996
    #code: "IEEE00005409"
    #attributes: Doctrine\ORM\PersistentCollection {#95583 …}
    #variants: Doctrine\ORM\PersistentCollection {#95585 …}
    #options: Doctrine\ORM\PersistentCollection {#95589 …}
    #associations: Doctrine\ORM\PersistentCollection {#95587 …}
    #createdAt: DateTime @1751039414 {#95561
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95562
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95573 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96740
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95566}
        #id: 38993
        #name: "IEEE/ISO/IEC 26515:2012"
        #slug: "ieee-iso-iec-26515-2012-ieee00005409-242648"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26515:2012 specifies the way in which user documentation can be developed in agile development projects. It is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. ISO/IEC/IEEE 26515:2012 addresses the relationship between the user documentation process and the life cycle documentation process in agile development. It describes how the information developer or project manager may plan and manage the user documentation development in an agile environment. It is intended neither to encourage nor to discourage the use of any particular agile development tools or methods.<br />\n
          \t\t\t\t<br />\n
          This clause presents the scope, purpose, organization, and candidate uses of this International Standard.<br />\n
          This International Standard supports the interest of technical writers and associated roles responsible for producing user documentation for software and systems developed within an agile environment. This<br />\n
          International Standard takes a process standard approach to specify the way in which user documentation can be developed in agile development projects.<br />\n
          This International Standard provides requirements on information management and documentation processes appropriate for software projects that are using agile development methods.<br />\n
          Clause 5 covers the overall requirements for documentation in the software life cycle.<br />\n
          Clause 6 describes how the information development lead or project manager may plan and manage the user documentation development team in an agile environment.<br />\n
          Clause 7 covers the relationship between the user documentation process and life cycle documentation process in agile development.<br />\n
          This International Standard is intended neither to encourage nor to discourage the use of any particular agile development tools or methods. This International Standard provides guidance on processes appropriate for developers of user documentation in software and systems projects that are using agile development methodologies. It will not be limited to the development phase of the life cycle of user documentation, but includes activities throughout the user documentation life cycle.<br />\n
          This International Standard is intended for use in all organizations that are using agile development, or are considering implementing their projects using these techniques. It is assumed that users of this International Standard have experience or general knowledge of traditional user documentation processes.<br />\n
          document does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Developing user documentation in an agile environment"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95575 …}
    #channels: Doctrine\ORM\PersistentCollection {#95581 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95577 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95579 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95567 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95563
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#95565
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26515"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#95569 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95571 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95596
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#95613 …}
    #variants: Doctrine\ORM\PersistentCollection {#95615 …}
    #options: Doctrine\ORM\PersistentCollection {#95619 …}
    #associations: Doctrine\ORM\PersistentCollection {#95617 …}
    #createdAt: DateTime @1751039567 {#95591
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95592
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95603 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96949
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95596}
        #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 {#95605 …}
    #channels: Doctrine\ORM\PersistentCollection {#95611 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95607 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95609 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95597 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95593
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#95594
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#95595
      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 {#95599 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95601 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96929
  +product: App\Entity\Product\Product {#95596
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#95613 …}
    #variants: Doctrine\ORM\PersistentCollection {#95615 …}
    #options: Doctrine\ORM\PersistentCollection {#95619 …}
    #associations: Doctrine\ORM\PersistentCollection {#95617 …}
    #createdAt: DateTime @1751039567 {#95591
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95592
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95603 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96949
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95596}
        #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 {#95605 …}
    #channels: Doctrine\ORM\PersistentCollection {#95611 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95607 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95609 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95597 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95593
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#95594
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#95595
      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 {#95599 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95601 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95596
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#95613 …}
    #variants: Doctrine\ORM\PersistentCollection {#95615 …}
    #options: Doctrine\ORM\PersistentCollection {#95619 …}
    #associations: Doctrine\ORM\PersistentCollection {#95617 …}
    #createdAt: DateTime @1751039567 {#95591
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95592
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95603 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96949
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95596}
        #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 {#95605 …}
    #channels: Doctrine\ORM\PersistentCollection {#95611 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95607 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95609 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95597 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95593
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#95594
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#95595
      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 {#95599 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95601 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96963
  +product: App\Entity\Product\Product {#95596
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#95613 …}
    #variants: Doctrine\ORM\PersistentCollection {#95615 …}
    #options: Doctrine\ORM\PersistentCollection {#95619 …}
    #associations: Doctrine\ORM\PersistentCollection {#95617 …}
    #createdAt: DateTime @1751039567 {#95591
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95592
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95603 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96949
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95596}
        #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 {#95605 …}
    #channels: Doctrine\ORM\PersistentCollection {#95611 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95607 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95609 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95597 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95593
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#95594
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#95595
      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 {#95599 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95601 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95596
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#95613 …}
    #variants: Doctrine\ORM\PersistentCollection {#95615 …}
    #options: Doctrine\ORM\PersistentCollection {#95619 …}
    #associations: Doctrine\ORM\PersistentCollection {#95617 …}
    #createdAt: DateTime @1751039567 {#95591
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95592
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95603 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96949
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95596}
        #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 {#95605 …}
    #channels: Doctrine\ORM\PersistentCollection {#95611 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95607 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95609 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95597 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95593
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#95594
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#95595
      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 {#95599 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95601 …}
  }
]

App\Twig\Components\ProductMostRecent {#97037
  +product: App\Entity\Product\Product {#95596
    #id: 11240
    #code: "IEEE00005789"
    #attributes: Doctrine\ORM\PersistentCollection {#95613 …}
    #variants: Doctrine\ORM\PersistentCollection {#95615 …}
    #options: Doctrine\ORM\PersistentCollection {#95619 …}
    #associations: Doctrine\ORM\PersistentCollection {#95617 …}
    #createdAt: DateTime @1751039567 {#95591
      date: 2025-06-27 17:52:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95592
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95603 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96949
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95596}
        #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 {#95605 …}
    #channels: Doctrine\ORM\PersistentCollection {#95611 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95607 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95609 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95467 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95597 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95593
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1645138800 {#95594
      date: 2022-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#95595
      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 {#95599 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95601 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}