Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7520
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751039319 {#7536
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#95002
  +product: App\Entity\Product\Product {#7520
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751039319 {#7536
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7520
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751039319 {#7536
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
]

App\Twig\Components\ProductType {#95182
  +product: App\Entity\Product\Product {#7520
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751039319 {#7536
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7520
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751039319 {#7536
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
]

App\Twig\Components\ProductMostRecent {#95257
  +product: App\Entity\Product\Product {#7520
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751039319 {#7536
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108691
    #id: 9071
    #code: "IEEE00001554"
    #attributes: Doctrine\ORM\PersistentCollection {#108672 …}
    #variants: Doctrine\ORM\PersistentCollection {#108669 …}
    #options: Doctrine\ORM\PersistentCollection {#108665 …}
    #associations: Doctrine\ORM\PersistentCollection {#108667 …}
    #createdAt: DateTime @1751037947 {#108698
      date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108671
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108682 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108721
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108691}
        #id: 31293
        #name: "IEEE 1063:2001 (R2007)"
        #slug: "ieee-1063-2001-r2007-ieee00001554-240723"
        #description: """
          Revision Standard - Superseded.<br />\n
          Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n
          A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software User Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108680 …}
    #channels: Doctrine\ORM\PersistentCollection {#108674 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108678 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108676 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108689 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108658
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108697
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1008802800 {#108696
      date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1190844000 {#108690
      date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1063"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#108687 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108685 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#108705
  +product: App\Entity\Product\Product {#108691
    #id: 9071
    #code: "IEEE00001554"
    #attributes: Doctrine\ORM\PersistentCollection {#108672 …}
    #variants: Doctrine\ORM\PersistentCollection {#108669 …}
    #options: Doctrine\ORM\PersistentCollection {#108665 …}
    #associations: Doctrine\ORM\PersistentCollection {#108667 …}
    #createdAt: DateTime @1751037947 {#108698
      date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108671
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108682 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108721
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108691}
        #id: 31293
        #name: "IEEE 1063:2001 (R2007)"
        #slug: "ieee-1063-2001-r2007-ieee00001554-240723"
        #description: """
          Revision Standard - Superseded.<br />\n
          Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n
          A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software User Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108680 …}
    #channels: Doctrine\ORM\PersistentCollection {#108674 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108678 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108676 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108689 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108658
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108697
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1008802800 {#108696
      date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1190844000 {#108690
      date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1063"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#108687 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108685 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108691
    #id: 9071
    #code: "IEEE00001554"
    #attributes: Doctrine\ORM\PersistentCollection {#108672 …}
    #variants: Doctrine\ORM\PersistentCollection {#108669 …}
    #options: Doctrine\ORM\PersistentCollection {#108665 …}
    #associations: Doctrine\ORM\PersistentCollection {#108667 …}
    #createdAt: DateTime @1751037947 {#108698
      date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108671
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108682 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108721
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108691}
        #id: 31293
        #name: "IEEE 1063:2001 (R2007)"
        #slug: "ieee-1063-2001-r2007-ieee00001554-240723"
        #description: """
          Revision Standard - Superseded.<br />\n
          Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n
          A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software User Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108680 …}
    #channels: Doctrine\ORM\PersistentCollection {#108674 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108678 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108676 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108689 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108658
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108697
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1008802800 {#108696
      date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1190844000 {#108690
      date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1063"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#108687 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108685 …}
  }
]

App\Twig\Components\ProductMostRecent {#108810
  +product: App\Entity\Product\Product {#108691
    #id: 9071
    #code: "IEEE00001554"
    #attributes: Doctrine\ORM\PersistentCollection {#108672 …}
    #variants: Doctrine\ORM\PersistentCollection {#108669 …}
    #options: Doctrine\ORM\PersistentCollection {#108665 …}
    #associations: Doctrine\ORM\PersistentCollection {#108667 …}
    #createdAt: DateTime @1751037947 {#108698
      date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108671
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108682 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108721
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108691}
        #id: 31293
        #name: "IEEE 1063:2001 (R2007)"
        #slug: "ieee-1063-2001-r2007-ieee00001554-240723"
        #description: """
          Revision Standard - Superseded.<br />\n
          Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n
          A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software User Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108680 …}
    #channels: Doctrine\ORM\PersistentCollection {#108674 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108678 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108676 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108689 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108658
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108697
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1008802800 {#108696
      date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1190844000 {#108690
      date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1063"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#108687 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108685 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95694
    #id: 13291
    #code: "IEEE00011893"
    #attributes: Doctrine\ORM\PersistentCollection {#95676 …}
    #variants: Doctrine\ORM\PersistentCollection {#95673 …}
    #options: Doctrine\ORM\PersistentCollection {#95669 …}
    #associations: Doctrine\ORM\PersistentCollection {#95671 …}
    #createdAt: DateTime @1751041032 {#95702
      date: 2025-06-27 18:17:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95681
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95687 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95722
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95694}
        #id: 48173
        #name: "IEEE/IEC P26512"
        #slug: "ieee-iec-p26512-ieee00011893-571176"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          This document was developed to assist users of ISO/IEC/IEEE 15288:2023 or ISO/IEC/IEEE 12207 to acquire or supply information for users as part of the system or life cycle processes. It defines the documentation<br />\n
          process from the acquirers standpoint and the supplier&#039;s standpoint. This document covers the requirements for information items used in the acquisition of user documentation products: the acquisition plan, information product specification, statement of work, request for proposals, and the proposal. It provides an overview of the information management processes which may require acquisition and supply of system or software user documentation products and services. It addresses the preparation of requirements for 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.<br />\n
          This document is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and onscreen documentation. Its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information. The acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following: information management; information design and development; information editing and review coordination; information testing, particularly usability testing; information production and packaging; information distribution and delivery; advice on the selection and implementation of information development tools and supporting systems; and information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information. These requirements are central to the information specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for information products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEC/IEEE Draft International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95685 …}
    #channels: Doctrine\ORM\PersistentCollection {#95678 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95683 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95680 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95695 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95665
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743030000 {#95701
      date: 2025-03-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1743202800 {#95700
      date: 2025-03-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#95691 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95689 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#115445
  +product: App\Entity\Product\Product {#95694
    #id: 13291
    #code: "IEEE00011893"
    #attributes: Doctrine\ORM\PersistentCollection {#95676 …}
    #variants: Doctrine\ORM\PersistentCollection {#95673 …}
    #options: Doctrine\ORM\PersistentCollection {#95669 …}
    #associations: Doctrine\ORM\PersistentCollection {#95671 …}
    #createdAt: DateTime @1751041032 {#95702
      date: 2025-06-27 18:17:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95681
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95687 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95722
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95694}
        #id: 48173
        #name: "IEEE/IEC P26512"
        #slug: "ieee-iec-p26512-ieee00011893-571176"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          This document was developed to assist users of ISO/IEC/IEEE 15288:2023 or ISO/IEC/IEEE 12207 to acquire or supply information for users as part of the system or life cycle processes. It defines the documentation<br />\n
          process from the acquirers standpoint and the supplier&#039;s standpoint. This document covers the requirements for information items used in the acquisition of user documentation products: the acquisition plan, information product specification, statement of work, request for proposals, and the proposal. It provides an overview of the information management processes which may require acquisition and supply of system or software user documentation products and services. It addresses the preparation of requirements for 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.<br />\n
          This document is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and onscreen documentation. Its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information. The acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following: information management; information design and development; information editing and review coordination; information testing, particularly usability testing; information production and packaging; information distribution and delivery; advice on the selection and implementation of information development tools and supporting systems; and information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information. These requirements are central to the information specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for information products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEC/IEEE Draft International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95685 …}
    #channels: Doctrine\ORM\PersistentCollection {#95678 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95683 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95680 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95695 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95665
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743030000 {#95701
      date: 2025-03-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1743202800 {#95700
      date: 2025-03-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#95691 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95689 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95694
    #id: 13291
    #code: "IEEE00011893"
    #attributes: Doctrine\ORM\PersistentCollection {#95676 …}
    #variants: Doctrine\ORM\PersistentCollection {#95673 …}
    #options: Doctrine\ORM\PersistentCollection {#95669 …}
    #associations: Doctrine\ORM\PersistentCollection {#95671 …}
    #createdAt: DateTime @1751041032 {#95702
      date: 2025-06-27 18:17:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95681
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95687 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95722
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95694}
        #id: 48173
        #name: "IEEE/IEC P26512"
        #slug: "ieee-iec-p26512-ieee00011893-571176"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          This document was developed to assist users of ISO/IEC/IEEE 15288:2023 or ISO/IEC/IEEE 12207 to acquire or supply information for users as part of the system or life cycle processes. It defines the documentation<br />\n
          process from the acquirers standpoint and the supplier&#039;s standpoint. This document covers the requirements for information items used in the acquisition of user documentation products: the acquisition plan, information product specification, statement of work, request for proposals, and the proposal. It provides an overview of the information management processes which may require acquisition and supply of system or software user documentation products and services. It addresses the preparation of requirements for 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.<br />\n
          This document is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and onscreen documentation. Its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information. The acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following: information management; information design and development; information editing and review coordination; information testing, particularly usability testing; information production and packaging; information distribution and delivery; advice on the selection and implementation of information development tools and supporting systems; and information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information. These requirements are central to the information specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for information products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEC/IEEE Draft International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95685 …}
    #channels: Doctrine\ORM\PersistentCollection {#95678 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95683 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95680 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95695 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95665
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743030000 {#95701
      date: 2025-03-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1743202800 {#95700
      date: 2025-03-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#95691 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95689 …}
  }
]

App\Twig\Components\ProductMostRecent {#115511
  +product: App\Entity\Product\Product {#95694
    #id: 13291
    #code: "IEEE00011893"
    #attributes: Doctrine\ORM\PersistentCollection {#95676 …}
    #variants: Doctrine\ORM\PersistentCollection {#95673 …}
    #options: Doctrine\ORM\PersistentCollection {#95669 …}
    #associations: Doctrine\ORM\PersistentCollection {#95671 …}
    #createdAt: DateTime @1751041032 {#95702
      date: 2025-06-27 18:17:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95681
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95687 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95722
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95694}
        #id: 48173
        #name: "IEEE/IEC P26512"
        #slug: "ieee-iec-p26512-ieee00011893-571176"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          This document was developed to assist users of ISO/IEC/IEEE 15288:2023 or ISO/IEC/IEEE 12207 to acquire or supply information for users as part of the system or life cycle processes. It defines the documentation<br />\n
          process from the acquirers standpoint and the supplier&#039;s standpoint. This document covers the requirements for information items used in the acquisition of user documentation products: the acquisition plan, information product specification, statement of work, request for proposals, and the proposal. It provides an overview of the information management processes which may require acquisition and supply of system or software user documentation products and services. It addresses the preparation of requirements for 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.<br />\n
          This document is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and onscreen documentation. Its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information. The acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following: information management; information design and development; information editing and review coordination; information testing, particularly usability testing; information production and packaging; information distribution and delivery; advice on the selection and implementation of information development tools and supporting systems; and information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information. These requirements are central to the information specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for information products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEC/IEEE Draft International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95685 …}
    #channels: Doctrine\ORM\PersistentCollection {#95678 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95683 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95680 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95695 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95665
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743030000 {#95701
      date: 2025-03-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1743202800 {#95700
      date: 2025-03-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#95691 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95689 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#115388
    #id: 11971
    #code: "IEEE00006845"
    #attributes: Doctrine\ORM\PersistentCollection {#115404 …}
    #variants: Doctrine\ORM\PersistentCollection {#115406 …}
    #options: Doctrine\ORM\PersistentCollection {#115410 …}
    #associations: Doctrine\ORM\PersistentCollection {#115408 …}
    #createdAt: DateTime @1751040110 {#115379
      date: 2025-06-27 18:01:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#115377
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#115394 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#115582
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#115388}
        #id: 42893
        #name: "IEEE/ISO/IEC 26512:2017"
        #slug: "ieee-iso-iec-26512-2017-ieee00006845-243623"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.<br />\n
          As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:<br />\n
          — information management;<br />\n
          — information design and development;<br />\n
          — information editing and review coordination;<br />\n
          — information testing, particularly usability testing;<br />\n
          — information production and packaging;<br />\n
          — information distribution and delivery;<br />\n
          — advice on the selection and implementation of information development tools and supporting systems; and<br />\n
          — information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information.<br />\n
          These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#115396 …}
    #channels: Doctrine\ORM\PersistentCollection {#115402 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#115398 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#115400 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#115387 …}
    -apiLastModifiedAt: DateTime @1754517600 {#115380
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#115373
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1509490800 {#115370
      date: 2017-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 47
    -documents: Doctrine\ORM\PersistentCollection {#115390 …}
    -favorites: Doctrine\ORM\PersistentCollection {#115392 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#115597
  +product: App\Entity\Product\Product {#115388
    #id: 11971
    #code: "IEEE00006845"
    #attributes: Doctrine\ORM\PersistentCollection {#115404 …}
    #variants: Doctrine\ORM\PersistentCollection {#115406 …}
    #options: Doctrine\ORM\PersistentCollection {#115410 …}
    #associations: Doctrine\ORM\PersistentCollection {#115408 …}
    #createdAt: DateTime @1751040110 {#115379
      date: 2025-06-27 18:01:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#115377
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#115394 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#115582
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#115388}
        #id: 42893
        #name: "IEEE/ISO/IEC 26512:2017"
        #slug: "ieee-iso-iec-26512-2017-ieee00006845-243623"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.<br />\n
          As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:<br />\n
          — information management;<br />\n
          — information design and development;<br />\n
          — information editing and review coordination;<br />\n
          — information testing, particularly usability testing;<br />\n
          — information production and packaging;<br />\n
          — information distribution and delivery;<br />\n
          — advice on the selection and implementation of information development tools and supporting systems; and<br />\n
          — information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information.<br />\n
          These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#115396 …}
    #channels: Doctrine\ORM\PersistentCollection {#115402 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#115398 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#115400 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#115387 …}
    -apiLastModifiedAt: DateTime @1754517600 {#115380
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#115373
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1509490800 {#115370
      date: 2017-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 47
    -documents: Doctrine\ORM\PersistentCollection {#115390 …}
    -favorites: Doctrine\ORM\PersistentCollection {#115392 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#115388
    #id: 11971
    #code: "IEEE00006845"
    #attributes: Doctrine\ORM\PersistentCollection {#115404 …}
    #variants: Doctrine\ORM\PersistentCollection {#115406 …}
    #options: Doctrine\ORM\PersistentCollection {#115410 …}
    #associations: Doctrine\ORM\PersistentCollection {#115408 …}
    #createdAt: DateTime @1751040110 {#115379
      date: 2025-06-27 18:01:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#115377
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#115394 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#115582
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#115388}
        #id: 42893
        #name: "IEEE/ISO/IEC 26512:2017"
        #slug: "ieee-iso-iec-26512-2017-ieee00006845-243623"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.<br />\n
          As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:<br />\n
          — information management;<br />\n
          — information design and development;<br />\n
          — information editing and review coordination;<br />\n
          — information testing, particularly usability testing;<br />\n
          — information production and packaging;<br />\n
          — information distribution and delivery;<br />\n
          — advice on the selection and implementation of information development tools and supporting systems; and<br />\n
          — information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information.<br />\n
          These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#115396 …}
    #channels: Doctrine\ORM\PersistentCollection {#115402 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#115398 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#115400 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#115387 …}
    -apiLastModifiedAt: DateTime @1754517600 {#115380
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#115373
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1509490800 {#115370
      date: 2017-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 47
    -documents: Doctrine\ORM\PersistentCollection {#115390 …}
    -favorites: Doctrine\ORM\PersistentCollection {#115392 …}
  }
]

App\Twig\Components\ProductMostRecent {#115649
  +product: App\Entity\Product\Product {#115388
    #id: 11971
    #code: "IEEE00006845"
    #attributes: Doctrine\ORM\PersistentCollection {#115404 …}
    #variants: Doctrine\ORM\PersistentCollection {#115406 …}
    #options: Doctrine\ORM\PersistentCollection {#115410 …}
    #associations: Doctrine\ORM\PersistentCollection {#115408 …}
    #createdAt: DateTime @1751040110 {#115379
      date: 2025-06-27 18:01:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#115377
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#115394 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#115582
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#115388}
        #id: 42893
        #name: "IEEE/ISO/IEC 26512:2017"
        #slug: "ieee-iso-iec-26512-2017-ieee00006845-243623"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.<br />\n
          As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:<br />\n
          — information management;<br />\n
          — information design and development;<br />\n
          — information editing and review coordination;<br />\n
          — information testing, particularly usability testing;<br />\n
          — information production and packaging;<br />\n
          — information distribution and delivery;<br />\n
          — advice on the selection and implementation of information development tools and supporting systems; and<br />\n
          — information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information.<br />\n
          These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#115396 …}
    #channels: Doctrine\ORM\PersistentCollection {#115402 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#115398 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#115400 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#115387 …}
    -apiLastModifiedAt: DateTime @1754517600 {#115380
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#115373
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1509490800 {#115370
      date: 2017-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 47
    -documents: Doctrine\ORM\PersistentCollection {#115390 …}
    -favorites: Doctrine\ORM\PersistentCollection {#115392 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7520
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751039319 {#7536
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#115713
  +product: App\Entity\Product\Product {#7520
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751039319 {#7536
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7520
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751039319 {#7536
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
]

App\Twig\Components\ProductMostRecent {#115740
  +product: App\Entity\Product\Product {#7520
    #id: 10845
    #code: "IEEE00005160"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751039319 {#7536
      date: 2025-06-27 17:48:39.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1306879200 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#137264
    #id: 9958
    #code: "IEEE00003340"
    #attributes: Doctrine\ORM\PersistentCollection {#137247 …}
    #variants: Doctrine\ORM\PersistentCollection {#137245 …}
    #options: Doctrine\ORM\PersistentCollection {#137240 …}
    #associations: Doctrine\ORM\PersistentCollection {#137242 …}
    #createdAt: DateTime @1751038700 {#137237
      date: 2025-06-27 17:38:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#137230
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#137258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#137505
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#137264}
        #id: 34841
        #name: "IEEE 1490:2003"
        #slug: "ieee-1490-2003-ieee00003340-241610"
        #description: """
          Revision Standard - Inactive-Withdrawn.<br />\n
          Supersedes IEEE Std 1490-1998 SUMMARY: IEEE Std 1490-2003 is an adoption, in its entirety, of A Guide to Project Management Body of Knowledge (PMBOK® Guide). Project scope: The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc. Project purpose: SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.<br />\n
          \t\t\t\t<br />\n
          The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc.<br />\n
          SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide Adoption of PMI Standard - A Guide to the Project Management Body of Knowledge"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#137256 …}
    #channels: Doctrine\ORM\PersistentCollection {#137249 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#137253 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#137251 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#137266 …}
    -apiLastModifiedAt: DateTime @1754517600 {#137223
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#137272
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1085349600 {#137243
      date: 2004-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1232924400 {#137224
      date: 2009-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1490"
    -bookCollection: ""
    -pageCount: 194
    -documents: Doctrine\ORM\PersistentCollection {#137262 …}
    -favorites: Doctrine\ORM\PersistentCollection {#137260 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#137428
  +product: App\Entity\Product\Product {#137264
    #id: 9958
    #code: "IEEE00003340"
    #attributes: Doctrine\ORM\PersistentCollection {#137247 …}
    #variants: Doctrine\ORM\PersistentCollection {#137245 …}
    #options: Doctrine\ORM\PersistentCollection {#137240 …}
    #associations: Doctrine\ORM\PersistentCollection {#137242 …}
    #createdAt: DateTime @1751038700 {#137237
      date: 2025-06-27 17:38:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#137230
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#137258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#137505
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#137264}
        #id: 34841
        #name: "IEEE 1490:2003"
        #slug: "ieee-1490-2003-ieee00003340-241610"
        #description: """
          Revision Standard - Inactive-Withdrawn.<br />\n
          Supersedes IEEE Std 1490-1998 SUMMARY: IEEE Std 1490-2003 is an adoption, in its entirety, of A Guide to Project Management Body of Knowledge (PMBOK® Guide). Project scope: The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc. Project purpose: SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.<br />\n
          \t\t\t\t<br />\n
          The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc.<br />\n
          SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide Adoption of PMI Standard - A Guide to the Project Management Body of Knowledge"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#137256 …}
    #channels: Doctrine\ORM\PersistentCollection {#137249 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#137253 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#137251 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#137266 …}
    -apiLastModifiedAt: DateTime @1754517600 {#137223
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#137272
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1085349600 {#137243
      date: 2004-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1232924400 {#137224
      date: 2009-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1490"
    -bookCollection: ""
    -pageCount: 194
    -documents: Doctrine\ORM\PersistentCollection {#137262 …}
    -favorites: Doctrine\ORM\PersistentCollection {#137260 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}

[
  "product" => App\Entity\Product\Product {#137264
    #id: 9958
    #code: "IEEE00003340"
    #attributes: Doctrine\ORM\PersistentCollection {#137247 …}
    #variants: Doctrine\ORM\PersistentCollection {#137245 …}
    #options: Doctrine\ORM\PersistentCollection {#137240 …}
    #associations: Doctrine\ORM\PersistentCollection {#137242 …}
    #createdAt: DateTime @1751038700 {#137237
      date: 2025-06-27 17:38:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#137230
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#137258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#137505
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#137264}
        #id: 34841
        #name: "IEEE 1490:2003"
        #slug: "ieee-1490-2003-ieee00003340-241610"
        #description: """
          Revision Standard - Inactive-Withdrawn.<br />\n
          Supersedes IEEE Std 1490-1998 SUMMARY: IEEE Std 1490-2003 is an adoption, in its entirety, of A Guide to Project Management Body of Knowledge (PMBOK® Guide). Project scope: The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc. Project purpose: SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.<br />\n
          \t\t\t\t<br />\n
          The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc.<br />\n
          SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide Adoption of PMI Standard - A Guide to the Project Management Body of Knowledge"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#137256 …}
    #channels: Doctrine\ORM\PersistentCollection {#137249 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#137253 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#137251 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#137266 …}
    -apiLastModifiedAt: DateTime @1754517600 {#137223
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#137272
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1085349600 {#137243
      date: 2004-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1232924400 {#137224
      date: 2009-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1490"
    -bookCollection: ""
    -pageCount: 194
    -documents: Doctrine\ORM\PersistentCollection {#137262 …}
    -favorites: Doctrine\ORM\PersistentCollection {#137260 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#137509
  +product: App\Entity\Product\Product {#137264
    #id: 9958
    #code: "IEEE00003340"
    #attributes: Doctrine\ORM\PersistentCollection {#137247 …}
    #variants: Doctrine\ORM\PersistentCollection {#137245 …}
    #options: Doctrine\ORM\PersistentCollection {#137240 …}
    #associations: Doctrine\ORM\PersistentCollection {#137242 …}
    #createdAt: DateTime @1751038700 {#137237
      date: 2025-06-27 17:38:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#137230
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#137258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#137505
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#137264}
        #id: 34841
        #name: "IEEE 1490:2003"
        #slug: "ieee-1490-2003-ieee00003340-241610"
        #description: """
          Revision Standard - Inactive-Withdrawn.<br />\n
          Supersedes IEEE Std 1490-1998 SUMMARY: IEEE Std 1490-2003 is an adoption, in its entirety, of A Guide to Project Management Body of Knowledge (PMBOK® Guide). Project scope: The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc. Project purpose: SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.<br />\n
          \t\t\t\t<br />\n
          The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc.<br />\n
          SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide Adoption of PMI Standard - A Guide to the Project Management Body of Knowledge"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#137256 …}
    #channels: Doctrine\ORM\PersistentCollection {#137249 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#137253 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#137251 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#137266 …}
    -apiLastModifiedAt: DateTime @1754517600 {#137223
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#137272
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1085349600 {#137243
      date: 2004-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1232924400 {#137224
      date: 2009-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1490"
    -bookCollection: ""
    -pageCount: 194
    -documents: Doctrine\ORM\PersistentCollection {#137262 …}
    -favorites: Doctrine\ORM\PersistentCollection {#137260 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#137264
    #id: 9958
    #code: "IEEE00003340"
    #attributes: Doctrine\ORM\PersistentCollection {#137247 …}
    #variants: Doctrine\ORM\PersistentCollection {#137245 …}
    #options: Doctrine\ORM\PersistentCollection {#137240 …}
    #associations: Doctrine\ORM\PersistentCollection {#137242 …}
    #createdAt: DateTime @1751038700 {#137237
      date: 2025-06-27 17:38:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#137230
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#137258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#137505
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#137264}
        #id: 34841
        #name: "IEEE 1490:2003"
        #slug: "ieee-1490-2003-ieee00003340-241610"
        #description: """
          Revision Standard - Inactive-Withdrawn.<br />\n
          Supersedes IEEE Std 1490-1998 SUMMARY: IEEE Std 1490-2003 is an adoption, in its entirety, of A Guide to Project Management Body of Knowledge (PMBOK® Guide). Project scope: The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc. Project purpose: SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.<br />\n
          \t\t\t\t<br />\n
          The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc.<br />\n
          SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide Adoption of PMI Standard - A Guide to the Project Management Body of Knowledge"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#137256 …}
    #channels: Doctrine\ORM\PersistentCollection {#137249 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#137253 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#137251 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#137266 …}
    -apiLastModifiedAt: DateTime @1754517600 {#137223
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#137272
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1085349600 {#137243
      date: 2004-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1232924400 {#137224
      date: 2009-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1490"
    -bookCollection: ""
    -pageCount: 194
    -documents: Doctrine\ORM\PersistentCollection {#137262 …}
    -favorites: Doctrine\ORM\PersistentCollection {#137260 …}
  }
]

App\Twig\Components\ProductMostRecent {#137587
  +product: App\Entity\Product\Product {#137264
    #id: 9958
    #code: "IEEE00003340"
    #attributes: Doctrine\ORM\PersistentCollection {#137247 …}
    #variants: Doctrine\ORM\PersistentCollection {#137245 …}
    #options: Doctrine\ORM\PersistentCollection {#137240 …}
    #associations: Doctrine\ORM\PersistentCollection {#137242 …}
    #createdAt: DateTime @1751038700 {#137237
      date: 2025-06-27 17:38:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#137230
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#137258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#137505
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#137264}
        #id: 34841
        #name: "IEEE 1490:2003"
        #slug: "ieee-1490-2003-ieee00003340-241610"
        #description: """
          Revision Standard - Inactive-Withdrawn.<br />\n
          Supersedes IEEE Std 1490-1998 SUMMARY: IEEE Std 1490-2003 is an adoption, in its entirety, of A Guide to Project Management Body of Knowledge (PMBOK® Guide). Project scope: The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc. Project purpose: SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.<br />\n
          \t\t\t\t<br />\n
          The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted and adopt this as IEEE Std 1490-2002. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession for talking about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. Footnote: Project Management Body of Knowledge (PMBOK) and Project Management Institute (PMI) are registered as trademarks of the Project Management Institute, Inc.<br />\n
          SESC has previously adopted the 1996 version of PMIBOK to provide a framework for software engineering project management. PMBOK 2000 added new material to reflect the growth of the knowledge and practices in the field of project management by capturing those practices, tools, techniques, and other relevant items that have become generally accepted. Additionally, clarification text and figures, and corrections, have been added that make the document more valuable to users. SESC intends to adopt the current version of PMBOK, replacing the previous version.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide Adoption of PMI Standard - A Guide to the Project Management Body of Knowledge"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#137256 …}
    #channels: Doctrine\ORM\PersistentCollection {#137249 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#137253 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#137251 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#137266 …}
    -apiLastModifiedAt: DateTime @1754517600 {#137223
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#137272
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1085349600 {#137243
      date: 2004-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1232924400 {#137224
      date: 2009-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1490"
    -bookCollection: ""
    -pageCount: 194
    -documents: Doctrine\ORM\PersistentCollection {#137262 …}
    -favorites: Doctrine\ORM\PersistentCollection {#137260 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#137232
    #id: 10038
    #code: "IEEE00003497"
    #attributes: Doctrine\ORM\PersistentCollection {#137303 …}
    #variants: Doctrine\ORM\PersistentCollection {#137310 …}
    #options: Doctrine\ORM\PersistentCollection {#137304 …}
    #associations: Doctrine\ORM\PersistentCollection {#137313 …}
    #createdAt: DateTime @1751038766 {#137238
      date: 2025-06-27 17:39:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#137236
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#137225 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#137704
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#137232}
        #id: 35161
        #name: "IEEE 828:2005"
        #slug: "ieee-828-2005-ieee00003497-241690"
        #description: """
          Revision Standard - Superseded.<br />\n
          The minimum required contents of a Software Configuration Management (SCM) Plan<br />\n
          are established via this standard. This standard applies to the entire life cycle of critical software (e.g., where failure would impact safety or cause large financial or social losses). It also applies to noncritical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.<br />\n
          \t\t\t\t<br />\n
          This standard establishes the minimum required contents of a Software Configuration Management (SCM) Plan (also referred to as &quot;the Plan&quot;). This standard applies to the entire life cycle of critical software; e.g., where failure would impact safety or cause large financial or social losses. It also applies to noncritical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.<br />\n
          The SCM Plan documents what SCM activities are to be done, how they are to be done, who is responsible for doing specific activities, when they are to happen, and what resources are required. It can address SCM activities over any portion of a software product's life cycle. This standard is consistent with the IEEE Software Engineering Body of Knowledge (SWEBOK) project Stoneman release on the topic of configuration management and with IEEE/EIA Std 12207.0(TM).
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Configuration Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#137306 …}
    #channels: Doctrine\ORM\PersistentCollection {#137316 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#137288 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#137322 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#137231 …}
    -apiLastModifiedAt: DateTime @1754517600 {#137235
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#137234
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1123797600 {#137233
      date: 2005-08-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "828"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#137228 …}
    -favorites: Doctrine\ORM\PersistentCollection {#137226 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#137662
  +product: App\Entity\Product\Product {#137232
    #id: 10038
    #code: "IEEE00003497"
    #attributes: Doctrine\ORM\PersistentCollection {#137303 …}
    #variants: Doctrine\ORM\PersistentCollection {#137310 …}
    #options: Doctrine\ORM\PersistentCollection {#137304 …}
    #associations: Doctrine\ORM\PersistentCollection {#137313 …}
    #createdAt: DateTime @1751038766 {#137238
      date: 2025-06-27 17:39:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#137236
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#137225 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#137704
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#137232}
        #id: 35161
        #name: "IEEE 828:2005"
        #slug: "ieee-828-2005-ieee00003497-241690"
        #description: """
          Revision Standard - Superseded.<br />\n
          The minimum required contents of a Software Configuration Management (SCM) Plan<br />\n
          are established via this standard. This standard applies to the entire life cycle of critical software (e.g., where failure would impact safety or cause large financial or social losses). It also applies to noncritical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.<br />\n
          \t\t\t\t<br />\n
          This standard establishes the minimum required contents of a Software Configuration Management (SCM) Plan (also referred to as &quot;the Plan&quot;). This standard applies to the entire life cycle of critical software; e.g., where failure would impact safety or cause large financial or social losses. It also applies to noncritical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.<br />\n
          The SCM Plan documents what SCM activities are to be done, how they are to be done, who is responsible for doing specific activities, when they are to happen, and what resources are required. It can address SCM activities over any portion of a software product's life cycle. This standard is consistent with the IEEE Software Engineering Body of Knowledge (SWEBOK) project Stoneman release on the topic of configuration management and with IEEE/EIA Std 12207.0(TM).
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Configuration Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#137306 …}
    #channels: Doctrine\ORM\PersistentCollection {#137316 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#137288 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#137322 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#137231 …}
    -apiLastModifiedAt: DateTime @1754517600 {#137235
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#137234
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1123797600 {#137233
      date: 2005-08-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "828"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#137228 …}
    -favorites: Doctrine\ORM\PersistentCollection {#137226 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}