Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9038
    #code: "IEEE00001502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037919 {#7274
      date: 2025-06-27 17:25:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31161
        #name: "IEEE 1028:1998 (R2002)"
        #slug: "ieee-1028-1998-r2002-ieee00001502-240690"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n
          Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @883609200 {#7318
      date: 1998-01-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#93008
  +product: App\Entity\Product\Product {#7311
    #id: 9038
    #code: "IEEE00001502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037919 {#7274
      date: 2025-06-27 17:25:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31161
        #name: "IEEE 1028:1998 (R2002)"
        #slug: "ieee-1028-1998-r2002-ieee00001502-240690"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n
          Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @883609200 {#7318
      date: 1998-01-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9038
    #code: "IEEE00001502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037919 {#7274
      date: 2025-06-27 17:25:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31161
        #name: "IEEE 1028:1998 (R2002)"
        #slug: "ieee-1028-1998-r2002-ieee00001502-240690"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n
          Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @883609200 {#7318
      date: 1998-01-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductType {#93201
  +product: App\Entity\Product\Product {#7311
    #id: 9038
    #code: "IEEE00001502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037919 {#7274
      date: 2025-06-27 17:25:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31161
        #name: "IEEE 1028:1998 (R2002)"
        #slug: "ieee-1028-1998-r2002-ieee00001502-240690"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n
          Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @883609200 {#7318
      date: 1998-01-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9038
    #code: "IEEE00001502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037919 {#7274
      date: 2025-06-27 17:25:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31161
        #name: "IEEE 1028:1998 (R2002)"
        #slug: "ieee-1028-1998-r2002-ieee00001502-240690"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n
          Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @883609200 {#7318
      date: 1998-01-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#93276
  +product: App\Entity\Product\Product {#7311
    #id: 9038
    #code: "IEEE00001502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037919 {#7274
      date: 2025-06-27 17:25:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31161
        #name: "IEEE 1028:1998 (R2002)"
        #slug: "ieee-1028-1998-r2002-ieee00001502-240690"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n
          Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @883609200 {#7318
      date: 1998-01-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106828
    #id: 9037
    #code: "IEEE00001501"
    #attributes: Doctrine\ORM\PersistentCollection {#106809 …}
    #variants: Doctrine\ORM\PersistentCollection {#106806 …}
    #options: Doctrine\ORM\PersistentCollection {#106802 …}
    #associations: Doctrine\ORM\PersistentCollection {#106804 …}
    #createdAt: DateTime @1751037918 {#106835
      date: 2025-06-27 17:25:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106808
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106819 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106858
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106828}
        #id: 31157
        #name: "IEEE 1028:1988 (R1993)"
        #slug: "ieee-1028-1988-r1993-ieee00001501-240689"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Definitions and uniform procedures for review and audit applicable to both critical and noncritical software are provided. The processes include management review, technical review, software inspection, walkthrough, and audit. The processes defined are applicable throughout the software life cycle.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide definitions and uniform requirements for review and audit processes. It does not establish the need to conduct specific reviews or audits; that need is defined by local policy. Where specific reviews and audits are required, standard procedures for their execution must be defined. This standard provides such definition for review and audit processes that are applicable to products and processes throughout the software life cycle. Each organization shall specify where and when this standard applies and any intended deviations from this standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Software Reviews and Audits"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106817 …}
    #channels: Doctrine\ORM\PersistentCollection {#106811 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106815 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106813 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106826 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106834
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @615160800 {#106833
      date: 1989-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106827
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106824 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106822 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106842
  +product: App\Entity\Product\Product {#106828
    #id: 9037
    #code: "IEEE00001501"
    #attributes: Doctrine\ORM\PersistentCollection {#106809 …}
    #variants: Doctrine\ORM\PersistentCollection {#106806 …}
    #options: Doctrine\ORM\PersistentCollection {#106802 …}
    #associations: Doctrine\ORM\PersistentCollection {#106804 …}
    #createdAt: DateTime @1751037918 {#106835
      date: 2025-06-27 17:25:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106808
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106819 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106858
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106828}
        #id: 31157
        #name: "IEEE 1028:1988 (R1993)"
        #slug: "ieee-1028-1988-r1993-ieee00001501-240689"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Definitions and uniform procedures for review and audit applicable to both critical and noncritical software are provided. The processes include management review, technical review, software inspection, walkthrough, and audit. The processes defined are applicable throughout the software life cycle.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide definitions and uniform requirements for review and audit processes. It does not establish the need to conduct specific reviews or audits; that need is defined by local policy. Where specific reviews and audits are required, standard procedures for their execution must be defined. This standard provides such definition for review and audit processes that are applicable to products and processes throughout the software life cycle. Each organization shall specify where and when this standard applies and any intended deviations from this standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Software Reviews and Audits"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106817 …}
    #channels: Doctrine\ORM\PersistentCollection {#106811 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106815 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106813 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106826 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106834
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @615160800 {#106833
      date: 1989-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106827
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106824 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106822 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106828
    #id: 9037
    #code: "IEEE00001501"
    #attributes: Doctrine\ORM\PersistentCollection {#106809 …}
    #variants: Doctrine\ORM\PersistentCollection {#106806 …}
    #options: Doctrine\ORM\PersistentCollection {#106802 …}
    #associations: Doctrine\ORM\PersistentCollection {#106804 …}
    #createdAt: DateTime @1751037918 {#106835
      date: 2025-06-27 17:25:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106808
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106819 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106858
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106828}
        #id: 31157
        #name: "IEEE 1028:1988 (R1993)"
        #slug: "ieee-1028-1988-r1993-ieee00001501-240689"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Definitions and uniform procedures for review and audit applicable to both critical and noncritical software are provided. The processes include management review, technical review, software inspection, walkthrough, and audit. The processes defined are applicable throughout the software life cycle.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide definitions and uniform requirements for review and audit processes. It does not establish the need to conduct specific reviews or audits; that need is defined by local policy. Where specific reviews and audits are required, standard procedures for their execution must be defined. This standard provides such definition for review and audit processes that are applicable to products and processes throughout the software life cycle. Each organization shall specify where and when this standard applies and any intended deviations from this standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Software Reviews and Audits"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106817 …}
    #channels: Doctrine\ORM\PersistentCollection {#106811 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106815 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106813 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106826 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106834
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @615160800 {#106833
      date: 1989-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106827
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106824 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106822 …}
  }
]

App\Twig\Components\ProductMostRecent {#106943
  +product: App\Entity\Product\Product {#106828
    #id: 9037
    #code: "IEEE00001501"
    #attributes: Doctrine\ORM\PersistentCollection {#106809 …}
    #variants: Doctrine\ORM\PersistentCollection {#106806 …}
    #options: Doctrine\ORM\PersistentCollection {#106802 …}
    #associations: Doctrine\ORM\PersistentCollection {#106804 …}
    #createdAt: DateTime @1751037918 {#106835
      date: 2025-06-27 17:25:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106808
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106819 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106858
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106828}
        #id: 31157
        #name: "IEEE 1028:1988 (R1993)"
        #slug: "ieee-1028-1988-r1993-ieee00001501-240689"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Definitions and uniform procedures for review and audit applicable to both critical and noncritical software are provided. The processes include management review, technical review, software inspection, walkthrough, and audit. The processes defined are applicable throughout the software life cycle.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide definitions and uniform requirements for review and audit processes. It does not establish the need to conduct specific reviews or audits; that need is defined by local policy. Where specific reviews and audits are required, standard procedures for their execution must be defined. This standard provides such definition for review and audit processes that are applicable to products and processes throughout the software life cycle. Each organization shall specify where and when this standard applies and any intended deviations from this standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Software Reviews and Audits"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106817 …}
    #channels: Doctrine\ORM\PersistentCollection {#106811 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106815 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106813 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106826 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106834
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @615160800 {#106833
      date: 1989-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106827
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106824 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106822 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93699
    #id: 10442
    #code: "IEEE00004402"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039064 {#93706
      date: 2025-06-27 17:44:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#93685
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 36777
        #name: "IEEE 1028:2008"
        #slug: "ieee-1028-2008-ieee00004402-242094"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Five types of software reviews and audits, together with procedures required for the execution of each type, are defined in this standard. This standard is concerned only with the reviews and audits; procedures for determining the necessity of a review or audit are not defined, and the disposition of the results of the review or audit is not specified. Types included are management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum acceptable requirements for systematic software reviews, where “systematic” includes the following attributes:<br />\n
          -- Team participation<br />\n
          -- Documented results of the review<br />\n
          -- Documented procedures for conducting the review<br />\n
          Reviews that do not meet the requirements of this standard are considered to be non-systematic reviews. The standard is not intended to discourage or prohibit the use of non-systematic reviews.<br />\n
          The definitions, requirements, and procedures for the following five types of reviews are included within this standard:<br />\n
          a) Management reviews<br />\n
          b) Technical reviews<br />\n
          c) Inspections<br />\n
          d) Walk-throughs<br />\n
          e) Audits<br />\n
          This standard does not establish the need to conduct specific reviews; that need is defined by other software engineering standards or by local procedures. This standard provides definitions, requirements, and procedures that are applicable to the reviews of software development products throughout the software life cycle. Users of this standard shall specify where and when this standard applies and any intended deviations from this standard.<br />\n
          This standard may be used with other software engineering standards that determine the products to be reviewed, the timing of reviews, and the necessity of reviews. This standard is closely aligned with IEEE Std 1012-2004 [B6], but it can also be used with IEEE Std 1074-2006 [B11], IEEE Std 730-2002 [B2], IEEE Std 12207-2008 [B15], and other standards. A useful model is to consider IEEE Std 1028-2008 as a subroutine to the other standards. Thus, if IEEE Std 1012-2004 [B6] were used to carry out the verification and validation process, the procedure in IEEE Std 1012-2004 [B6] could be followed until such time as instructions to carry out a specific review are encountered. At that point, IEEE Std 1028-2008 would be “called” to carry out the review, using the specific review type described herein. Once the review has been completed, IEEE Std 1012-2004 [B6] would be “returned to” for disposition of the results of the review and any additional action required by IEEE Std 1012-2004 [B6].<br />\n
          This standard may also be used as a stand-alone definition of software review and audit procedures. In this case, local management must determine the events that precede and follow the actual software reviews and audits.<br />\n
          In this model, requirements and quality attributes for the software product are “parameter inputs” to the review and are imposed by the “caller.” When the review is finished, the review outputs are “returned” to the “caller” for action. Review outputs typically include anomaly lists and action item lists; the resolution of the anomalies and action items are the responsibility of the “caller.”<br />\n
          The purpose of this standard is to define systematic reviews and audits applicable to software acquisition, supply, development, operation, and maintenance. This standard describes how to carry out a review. Other standards or local management define the context within which a review is performed, and the use made of the results of the review. Software reviews can be used in support of the objectives of project management, system engineering (for example, functional allocation between hardware and software), verification and validation, configuration management, quality assurance and auditing. Different types of reviews reflect differences in the goals of each review type. Systematic reviews are described by their defined procedures, scope, and objectives.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews and Audits"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93669
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1579820400 {#93705
      date: 2020-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1218751200 {#93704
      date: 2008-08-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#93698
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 53
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113411
  +product: App\Entity\Product\Product {#93699
    #id: 10442
    #code: "IEEE00004402"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039064 {#93706
      date: 2025-06-27 17:44:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#93685
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 36777
        #name: "IEEE 1028:2008"
        #slug: "ieee-1028-2008-ieee00004402-242094"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Five types of software reviews and audits, together with procedures required for the execution of each type, are defined in this standard. This standard is concerned only with the reviews and audits; procedures for determining the necessity of a review or audit are not defined, and the disposition of the results of the review or audit is not specified. Types included are management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum acceptable requirements for systematic software reviews, where “systematic” includes the following attributes:<br />\n
          -- Team participation<br />\n
          -- Documented results of the review<br />\n
          -- Documented procedures for conducting the review<br />\n
          Reviews that do not meet the requirements of this standard are considered to be non-systematic reviews. The standard is not intended to discourage or prohibit the use of non-systematic reviews.<br />\n
          The definitions, requirements, and procedures for the following five types of reviews are included within this standard:<br />\n
          a) Management reviews<br />\n
          b) Technical reviews<br />\n
          c) Inspections<br />\n
          d) Walk-throughs<br />\n
          e) Audits<br />\n
          This standard does not establish the need to conduct specific reviews; that need is defined by other software engineering standards or by local procedures. This standard provides definitions, requirements, and procedures that are applicable to the reviews of software development products throughout the software life cycle. Users of this standard shall specify where and when this standard applies and any intended deviations from this standard.<br />\n
          This standard may be used with other software engineering standards that determine the products to be reviewed, the timing of reviews, and the necessity of reviews. This standard is closely aligned with IEEE Std 1012-2004 [B6], but it can also be used with IEEE Std 1074-2006 [B11], IEEE Std 730-2002 [B2], IEEE Std 12207-2008 [B15], and other standards. A useful model is to consider IEEE Std 1028-2008 as a subroutine to the other standards. Thus, if IEEE Std 1012-2004 [B6] were used to carry out the verification and validation process, the procedure in IEEE Std 1012-2004 [B6] could be followed until such time as instructions to carry out a specific review are encountered. At that point, IEEE Std 1028-2008 would be “called” to carry out the review, using the specific review type described herein. Once the review has been completed, IEEE Std 1012-2004 [B6] would be “returned to” for disposition of the results of the review and any additional action required by IEEE Std 1012-2004 [B6].<br />\n
          This standard may also be used as a stand-alone definition of software review and audit procedures. In this case, local management must determine the events that precede and follow the actual software reviews and audits.<br />\n
          In this model, requirements and quality attributes for the software product are “parameter inputs” to the review and are imposed by the “caller.” When the review is finished, the review outputs are “returned” to the “caller” for action. Review outputs typically include anomaly lists and action item lists; the resolution of the anomalies and action items are the responsibility of the “caller.”<br />\n
          The purpose of this standard is to define systematic reviews and audits applicable to software acquisition, supply, development, operation, and maintenance. This standard describes how to carry out a review. Other standards or local management define the context within which a review is performed, and the use made of the results of the review. Software reviews can be used in support of the objectives of project management, system engineering (for example, functional allocation between hardware and software), verification and validation, configuration management, quality assurance and auditing. Different types of reviews reflect differences in the goals of each review type. Systematic reviews are described by their defined procedures, scope, and objectives.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews and Audits"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93669
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1579820400 {#93705
      date: 2020-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1218751200 {#93704
      date: 2008-08-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#93698
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 53
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93699
    #id: 10442
    #code: "IEEE00004402"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039064 {#93706
      date: 2025-06-27 17:44:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#93685
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 36777
        #name: "IEEE 1028:2008"
        #slug: "ieee-1028-2008-ieee00004402-242094"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Five types of software reviews and audits, together with procedures required for the execution of each type, are defined in this standard. This standard is concerned only with the reviews and audits; procedures for determining the necessity of a review or audit are not defined, and the disposition of the results of the review or audit is not specified. Types included are management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum acceptable requirements for systematic software reviews, where “systematic” includes the following attributes:<br />\n
          -- Team participation<br />\n
          -- Documented results of the review<br />\n
          -- Documented procedures for conducting the review<br />\n
          Reviews that do not meet the requirements of this standard are considered to be non-systematic reviews. The standard is not intended to discourage or prohibit the use of non-systematic reviews.<br />\n
          The definitions, requirements, and procedures for the following five types of reviews are included within this standard:<br />\n
          a) Management reviews<br />\n
          b) Technical reviews<br />\n
          c) Inspections<br />\n
          d) Walk-throughs<br />\n
          e) Audits<br />\n
          This standard does not establish the need to conduct specific reviews; that need is defined by other software engineering standards or by local procedures. This standard provides definitions, requirements, and procedures that are applicable to the reviews of software development products throughout the software life cycle. Users of this standard shall specify where and when this standard applies and any intended deviations from this standard.<br />\n
          This standard may be used with other software engineering standards that determine the products to be reviewed, the timing of reviews, and the necessity of reviews. This standard is closely aligned with IEEE Std 1012-2004 [B6], but it can also be used with IEEE Std 1074-2006 [B11], IEEE Std 730-2002 [B2], IEEE Std 12207-2008 [B15], and other standards. A useful model is to consider IEEE Std 1028-2008 as a subroutine to the other standards. Thus, if IEEE Std 1012-2004 [B6] were used to carry out the verification and validation process, the procedure in IEEE Std 1012-2004 [B6] could be followed until such time as instructions to carry out a specific review are encountered. At that point, IEEE Std 1028-2008 would be “called” to carry out the review, using the specific review type described herein. Once the review has been completed, IEEE Std 1012-2004 [B6] would be “returned to” for disposition of the results of the review and any additional action required by IEEE Std 1012-2004 [B6].<br />\n
          This standard may also be used as a stand-alone definition of software review and audit procedures. In this case, local management must determine the events that precede and follow the actual software reviews and audits.<br />\n
          In this model, requirements and quality attributes for the software product are “parameter inputs” to the review and are imposed by the “caller.” When the review is finished, the review outputs are “returned” to the “caller” for action. Review outputs typically include anomaly lists and action item lists; the resolution of the anomalies and action items are the responsibility of the “caller.”<br />\n
          The purpose of this standard is to define systematic reviews and audits applicable to software acquisition, supply, development, operation, and maintenance. This standard describes how to carry out a review. Other standards or local management define the context within which a review is performed, and the use made of the results of the review. Software reviews can be used in support of the objectives of project management, system engineering (for example, functional allocation between hardware and software), verification and validation, configuration management, quality assurance and auditing. Different types of reviews reflect differences in the goals of each review type. Systematic reviews are described by their defined procedures, scope, and objectives.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews and Audits"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93669
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1579820400 {#93705
      date: 2020-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1218751200 {#93704
      date: 2008-08-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#93698
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 53
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
]

App\Twig\Components\ProductMostRecent {#113478
  +product: App\Entity\Product\Product {#93699
    #id: 10442
    #code: "IEEE00004402"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039064 {#93706
      date: 2025-06-27 17:44:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#93685
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 36777
        #name: "IEEE 1028:2008"
        #slug: "ieee-1028-2008-ieee00004402-242094"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Five types of software reviews and audits, together with procedures required for the execution of each type, are defined in this standard. This standard is concerned only with the reviews and audits; procedures for determining the necessity of a review or audit are not defined, and the disposition of the results of the review or audit is not specified. Types included are management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum acceptable requirements for systematic software reviews, where “systematic” includes the following attributes:<br />\n
          -- Team participation<br />\n
          -- Documented results of the review<br />\n
          -- Documented procedures for conducting the review<br />\n
          Reviews that do not meet the requirements of this standard are considered to be non-systematic reviews. The standard is not intended to discourage or prohibit the use of non-systematic reviews.<br />\n
          The definitions, requirements, and procedures for the following five types of reviews are included within this standard:<br />\n
          a) Management reviews<br />\n
          b) Technical reviews<br />\n
          c) Inspections<br />\n
          d) Walk-throughs<br />\n
          e) Audits<br />\n
          This standard does not establish the need to conduct specific reviews; that need is defined by other software engineering standards or by local procedures. This standard provides definitions, requirements, and procedures that are applicable to the reviews of software development products throughout the software life cycle. Users of this standard shall specify where and when this standard applies and any intended deviations from this standard.<br />\n
          This standard may be used with other software engineering standards that determine the products to be reviewed, the timing of reviews, and the necessity of reviews. This standard is closely aligned with IEEE Std 1012-2004 [B6], but it can also be used with IEEE Std 1074-2006 [B11], IEEE Std 730-2002 [B2], IEEE Std 12207-2008 [B15], and other standards. A useful model is to consider IEEE Std 1028-2008 as a subroutine to the other standards. Thus, if IEEE Std 1012-2004 [B6] were used to carry out the verification and validation process, the procedure in IEEE Std 1012-2004 [B6] could be followed until such time as instructions to carry out a specific review are encountered. At that point, IEEE Std 1028-2008 would be “called” to carry out the review, using the specific review type described herein. Once the review has been completed, IEEE Std 1012-2004 [B6] would be “returned to” for disposition of the results of the review and any additional action required by IEEE Std 1012-2004 [B6].<br />\n
          This standard may also be used as a stand-alone definition of software review and audit procedures. In this case, local management must determine the events that precede and follow the actual software reviews and audits.<br />\n
          In this model, requirements and quality attributes for the software product are “parameter inputs” to the review and are imposed by the “caller.” When the review is finished, the review outputs are “returned” to the “caller” for action. Review outputs typically include anomaly lists and action item lists; the resolution of the anomalies and action items are the responsibility of the “caller.”<br />\n
          The purpose of this standard is to define systematic reviews and audits applicable to software acquisition, supply, development, operation, and maintenance. This standard describes how to carry out a review. Other standards or local management define the context within which a review is performed, and the use made of the results of the review. Software reviews can be used in support of the objectives of project management, system engineering (for example, functional allocation between hardware and software), verification and validation, configuration management, quality assurance and auditing. Different types of reviews reflect differences in the goals of each review type. Systematic reviews are described by their defined procedures, scope, and objectives.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews and Audits"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93669
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1579820400 {#93705
      date: 2020-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1218751200 {#93704
      date: 2008-08-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#93698
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 53
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9038
    #code: "IEEE00001502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037919 {#7274
      date: 2025-06-27 17:25:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31161
        #name: "IEEE 1028:1998 (R2002)"
        #slug: "ieee-1028-1998-r2002-ieee00001502-240690"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n
          Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @883609200 {#7318
      date: 1998-01-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113543
  +product: App\Entity\Product\Product {#7311
    #id: 9038
    #code: "IEEE00001502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037919 {#7274
      date: 2025-06-27 17:25:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31161
        #name: "IEEE 1028:1998 (R2002)"
        #slug: "ieee-1028-1998-r2002-ieee00001502-240690"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n
          Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @883609200 {#7318
      date: 1998-01-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9038
    #code: "IEEE00001502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037919 {#7274
      date: 2025-06-27 17:25:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31161
        #name: "IEEE 1028:1998 (R2002)"
        #slug: "ieee-1028-1998-r2002-ieee00001502-240690"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n
          Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @883609200 {#7318
      date: 1998-01-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#113570
  +product: App\Entity\Product\Product {#7311
    #id: 9038
    #code: "IEEE00001502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037919 {#7274
      date: 2025-06-27 17:25:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31161
        #name: "IEEE 1028:1998 (R2002)"
        #slug: "ieee-1028-1998-r2002-ieee00001502-240690"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n
          \t\t\t\t<br />\n
          Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n
          Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Reviews"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @883609200 {#7318
      date: 1998-01-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106828
    #id: 9037
    #code: "IEEE00001501"
    #attributes: Doctrine\ORM\PersistentCollection {#106809 …}
    #variants: Doctrine\ORM\PersistentCollection {#106806 …}
    #options: Doctrine\ORM\PersistentCollection {#106802 …}
    #associations: Doctrine\ORM\PersistentCollection {#106804 …}
    #createdAt: DateTime @1751037918 {#106835
      date: 2025-06-27 17:25:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106808
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106819 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106858
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106828}
        #id: 31157
        #name: "IEEE 1028:1988 (R1993)"
        #slug: "ieee-1028-1988-r1993-ieee00001501-240689"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Definitions and uniform procedures for review and audit applicable to both critical and noncritical software are provided. The processes include management review, technical review, software inspection, walkthrough, and audit. The processes defined are applicable throughout the software life cycle.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide definitions and uniform requirements for review and audit processes. It does not establish the need to conduct specific reviews or audits; that need is defined by local policy. Where specific reviews and audits are required, standard procedures for their execution must be defined. This standard provides such definition for review and audit processes that are applicable to products and processes throughout the software life cycle. Each organization shall specify where and when this standard applies and any intended deviations from this standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Software Reviews and Audits"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106817 …}
    #channels: Doctrine\ORM\PersistentCollection {#106811 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106815 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106813 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106826 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106834
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @615160800 {#106833
      date: 1989-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106827
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106824 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106822 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113634
  +product: App\Entity\Product\Product {#106828
    #id: 9037
    #code: "IEEE00001501"
    #attributes: Doctrine\ORM\PersistentCollection {#106809 …}
    #variants: Doctrine\ORM\PersistentCollection {#106806 …}
    #options: Doctrine\ORM\PersistentCollection {#106802 …}
    #associations: Doctrine\ORM\PersistentCollection {#106804 …}
    #createdAt: DateTime @1751037918 {#106835
      date: 2025-06-27 17:25:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106808
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106819 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106858
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106828}
        #id: 31157
        #name: "IEEE 1028:1988 (R1993)"
        #slug: "ieee-1028-1988-r1993-ieee00001501-240689"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Definitions and uniform procedures for review and audit applicable to both critical and noncritical software are provided. The processes include management review, technical review, software inspection, walkthrough, and audit. The processes defined are applicable throughout the software life cycle.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide definitions and uniform requirements for review and audit processes. It does not establish the need to conduct specific reviews or audits; that need is defined by local policy. Where specific reviews and audits are required, standard procedures for their execution must be defined. This standard provides such definition for review and audit processes that are applicable to products and processes throughout the software life cycle. Each organization shall specify where and when this standard applies and any intended deviations from this standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Software Reviews and Audits"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106817 …}
    #channels: Doctrine\ORM\PersistentCollection {#106811 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106815 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106813 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106826 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106834
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @615160800 {#106833
      date: 1989-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106827
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106824 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106822 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106828
    #id: 9037
    #code: "IEEE00001501"
    #attributes: Doctrine\ORM\PersistentCollection {#106809 …}
    #variants: Doctrine\ORM\PersistentCollection {#106806 …}
    #options: Doctrine\ORM\PersistentCollection {#106802 …}
    #associations: Doctrine\ORM\PersistentCollection {#106804 …}
    #createdAt: DateTime @1751037918 {#106835
      date: 2025-06-27 17:25:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106808
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106819 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106858
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106828}
        #id: 31157
        #name: "IEEE 1028:1988 (R1993)"
        #slug: "ieee-1028-1988-r1993-ieee00001501-240689"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Definitions and uniform procedures for review and audit applicable to both critical and noncritical software are provided. The processes include management review, technical review, software inspection, walkthrough, and audit. The processes defined are applicable throughout the software life cycle.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide definitions and uniform requirements for review and audit processes. It does not establish the need to conduct specific reviews or audits; that need is defined by local policy. Where specific reviews and audits are required, standard procedures for their execution must be defined. This standard provides such definition for review and audit processes that are applicable to products and processes throughout the software life cycle. Each organization shall specify where and when this standard applies and any intended deviations from this standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Software Reviews and Audits"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106817 …}
    #channels: Doctrine\ORM\PersistentCollection {#106811 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106815 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106813 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106826 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106834
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @615160800 {#106833
      date: 1989-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106827
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106824 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106822 …}
  }
]

App\Twig\Components\ProductMostRecent {#113661
  +product: App\Entity\Product\Product {#106828
    #id: 9037
    #code: "IEEE00001501"
    #attributes: Doctrine\ORM\PersistentCollection {#106809 …}
    #variants: Doctrine\ORM\PersistentCollection {#106806 …}
    #options: Doctrine\ORM\PersistentCollection {#106802 …}
    #associations: Doctrine\ORM\PersistentCollection {#106804 …}
    #createdAt: DateTime @1751037918 {#106835
      date: 2025-06-27 17:25:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106808
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106819 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106858
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106828}
        #id: 31157
        #name: "IEEE 1028:1988 (R1993)"
        #slug: "ieee-1028-1988-r1993-ieee00001501-240689"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Definitions and uniform procedures for review and audit applicable to both critical and noncritical software are provided. The processes include management review, technical review, software inspection, walkthrough, and audit. The processes defined are applicable throughout the software life cycle.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide definitions and uniform requirements for review and audit processes. It does not establish the need to conduct specific reviews or audits; that need is defined by local policy. Where specific reviews and audits are required, standard procedures for their execution must be defined. This standard provides such definition for review and audit processes that are applicable to products and processes throughout the software life cycle. Each organization shall specify where and when this standard applies and any intended deviations from this standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Software Reviews and Audits"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106817 …}
    #channels: Doctrine\ORM\PersistentCollection {#106811 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106815 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106813 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106826 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106834
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @615160800 {#106833
      date: 1989-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106827
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1028"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106824 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106822 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}