Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9068
    #code: "IEEE00001550"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037944 {#7274
      date: 2025-06-27 17:25:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31281
        #name: "IEEE 1062:1993 (R2002)"
        #slug: "ieee-1062-1993-r2002-ieee00001550-240720"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.<br />\n
          In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item.<br />\n
          Commercial-off-the-shelf (COTS) software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with &quot;how to operate&quot; documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.<br />\n
          Modified-off-the-shelf (MOTS) software is similar to COTS software; however, the MOTS software does<br />\n
          advertise service to tailor the software to acquirer-specific requirements.<br />\n
          Fully developed software will often be unique for a specific application and will be produced on a one-of-akind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).<br />\n
          This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on modified-off-the-shelf software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @723078000 {#7318
      date: 1992-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#93008
  +product: App\Entity\Product\Product {#7311
    #id: 9068
    #code: "IEEE00001550"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037944 {#7274
      date: 2025-06-27 17:25:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31281
        #name: "IEEE 1062:1993 (R2002)"
        #slug: "ieee-1062-1993-r2002-ieee00001550-240720"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.<br />\n
          In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item.<br />\n
          Commercial-off-the-shelf (COTS) software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with &quot;how to operate&quot; documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.<br />\n
          Modified-off-the-shelf (MOTS) software is similar to COTS software; however, the MOTS software does<br />\n
          advertise service to tailor the software to acquirer-specific requirements.<br />\n
          Fully developed software will often be unique for a specific application and will be produced on a one-of-akind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).<br />\n
          This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on modified-off-the-shelf software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @723078000 {#7318
      date: 1992-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9068
    #code: "IEEE00001550"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037944 {#7274
      date: 2025-06-27 17:25:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31281
        #name: "IEEE 1062:1993 (R2002)"
        #slug: "ieee-1062-1993-r2002-ieee00001550-240720"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.<br />\n
          In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item.<br />\n
          Commercial-off-the-shelf (COTS) software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with &quot;how to operate&quot; documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.<br />\n
          Modified-off-the-shelf (MOTS) software is similar to COTS software; however, the MOTS software does<br />\n
          advertise service to tailor the software to acquirer-specific requirements.<br />\n
          Fully developed software will often be unique for a specific application and will be produced on a one-of-akind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).<br />\n
          This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on modified-off-the-shelf software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @723078000 {#7318
      date: 1992-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductType {#93201
  +product: App\Entity\Product\Product {#7311
    #id: 9068
    #code: "IEEE00001550"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037944 {#7274
      date: 2025-06-27 17:25:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31281
        #name: "IEEE 1062:1993 (R2002)"
        #slug: "ieee-1062-1993-r2002-ieee00001550-240720"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.<br />\n
          In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item.<br />\n
          Commercial-off-the-shelf (COTS) software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with &quot;how to operate&quot; documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.<br />\n
          Modified-off-the-shelf (MOTS) software is similar to COTS software; however, the MOTS software does<br />\n
          advertise service to tailor the software to acquirer-specific requirements.<br />\n
          Fully developed software will often be unique for a specific application and will be produced on a one-of-akind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).<br />\n
          This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on modified-off-the-shelf software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @723078000 {#7318
      date: 1992-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9068
    #code: "IEEE00001550"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037944 {#7274
      date: 2025-06-27 17:25:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31281
        #name: "IEEE 1062:1993 (R2002)"
        #slug: "ieee-1062-1993-r2002-ieee00001550-240720"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.<br />\n
          In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item.<br />\n
          Commercial-off-the-shelf (COTS) software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with &quot;how to operate&quot; documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.<br />\n
          Modified-off-the-shelf (MOTS) software is similar to COTS software; however, the MOTS software does<br />\n
          advertise service to tailor the software to acquirer-specific requirements.<br />\n
          Fully developed software will often be unique for a specific application and will be produced on a one-of-akind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).<br />\n
          This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on modified-off-the-shelf software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @723078000 {#7318
      date: 1992-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#93276
  +product: App\Entity\Product\Product {#7311
    #id: 9068
    #code: "IEEE00001550"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037944 {#7274
      date: 2025-06-27 17:25:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31281
        #name: "IEEE 1062:1993 (R2002)"
        #slug: "ieee-1062-1993-r2002-ieee00001550-240720"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.<br />\n
          In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item.<br />\n
          Commercial-off-the-shelf (COTS) software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with &quot;how to operate&quot; documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.<br />\n
          Modified-off-the-shelf (MOTS) software is similar to COTS software; however, the MOTS software does<br />\n
          advertise service to tailor the software to acquirer-specific requirements.<br />\n
          Fully developed software will often be unique for a specific application and will be produced on a one-of-akind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).<br />\n
          This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on modified-off-the-shelf software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @723078000 {#7318
      date: 1992-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93699
    #id: 10448
    #code: "IEEE00004411"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039068 {#93706
      date: 2025-06-27 17:44:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93685
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 36801
        #name: "IEEE 1062:2015"
        #slug: "ieee-1062-2015-ieee00004411-242100"
        #description: """
          Revision Standard - Active.<br />\n
          A set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process is described in this recommended practice. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of off-the-shelf (OTS), custom, or free and open source software (FOSS). Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within its acquisition process.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes a set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of commercial-off-the-shelf (COTS), custom, or free and open source software (FOSS). Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within the organization’s acquisition process. Security will be included as a quality attribute considered during the acquisition.<br />\n
          This recommended practice is designed to help organizations and individuals incorporate quality, including security considerations during the definition, evaluation, selection, and acceptance of supplier software for operational use. It will also help determine how supplier software should be evaluated, tested, and accepted for delivery to end users. This recommended practice is intended to satisfy the following objectives: - Promote consistency within organizations in acquiring software from software suppliers. - Provide useful practices on including quality, security, safety and data rights considerations during acquisition planning. - Provide useful practices on evaluating and qualifying supplier capabilities to meet user requirements. - Provide useful practices on evaluating and qualifying supplier software. - Assist individuals or organizations judging the quality of supplier software for referral to end users. - Assist suppliers in understanding how the software will be evaluated, tested, and accepted for delivery to end users. Success in acquiring high-quality software products and services from software suppliers can be achieved by doing the following things: a) Identifying quality characteristics necessary to achieve the acquirer’s objectives b) Selecting suppliers most capable of meeting the acquisition objectives c) Including quality considerations in the planning, evaluation, and acceptance activities d) Developing an organizational strategy for acquiring software e) Establishing a software acquisition process using the eight steps stated in 5.2 as a starting point f) Putting the defined process into practice
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93669
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1734044400 {#93705
      date: 2024-12-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1456441200 {#93704
      date: 2016-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1456441200 {#93698
      date: 2016-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 69
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106888
  +product: App\Entity\Product\Product {#93699
    #id: 10448
    #code: "IEEE00004411"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039068 {#93706
      date: 2025-06-27 17:44:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93685
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 36801
        #name: "IEEE 1062:2015"
        #slug: "ieee-1062-2015-ieee00004411-242100"
        #description: """
          Revision Standard - Active.<br />\n
          A set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process is described in this recommended practice. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of off-the-shelf (OTS), custom, or free and open source software (FOSS). Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within its acquisition process.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes a set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of commercial-off-the-shelf (COTS), custom, or free and open source software (FOSS). Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within the organization’s acquisition process. Security will be included as a quality attribute considered during the acquisition.<br />\n
          This recommended practice is designed to help organizations and individuals incorporate quality, including security considerations during the definition, evaluation, selection, and acceptance of supplier software for operational use. It will also help determine how supplier software should be evaluated, tested, and accepted for delivery to end users. This recommended practice is intended to satisfy the following objectives: - Promote consistency within organizations in acquiring software from software suppliers. - Provide useful practices on including quality, security, safety and data rights considerations during acquisition planning. - Provide useful practices on evaluating and qualifying supplier capabilities to meet user requirements. - Provide useful practices on evaluating and qualifying supplier software. - Assist individuals or organizations judging the quality of supplier software for referral to end users. - Assist suppliers in understanding how the software will be evaluated, tested, and accepted for delivery to end users. Success in acquiring high-quality software products and services from software suppliers can be achieved by doing the following things: a) Identifying quality characteristics necessary to achieve the acquirer’s objectives b) Selecting suppliers most capable of meeting the acquisition objectives c) Including quality considerations in the planning, evaluation, and acceptance activities d) Developing an organizational strategy for acquiring software e) Establishing a software acquisition process using the eight steps stated in 5.2 as a starting point f) Putting the defined process into practice
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93669
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1734044400 {#93705
      date: 2024-12-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1456441200 {#93704
      date: 2016-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1456441200 {#93698
      date: 2016-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 69
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93699
    #id: 10448
    #code: "IEEE00004411"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039068 {#93706
      date: 2025-06-27 17:44:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93685
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 36801
        #name: "IEEE 1062:2015"
        #slug: "ieee-1062-2015-ieee00004411-242100"
        #description: """
          Revision Standard - Active.<br />\n
          A set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process is described in this recommended practice. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of off-the-shelf (OTS), custom, or free and open source software (FOSS). Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within its acquisition process.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes a set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of commercial-off-the-shelf (COTS), custom, or free and open source software (FOSS). Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within the organization’s acquisition process. Security will be included as a quality attribute considered during the acquisition.<br />\n
          This recommended practice is designed to help organizations and individuals incorporate quality, including security considerations during the definition, evaluation, selection, and acceptance of supplier software for operational use. It will also help determine how supplier software should be evaluated, tested, and accepted for delivery to end users. This recommended practice is intended to satisfy the following objectives: - Promote consistency within organizations in acquiring software from software suppliers. - Provide useful practices on including quality, security, safety and data rights considerations during acquisition planning. - Provide useful practices on evaluating and qualifying supplier capabilities to meet user requirements. - Provide useful practices on evaluating and qualifying supplier software. - Assist individuals or organizations judging the quality of supplier software for referral to end users. - Assist suppliers in understanding how the software will be evaluated, tested, and accepted for delivery to end users. Success in acquiring high-quality software products and services from software suppliers can be achieved by doing the following things: a) Identifying quality characteristics necessary to achieve the acquirer’s objectives b) Selecting suppliers most capable of meeting the acquisition objectives c) Including quality considerations in the planning, evaluation, and acceptance activities d) Developing an organizational strategy for acquiring software e) Establishing a software acquisition process using the eight steps stated in 5.2 as a starting point f) Putting the defined process into practice
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93669
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1734044400 {#93705
      date: 2024-12-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1456441200 {#93704
      date: 2016-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1456441200 {#93698
      date: 2016-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 69
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
]

App\Twig\Components\ProductMostRecent {#106955
  +product: App\Entity\Product\Product {#93699
    #id: 10448
    #code: "IEEE00004411"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039068 {#93706
      date: 2025-06-27 17:44:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93685
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 36801
        #name: "IEEE 1062:2015"
        #slug: "ieee-1062-2015-ieee00004411-242100"
        #description: """
          Revision Standard - Active.<br />\n
          A set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process is described in this recommended practice. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of off-the-shelf (OTS), custom, or free and open source software (FOSS). Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within its acquisition process.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes a set of useful quality considerations that can be selected and applied during one or more steps in a software acquisition process. The recommended practices can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. The software supply chain may include integration of commercial-off-the-shelf (COTS), custom, or free and open source software (FOSS). Each organization or individual using this recommended practice will need to identify the specific quality and activities that need to be included within the organization’s acquisition process. Security will be included as a quality attribute considered during the acquisition.<br />\n
          This recommended practice is designed to help organizations and individuals incorporate quality, including security considerations during the definition, evaluation, selection, and acceptance of supplier software for operational use. It will also help determine how supplier software should be evaluated, tested, and accepted for delivery to end users. This recommended practice is intended to satisfy the following objectives: - Promote consistency within organizations in acquiring software from software suppliers. - Provide useful practices on including quality, security, safety and data rights considerations during acquisition planning. - Provide useful practices on evaluating and qualifying supplier capabilities to meet user requirements. - Provide useful practices on evaluating and qualifying supplier software. - Assist individuals or organizations judging the quality of supplier software for referral to end users. - Assist suppliers in understanding how the software will be evaluated, tested, and accepted for delivery to end users. Success in acquiring high-quality software products and services from software suppliers can be achieved by doing the following things: a) Identifying quality characteristics necessary to achieve the acquirer’s objectives b) Selecting suppliers most capable of meeting the acquisition objectives c) Including quality considerations in the planning, evaluation, and acceptance activities d) Developing an organizational strategy for acquiring software e) Establishing a software acquisition process using the eight steps stated in 5.2 as a starting point f) Putting the defined process into practice
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93669
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1734044400 {#93705
      date: 2024-12-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1456441200 {#93704
      date: 2016-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1456441200 {#93698
      date: 2016-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 69
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106787
    #id: 9069
    #code: "IEEE00001551"
    #attributes: Doctrine\ORM\PersistentCollection {#106804 …}
    #variants: Doctrine\ORM\PersistentCollection {#106801 …}
    #options: Doctrine\ORM\PersistentCollection {#106797 …}
    #associations: Doctrine\ORM\PersistentCollection {#106799 …}
    #createdAt: DateTime @1751037945 {#106828
      date: 2025-06-27 17:25:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106789
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106815 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107022
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106787}
        #id: 31285
        #name: "IEEE 1062:1998"
        #slug: "ieee-1062-1998-ieee00001551-240721"
        #description: """
          Revision Standard - Superseded.<br />\n
          IEEE Std 1062, 1998 Edition (R2002), Includes IEEE Std 1062-1993 and IEEE Std 1062a-1998. A set of useful quality practices that can be selected and applied during one or moresteps in a software acquisition process is described. This recommended practice can be applied tosoftware that runs on any computer system regardless of the size, complexity, or criticality of thesoftware, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process. In this recommended practice, software products have been classfied according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition, 1998 Edition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106812 …}
    #channels: Doctrine\ORM\PersistentCollection {#106806 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106810 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106808 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106822 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106802
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106829
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914886000 {#106833
      date: 1998-12-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 49
    -documents: Doctrine\ORM\PersistentCollection {#106819 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106817 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#107037
  +product: App\Entity\Product\Product {#106787
    #id: 9069
    #code: "IEEE00001551"
    #attributes: Doctrine\ORM\PersistentCollection {#106804 …}
    #variants: Doctrine\ORM\PersistentCollection {#106801 …}
    #options: Doctrine\ORM\PersistentCollection {#106797 …}
    #associations: Doctrine\ORM\PersistentCollection {#106799 …}
    #createdAt: DateTime @1751037945 {#106828
      date: 2025-06-27 17:25:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106789
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106815 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107022
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106787}
        #id: 31285
        #name: "IEEE 1062:1998"
        #slug: "ieee-1062-1998-ieee00001551-240721"
        #description: """
          Revision Standard - Superseded.<br />\n
          IEEE Std 1062, 1998 Edition (R2002), Includes IEEE Std 1062-1993 and IEEE Std 1062a-1998. A set of useful quality practices that can be selected and applied during one or moresteps in a software acquisition process is described. This recommended practice can be applied tosoftware that runs on any computer system regardless of the size, complexity, or criticality of thesoftware, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process. In this recommended practice, software products have been classfied according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition, 1998 Edition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106812 …}
    #channels: Doctrine\ORM\PersistentCollection {#106806 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106810 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106808 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106822 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106802
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106829
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914886000 {#106833
      date: 1998-12-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 49
    -documents: Doctrine\ORM\PersistentCollection {#106819 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106817 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106787
    #id: 9069
    #code: "IEEE00001551"
    #attributes: Doctrine\ORM\PersistentCollection {#106804 …}
    #variants: Doctrine\ORM\PersistentCollection {#106801 …}
    #options: Doctrine\ORM\PersistentCollection {#106797 …}
    #associations: Doctrine\ORM\PersistentCollection {#106799 …}
    #createdAt: DateTime @1751037945 {#106828
      date: 2025-06-27 17:25:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106789
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106815 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107022
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106787}
        #id: 31285
        #name: "IEEE 1062:1998"
        #slug: "ieee-1062-1998-ieee00001551-240721"
        #description: """
          Revision Standard - Superseded.<br />\n
          IEEE Std 1062, 1998 Edition (R2002), Includes IEEE Std 1062-1993 and IEEE Std 1062a-1998. A set of useful quality practices that can be selected and applied during one or moresteps in a software acquisition process is described. This recommended practice can be applied tosoftware that runs on any computer system regardless of the size, complexity, or criticality of thesoftware, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process. In this recommended practice, software products have been classfied according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition, 1998 Edition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106812 …}
    #channels: Doctrine\ORM\PersistentCollection {#106806 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106810 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106808 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106822 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106802
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106829
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914886000 {#106833
      date: 1998-12-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 49
    -documents: Doctrine\ORM\PersistentCollection {#106819 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106817 …}
  }
]

App\Twig\Components\ProductMostRecent {#107089
  +product: App\Entity\Product\Product {#106787
    #id: 9069
    #code: "IEEE00001551"
    #attributes: Doctrine\ORM\PersistentCollection {#106804 …}
    #variants: Doctrine\ORM\PersistentCollection {#106801 …}
    #options: Doctrine\ORM\PersistentCollection {#106797 …}
    #associations: Doctrine\ORM\PersistentCollection {#106799 …}
    #createdAt: DateTime @1751037945 {#106828
      date: 2025-06-27 17:25:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106789
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106815 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107022
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106787}
        #id: 31285
        #name: "IEEE 1062:1998"
        #slug: "ieee-1062-1998-ieee00001551-240721"
        #description: """
          Revision Standard - Superseded.<br />\n
          IEEE Std 1062, 1998 Edition (R2002), Includes IEEE Std 1062-1993 and IEEE Std 1062a-1998. A set of useful quality practices that can be selected and applied during one or moresteps in a software acquisition process is described. This recommended practice can be applied tosoftware that runs on any computer system regardless of the size, complexity, or criticality of thesoftware, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process. In this recommended practice, software products have been classfied according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition, 1998 Edition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106812 …}
    #channels: Doctrine\ORM\PersistentCollection {#106806 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106810 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106808 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106822 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106802
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106829
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914886000 {#106833
      date: 1998-12-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 49
    -documents: Doctrine\ORM\PersistentCollection {#106819 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106817 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9068
    #code: "IEEE00001550"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037944 {#7274
      date: 2025-06-27 17:25:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31281
        #name: "IEEE 1062:1993 (R2002)"
        #slug: "ieee-1062-1993-r2002-ieee00001550-240720"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.<br />\n
          In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item.<br />\n
          Commercial-off-the-shelf (COTS) software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with &quot;how to operate&quot; documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.<br />\n
          Modified-off-the-shelf (MOTS) software is similar to COTS software; however, the MOTS software does<br />\n
          advertise service to tailor the software to acquirer-specific requirements.<br />\n
          Fully developed software will often be unique for a specific application and will be produced on a one-of-akind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).<br />\n
          This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on modified-off-the-shelf software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @723078000 {#7318
      date: 1992-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#107153
  +product: App\Entity\Product\Product {#7311
    #id: 9068
    #code: "IEEE00001550"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037944 {#7274
      date: 2025-06-27 17:25:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31281
        #name: "IEEE 1062:1993 (R2002)"
        #slug: "ieee-1062-1993-r2002-ieee00001550-240720"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.<br />\n
          In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item.<br />\n
          Commercial-off-the-shelf (COTS) software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with &quot;how to operate&quot; documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.<br />\n
          Modified-off-the-shelf (MOTS) software is similar to COTS software; however, the MOTS software does<br />\n
          advertise service to tailor the software to acquirer-specific requirements.<br />\n
          Fully developed software will often be unique for a specific application and will be produced on a one-of-akind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).<br />\n
          This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on modified-off-the-shelf software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @723078000 {#7318
      date: 1992-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9068
    #code: "IEEE00001550"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037944 {#7274
      date: 2025-06-27 17:25:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31281
        #name: "IEEE 1062:1993 (R2002)"
        #slug: "ieee-1062-1993-r2002-ieee00001550-240720"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.<br />\n
          In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item.<br />\n
          Commercial-off-the-shelf (COTS) software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with &quot;how to operate&quot; documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.<br />\n
          Modified-off-the-shelf (MOTS) software is similar to COTS software; however, the MOTS software does<br />\n
          advertise service to tailor the software to acquirer-specific requirements.<br />\n
          Fully developed software will often be unique for a specific application and will be produced on a one-of-akind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).<br />\n
          This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on modified-off-the-shelf software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @723078000 {#7318
      date: 1992-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#107180
  +product: App\Entity\Product\Product {#7311
    #id: 9068
    #code: "IEEE00001550"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037944 {#7274
      date: 2025-06-27 17:25:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31281
        #name: "IEEE 1062:1993 (R2002)"
        #slug: "ieee-1062-1993-r2002-ieee00001550-240720"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 1062-1998. A set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process is described. This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on modified-off-the-shelf software and fully developed software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for performing software acquisitions. It describes a set of useful quality practices that can be selected and applied during one or more steps in a software acquisition process.<br />\n
          In this recommended practice, software products have been classified according to the degree to which the acquirer may specify the features of the software. They are: commercial-of-the-shelf (COTS), modified-off-the-shelf (MOTS), and fully developed item.<br />\n
          Commercial-off-the-shelf (COTS) software is stable and is normally well-defined in terms of documentation and known capabilities and limitations. It usually comes with &quot;how to operate&quot; documentation. COTS software is defined by a market-driven need. It is commercially available and its fitness for use has been demonstrated by a broad spectrum of commercial users. Also, the COTS software supplier does not advertise any willingness to modify the software for a specific customer.<br />\n
          Modified-off-the-shelf (MOTS) software is similar to COTS software; however, the MOTS software does<br />\n
          advertise service to tailor the software to acquirer-specific requirements.<br />\n
          Fully developed software will often be unique for a specific application and will be produced on a one-of-akind or low-volume basis. The software typically will have the potential for future modification by the acquirer to meet changing needs. As a result, most of the documentation will be special to the project (with the exception of the supplier's standard documentation for the operating system, any standard application packages, and programming languages).<br />\n
          This recommended practice can be applied to software that runs on any computer system regardless of the size, complexity, or criticality of the software. However, this recommended practice is more suited for use on modified-off-the-shelf software and fully developed software. Each organization using this recommended practice will need to identify the classes of software to which this recommended practice applies and the specific quality characteristics and activities that need to be included within the acquisition process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Acquisition"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @723078000 {#7318
      date: 1992-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1062"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#128653
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128636 …}
    #variants: Doctrine\ORM\PersistentCollection {#128634 …}
    #options: Doctrine\ORM\PersistentCollection {#128629 …}
    #associations: Doctrine\ORM\PersistentCollection {#128631 …}
    #createdAt: DateTime @1751037622 {#128626
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128661
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128647 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128738
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128653}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128645 …}
    #channels: Doctrine\ORM\PersistentCollection {#128638 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128642 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128640 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128655 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128612
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128660
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128619
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128632
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128651 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128649 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#128709
  +product: App\Entity\Product\Product {#128653
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128636 …}
    #variants: Doctrine\ORM\PersistentCollection {#128634 …}
    #options: Doctrine\ORM\PersistentCollection {#128629 …}
    #associations: Doctrine\ORM\PersistentCollection {#128631 …}
    #createdAt: DateTime @1751037622 {#128626
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128661
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128647 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128738
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128653}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128645 …}
    #channels: Doctrine\ORM\PersistentCollection {#128638 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128642 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128640 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128655 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128612
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128660
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128619
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128632
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128651 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128649 …}
  }
  +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 {#128653
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128636 …}
    #variants: Doctrine\ORM\PersistentCollection {#128634 …}
    #options: Doctrine\ORM\PersistentCollection {#128629 …}
    #associations: Doctrine\ORM\PersistentCollection {#128631 …}
    #createdAt: DateTime @1751037622 {#128626
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128661
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128647 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128738
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128653}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128645 …}
    #channels: Doctrine\ORM\PersistentCollection {#128638 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128642 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128640 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128655 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128612
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128660
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128619
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128632
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128651 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128649 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#128742
  +product: App\Entity\Product\Product {#128653
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128636 …}
    #variants: Doctrine\ORM\PersistentCollection {#128634 …}
    #options: Doctrine\ORM\PersistentCollection {#128629 …}
    #associations: Doctrine\ORM\PersistentCollection {#128631 …}
    #createdAt: DateTime @1751037622 {#128626
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128661
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128647 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128738
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128653}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128645 …}
    #channels: Doctrine\ORM\PersistentCollection {#128638 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128642 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128640 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128655 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128612
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128660
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128619
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128632
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128651 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128649 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#128653
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128636 …}
    #variants: Doctrine\ORM\PersistentCollection {#128634 …}
    #options: Doctrine\ORM\PersistentCollection {#128629 …}
    #associations: Doctrine\ORM\PersistentCollection {#128631 …}
    #createdAt: DateTime @1751037622 {#128626
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128661
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128647 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128738
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128653}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128645 …}
    #channels: Doctrine\ORM\PersistentCollection {#128638 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128642 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128640 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128655 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128612
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128660
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128619
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128632
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128651 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128649 …}
  }
]

App\Twig\Components\ProductMostRecent {#128820
  +product: App\Entity\Product\Product {#128653
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128636 …}
    #variants: Doctrine\ORM\PersistentCollection {#128634 …}
    #options: Doctrine\ORM\PersistentCollection {#128629 …}
    #associations: Doctrine\ORM\PersistentCollection {#128631 …}
    #createdAt: DateTime @1751037622 {#128626
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128661
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128647 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128738
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128653}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128645 …}
    #channels: Doctrine\ORM\PersistentCollection {#128638 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128642 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128640 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128655 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128612
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128660
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128619
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128632
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128651 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128649 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}