Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10352
    #code: "IEEE00004226"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039008 {#7274
      date: 2025-06-27 17:43:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 36417
        #name: "IEEE/ISO/IEC 26702:2007"
        #slug: "ieee-iso-iec-26702-2007-ieee00004226-242004"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.<br />\n
          \t\t\t\t<br />\n
          This standard defines the interdisciplinary tasks that are required throughout a system’s life cycle to<br />\n
          transform stakeholder needs, requirements, and constraints into a system solution. This standard is intended<br />\n
          to guide the development of systems for commercial, government, military, and space applications. The<br />\n
          information applies to a project within an enterprise that is responsible for developing a product design and<br />\n
          establishing the life cycle infrastructure needed to provide for life cycle sustainment.<br />\n
          This standard specifies the requirements for the systems engineering process (SEP) and its application<br />\n
          throughout the product life cycle. It does not attempt to define the implementation of each system life cycle<br />\n
          process, but addresses the issues associated with defining and establishing supportive life cycle processes<br />\n
          early and continuously throughout product development. In addition, the standard does not address the many<br />\n
          cultural or quality variables that should be considered for successful product development. The standard<br />\n
          focuses on the engineering activities necessary to guide product development while ensuring that the<br />\n
          product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to<br />\n
          dispose of, without undue risk to health or the environment.<br />\n
          The requirements of this standard are applicable to new products as well as incremental enhancements to<br />\n
          existing products. It applies to one-of-a-kind products, such as a satellite, as well as products that are massproduced<br />\n
          for the consumer marketplace. The requirements of this standard should be selectively applied for<br />\n
          each specific system-development project. The role of systems engineering within the enterprise<br />\n
          environment is described in Annex A.<br />\n
          The content of this standard describes an integrated approach to product development, which represents the<br />\n
          total technical effort for the following:<br />\n
          a) Understanding the environments and the related conditions in which the product may be utilized and<br />\n
          for which the product should be designed to accommodate<br />\n
          b) Defining product requirements in terms of functional and performance requirements, quality factors,<br />\n
          usability, producibility, supportability, safety, and environmental impacts<br />\n
          c) Defining the life cycle processes for manufacturing, test, distribution, support, training, and<br />\n
          disposal, which are necessary to provide life cycle support for products<br />\n
          The purpose of this document is to provide a standard for managing a system from initial concept through<br />\n
          development, operations, and disposal. The inclusion of computers and associated software in today’s<br />\n
          products has made the need to engineer each of those products as a total system more acute. The human,<br />\n
          physical, and software components should all be addressed to optimize overall system performance.<br />\n
          This standard, IEEE Std 1220-2005, may be used in conjunction with ISO/IEC 15288:2002 [B3].<br />\n
          1<br />\n
          This<br />\n
          standard generally prescribes more detailed systems engineering process and management requirements that<br />\n
          complete or complement the process activities described in ISO/IEC 15288:2002. However, ISO/IEC<br />\n
          15288:2002 provides additional process definition and guidance that supports life cycle model definition<br />\n
          and application of the systems engineering process across a system’s life cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -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 @1184450400 {#7318
      date: 2007-07-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26702"
    -bookCollection: ""
    -pageCount: 101
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#93007
  +product: App\Entity\Product\Product {#7310
    #id: 10352
    #code: "IEEE00004226"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039008 {#7274
      date: 2025-06-27 17:43:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 36417
        #name: "IEEE/ISO/IEC 26702:2007"
        #slug: "ieee-iso-iec-26702-2007-ieee00004226-242004"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.<br />\n
          \t\t\t\t<br />\n
          This standard defines the interdisciplinary tasks that are required throughout a system’s life cycle to<br />\n
          transform stakeholder needs, requirements, and constraints into a system solution. This standard is intended<br />\n
          to guide the development of systems for commercial, government, military, and space applications. The<br />\n
          information applies to a project within an enterprise that is responsible for developing a product design and<br />\n
          establishing the life cycle infrastructure needed to provide for life cycle sustainment.<br />\n
          This standard specifies the requirements for the systems engineering process (SEP) and its application<br />\n
          throughout the product life cycle. It does not attempt to define the implementation of each system life cycle<br />\n
          process, but addresses the issues associated with defining and establishing supportive life cycle processes<br />\n
          early and continuously throughout product development. In addition, the standard does not address the many<br />\n
          cultural or quality variables that should be considered for successful product development. The standard<br />\n
          focuses on the engineering activities necessary to guide product development while ensuring that the<br />\n
          product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to<br />\n
          dispose of, without undue risk to health or the environment.<br />\n
          The requirements of this standard are applicable to new products as well as incremental enhancements to<br />\n
          existing products. It applies to one-of-a-kind products, such as a satellite, as well as products that are massproduced<br />\n
          for the consumer marketplace. The requirements of this standard should be selectively applied for<br />\n
          each specific system-development project. The role of systems engineering within the enterprise<br />\n
          environment is described in Annex A.<br />\n
          The content of this standard describes an integrated approach to product development, which represents the<br />\n
          total technical effort for the following:<br />\n
          a) Understanding the environments and the related conditions in which the product may be utilized and<br />\n
          for which the product should be designed to accommodate<br />\n
          b) Defining product requirements in terms of functional and performance requirements, quality factors,<br />\n
          usability, producibility, supportability, safety, and environmental impacts<br />\n
          c) Defining the life cycle processes for manufacturing, test, distribution, support, training, and<br />\n
          disposal, which are necessary to provide life cycle support for products<br />\n
          The purpose of this document is to provide a standard for managing a system from initial concept through<br />\n
          development, operations, and disposal. The inclusion of computers and associated software in today’s<br />\n
          products has made the need to engineer each of those products as a total system more acute. The human,<br />\n
          physical, and software components should all be addressed to optimize overall system performance.<br />\n
          This standard, IEEE Std 1220-2005, may be used in conjunction with ISO/IEC 15288:2002 [B3].<br />\n
          1<br />\n
          This<br />\n
          standard generally prescribes more detailed systems engineering process and management requirements that<br />\n
          complete or complement the process activities described in ISO/IEC 15288:2002. However, ISO/IEC<br />\n
          15288:2002 provides additional process definition and guidance that supports life cycle model definition<br />\n
          and application of the systems engineering process across a system’s life cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -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 @1184450400 {#7318
      date: 2007-07-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26702"
    -bookCollection: ""
    -pageCount: 101
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10352
    #code: "IEEE00004226"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039008 {#7274
      date: 2025-06-27 17:43:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 36417
        #name: "IEEE/ISO/IEC 26702:2007"
        #slug: "ieee-iso-iec-26702-2007-ieee00004226-242004"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.<br />\n
          \t\t\t\t<br />\n
          This standard defines the interdisciplinary tasks that are required throughout a system’s life cycle to<br />\n
          transform stakeholder needs, requirements, and constraints into a system solution. This standard is intended<br />\n
          to guide the development of systems for commercial, government, military, and space applications. The<br />\n
          information applies to a project within an enterprise that is responsible for developing a product design and<br />\n
          establishing the life cycle infrastructure needed to provide for life cycle sustainment.<br />\n
          This standard specifies the requirements for the systems engineering process (SEP) and its application<br />\n
          throughout the product life cycle. It does not attempt to define the implementation of each system life cycle<br />\n
          process, but addresses the issues associated with defining and establishing supportive life cycle processes<br />\n
          early and continuously throughout product development. In addition, the standard does not address the many<br />\n
          cultural or quality variables that should be considered for successful product development. The standard<br />\n
          focuses on the engineering activities necessary to guide product development while ensuring that the<br />\n
          product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to<br />\n
          dispose of, without undue risk to health or the environment.<br />\n
          The requirements of this standard are applicable to new products as well as incremental enhancements to<br />\n
          existing products. It applies to one-of-a-kind products, such as a satellite, as well as products that are massproduced<br />\n
          for the consumer marketplace. The requirements of this standard should be selectively applied for<br />\n
          each specific system-development project. The role of systems engineering within the enterprise<br />\n
          environment is described in Annex A.<br />\n
          The content of this standard describes an integrated approach to product development, which represents the<br />\n
          total technical effort for the following:<br />\n
          a) Understanding the environments and the related conditions in which the product may be utilized and<br />\n
          for which the product should be designed to accommodate<br />\n
          b) Defining product requirements in terms of functional and performance requirements, quality factors,<br />\n
          usability, producibility, supportability, safety, and environmental impacts<br />\n
          c) Defining the life cycle processes for manufacturing, test, distribution, support, training, and<br />\n
          disposal, which are necessary to provide life cycle support for products<br />\n
          The purpose of this document is to provide a standard for managing a system from initial concept through<br />\n
          development, operations, and disposal. The inclusion of computers and associated software in today’s<br />\n
          products has made the need to engineer each of those products as a total system more acute. The human,<br />\n
          physical, and software components should all be addressed to optimize overall system performance.<br />\n
          This standard, IEEE Std 1220-2005, may be used in conjunction with ISO/IEC 15288:2002 [B3].<br />\n
          1<br />\n
          This<br />\n
          standard generally prescribes more detailed systems engineering process and management requirements that<br />\n
          complete or complement the process activities described in ISO/IEC 15288:2002. However, ISO/IEC<br />\n
          15288:2002 provides additional process definition and guidance that supports life cycle model definition<br />\n
          and application of the systems engineering process across a system’s life cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -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 @1184450400 {#7318
      date: 2007-07-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26702"
    -bookCollection: ""
    -pageCount: 101
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductType {#93187
  +product: App\Entity\Product\Product {#7310
    #id: 10352
    #code: "IEEE00004226"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039008 {#7274
      date: 2025-06-27 17:43:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 36417
        #name: "IEEE/ISO/IEC 26702:2007"
        #slug: "ieee-iso-iec-26702-2007-ieee00004226-242004"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.<br />\n
          \t\t\t\t<br />\n
          This standard defines the interdisciplinary tasks that are required throughout a system’s life cycle to<br />\n
          transform stakeholder needs, requirements, and constraints into a system solution. This standard is intended<br />\n
          to guide the development of systems for commercial, government, military, and space applications. The<br />\n
          information applies to a project within an enterprise that is responsible for developing a product design and<br />\n
          establishing the life cycle infrastructure needed to provide for life cycle sustainment.<br />\n
          This standard specifies the requirements for the systems engineering process (SEP) and its application<br />\n
          throughout the product life cycle. It does not attempt to define the implementation of each system life cycle<br />\n
          process, but addresses the issues associated with defining and establishing supportive life cycle processes<br />\n
          early and continuously throughout product development. In addition, the standard does not address the many<br />\n
          cultural or quality variables that should be considered for successful product development. The standard<br />\n
          focuses on the engineering activities necessary to guide product development while ensuring that the<br />\n
          product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to<br />\n
          dispose of, without undue risk to health or the environment.<br />\n
          The requirements of this standard are applicable to new products as well as incremental enhancements to<br />\n
          existing products. It applies to one-of-a-kind products, such as a satellite, as well as products that are massproduced<br />\n
          for the consumer marketplace. The requirements of this standard should be selectively applied for<br />\n
          each specific system-development project. The role of systems engineering within the enterprise<br />\n
          environment is described in Annex A.<br />\n
          The content of this standard describes an integrated approach to product development, which represents the<br />\n
          total technical effort for the following:<br />\n
          a) Understanding the environments and the related conditions in which the product may be utilized and<br />\n
          for which the product should be designed to accommodate<br />\n
          b) Defining product requirements in terms of functional and performance requirements, quality factors,<br />\n
          usability, producibility, supportability, safety, and environmental impacts<br />\n
          c) Defining the life cycle processes for manufacturing, test, distribution, support, training, and<br />\n
          disposal, which are necessary to provide life cycle support for products<br />\n
          The purpose of this document is to provide a standard for managing a system from initial concept through<br />\n
          development, operations, and disposal. The inclusion of computers and associated software in today’s<br />\n
          products has made the need to engineer each of those products as a total system more acute. The human,<br />\n
          physical, and software components should all be addressed to optimize overall system performance.<br />\n
          This standard, IEEE Std 1220-2005, may be used in conjunction with ISO/IEC 15288:2002 [B3].<br />\n
          1<br />\n
          This<br />\n
          standard generally prescribes more detailed systems engineering process and management requirements that<br />\n
          complete or complement the process activities described in ISO/IEC 15288:2002. However, ISO/IEC<br />\n
          15288:2002 provides additional process definition and guidance that supports life cycle model definition<br />\n
          and application of the systems engineering process across a system’s life cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -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 @1184450400 {#7318
      date: 2007-07-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26702"
    -bookCollection: ""
    -pageCount: 101
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10352
    #code: "IEEE00004226"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039008 {#7274
      date: 2025-06-27 17:43:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 36417
        #name: "IEEE/ISO/IEC 26702:2007"
        #slug: "ieee-iso-iec-26702-2007-ieee00004226-242004"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.<br />\n
          \t\t\t\t<br />\n
          This standard defines the interdisciplinary tasks that are required throughout a system’s life cycle to<br />\n
          transform stakeholder needs, requirements, and constraints into a system solution. This standard is intended<br />\n
          to guide the development of systems for commercial, government, military, and space applications. The<br />\n
          information applies to a project within an enterprise that is responsible for developing a product design and<br />\n
          establishing the life cycle infrastructure needed to provide for life cycle sustainment.<br />\n
          This standard specifies the requirements for the systems engineering process (SEP) and its application<br />\n
          throughout the product life cycle. It does not attempt to define the implementation of each system life cycle<br />\n
          process, but addresses the issues associated with defining and establishing supportive life cycle processes<br />\n
          early and continuously throughout product development. In addition, the standard does not address the many<br />\n
          cultural or quality variables that should be considered for successful product development. The standard<br />\n
          focuses on the engineering activities necessary to guide product development while ensuring that the<br />\n
          product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to<br />\n
          dispose of, without undue risk to health or the environment.<br />\n
          The requirements of this standard are applicable to new products as well as incremental enhancements to<br />\n
          existing products. It applies to one-of-a-kind products, such as a satellite, as well as products that are massproduced<br />\n
          for the consumer marketplace. The requirements of this standard should be selectively applied for<br />\n
          each specific system-development project. The role of systems engineering within the enterprise<br />\n
          environment is described in Annex A.<br />\n
          The content of this standard describes an integrated approach to product development, which represents the<br />\n
          total technical effort for the following:<br />\n
          a) Understanding the environments and the related conditions in which the product may be utilized and<br />\n
          for which the product should be designed to accommodate<br />\n
          b) Defining product requirements in terms of functional and performance requirements, quality factors,<br />\n
          usability, producibility, supportability, safety, and environmental impacts<br />\n
          c) Defining the life cycle processes for manufacturing, test, distribution, support, training, and<br />\n
          disposal, which are necessary to provide life cycle support for products<br />\n
          The purpose of this document is to provide a standard for managing a system from initial concept through<br />\n
          development, operations, and disposal. The inclusion of computers and associated software in today’s<br />\n
          products has made the need to engineer each of those products as a total system more acute. The human,<br />\n
          physical, and software components should all be addressed to optimize overall system performance.<br />\n
          This standard, IEEE Std 1220-2005, may be used in conjunction with ISO/IEC 15288:2002 [B3].<br />\n
          1<br />\n
          This<br />\n
          standard generally prescribes more detailed systems engineering process and management requirements that<br />\n
          complete or complement the process activities described in ISO/IEC 15288:2002. However, ISO/IEC<br />\n
          15288:2002 provides additional process definition and guidance that supports life cycle model definition<br />\n
          and application of the systems engineering process across a system’s life cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -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 @1184450400 {#7318
      date: 2007-07-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26702"
    -bookCollection: ""
    -pageCount: 101
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#93262
  +product: App\Entity\Product\Product {#7310
    #id: 10352
    #code: "IEEE00004226"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039008 {#7274
      date: 2025-06-27 17:43:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 36417
        #name: "IEEE/ISO/IEC 26702:2007"
        #slug: "ieee-iso-iec-26702-2007-ieee00004226-242004"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.<br />\n
          \t\t\t\t<br />\n
          This standard defines the interdisciplinary tasks that are required throughout a system’s life cycle to<br />\n
          transform stakeholder needs, requirements, and constraints into a system solution. This standard is intended<br />\n
          to guide the development of systems for commercial, government, military, and space applications. The<br />\n
          information applies to a project within an enterprise that is responsible for developing a product design and<br />\n
          establishing the life cycle infrastructure needed to provide for life cycle sustainment.<br />\n
          This standard specifies the requirements for the systems engineering process (SEP) and its application<br />\n
          throughout the product life cycle. It does not attempt to define the implementation of each system life cycle<br />\n
          process, but addresses the issues associated with defining and establishing supportive life cycle processes<br />\n
          early and continuously throughout product development. In addition, the standard does not address the many<br />\n
          cultural or quality variables that should be considered for successful product development. The standard<br />\n
          focuses on the engineering activities necessary to guide product development while ensuring that the<br />\n
          product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to<br />\n
          dispose of, without undue risk to health or the environment.<br />\n
          The requirements of this standard are applicable to new products as well as incremental enhancements to<br />\n
          existing products. It applies to one-of-a-kind products, such as a satellite, as well as products that are massproduced<br />\n
          for the consumer marketplace. The requirements of this standard should be selectively applied for<br />\n
          each specific system-development project. The role of systems engineering within the enterprise<br />\n
          environment is described in Annex A.<br />\n
          The content of this standard describes an integrated approach to product development, which represents the<br />\n
          total technical effort for the following:<br />\n
          a) Understanding the environments and the related conditions in which the product may be utilized and<br />\n
          for which the product should be designed to accommodate<br />\n
          b) Defining product requirements in terms of functional and performance requirements, quality factors,<br />\n
          usability, producibility, supportability, safety, and environmental impacts<br />\n
          c) Defining the life cycle processes for manufacturing, test, distribution, support, training, and<br />\n
          disposal, which are necessary to provide life cycle support for products<br />\n
          The purpose of this document is to provide a standard for managing a system from initial concept through<br />\n
          development, operations, and disposal. The inclusion of computers and associated software in today’s<br />\n
          products has made the need to engineer each of those products as a total system more acute. The human,<br />\n
          physical, and software components should all be addressed to optimize overall system performance.<br />\n
          This standard, IEEE Std 1220-2005, may be used in conjunction with ISO/IEC 15288:2002 [B3].<br />\n
          1<br />\n
          This<br />\n
          standard generally prescribes more detailed systems engineering process and management requirements that<br />\n
          complete or complement the process activities described in ISO/IEC 15288:2002. However, ISO/IEC<br />\n
          15288:2002 provides additional process definition and guidance that supports life cycle model definition<br />\n
          and application of the systems engineering process across a system’s life cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -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 @1184450400 {#7318
      date: 2007-07-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26702"
    -bookCollection: ""
    -pageCount: 101
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10352
    #code: "IEEE00004226"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039008 {#7274
      date: 2025-06-27 17:43:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 36417
        #name: "IEEE/ISO/IEC 26702:2007"
        #slug: "ieee-iso-iec-26702-2007-ieee00004226-242004"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.<br />\n
          \t\t\t\t<br />\n
          This standard defines the interdisciplinary tasks that are required throughout a system’s life cycle to<br />\n
          transform stakeholder needs, requirements, and constraints into a system solution. This standard is intended<br />\n
          to guide the development of systems for commercial, government, military, and space applications. The<br />\n
          information applies to a project within an enterprise that is responsible for developing a product design and<br />\n
          establishing the life cycle infrastructure needed to provide for life cycle sustainment.<br />\n
          This standard specifies the requirements for the systems engineering process (SEP) and its application<br />\n
          throughout the product life cycle. It does not attempt to define the implementation of each system life cycle<br />\n
          process, but addresses the issues associated with defining and establishing supportive life cycle processes<br />\n
          early and continuously throughout product development. In addition, the standard does not address the many<br />\n
          cultural or quality variables that should be considered for successful product development. The standard<br />\n
          focuses on the engineering activities necessary to guide product development while ensuring that the<br />\n
          product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to<br />\n
          dispose of, without undue risk to health or the environment.<br />\n
          The requirements of this standard are applicable to new products as well as incremental enhancements to<br />\n
          existing products. It applies to one-of-a-kind products, such as a satellite, as well as products that are massproduced<br />\n
          for the consumer marketplace. The requirements of this standard should be selectively applied for<br />\n
          each specific system-development project. The role of systems engineering within the enterprise<br />\n
          environment is described in Annex A.<br />\n
          The content of this standard describes an integrated approach to product development, which represents the<br />\n
          total technical effort for the following:<br />\n
          a) Understanding the environments and the related conditions in which the product may be utilized and<br />\n
          for which the product should be designed to accommodate<br />\n
          b) Defining product requirements in terms of functional and performance requirements, quality factors,<br />\n
          usability, producibility, supportability, safety, and environmental impacts<br />\n
          c) Defining the life cycle processes for manufacturing, test, distribution, support, training, and<br />\n
          disposal, which are necessary to provide life cycle support for products<br />\n
          The purpose of this document is to provide a standard for managing a system from initial concept through<br />\n
          development, operations, and disposal. The inclusion of computers and associated software in today’s<br />\n
          products has made the need to engineer each of those products as a total system more acute. The human,<br />\n
          physical, and software components should all be addressed to optimize overall system performance.<br />\n
          This standard, IEEE Std 1220-2005, may be used in conjunction with ISO/IEC 15288:2002 [B3].<br />\n
          1<br />\n
          This<br />\n
          standard generally prescribes more detailed systems engineering process and management requirements that<br />\n
          complete or complement the process activities described in ISO/IEC 15288:2002. However, ISO/IEC<br />\n
          15288:2002 provides additional process definition and guidance that supports life cycle model definition<br />\n
          and application of the systems engineering process across a system’s life cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -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 @1184450400 {#7318
      date: 2007-07-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26702"
    -bookCollection: ""
    -pageCount: 101
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#100215
  +product: App\Entity\Product\Product {#7310
    #id: 10352
    #code: "IEEE00004226"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039008 {#7274
      date: 2025-06-27 17:43:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 36417
        #name: "IEEE/ISO/IEC 26702:2007"
        #slug: "ieee-iso-iec-26702-2007-ieee00004226-242004"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.<br />\n
          \t\t\t\t<br />\n
          This standard defines the interdisciplinary tasks that are required throughout a system’s life cycle to<br />\n
          transform stakeholder needs, requirements, and constraints into a system solution. This standard is intended<br />\n
          to guide the development of systems for commercial, government, military, and space applications. The<br />\n
          information applies to a project within an enterprise that is responsible for developing a product design and<br />\n
          establishing the life cycle infrastructure needed to provide for life cycle sustainment.<br />\n
          This standard specifies the requirements for the systems engineering process (SEP) and its application<br />\n
          throughout the product life cycle. It does not attempt to define the implementation of each system life cycle<br />\n
          process, but addresses the issues associated with defining and establishing supportive life cycle processes<br />\n
          early and continuously throughout product development. In addition, the standard does not address the many<br />\n
          cultural or quality variables that should be considered for successful product development. The standard<br />\n
          focuses on the engineering activities necessary to guide product development while ensuring that the<br />\n
          product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to<br />\n
          dispose of, without undue risk to health or the environment.<br />\n
          The requirements of this standard are applicable to new products as well as incremental enhancements to<br />\n
          existing products. It applies to one-of-a-kind products, such as a satellite, as well as products that are massproduced<br />\n
          for the consumer marketplace. The requirements of this standard should be selectively applied for<br />\n
          each specific system-development project. The role of systems engineering within the enterprise<br />\n
          environment is described in Annex A.<br />\n
          The content of this standard describes an integrated approach to product development, which represents the<br />\n
          total technical effort for the following:<br />\n
          a) Understanding the environments and the related conditions in which the product may be utilized and<br />\n
          for which the product should be designed to accommodate<br />\n
          b) Defining product requirements in terms of functional and performance requirements, quality factors,<br />\n
          usability, producibility, supportability, safety, and environmental impacts<br />\n
          c) Defining the life cycle processes for manufacturing, test, distribution, support, training, and<br />\n
          disposal, which are necessary to provide life cycle support for products<br />\n
          The purpose of this document is to provide a standard for managing a system from initial concept through<br />\n
          development, operations, and disposal. The inclusion of computers and associated software in today’s<br />\n
          products has made the need to engineer each of those products as a total system more acute. The human,<br />\n
          physical, and software components should all be addressed to optimize overall system performance.<br />\n
          This standard, IEEE Std 1220-2005, may be used in conjunction with ISO/IEC 15288:2002 [B3].<br />\n
          1<br />\n
          This<br />\n
          standard generally prescribes more detailed systems engineering process and management requirements that<br />\n
          complete or complement the process activities described in ISO/IEC 15288:2002. However, ISO/IEC<br />\n
          15288:2002 provides additional process definition and guidance that supports life cycle model definition<br />\n
          and application of the systems engineering process across a system’s life cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -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 @1184450400 {#7318
      date: 2007-07-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26702"
    -bookCollection: ""
    -pageCount: 101
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10352
    #code: "IEEE00004226"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039008 {#7274
      date: 2025-06-27 17:43:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 36417
        #name: "IEEE/ISO/IEC 26702:2007"
        #slug: "ieee-iso-iec-26702-2007-ieee00004226-242004"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.<br />\n
          \t\t\t\t<br />\n
          This standard defines the interdisciplinary tasks that are required throughout a system’s life cycle to<br />\n
          transform stakeholder needs, requirements, and constraints into a system solution. This standard is intended<br />\n
          to guide the development of systems for commercial, government, military, and space applications. The<br />\n
          information applies to a project within an enterprise that is responsible for developing a product design and<br />\n
          establishing the life cycle infrastructure needed to provide for life cycle sustainment.<br />\n
          This standard specifies the requirements for the systems engineering process (SEP) and its application<br />\n
          throughout the product life cycle. It does not attempt to define the implementation of each system life cycle<br />\n
          process, but addresses the issues associated with defining and establishing supportive life cycle processes<br />\n
          early and continuously throughout product development. In addition, the standard does not address the many<br />\n
          cultural or quality variables that should be considered for successful product development. The standard<br />\n
          focuses on the engineering activities necessary to guide product development while ensuring that the<br />\n
          product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to<br />\n
          dispose of, without undue risk to health or the environment.<br />\n
          The requirements of this standard are applicable to new products as well as incremental enhancements to<br />\n
          existing products. It applies to one-of-a-kind products, such as a satellite, as well as products that are massproduced<br />\n
          for the consumer marketplace. The requirements of this standard should be selectively applied for<br />\n
          each specific system-development project. The role of systems engineering within the enterprise<br />\n
          environment is described in Annex A.<br />\n
          The content of this standard describes an integrated approach to product development, which represents the<br />\n
          total technical effort for the following:<br />\n
          a) Understanding the environments and the related conditions in which the product may be utilized and<br />\n
          for which the product should be designed to accommodate<br />\n
          b) Defining product requirements in terms of functional and performance requirements, quality factors,<br />\n
          usability, producibility, supportability, safety, and environmental impacts<br />\n
          c) Defining the life cycle processes for manufacturing, test, distribution, support, training, and<br />\n
          disposal, which are necessary to provide life cycle support for products<br />\n
          The purpose of this document is to provide a standard for managing a system from initial concept through<br />\n
          development, operations, and disposal. The inclusion of computers and associated software in today’s<br />\n
          products has made the need to engineer each of those products as a total system more acute. The human,<br />\n
          physical, and software components should all be addressed to optimize overall system performance.<br />\n
          This standard, IEEE Std 1220-2005, may be used in conjunction with ISO/IEC 15288:2002 [B3].<br />\n
          1<br />\n
          This<br />\n
          standard generally prescribes more detailed systems engineering process and management requirements that<br />\n
          complete or complement the process activities described in ISO/IEC 15288:2002. However, ISO/IEC<br />\n
          15288:2002 provides additional process definition and guidance that supports life cycle model definition<br />\n
          and application of the systems engineering process across a system’s life cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -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 @1184450400 {#7318
      date: 2007-07-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26702"
    -bookCollection: ""
    -pageCount: 101
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#100299
  +product: App\Entity\Product\Product {#7310
    #id: 10352
    #code: "IEEE00004226"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039008 {#7274
      date: 2025-06-27 17:43:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 36417
        #name: "IEEE/ISO/IEC 26702:2007"
        #slug: "ieee-iso-iec-26702-2007-ieee00004226-242004"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The interdisciplinary tasks, which are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.<br />\n
          \t\t\t\t<br />\n
          This standard defines the interdisciplinary tasks that are required throughout a system’s life cycle to<br />\n
          transform stakeholder needs, requirements, and constraints into a system solution. This standard is intended<br />\n
          to guide the development of systems for commercial, government, military, and space applications. The<br />\n
          information applies to a project within an enterprise that is responsible for developing a product design and<br />\n
          establishing the life cycle infrastructure needed to provide for life cycle sustainment.<br />\n
          This standard specifies the requirements for the systems engineering process (SEP) and its application<br />\n
          throughout the product life cycle. It does not attempt to define the implementation of each system life cycle<br />\n
          process, but addresses the issues associated with defining and establishing supportive life cycle processes<br />\n
          early and continuously throughout product development. In addition, the standard does not address the many<br />\n
          cultural or quality variables that should be considered for successful product development. The standard<br />\n
          focuses on the engineering activities necessary to guide product development while ensuring that the<br />\n
          product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to<br />\n
          dispose of, without undue risk to health or the environment.<br />\n
          The requirements of this standard are applicable to new products as well as incremental enhancements to<br />\n
          existing products. It applies to one-of-a-kind products, such as a satellite, as well as products that are massproduced<br />\n
          for the consumer marketplace. The requirements of this standard should be selectively applied for<br />\n
          each specific system-development project. The role of systems engineering within the enterprise<br />\n
          environment is described in Annex A.<br />\n
          The content of this standard describes an integrated approach to product development, which represents the<br />\n
          total technical effort for the following:<br />\n
          a) Understanding the environments and the related conditions in which the product may be utilized and<br />\n
          for which the product should be designed to accommodate<br />\n
          b) Defining product requirements in terms of functional and performance requirements, quality factors,<br />\n
          usability, producibility, supportability, safety, and environmental impacts<br />\n
          c) Defining the life cycle processes for manufacturing, test, distribution, support, training, and<br />\n
          disposal, which are necessary to provide life cycle support for products<br />\n
          The purpose of this document is to provide a standard for managing a system from initial concept through<br />\n
          development, operations, and disposal. The inclusion of computers and associated software in today’s<br />\n
          products has made the need to engineer each of those products as a total system more acute. The human,<br />\n
          physical, and software components should all be addressed to optimize overall system performance.<br />\n
          This standard, IEEE Std 1220-2005, may be used in conjunction with ISO/IEC 15288:2002 [B3].<br />\n
          1<br />\n
          This<br />\n
          standard generally prescribes more detailed systems engineering process and management requirements that<br />\n
          complete or complement the process activities described in ISO/IEC 15288:2002. However, ISO/IEC<br />\n
          15288:2002 provides additional process definition and guidance that supports life cycle model definition<br />\n
          and application of the systems engineering process across a system’s life cycle.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems Engineering - Application and Management of the Systems Engineering Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -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 @1184450400 {#7318
      date: 2007-07-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26702"
    -bookCollection: ""
    -pageCount: 101
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

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

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

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

[
  "showFullLabel" => false
]

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

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

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