Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7519
    #id: 9007
    #code: "IEEE00001467"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037893 {#7536
      date: 2025-06-27 17:24:53.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31037
        #name: "IEEE 1012:1986 (R1992)"
        #slug: "ieee-1012-1986-r1992-ieee00001467-240659"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Uniform and minimum requirements for the format and content of software verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are provided for both critical and noncritical software. For critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are defined. Optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V effort are suggested. An overview of V&amp;V is given, and life-cycle V&amp;V, software V&amp;V reporting, and V&amp;V administrative procedures are covered.<br />\n
          \t\t\t\t<br />\n
          This standard has a threefold purpose:<br />\n
          1) To provide, for both critical and noncritical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs)<br />\n
          2) To define, for critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that shall be included in SVVPsi<br />\n
          3) To suggest optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V<br />\n
          effort This standard requires that an SVVP be written for both critical and noncritical software. Critical software is software in which a failure could have an impact on safety or could cause large financial or social losses.<br />\n
          This SVVP shall include V&amp;V tasks to:<br />\n
          1) Verify that the products of each software life-cycle phase:<br />\n
          a) Comply with previous life-cycle phase requirements and products (for example, for correctness,<br />\n
          completeness, consistency, accuracy)<br />\n
          b) Satisfy the standards, practices, and conventions of the phase<br />\n
          c) Establish the proper basis for initiating the next life-cycle phase activities<br />\n
          2) Validate that the completed end product complies with established software and system requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @532306800 {#7531
      date: 1986-11-14 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @716680800 {#7521
      date: 1992-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#95003
  +product: App\Entity\Product\Product {#7519
    #id: 9007
    #code: "IEEE00001467"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037893 {#7536
      date: 2025-06-27 17:24:53.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31037
        #name: "IEEE 1012:1986 (R1992)"
        #slug: "ieee-1012-1986-r1992-ieee00001467-240659"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Uniform and minimum requirements for the format and content of software verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are provided for both critical and noncritical software. For critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are defined. Optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V effort are suggested. An overview of V&amp;V is given, and life-cycle V&amp;V, software V&amp;V reporting, and V&amp;V administrative procedures are covered.<br />\n
          \t\t\t\t<br />\n
          This standard has a threefold purpose:<br />\n
          1) To provide, for both critical and noncritical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs)<br />\n
          2) To define, for critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that shall be included in SVVPsi<br />\n
          3) To suggest optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V<br />\n
          effort This standard requires that an SVVP be written for both critical and noncritical software. Critical software is software in which a failure could have an impact on safety or could cause large financial or social losses.<br />\n
          This SVVP shall include V&amp;V tasks to:<br />\n
          1) Verify that the products of each software life-cycle phase:<br />\n
          a) Comply with previous life-cycle phase requirements and products (for example, for correctness,<br />\n
          completeness, consistency, accuracy)<br />\n
          b) Satisfy the standards, practices, and conventions of the phase<br />\n
          c) Establish the proper basis for initiating the next life-cycle phase activities<br />\n
          2) Validate that the completed end product complies with established software and system requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @532306800 {#7531
      date: 1986-11-14 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @716680800 {#7521
      date: 1992-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7519
    #id: 9007
    #code: "IEEE00001467"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037893 {#7536
      date: 2025-06-27 17:24:53.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31037
        #name: "IEEE 1012:1986 (R1992)"
        #slug: "ieee-1012-1986-r1992-ieee00001467-240659"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Uniform and minimum requirements for the format and content of software verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are provided for both critical and noncritical software. For critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are defined. Optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V effort are suggested. An overview of V&amp;V is given, and life-cycle V&amp;V, software V&amp;V reporting, and V&amp;V administrative procedures are covered.<br />\n
          \t\t\t\t<br />\n
          This standard has a threefold purpose:<br />\n
          1) To provide, for both critical and noncritical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs)<br />\n
          2) To define, for critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that shall be included in SVVPsi<br />\n
          3) To suggest optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V<br />\n
          effort This standard requires that an SVVP be written for both critical and noncritical software. Critical software is software in which a failure could have an impact on safety or could cause large financial or social losses.<br />\n
          This SVVP shall include V&amp;V tasks to:<br />\n
          1) Verify that the products of each software life-cycle phase:<br />\n
          a) Comply with previous life-cycle phase requirements and products (for example, for correctness,<br />\n
          completeness, consistency, accuracy)<br />\n
          b) Satisfy the standards, practices, and conventions of the phase<br />\n
          c) Establish the proper basis for initiating the next life-cycle phase activities<br />\n
          2) Validate that the completed end product complies with established software and system requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @532306800 {#7531
      date: 1986-11-14 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @716680800 {#7521
      date: 1992-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]

App\Twig\Components\ProductType {#95196
  +product: App\Entity\Product\Product {#7519
    #id: 9007
    #code: "IEEE00001467"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037893 {#7536
      date: 2025-06-27 17:24:53.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31037
        #name: "IEEE 1012:1986 (R1992)"
        #slug: "ieee-1012-1986-r1992-ieee00001467-240659"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Uniform and minimum requirements for the format and content of software verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are provided for both critical and noncritical software. For critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are defined. Optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V effort are suggested. An overview of V&amp;V is given, and life-cycle V&amp;V, software V&amp;V reporting, and V&amp;V administrative procedures are covered.<br />\n
          \t\t\t\t<br />\n
          This standard has a threefold purpose:<br />\n
          1) To provide, for both critical and noncritical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs)<br />\n
          2) To define, for critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that shall be included in SVVPsi<br />\n
          3) To suggest optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V<br />\n
          effort This standard requires that an SVVP be written for both critical and noncritical software. Critical software is software in which a failure could have an impact on safety or could cause large financial or social losses.<br />\n
          This SVVP shall include V&amp;V tasks to:<br />\n
          1) Verify that the products of each software life-cycle phase:<br />\n
          a) Comply with previous life-cycle phase requirements and products (for example, for correctness,<br />\n
          completeness, consistency, accuracy)<br />\n
          b) Satisfy the standards, practices, and conventions of the phase<br />\n
          c) Establish the proper basis for initiating the next life-cycle phase activities<br />\n
          2) Validate that the completed end product complies with established software and system requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @532306800 {#7531
      date: 1986-11-14 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @716680800 {#7521
      date: 1992-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7519
    #id: 9007
    #code: "IEEE00001467"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037893 {#7536
      date: 2025-06-27 17:24:53.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31037
        #name: "IEEE 1012:1986 (R1992)"
        #slug: "ieee-1012-1986-r1992-ieee00001467-240659"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Uniform and minimum requirements for the format and content of software verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are provided for both critical and noncritical software. For critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are defined. Optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V effort are suggested. An overview of V&amp;V is given, and life-cycle V&amp;V, software V&amp;V reporting, and V&amp;V administrative procedures are covered.<br />\n
          \t\t\t\t<br />\n
          This standard has a threefold purpose:<br />\n
          1) To provide, for both critical and noncritical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs)<br />\n
          2) To define, for critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that shall be included in SVVPsi<br />\n
          3) To suggest optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V<br />\n
          effort This standard requires that an SVVP be written for both critical and noncritical software. Critical software is software in which a failure could have an impact on safety or could cause large financial or social losses.<br />\n
          This SVVP shall include V&amp;V tasks to:<br />\n
          1) Verify that the products of each software life-cycle phase:<br />\n
          a) Comply with previous life-cycle phase requirements and products (for example, for correctness,<br />\n
          completeness, consistency, accuracy)<br />\n
          b) Satisfy the standards, practices, and conventions of the phase<br />\n
          c) Establish the proper basis for initiating the next life-cycle phase activities<br />\n
          2) Validate that the completed end product complies with established software and system requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @532306800 {#7531
      date: 1986-11-14 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @716680800 {#7521
      date: 1992-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]

App\Twig\Components\ProductMostRecent {#95271
  +product: App\Entity\Product\Product {#7519
    #id: 9007
    #code: "IEEE00001467"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037893 {#7536
      date: 2025-06-27 17:24:53.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31037
        #name: "IEEE 1012:1986 (R1992)"
        #slug: "ieee-1012-1986-r1992-ieee00001467-240659"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Uniform and minimum requirements for the format and content of software verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are provided for both critical and noncritical software. For critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are defined. Optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V effort are suggested. An overview of V&amp;V is given, and life-cycle V&amp;V, software V&amp;V reporting, and V&amp;V administrative procedures are covered.<br />\n
          \t\t\t\t<br />\n
          This standard has a threefold purpose:<br />\n
          1) To provide, for both critical and noncritical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs)<br />\n
          2) To define, for critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that shall be included in SVVPsi<br />\n
          3) To suggest optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V<br />\n
          effort This standard requires that an SVVP be written for both critical and noncritical software. Critical software is software in which a failure could have an impact on safety or could cause large financial or social losses.<br />\n
          This SVVP shall include V&amp;V tasks to:<br />\n
          1) Verify that the products of each software life-cycle phase:<br />\n
          a) Comply with previous life-cycle phase requirements and products (for example, for correctness,<br />\n
          completeness, consistency, accuracy)<br />\n
          b) Satisfy the standards, practices, and conventions of the phase<br />\n
          c) Establish the proper basis for initiating the next life-cycle phase activities<br />\n
          2) Validate that the completed end product complies with established software and system requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @532306800 {#7531
      date: 1986-11-14 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @716680800 {#7521
      date: 1992-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95694
    #id: 12249
    #code: "IEEE00007324"
    #attributes: Doctrine\ORM\PersistentCollection {#95674 …}
    #variants: Doctrine\ORM\PersistentCollection {#95671 …}
    #options: Doctrine\ORM\PersistentCollection {#95667 …}
    #associations: Doctrine\ORM\PersistentCollection {#95663 …}
    #createdAt: DateTime @1751040298 {#95701
      date: 2025-06-27 18:04:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95680
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95685 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95726
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95694}
        #id: 44005
        #name: "IEEE P1012"
        #slug: "ieee-p1012-ieee00007324-243902"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          Verification and validation 1 (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused [legacy, commercial off-the-shelf (COTS), non-developmental items]. The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes related information or documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of product<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system, software, and hardware life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes.<br />\n
          The purpose of this standard is to: - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes. - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process. - Identify the minimum V&amp;V tasks corresponding to a four-level integrity schema. - Define the content of the Verification and Validation Plan.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for System, Software, and Hardware Verification and Validation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95683 …}
    #channels: Doctrine\ORM\PersistentCollection {#95676 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95681 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95678 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95691 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95664
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#95700
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1745964000 {#95699
      date: 2025-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: DateTime @1745964000 {#95693
      date: 2025-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 324
    -documents: Doctrine\ORM\PersistentCollection {#95689 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95687 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#108999
  +product: App\Entity\Product\Product {#95694
    #id: 12249
    #code: "IEEE00007324"
    #attributes: Doctrine\ORM\PersistentCollection {#95674 …}
    #variants: Doctrine\ORM\PersistentCollection {#95671 …}
    #options: Doctrine\ORM\PersistentCollection {#95667 …}
    #associations: Doctrine\ORM\PersistentCollection {#95663 …}
    #createdAt: DateTime @1751040298 {#95701
      date: 2025-06-27 18:04:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95680
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95685 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95726
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95694}
        #id: 44005
        #name: "IEEE P1012"
        #slug: "ieee-p1012-ieee00007324-243902"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          Verification and validation 1 (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused [legacy, commercial off-the-shelf (COTS), non-developmental items]. The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes related information or documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of product<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system, software, and hardware life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes.<br />\n
          The purpose of this standard is to: - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes. - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process. - Identify the minimum V&amp;V tasks corresponding to a four-level integrity schema. - Define the content of the Verification and Validation Plan.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for System, Software, and Hardware Verification and Validation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95683 …}
    #channels: Doctrine\ORM\PersistentCollection {#95676 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95681 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95678 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95691 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95664
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#95700
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1745964000 {#95699
      date: 2025-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: DateTime @1745964000 {#95693
      date: 2025-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 324
    -documents: Doctrine\ORM\PersistentCollection {#95689 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95687 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95694
    #id: 12249
    #code: "IEEE00007324"
    #attributes: Doctrine\ORM\PersistentCollection {#95674 …}
    #variants: Doctrine\ORM\PersistentCollection {#95671 …}
    #options: Doctrine\ORM\PersistentCollection {#95667 …}
    #associations: Doctrine\ORM\PersistentCollection {#95663 …}
    #createdAt: DateTime @1751040298 {#95701
      date: 2025-06-27 18:04:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95680
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95685 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95726
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95694}
        #id: 44005
        #name: "IEEE P1012"
        #slug: "ieee-p1012-ieee00007324-243902"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          Verification and validation 1 (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused [legacy, commercial off-the-shelf (COTS), non-developmental items]. The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes related information or documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of product<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system, software, and hardware life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes.<br />\n
          The purpose of this standard is to: - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes. - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process. - Identify the minimum V&amp;V tasks corresponding to a four-level integrity schema. - Define the content of the Verification and Validation Plan.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for System, Software, and Hardware Verification and Validation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95683 …}
    #channels: Doctrine\ORM\PersistentCollection {#95676 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95681 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95678 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95691 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95664
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#95700
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1745964000 {#95699
      date: 2025-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: DateTime @1745964000 {#95693
      date: 2025-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 324
    -documents: Doctrine\ORM\PersistentCollection {#95689 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95687 …}
  }
]

App\Twig\Components\ProductMostRecent {#109066
  +product: App\Entity\Product\Product {#95694
    #id: 12249
    #code: "IEEE00007324"
    #attributes: Doctrine\ORM\PersistentCollection {#95674 …}
    #variants: Doctrine\ORM\PersistentCollection {#95671 …}
    #options: Doctrine\ORM\PersistentCollection {#95667 …}
    #associations: Doctrine\ORM\PersistentCollection {#95663 …}
    #createdAt: DateTime @1751040298 {#95701
      date: 2025-06-27 18:04:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95680
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95685 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95726
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95694}
        #id: 44005
        #name: "IEEE P1012"
        #slug: "ieee-p1012-ieee00007324-243902"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          Verification and validation 1 (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused [legacy, commercial off-the-shelf (COTS), non-developmental items]. The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes related information or documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of product<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system, software, and hardware life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes.<br />\n
          The purpose of this standard is to: - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes. - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process. - Identify the minimum V&amp;V tasks corresponding to a four-level integrity schema. - Define the content of the Verification and Validation Plan.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for System, Software, and Hardware Verification and Validation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95683 …}
    #channels: Doctrine\ORM\PersistentCollection {#95676 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95681 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95678 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95691 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95664
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#95700
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1745964000 {#95699
      date: 2025-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: DateTime @1745964000 {#95693
      date: 2025-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 324
    -documents: Doctrine\ORM\PersistentCollection {#95689 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95687 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108782
    #id: 11127
    #code: "IEEE00005609"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751039496 {#108823
      date: 2025-06-27 17:51:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#108784
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108810 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109141
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108782}
        #id: 39517
        #name: "IEEE 1012:2016"
        #slug: "ieee-1012-2016-ieee00005609-242779"
        #description: """
          Revision Standard - Active.<br />\n
          Verification and validation (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused (legacy, commercial off-the-shelf [COTS], non-developmental items). The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of products.<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system, software, and hardware life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes.<br />\n
          The purpose of this standard is to:<br />\n
          - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes.<br />\n
          - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process.<br />\n
          - Identify the minimum V&amp;V tasks corresponding to a four-level integrity schema.<br />\n
          - Define the content of the Verification and Validation Plan.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for System, Software, and Hardware Verification and Validation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108817 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108797
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#108824
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1506636000 {#108828
      date: 2017-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 260
    -documents: Doctrine\ORM\PersistentCollection {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#109156
  +product: App\Entity\Product\Product {#108782
    #id: 11127
    #code: "IEEE00005609"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751039496 {#108823
      date: 2025-06-27 17:51:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#108784
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108810 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109141
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108782}
        #id: 39517
        #name: "IEEE 1012:2016"
        #slug: "ieee-1012-2016-ieee00005609-242779"
        #description: """
          Revision Standard - Active.<br />\n
          Verification and validation (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused (legacy, commercial off-the-shelf [COTS], non-developmental items). The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of products.<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system, software, and hardware life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes.<br />\n
          The purpose of this standard is to:<br />\n
          - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes.<br />\n
          - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process.<br />\n
          - Identify the minimum V&amp;V tasks corresponding to a four-level integrity schema.<br />\n
          - Define the content of the Verification and Validation Plan.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for System, Software, and Hardware Verification and Validation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108817 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108797
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#108824
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1506636000 {#108828
      date: 2017-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 260
    -documents: Doctrine\ORM\PersistentCollection {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108782
    #id: 11127
    #code: "IEEE00005609"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751039496 {#108823
      date: 2025-06-27 17:51:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#108784
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108810 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109141
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108782}
        #id: 39517
        #name: "IEEE 1012:2016"
        #slug: "ieee-1012-2016-ieee00005609-242779"
        #description: """
          Revision Standard - Active.<br />\n
          Verification and validation (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused (legacy, commercial off-the-shelf [COTS], non-developmental items). The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of products.<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system, software, and hardware life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes.<br />\n
          The purpose of this standard is to:<br />\n
          - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes.<br />\n
          - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process.<br />\n
          - Identify the minimum V&amp;V tasks corresponding to a four-level integrity schema.<br />\n
          - Define the content of the Verification and Validation Plan.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for System, Software, and Hardware Verification and Validation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108817 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108797
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#108824
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1506636000 {#108828
      date: 2017-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 260
    -documents: Doctrine\ORM\PersistentCollection {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
]

App\Twig\Components\ProductMostRecent {#109208
  +product: App\Entity\Product\Product {#108782
    #id: 11127
    #code: "IEEE00005609"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751039496 {#108823
      date: 2025-06-27 17:51:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#108784
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108810 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109141
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108782}
        #id: 39517
        #name: "IEEE 1012:2016"
        #slug: "ieee-1012-2016-ieee00005609-242779"
        #description: """
          Revision Standard - Active.<br />\n
          Verification and validation (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused (legacy, commercial off-the-shelf [COTS], non-developmental items). The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of products.<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system, software, and hardware life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes.<br />\n
          The purpose of this standard is to:<br />\n
          - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes.<br />\n
          - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process.<br />\n
          - Identify the minimum V&amp;V tasks corresponding to a four-level integrity schema.<br />\n
          - Define the content of the Verification and Validation Plan.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for System, Software, and Hardware Verification and Validation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108817 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108797
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#108824
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1506636000 {#108828
      date: 2017-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 260
    -documents: Doctrine\ORM\PersistentCollection {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108785
    #id: 10263
    #code: "IEEE00004021"
    #attributes: Doctrine\ORM\PersistentCollection {#108851 …}
    #variants: Doctrine\ORM\PersistentCollection {#108843 …}
    #options: Doctrine\ORM\PersistentCollection {#108848 …}
    #associations: Doctrine\ORM\PersistentCollection {#108849 …}
    #createdAt: DateTime @1751038948 {#108789
      date: 2025-06-27 17:42:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#108788
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108866 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109278
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108785}
        #id: 36061
        #name: "IEEE 1012:2012"
        #slug: "ieee-1012-2012-ieee00004021-241915"
        #description: """
          Revision Standard - Superseded.<br />\n
          Verification and validation (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused [legacy, commercial off-the-shelf (COTS), non developmental items]. The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of products.<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system and software life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes<br />\n
          The purpose of the standard is to perform the following:<br />\n
          - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes<br />\n
          - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for System and Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108861 …}
    #channels: Doctrine\ORM\PersistentCollection {#108857 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108852 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108858 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108859 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108787
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108786
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1337896800 {#108780
      date: 2012-05-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 223
    -documents: Doctrine\ORM\PersistentCollection {#108846 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108827 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#109293
  +product: App\Entity\Product\Product {#108785
    #id: 10263
    #code: "IEEE00004021"
    #attributes: Doctrine\ORM\PersistentCollection {#108851 …}
    #variants: Doctrine\ORM\PersistentCollection {#108843 …}
    #options: Doctrine\ORM\PersistentCollection {#108848 …}
    #associations: Doctrine\ORM\PersistentCollection {#108849 …}
    #createdAt: DateTime @1751038948 {#108789
      date: 2025-06-27 17:42:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#108788
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108866 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109278
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108785}
        #id: 36061
        #name: "IEEE 1012:2012"
        #slug: "ieee-1012-2012-ieee00004021-241915"
        #description: """
          Revision Standard - Superseded.<br />\n
          Verification and validation (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused [legacy, commercial off-the-shelf (COTS), non developmental items]. The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of products.<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system and software life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes<br />\n
          The purpose of the standard is to perform the following:<br />\n
          - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes<br />\n
          - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for System and Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108861 …}
    #channels: Doctrine\ORM\PersistentCollection {#108857 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108852 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108858 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108859 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108787
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108786
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1337896800 {#108780
      date: 2012-05-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 223
    -documents: Doctrine\ORM\PersistentCollection {#108846 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108827 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108785
    #id: 10263
    #code: "IEEE00004021"
    #attributes: Doctrine\ORM\PersistentCollection {#108851 …}
    #variants: Doctrine\ORM\PersistentCollection {#108843 …}
    #options: Doctrine\ORM\PersistentCollection {#108848 …}
    #associations: Doctrine\ORM\PersistentCollection {#108849 …}
    #createdAt: DateTime @1751038948 {#108789
      date: 2025-06-27 17:42:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#108788
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108866 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109278
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108785}
        #id: 36061
        #name: "IEEE 1012:2012"
        #slug: "ieee-1012-2012-ieee00004021-241915"
        #description: """
          Revision Standard - Superseded.<br />\n
          Verification and validation (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused [legacy, commercial off-the-shelf (COTS), non developmental items]. The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of products.<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system and software life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes<br />\n
          The purpose of the standard is to perform the following:<br />\n
          - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes<br />\n
          - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for System and Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108861 …}
    #channels: Doctrine\ORM\PersistentCollection {#108857 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108852 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108858 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108859 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108787
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108786
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1337896800 {#108780
      date: 2012-05-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 223
    -documents: Doctrine\ORM\PersistentCollection {#108846 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108827 …}
  }
]

App\Twig\Components\ProductMostRecent {#109345
  +product: App\Entity\Product\Product {#108785
    #id: 10263
    #code: "IEEE00004021"
    #attributes: Doctrine\ORM\PersistentCollection {#108851 …}
    #variants: Doctrine\ORM\PersistentCollection {#108843 …}
    #options: Doctrine\ORM\PersistentCollection {#108848 …}
    #associations: Doctrine\ORM\PersistentCollection {#108849 …}
    #createdAt: DateTime @1751038948 {#108789
      date: 2025-06-27 17:42:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#108788
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108866 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109278
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108785}
        #id: 36061
        #name: "IEEE 1012:2012"
        #slug: "ieee-1012-2012-ieee00004021-241915"
        #description: """
          Revision Standard - Superseded.<br />\n
          Verification and validation (V&amp;V) processes are used to determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. V&amp;V life cycle process requirements are specified for different integrity levels. The scope of V&amp;V processes encompasses systems, software, and hardware, and it includes their interfaces. This standard applies to systems, software, and hardware being developed, maintained, or reused [legacy, commercial off-the-shelf (COTS), non developmental items]. The term software also includes firmware and microcode, and each of the terms system, software, and hardware includes documentation. V&amp;V processes include the analysis, evaluation, review, inspection, assessment, and testing of products.<br />\n
          \t\t\t\t<br />\n
          This verification and validation (V&amp;V) standard is a process standard that addresses all system and software life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups. This standard is compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle models use all of the processes listed in this standard. V&amp;V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs. This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes<br />\n
          The purpose of the standard is to perform the following:<br />\n
          - Establish a common framework of the V&amp;V processes, activities, and tasks in support of all system, software, and hardware life cycle processes<br />\n
          - Define the V&amp;V tasks, required inputs, and required outputs in each life cycle process
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for System and Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108861 …}
    #channels: Doctrine\ORM\PersistentCollection {#108857 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108852 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108858 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108859 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108787
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108786
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1337896800 {#108780
      date: 2012-05-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 223
    -documents: Doctrine\ORM\PersistentCollection {#108846 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108827 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108838
    #id: 10017
    #code: "IEEE00003450"
    #attributes: Doctrine\ORM\PersistentCollection {#108877 …}
    #variants: Doctrine\ORM\PersistentCollection {#108879 …}
    #options: Doctrine\ORM\PersistentCollection {#108883 …}
    #associations: Doctrine\ORM\PersistentCollection {#108881 …}
    #createdAt: DateTime @1751038749 {#108842
      date: 2025-06-27 17:39:09.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#108841
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108863 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109411
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108838}
        #id: 35077
        #name: "IEEE 1012:2004"
        #slug: "ieee-1012-2004-ieee00003450-241669"
        #description: """
          Revision Standard - Superseded.<br />\n
          Software verification and validation (V&amp;V) processes determine whether the development products of a given activity conform to the requirements of that activity and whether the software satisfies its intended use and user needs. Software V&amp;V life cycle process requirements are specified for different software integrity levels. The scope of V&amp;V processes encompasses software-based systems, computer software, hardware, and interfaces. This standard applies to software being developed, maintained, or reused [legacy, commercial off-the-shelf(COTS), non-developmental items]. The term software also includes firmware, microcode,and documentation. Software V&amp;V processes include analysis, evaluation, review, inspection,assessment, and testing of software products.<br />\n
          \t\t\t\t<br />\n
          The scope of the proposed project does not change from the original scope of the standard. Software V&amp;V is an technical discipline of the systems engineering process. IEEE Std 1012-1986 was a product standard defining the contents of the Software V&amp;V Plan. IEEE Std 1012-1998 was a process standard defining the verification and validation processes in terms of specific activities and tasks. This proposed project will retain the standard as a process standard and will revise and update the definition of the activities and tasks to be consistent with industry usage. The updates are contained to selected sections and the project is scheduled to complete its work in a year with balloting in early 2004.<br />\n
          The purpose is to correct duplication detected during its usage over the past 5 years, make all references consistent with revised standards (IEEE and ISO), and incorporate user changes detected during operational use of the standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108869 …}
    #channels: Doctrine\ORM\PersistentCollection {#108875 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108871 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108873 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108839 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108834
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108835
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1118181600 {#108840
      date: 2005-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#108833 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108831 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#109426
  +product: App\Entity\Product\Product {#108838
    #id: 10017
    #code: "IEEE00003450"
    #attributes: Doctrine\ORM\PersistentCollection {#108877 …}
    #variants: Doctrine\ORM\PersistentCollection {#108879 …}
    #options: Doctrine\ORM\PersistentCollection {#108883 …}
    #associations: Doctrine\ORM\PersistentCollection {#108881 …}
    #createdAt: DateTime @1751038749 {#108842
      date: 2025-06-27 17:39:09.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#108841
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108863 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109411
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108838}
        #id: 35077
        #name: "IEEE 1012:2004"
        #slug: "ieee-1012-2004-ieee00003450-241669"
        #description: """
          Revision Standard - Superseded.<br />\n
          Software verification and validation (V&amp;V) processes determine whether the development products of a given activity conform to the requirements of that activity and whether the software satisfies its intended use and user needs. Software V&amp;V life cycle process requirements are specified for different software integrity levels. The scope of V&amp;V processes encompasses software-based systems, computer software, hardware, and interfaces. This standard applies to software being developed, maintained, or reused [legacy, commercial off-the-shelf(COTS), non-developmental items]. The term software also includes firmware, microcode,and documentation. Software V&amp;V processes include analysis, evaluation, review, inspection,assessment, and testing of software products.<br />\n
          \t\t\t\t<br />\n
          The scope of the proposed project does not change from the original scope of the standard. Software V&amp;V is an technical discipline of the systems engineering process. IEEE Std 1012-1986 was a product standard defining the contents of the Software V&amp;V Plan. IEEE Std 1012-1998 was a process standard defining the verification and validation processes in terms of specific activities and tasks. This proposed project will retain the standard as a process standard and will revise and update the definition of the activities and tasks to be consistent with industry usage. The updates are contained to selected sections and the project is scheduled to complete its work in a year with balloting in early 2004.<br />\n
          The purpose is to correct duplication detected during its usage over the past 5 years, make all references consistent with revised standards (IEEE and ISO), and incorporate user changes detected during operational use of the standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108869 …}
    #channels: Doctrine\ORM\PersistentCollection {#108875 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108871 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108873 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108839 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108834
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108835
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1118181600 {#108840
      date: 2005-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#108833 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108831 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108838
    #id: 10017
    #code: "IEEE00003450"
    #attributes: Doctrine\ORM\PersistentCollection {#108877 …}
    #variants: Doctrine\ORM\PersistentCollection {#108879 …}
    #options: Doctrine\ORM\PersistentCollection {#108883 …}
    #associations: Doctrine\ORM\PersistentCollection {#108881 …}
    #createdAt: DateTime @1751038749 {#108842
      date: 2025-06-27 17:39:09.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#108841
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108863 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109411
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108838}
        #id: 35077
        #name: "IEEE 1012:2004"
        #slug: "ieee-1012-2004-ieee00003450-241669"
        #description: """
          Revision Standard - Superseded.<br />\n
          Software verification and validation (V&amp;V) processes determine whether the development products of a given activity conform to the requirements of that activity and whether the software satisfies its intended use and user needs. Software V&amp;V life cycle process requirements are specified for different software integrity levels. The scope of V&amp;V processes encompasses software-based systems, computer software, hardware, and interfaces. This standard applies to software being developed, maintained, or reused [legacy, commercial off-the-shelf(COTS), non-developmental items]. The term software also includes firmware, microcode,and documentation. Software V&amp;V processes include analysis, evaluation, review, inspection,assessment, and testing of software products.<br />\n
          \t\t\t\t<br />\n
          The scope of the proposed project does not change from the original scope of the standard. Software V&amp;V is an technical discipline of the systems engineering process. IEEE Std 1012-1986 was a product standard defining the contents of the Software V&amp;V Plan. IEEE Std 1012-1998 was a process standard defining the verification and validation processes in terms of specific activities and tasks. This proposed project will retain the standard as a process standard and will revise and update the definition of the activities and tasks to be consistent with industry usage. The updates are contained to selected sections and the project is scheduled to complete its work in a year with balloting in early 2004.<br />\n
          The purpose is to correct duplication detected during its usage over the past 5 years, make all references consistent with revised standards (IEEE and ISO), and incorporate user changes detected during operational use of the standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108869 …}
    #channels: Doctrine\ORM\PersistentCollection {#108875 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108871 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108873 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108839 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108834
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108835
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1118181600 {#108840
      date: 2005-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#108833 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108831 …}
  }
]

App\Twig\Components\ProductMostRecent {#109478
  +product: App\Entity\Product\Product {#108838
    #id: 10017
    #code: "IEEE00003450"
    #attributes: Doctrine\ORM\PersistentCollection {#108877 …}
    #variants: Doctrine\ORM\PersistentCollection {#108879 …}
    #options: Doctrine\ORM\PersistentCollection {#108883 …}
    #associations: Doctrine\ORM\PersistentCollection {#108881 …}
    #createdAt: DateTime @1751038749 {#108842
      date: 2025-06-27 17:39:09.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#108841
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108863 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109411
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108838}
        #id: 35077
        #name: "IEEE 1012:2004"
        #slug: "ieee-1012-2004-ieee00003450-241669"
        #description: """
          Revision Standard - Superseded.<br />\n
          Software verification and validation (V&amp;V) processes determine whether the development products of a given activity conform to the requirements of that activity and whether the software satisfies its intended use and user needs. Software V&amp;V life cycle process requirements are specified for different software integrity levels. The scope of V&amp;V processes encompasses software-based systems, computer software, hardware, and interfaces. This standard applies to software being developed, maintained, or reused [legacy, commercial off-the-shelf(COTS), non-developmental items]. The term software also includes firmware, microcode,and documentation. Software V&amp;V processes include analysis, evaluation, review, inspection,assessment, and testing of software products.<br />\n
          \t\t\t\t<br />\n
          The scope of the proposed project does not change from the original scope of the standard. Software V&amp;V is an technical discipline of the systems engineering process. IEEE Std 1012-1986 was a product standard defining the contents of the Software V&amp;V Plan. IEEE Std 1012-1998 was a process standard defining the verification and validation processes in terms of specific activities and tasks. This proposed project will retain the standard as a process standard and will revise and update the definition of the activities and tasks to be consistent with industry usage. The updates are contained to selected sections and the project is scheduled to complete its work in a year with balloting in early 2004.<br />\n
          The purpose is to correct duplication detected during its usage over the past 5 years, make all references consistent with revised standards (IEEE and ISO), and incorporate user changes detected during operational use of the standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108869 …}
    #channels: Doctrine\ORM\PersistentCollection {#108875 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108871 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108873 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108839 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108834
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108835
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1118181600 {#108840
      date: 2005-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#108833 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108831 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108890
    #id: 9009
    #code: "IEEE00001469"
    #attributes: Doctrine\ORM\PersistentCollection {#108907 …}
    #variants: Doctrine\ORM\PersistentCollection {#108909 …}
    #options: Doctrine\ORM\PersistentCollection {#108913 …}
    #associations: Doctrine\ORM\PersistentCollection {#108911 …}
    #createdAt: DateTime @1751037895 {#108885
      date: 2025-06-27 17:24:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108886
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108897 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109544
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108890}
        #id: 31045
        #name: "IEEE 1012a:1998"
        #slug: "ieee-1012a-1998-ieee00001469-240661"
        #description: """
          Amendment Standard - Superseded.<br />\n
          The relationship between the two sets of requirements on plans for verification and validation of software, found in IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997, is explained so that users may produce documents that comply with both standards.<br />\n
          \t\t\t\t<br />\n
          To establish a correlation between the content of software V&amp;V plans as defined in 1012 and the content of such plans as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace contenct between submect documentation.<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation - Content Map to IEEE 12207.1"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108899 …}
    #channels: Doctrine\ORM\PersistentCollection {#108905 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108901 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108903 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108891 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108887
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108888
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914194800 {#108889
      date: 1998-12-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 13
    -documents: Doctrine\ORM\PersistentCollection {#108893 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108895 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#109559
  +product: App\Entity\Product\Product {#108890
    #id: 9009
    #code: "IEEE00001469"
    #attributes: Doctrine\ORM\PersistentCollection {#108907 …}
    #variants: Doctrine\ORM\PersistentCollection {#108909 …}
    #options: Doctrine\ORM\PersistentCollection {#108913 …}
    #associations: Doctrine\ORM\PersistentCollection {#108911 …}
    #createdAt: DateTime @1751037895 {#108885
      date: 2025-06-27 17:24:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108886
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108897 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109544
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108890}
        #id: 31045
        #name: "IEEE 1012a:1998"
        #slug: "ieee-1012a-1998-ieee00001469-240661"
        #description: """
          Amendment Standard - Superseded.<br />\n
          The relationship between the two sets of requirements on plans for verification and validation of software, found in IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997, is explained so that users may produce documents that comply with both standards.<br />\n
          \t\t\t\t<br />\n
          To establish a correlation between the content of software V&amp;V plans as defined in 1012 and the content of such plans as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace contenct between submect documentation.<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation - Content Map to IEEE 12207.1"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108899 …}
    #channels: Doctrine\ORM\PersistentCollection {#108905 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108901 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108903 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108891 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108887
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108888
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914194800 {#108889
      date: 1998-12-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 13
    -documents: Doctrine\ORM\PersistentCollection {#108893 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108895 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108890
    #id: 9009
    #code: "IEEE00001469"
    #attributes: Doctrine\ORM\PersistentCollection {#108907 …}
    #variants: Doctrine\ORM\PersistentCollection {#108909 …}
    #options: Doctrine\ORM\PersistentCollection {#108913 …}
    #associations: Doctrine\ORM\PersistentCollection {#108911 …}
    #createdAt: DateTime @1751037895 {#108885
      date: 2025-06-27 17:24:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108886
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108897 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109544
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108890}
        #id: 31045
        #name: "IEEE 1012a:1998"
        #slug: "ieee-1012a-1998-ieee00001469-240661"
        #description: """
          Amendment Standard - Superseded.<br />\n
          The relationship between the two sets of requirements on plans for verification and validation of software, found in IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997, is explained so that users may produce documents that comply with both standards.<br />\n
          \t\t\t\t<br />\n
          To establish a correlation between the content of software V&amp;V plans as defined in 1012 and the content of such plans as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace contenct between submect documentation.<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation - Content Map to IEEE 12207.1"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108899 …}
    #channels: Doctrine\ORM\PersistentCollection {#108905 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108901 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108903 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108891 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108887
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108888
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914194800 {#108889
      date: 1998-12-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 13
    -documents: Doctrine\ORM\PersistentCollection {#108893 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108895 …}
  }
]

App\Twig\Components\ProductMostRecent {#109611
  +product: App\Entity\Product\Product {#108890
    #id: 9009
    #code: "IEEE00001469"
    #attributes: Doctrine\ORM\PersistentCollection {#108907 …}
    #variants: Doctrine\ORM\PersistentCollection {#108909 …}
    #options: Doctrine\ORM\PersistentCollection {#108913 …}
    #associations: Doctrine\ORM\PersistentCollection {#108911 …}
    #createdAt: DateTime @1751037895 {#108885
      date: 2025-06-27 17:24:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108886
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108897 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109544
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108890}
        #id: 31045
        #name: "IEEE 1012a:1998"
        #slug: "ieee-1012a-1998-ieee00001469-240661"
        #description: """
          Amendment Standard - Superseded.<br />\n
          The relationship between the two sets of requirements on plans for verification and validation of software, found in IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997, is explained so that users may produce documents that comply with both standards.<br />\n
          \t\t\t\t<br />\n
          To establish a correlation between the content of software V&amp;V plans as defined in 1012 and the content of such plans as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace contenct between submect documentation.<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation - Content Map to IEEE 12207.1"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108899 …}
    #channels: Doctrine\ORM\PersistentCollection {#108905 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108901 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108903 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108891 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108887
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108888
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914194800 {#108889
      date: 1998-12-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 13
    -documents: Doctrine\ORM\PersistentCollection {#108893 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108895 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108920
    #id: 9008
    #code: "IEEE00001468"
    #attributes: Doctrine\ORM\PersistentCollection {#108937 …}
    #variants: Doctrine\ORM\PersistentCollection {#108939 …}
    #options: Doctrine\ORM\PersistentCollection {#108943 …}
    #associations: Doctrine\ORM\PersistentCollection {#108941 …}
    #createdAt: DateTime @1751037894 {#108915
      date: 2025-06-27 17:24:54.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#108916
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108927 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109681
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108920}
        #id: 31041
        #name: "IEEE 1012:1998"
        #slug: "ieee-1012-1998-ieee00001468-240660"
        #description: """
          Revision Standard - Superseded.<br />\n
          Software verification and validation (V&amp;V) processes, which determine whether development products of a given activity conform to the requirements of that activity, and whether the software satisfies its intended use and user needs, are described. This determination may include analysis, evaluation, review, inspection, assessment, and testing of software products and processes. V&amp;V processes assess the software in the context of the system, including the operational environment, hardware, interfacing software, operators, and users.<br />\n
          \t\t\t\t<br />\n
          Expand the scope of the standard to include the use of software integrity levels as applied to software V&amp;V, minimum V&amp;V activities and tasks associated with each integrity level, V&amp;V of reusable software, definition of independent V&amp;V and V&amp;V metrics.<br />\n
          To clarify the use of terminology in the document, incorporate lessons learned during field experience of users, and clarify definition of V&amp;V processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108929 …}
    #channels: Doctrine\ORM\PersistentCollection {#108935 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108931 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108933 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108921 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108917
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108918
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @900885600 {#108919
      date: 1998-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 80
    -documents: Doctrine\ORM\PersistentCollection {#108923 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108925 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#109696
  +product: App\Entity\Product\Product {#108920
    #id: 9008
    #code: "IEEE00001468"
    #attributes: Doctrine\ORM\PersistentCollection {#108937 …}
    #variants: Doctrine\ORM\PersistentCollection {#108939 …}
    #options: Doctrine\ORM\PersistentCollection {#108943 …}
    #associations: Doctrine\ORM\PersistentCollection {#108941 …}
    #createdAt: DateTime @1751037894 {#108915
      date: 2025-06-27 17:24:54.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#108916
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108927 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109681
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108920}
        #id: 31041
        #name: "IEEE 1012:1998"
        #slug: "ieee-1012-1998-ieee00001468-240660"
        #description: """
          Revision Standard - Superseded.<br />\n
          Software verification and validation (V&amp;V) processes, which determine whether development products of a given activity conform to the requirements of that activity, and whether the software satisfies its intended use and user needs, are described. This determination may include analysis, evaluation, review, inspection, assessment, and testing of software products and processes. V&amp;V processes assess the software in the context of the system, including the operational environment, hardware, interfacing software, operators, and users.<br />\n
          \t\t\t\t<br />\n
          Expand the scope of the standard to include the use of software integrity levels as applied to software V&amp;V, minimum V&amp;V activities and tasks associated with each integrity level, V&amp;V of reusable software, definition of independent V&amp;V and V&amp;V metrics.<br />\n
          To clarify the use of terminology in the document, incorporate lessons learned during field experience of users, and clarify definition of V&amp;V processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108929 …}
    #channels: Doctrine\ORM\PersistentCollection {#108935 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108931 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108933 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108921 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108917
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108918
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @900885600 {#108919
      date: 1998-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 80
    -documents: Doctrine\ORM\PersistentCollection {#108923 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108925 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108920
    #id: 9008
    #code: "IEEE00001468"
    #attributes: Doctrine\ORM\PersistentCollection {#108937 …}
    #variants: Doctrine\ORM\PersistentCollection {#108939 …}
    #options: Doctrine\ORM\PersistentCollection {#108943 …}
    #associations: Doctrine\ORM\PersistentCollection {#108941 …}
    #createdAt: DateTime @1751037894 {#108915
      date: 2025-06-27 17:24:54.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#108916
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108927 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109681
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108920}
        #id: 31041
        #name: "IEEE 1012:1998"
        #slug: "ieee-1012-1998-ieee00001468-240660"
        #description: """
          Revision Standard - Superseded.<br />\n
          Software verification and validation (V&amp;V) processes, which determine whether development products of a given activity conform to the requirements of that activity, and whether the software satisfies its intended use and user needs, are described. This determination may include analysis, evaluation, review, inspection, assessment, and testing of software products and processes. V&amp;V processes assess the software in the context of the system, including the operational environment, hardware, interfacing software, operators, and users.<br />\n
          \t\t\t\t<br />\n
          Expand the scope of the standard to include the use of software integrity levels as applied to software V&amp;V, minimum V&amp;V activities and tasks associated with each integrity level, V&amp;V of reusable software, definition of independent V&amp;V and V&amp;V metrics.<br />\n
          To clarify the use of terminology in the document, incorporate lessons learned during field experience of users, and clarify definition of V&amp;V processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108929 …}
    #channels: Doctrine\ORM\PersistentCollection {#108935 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108931 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108933 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108921 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108917
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108918
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @900885600 {#108919
      date: 1998-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 80
    -documents: Doctrine\ORM\PersistentCollection {#108923 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108925 …}
  }
]

App\Twig\Components\ProductMostRecent {#109748
  +product: App\Entity\Product\Product {#108920
    #id: 9008
    #code: "IEEE00001468"
    #attributes: Doctrine\ORM\PersistentCollection {#108937 …}
    #variants: Doctrine\ORM\PersistentCollection {#108939 …}
    #options: Doctrine\ORM\PersistentCollection {#108943 …}
    #associations: Doctrine\ORM\PersistentCollection {#108941 …}
    #createdAt: DateTime @1751037894 {#108915
      date: 2025-06-27 17:24:54.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#108916
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108927 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109681
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108920}
        #id: 31041
        #name: "IEEE 1012:1998"
        #slug: "ieee-1012-1998-ieee00001468-240660"
        #description: """
          Revision Standard - Superseded.<br />\n
          Software verification and validation (V&amp;V) processes, which determine whether development products of a given activity conform to the requirements of that activity, and whether the software satisfies its intended use and user needs, are described. This determination may include analysis, evaluation, review, inspection, assessment, and testing of software products and processes. V&amp;V processes assess the software in the context of the system, including the operational environment, hardware, interfacing software, operators, and users.<br />\n
          \t\t\t\t<br />\n
          Expand the scope of the standard to include the use of software integrity levels as applied to software V&amp;V, minimum V&amp;V activities and tasks associated with each integrity level, V&amp;V of reusable software, definition of independent V&amp;V and V&amp;V metrics.<br />\n
          To clarify the use of terminology in the document, incorporate lessons learned during field experience of users, and clarify definition of V&amp;V processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#108929 …}
    #channels: Doctrine\ORM\PersistentCollection {#108935 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108931 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108933 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108921 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108917
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108918
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @900885600 {#108919
      date: 1998-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 80
    -documents: Doctrine\ORM\PersistentCollection {#108923 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108925 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7519
    #id: 9007
    #code: "IEEE00001467"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037893 {#7536
      date: 2025-06-27 17:24:53.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31037
        #name: "IEEE 1012:1986 (R1992)"
        #slug: "ieee-1012-1986-r1992-ieee00001467-240659"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Uniform and minimum requirements for the format and content of software verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are provided for both critical and noncritical software. For critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are defined. Optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V effort are suggested. An overview of V&amp;V is given, and life-cycle V&amp;V, software V&amp;V reporting, and V&amp;V administrative procedures are covered.<br />\n
          \t\t\t\t<br />\n
          This standard has a threefold purpose:<br />\n
          1) To provide, for both critical and noncritical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs)<br />\n
          2) To define, for critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that shall be included in SVVPsi<br />\n
          3) To suggest optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V<br />\n
          effort This standard requires that an SVVP be written for both critical and noncritical software. Critical software is software in which a failure could have an impact on safety or could cause large financial or social losses.<br />\n
          This SVVP shall include V&amp;V tasks to:<br />\n
          1) Verify that the products of each software life-cycle phase:<br />\n
          a) Comply with previous life-cycle phase requirements and products (for example, for correctness,<br />\n
          completeness, consistency, accuracy)<br />\n
          b) Satisfy the standards, practices, and conventions of the phase<br />\n
          c) Establish the proper basis for initiating the next life-cycle phase activities<br />\n
          2) Validate that the completed end product complies with established software and system requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @532306800 {#7531
      date: 1986-11-14 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @716680800 {#7521
      date: 1992-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#109812
  +product: App\Entity\Product\Product {#7519
    #id: 9007
    #code: "IEEE00001467"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037893 {#7536
      date: 2025-06-27 17:24:53.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31037
        #name: "IEEE 1012:1986 (R1992)"
        #slug: "ieee-1012-1986-r1992-ieee00001467-240659"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Uniform and minimum requirements for the format and content of software verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are provided for both critical and noncritical software. For critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are defined. Optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V effort are suggested. An overview of V&amp;V is given, and life-cycle V&amp;V, software V&amp;V reporting, and V&amp;V administrative procedures are covered.<br />\n
          \t\t\t\t<br />\n
          This standard has a threefold purpose:<br />\n
          1) To provide, for both critical and noncritical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs)<br />\n
          2) To define, for critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that shall be included in SVVPsi<br />\n
          3) To suggest optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V<br />\n
          effort This standard requires that an SVVP be written for both critical and noncritical software. Critical software is software in which a failure could have an impact on safety or could cause large financial or social losses.<br />\n
          This SVVP shall include V&amp;V tasks to:<br />\n
          1) Verify that the products of each software life-cycle phase:<br />\n
          a) Comply with previous life-cycle phase requirements and products (for example, for correctness,<br />\n
          completeness, consistency, accuracy)<br />\n
          b) Satisfy the standards, practices, and conventions of the phase<br />\n
          c) Establish the proper basis for initiating the next life-cycle phase activities<br />\n
          2) Validate that the completed end product complies with established software and system requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @532306800 {#7531
      date: 1986-11-14 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @716680800 {#7521
      date: 1992-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7519
    #id: 9007
    #code: "IEEE00001467"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037893 {#7536
      date: 2025-06-27 17:24:53.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31037
        #name: "IEEE 1012:1986 (R1992)"
        #slug: "ieee-1012-1986-r1992-ieee00001467-240659"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Uniform and minimum requirements for the format and content of software verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are provided for both critical and noncritical software. For critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that are to be included in SVVPs are defined. Optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V effort are suggested. An overview of V&amp;V is given, and life-cycle V&amp;V, software V&amp;V reporting, and V&amp;V administrative procedures are covered.<br />\n
          \t\t\t\t<br />\n
          This standard has a threefold purpose:<br />\n
          1) To provide, for both critical and noncritical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs)<br />\n
          2) To define, for critical software, specific minimum verification and validation (V&amp;V) tasks and their required inputs and outputs that shall be included in SVVPsi<br />\n
          3) To suggest optional V&amp;V tasks to be used to tailor SVVPs as appropriate for the particular V&amp;V<br />\n
          effort This standard requires that an SVVP be written for both critical and noncritical software. Critical software is software in which a failure could have an impact on safety or could cause large financial or social losses.<br />\n
          This SVVP shall include V&amp;V tasks to:<br />\n
          1) Verify that the products of each software life-cycle phase:<br />\n
          a) Comply with previous life-cycle phase requirements and products (for example, for correctness,<br />\n
          completeness, consistency, accuracy)<br />\n
          b) Satisfy the standards, practices, and conventions of the phase<br />\n
          c) Establish the proper basis for initiating the next life-cycle phase activities<br />\n
          2) Validate that the completed end product complies with established software and system requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Verification and Validation Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @532306800 {#7531
      date: 1986-11-14 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @716680800 {#7521
      date: 1992-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1012"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]