Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039009 {#7274
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.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: 36425
        #name: "IEEE/ISO/IEC 42010:2007"
        #slug: "ieee-iso-iec-42010-2007-ieee00004228-242006"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This recommended practice addresses the activities of the creation, analysis, and sustainment<br />\n
          of architectures of software-intensive systems, and the recording of such architectures in<br />\n
          terms of<br />\n
          architectural descriptions<br />\n
          . A conceptual framework for architectural description is established.<br />\n
          The content of an architectural description is defined. Annexes provide the rationale for key<br />\n
          concepts and terminology, the relationships to other standards, and examples of usage.<br />\n
          \t\t\t\t<br />\n
          This recommended practice addresses the architectural description of software-intensive systems. A<br />\n
          software-intensive system<br />\n
          is any system where software contributes essential influences to the design,<br />\n
          construction, deployment, and evolution of the system as a whole.<br />\n
          The scope of this recommended practice encompasses those products of system development that capture<br />\n
          architectural information. This includes architectural descriptions that are used for the following:<br />\n
          a) Expression of the system and its evolution<br />\n
          b) Communication among the system stakeholders<br />\n
          c) Evaluation and comparison of architectures in a consistent manner<br />\n
          d) Planning, managing, and executing the activities of system development<br />\n
          e) Expression of the persistent characteristics and supporting principles of a system to guide acceptable<br />\n
          change<br />\n
          f) Verification of a system implementation's compliance with an architectural description<br />\n
          g) Recording contributions to the body of knowledge of software-intensive systems architecture<br />\n
          The purpose of this recommended practice is to facilitate the expression and communication of architectures<br />\n
          and thereby lay a foundation for quality and cost gains through standardization of elements and practices for<br />\n
          architectural description.<br />\n
          Despite significant efforts to improve engineering practices and technologies, software-intensive systems<br />\n
          continue to present formidable risks and difficulties in their design, construction, deployment, and evolution.<br />\n
          Recent attempts to address these difficulties have focused on the earliest period of design decision-making<br />\n
          and evaluation, increasingly referred to as the<br />\n
          architectural level<br />\n
          of system development. The phrases<br />\n
          archi-tectural<br />\n
          level<br />\n
          and<br />\n
          architecture<br />\n
          are widely, if imprecisely, used. Their use reflects acceptance of an architectural<br />\n
          metaphor in the analysis and development of software-intensive systems. A key premise of this<br />\n
          metaphor is that important decisions may be made early in system development in a manner similar to the<br />\n
          early decision-making found in the development of civil architecture projects.<br />\n
          Many innovations are resulting from this attention to the architectural level, among them architectural<br />\n
          description languages and associated tools and environments; architectural frameworks, models, and<br />\n
          patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these<br />\n
          efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of<br />\n
          a recommended practice to codify their common elements.<br />\n
          These innovations are occurring, and maturing, rapidly within many research and application communities,<br />\n
          and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the<br />\n
          importance of the<br />\n
          architectural level of systems development<br />\n
          , and that that level consists of early decisionmaking<br />\n
          about overall design structure, goals, requirements, and development strategies. However, there has<br />\n
          not yet emerged any reliable consensus on a precise definition of a system's<br />\n
          , i.e., how it should<br />\n
          be described, what uses such a description may serve, or where and when it should be defined. The boundaries<br />\n
          and relationships between architectural trends and practices, and other practices; and between architectural<br />\n
          technology and other technology, are not yet widely recognized.<br />\n
          In such situations, progress often depends on mediating influences. Potential adopters of architectural<br />\n
          practices and technology need a frame of reference within which to address implementation and adoption<br />\n
          decisions. Technology developers need a frame of reference within which to communicate the motivating<br />\n
          concepts of their technology, and to accumulate and appreciate feedback from early adoption.<br />\n
          To these ends, this recommended practice is intended to reflect generally accepted trends in practices for<br />\n
          architectural description and to provide a technical framework for further evolution in this area.<br />\n
          Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future<br />\n
          developments in system architectural technology can be deployed. This recommended practice codifies<br />\n
          those elements on which there is consensus; specifically the use of multiple views, reusable specifications<br />\n
          for models within views, and the relation of architecture to system context.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems and Software Engineering - Recommended Practice for Architectural Description of Software-Intensive Systems"
        -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: "42010"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#92891
  +product: App\Entity\Product\Product {#7310
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039009 {#7274
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.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: 36425
        #name: "IEEE/ISO/IEC 42010:2007"
        #slug: "ieee-iso-iec-42010-2007-ieee00004228-242006"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This recommended practice addresses the activities of the creation, analysis, and sustainment<br />\n
          of architectures of software-intensive systems, and the recording of such architectures in<br />\n
          terms of<br />\n
          architectural descriptions<br />\n
          . A conceptual framework for architectural description is established.<br />\n
          The content of an architectural description is defined. Annexes provide the rationale for key<br />\n
          concepts and terminology, the relationships to other standards, and examples of usage.<br />\n
          \t\t\t\t<br />\n
          This recommended practice addresses the architectural description of software-intensive systems. A<br />\n
          software-intensive system<br />\n
          is any system where software contributes essential influences to the design,<br />\n
          construction, deployment, and evolution of the system as a whole.<br />\n
          The scope of this recommended practice encompasses those products of system development that capture<br />\n
          architectural information. This includes architectural descriptions that are used for the following:<br />\n
          a) Expression of the system and its evolution<br />\n
          b) Communication among the system stakeholders<br />\n
          c) Evaluation and comparison of architectures in a consistent manner<br />\n
          d) Planning, managing, and executing the activities of system development<br />\n
          e) Expression of the persistent characteristics and supporting principles of a system to guide acceptable<br />\n
          change<br />\n
          f) Verification of a system implementation's compliance with an architectural description<br />\n
          g) Recording contributions to the body of knowledge of software-intensive systems architecture<br />\n
          The purpose of this recommended practice is to facilitate the expression and communication of architectures<br />\n
          and thereby lay a foundation for quality and cost gains through standardization of elements and practices for<br />\n
          architectural description.<br />\n
          Despite significant efforts to improve engineering practices and technologies, software-intensive systems<br />\n
          continue to present formidable risks and difficulties in their design, construction, deployment, and evolution.<br />\n
          Recent attempts to address these difficulties have focused on the earliest period of design decision-making<br />\n
          and evaluation, increasingly referred to as the<br />\n
          architectural level<br />\n
          of system development. The phrases<br />\n
          archi-tectural<br />\n
          level<br />\n
          and<br />\n
          architecture<br />\n
          are widely, if imprecisely, used. Their use reflects acceptance of an architectural<br />\n
          metaphor in the analysis and development of software-intensive systems. A key premise of this<br />\n
          metaphor is that important decisions may be made early in system development in a manner similar to the<br />\n
          early decision-making found in the development of civil architecture projects.<br />\n
          Many innovations are resulting from this attention to the architectural level, among them architectural<br />\n
          description languages and associated tools and environments; architectural frameworks, models, and<br />\n
          patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these<br />\n
          efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of<br />\n
          a recommended practice to codify their common elements.<br />\n
          These innovations are occurring, and maturing, rapidly within many research and application communities,<br />\n
          and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the<br />\n
          importance of the<br />\n
          architectural level of systems development<br />\n
          , and that that level consists of early decisionmaking<br />\n
          about overall design structure, goals, requirements, and development strategies. However, there has<br />\n
          not yet emerged any reliable consensus on a precise definition of a system's<br />\n
          , i.e., how it should<br />\n
          be described, what uses such a description may serve, or where and when it should be defined. The boundaries<br />\n
          and relationships between architectural trends and practices, and other practices; and between architectural<br />\n
          technology and other technology, are not yet widely recognized.<br />\n
          In such situations, progress often depends on mediating influences. Potential adopters of architectural<br />\n
          practices and technology need a frame of reference within which to address implementation and adoption<br />\n
          decisions. Technology developers need a frame of reference within which to communicate the motivating<br />\n
          concepts of their technology, and to accumulate and appreciate feedback from early adoption.<br />\n
          To these ends, this recommended practice is intended to reflect generally accepted trends in practices for<br />\n
          architectural description and to provide a technical framework for further evolution in this area.<br />\n
          Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future<br />\n
          developments in system architectural technology can be deployed. This recommended practice codifies<br />\n
          those elements on which there is consensus; specifically the use of multiple views, reusable specifications<br />\n
          for models within views, and the relation of architecture to system context.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems and Software Engineering - Recommended Practice for Architectural Description of Software-Intensive Systems"
        -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: "42010"
    -bookCollection: ""
    -pageCount: 24
    -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: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039009 {#7274
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.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: 36425
        #name: "IEEE/ISO/IEC 42010:2007"
        #slug: "ieee-iso-iec-42010-2007-ieee00004228-242006"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This recommended practice addresses the activities of the creation, analysis, and sustainment<br />\n
          of architectures of software-intensive systems, and the recording of such architectures in<br />\n
          terms of<br />\n
          architectural descriptions<br />\n
          . A conceptual framework for architectural description is established.<br />\n
          The content of an architectural description is defined. Annexes provide the rationale for key<br />\n
          concepts and terminology, the relationships to other standards, and examples of usage.<br />\n
          \t\t\t\t<br />\n
          This recommended practice addresses the architectural description of software-intensive systems. A<br />\n
          software-intensive system<br />\n
          is any system where software contributes essential influences to the design,<br />\n
          construction, deployment, and evolution of the system as a whole.<br />\n
          The scope of this recommended practice encompasses those products of system development that capture<br />\n
          architectural information. This includes architectural descriptions that are used for the following:<br />\n
          a) Expression of the system and its evolution<br />\n
          b) Communication among the system stakeholders<br />\n
          c) Evaluation and comparison of architectures in a consistent manner<br />\n
          d) Planning, managing, and executing the activities of system development<br />\n
          e) Expression of the persistent characteristics and supporting principles of a system to guide acceptable<br />\n
          change<br />\n
          f) Verification of a system implementation's compliance with an architectural description<br />\n
          g) Recording contributions to the body of knowledge of software-intensive systems architecture<br />\n
          The purpose of this recommended practice is to facilitate the expression and communication of architectures<br />\n
          and thereby lay a foundation for quality and cost gains through standardization of elements and practices for<br />\n
          architectural description.<br />\n
          Despite significant efforts to improve engineering practices and technologies, software-intensive systems<br />\n
          continue to present formidable risks and difficulties in their design, construction, deployment, and evolution.<br />\n
          Recent attempts to address these difficulties have focused on the earliest period of design decision-making<br />\n
          and evaluation, increasingly referred to as the<br />\n
          architectural level<br />\n
          of system development. The phrases<br />\n
          archi-tectural<br />\n
          level<br />\n
          and<br />\n
          architecture<br />\n
          are widely, if imprecisely, used. Their use reflects acceptance of an architectural<br />\n
          metaphor in the analysis and development of software-intensive systems. A key premise of this<br />\n
          metaphor is that important decisions may be made early in system development in a manner similar to the<br />\n
          early decision-making found in the development of civil architecture projects.<br />\n
          Many innovations are resulting from this attention to the architectural level, among them architectural<br />\n
          description languages and associated tools and environments; architectural frameworks, models, and<br />\n
          patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these<br />\n
          efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of<br />\n
          a recommended practice to codify their common elements.<br />\n
          These innovations are occurring, and maturing, rapidly within many research and application communities,<br />\n
          and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the<br />\n
          importance of the<br />\n
          architectural level of systems development<br />\n
          , and that that level consists of early decisionmaking<br />\n
          about overall design structure, goals, requirements, and development strategies. However, there has<br />\n
          not yet emerged any reliable consensus on a precise definition of a system's<br />\n
          , i.e., how it should<br />\n
          be described, what uses such a description may serve, or where and when it should be defined. The boundaries<br />\n
          and relationships between architectural trends and practices, and other practices; and between architectural<br />\n
          technology and other technology, are not yet widely recognized.<br />\n
          In such situations, progress often depends on mediating influences. Potential adopters of architectural<br />\n
          practices and technology need a frame of reference within which to address implementation and adoption<br />\n
          decisions. Technology developers need a frame of reference within which to communicate the motivating<br />\n
          concepts of their technology, and to accumulate and appreciate feedback from early adoption.<br />\n
          To these ends, this recommended practice is intended to reflect generally accepted trends in practices for<br />\n
          architectural description and to provide a technical framework for further evolution in this area.<br />\n
          Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future<br />\n
          developments in system architectural technology can be deployed. This recommended practice codifies<br />\n
          those elements on which there is consensus; specifically the use of multiple views, reusable specifications<br />\n
          for models within views, and the relation of architecture to system context.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems and Software Engineering - Recommended Practice for Architectural Description of Software-Intensive Systems"
        -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: "42010"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductType {#93062
  +product: App\Entity\Product\Product {#7310
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039009 {#7274
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.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: 36425
        #name: "IEEE/ISO/IEC 42010:2007"
        #slug: "ieee-iso-iec-42010-2007-ieee00004228-242006"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This recommended practice addresses the activities of the creation, analysis, and sustainment<br />\n
          of architectures of software-intensive systems, and the recording of such architectures in<br />\n
          terms of<br />\n
          architectural descriptions<br />\n
          . A conceptual framework for architectural description is established.<br />\n
          The content of an architectural description is defined. Annexes provide the rationale for key<br />\n
          concepts and terminology, the relationships to other standards, and examples of usage.<br />\n
          \t\t\t\t<br />\n
          This recommended practice addresses the architectural description of software-intensive systems. A<br />\n
          software-intensive system<br />\n
          is any system where software contributes essential influences to the design,<br />\n
          construction, deployment, and evolution of the system as a whole.<br />\n
          The scope of this recommended practice encompasses those products of system development that capture<br />\n
          architectural information. This includes architectural descriptions that are used for the following:<br />\n
          a) Expression of the system and its evolution<br />\n
          b) Communication among the system stakeholders<br />\n
          c) Evaluation and comparison of architectures in a consistent manner<br />\n
          d) Planning, managing, and executing the activities of system development<br />\n
          e) Expression of the persistent characteristics and supporting principles of a system to guide acceptable<br />\n
          change<br />\n
          f) Verification of a system implementation's compliance with an architectural description<br />\n
          g) Recording contributions to the body of knowledge of software-intensive systems architecture<br />\n
          The purpose of this recommended practice is to facilitate the expression and communication of architectures<br />\n
          and thereby lay a foundation for quality and cost gains through standardization of elements and practices for<br />\n
          architectural description.<br />\n
          Despite significant efforts to improve engineering practices and technologies, software-intensive systems<br />\n
          continue to present formidable risks and difficulties in their design, construction, deployment, and evolution.<br />\n
          Recent attempts to address these difficulties have focused on the earliest period of design decision-making<br />\n
          and evaluation, increasingly referred to as the<br />\n
          architectural level<br />\n
          of system development. The phrases<br />\n
          archi-tectural<br />\n
          level<br />\n
          and<br />\n
          architecture<br />\n
          are widely, if imprecisely, used. Their use reflects acceptance of an architectural<br />\n
          metaphor in the analysis and development of software-intensive systems. A key premise of this<br />\n
          metaphor is that important decisions may be made early in system development in a manner similar to the<br />\n
          early decision-making found in the development of civil architecture projects.<br />\n
          Many innovations are resulting from this attention to the architectural level, among them architectural<br />\n
          description languages and associated tools and environments; architectural frameworks, models, and<br />\n
          patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these<br />\n
          efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of<br />\n
          a recommended practice to codify their common elements.<br />\n
          These innovations are occurring, and maturing, rapidly within many research and application communities,<br />\n
          and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the<br />\n
          importance of the<br />\n
          architectural level of systems development<br />\n
          , and that that level consists of early decisionmaking<br />\n
          about overall design structure, goals, requirements, and development strategies. However, there has<br />\n
          not yet emerged any reliable consensus on a precise definition of a system's<br />\n
          , i.e., how it should<br />\n
          be described, what uses such a description may serve, or where and when it should be defined. The boundaries<br />\n
          and relationships between architectural trends and practices, and other practices; and between architectural<br />\n
          technology and other technology, are not yet widely recognized.<br />\n
          In such situations, progress often depends on mediating influences. Potential adopters of architectural<br />\n
          practices and technology need a frame of reference within which to address implementation and adoption<br />\n
          decisions. Technology developers need a frame of reference within which to communicate the motivating<br />\n
          concepts of their technology, and to accumulate and appreciate feedback from early adoption.<br />\n
          To these ends, this recommended practice is intended to reflect generally accepted trends in practices for<br />\n
          architectural description and to provide a technical framework for further evolution in this area.<br />\n
          Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future<br />\n
          developments in system architectural technology can be deployed. This recommended practice codifies<br />\n
          those elements on which there is consensus; specifically the use of multiple views, reusable specifications<br />\n
          for models within views, and the relation of architecture to system context.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems and Software Engineering - Recommended Practice for Architectural Description of Software-Intensive Systems"
        -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: "42010"
    -bookCollection: ""
    -pageCount: 24
    -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: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039009 {#7274
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.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: 36425
        #name: "IEEE/ISO/IEC 42010:2007"
        #slug: "ieee-iso-iec-42010-2007-ieee00004228-242006"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This recommended practice addresses the activities of the creation, analysis, and sustainment<br />\n
          of architectures of software-intensive systems, and the recording of such architectures in<br />\n
          terms of<br />\n
          architectural descriptions<br />\n
          . A conceptual framework for architectural description is established.<br />\n
          The content of an architectural description is defined. Annexes provide the rationale for key<br />\n
          concepts and terminology, the relationships to other standards, and examples of usage.<br />\n
          \t\t\t\t<br />\n
          This recommended practice addresses the architectural description of software-intensive systems. A<br />\n
          software-intensive system<br />\n
          is any system where software contributes essential influences to the design,<br />\n
          construction, deployment, and evolution of the system as a whole.<br />\n
          The scope of this recommended practice encompasses those products of system development that capture<br />\n
          architectural information. This includes architectural descriptions that are used for the following:<br />\n
          a) Expression of the system and its evolution<br />\n
          b) Communication among the system stakeholders<br />\n
          c) Evaluation and comparison of architectures in a consistent manner<br />\n
          d) Planning, managing, and executing the activities of system development<br />\n
          e) Expression of the persistent characteristics and supporting principles of a system to guide acceptable<br />\n
          change<br />\n
          f) Verification of a system implementation's compliance with an architectural description<br />\n
          g) Recording contributions to the body of knowledge of software-intensive systems architecture<br />\n
          The purpose of this recommended practice is to facilitate the expression and communication of architectures<br />\n
          and thereby lay a foundation for quality and cost gains through standardization of elements and practices for<br />\n
          architectural description.<br />\n
          Despite significant efforts to improve engineering practices and technologies, software-intensive systems<br />\n
          continue to present formidable risks and difficulties in their design, construction, deployment, and evolution.<br />\n
          Recent attempts to address these difficulties have focused on the earliest period of design decision-making<br />\n
          and evaluation, increasingly referred to as the<br />\n
          architectural level<br />\n
          of system development. The phrases<br />\n
          archi-tectural<br />\n
          level<br />\n
          and<br />\n
          architecture<br />\n
          are widely, if imprecisely, used. Their use reflects acceptance of an architectural<br />\n
          metaphor in the analysis and development of software-intensive systems. A key premise of this<br />\n
          metaphor is that important decisions may be made early in system development in a manner similar to the<br />\n
          early decision-making found in the development of civil architecture projects.<br />\n
          Many innovations are resulting from this attention to the architectural level, among them architectural<br />\n
          description languages and associated tools and environments; architectural frameworks, models, and<br />\n
          patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these<br />\n
          efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of<br />\n
          a recommended practice to codify their common elements.<br />\n
          These innovations are occurring, and maturing, rapidly within many research and application communities,<br />\n
          and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the<br />\n
          importance of the<br />\n
          architectural level of systems development<br />\n
          , and that that level consists of early decisionmaking<br />\n
          about overall design structure, goals, requirements, and development strategies. However, there has<br />\n
          not yet emerged any reliable consensus on a precise definition of a system's<br />\n
          , i.e., how it should<br />\n
          be described, what uses such a description may serve, or where and when it should be defined. The boundaries<br />\n
          and relationships between architectural trends and practices, and other practices; and between architectural<br />\n
          technology and other technology, are not yet widely recognized.<br />\n
          In such situations, progress often depends on mediating influences. Potential adopters of architectural<br />\n
          practices and technology need a frame of reference within which to address implementation and adoption<br />\n
          decisions. Technology developers need a frame of reference within which to communicate the motivating<br />\n
          concepts of their technology, and to accumulate and appreciate feedback from early adoption.<br />\n
          To these ends, this recommended practice is intended to reflect generally accepted trends in practices for<br />\n
          architectural description and to provide a technical framework for further evolution in this area.<br />\n
          Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future<br />\n
          developments in system architectural technology can be deployed. This recommended practice codifies<br />\n
          those elements on which there is consensus; specifically the use of multiple views, reusable specifications<br />\n
          for models within views, and the relation of architecture to system context.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems and Software Engineering - Recommended Practice for Architectural Description of Software-Intensive Systems"
        -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: "42010"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#93137
  +product: App\Entity\Product\Product {#7310
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039009 {#7274
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.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: 36425
        #name: "IEEE/ISO/IEC 42010:2007"
        #slug: "ieee-iso-iec-42010-2007-ieee00004228-242006"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This recommended practice addresses the activities of the creation, analysis, and sustainment<br />\n
          of architectures of software-intensive systems, and the recording of such architectures in<br />\n
          terms of<br />\n
          architectural descriptions<br />\n
          . A conceptual framework for architectural description is established.<br />\n
          The content of an architectural description is defined. Annexes provide the rationale for key<br />\n
          concepts and terminology, the relationships to other standards, and examples of usage.<br />\n
          \t\t\t\t<br />\n
          This recommended practice addresses the architectural description of software-intensive systems. A<br />\n
          software-intensive system<br />\n
          is any system where software contributes essential influences to the design,<br />\n
          construction, deployment, and evolution of the system as a whole.<br />\n
          The scope of this recommended practice encompasses those products of system development that capture<br />\n
          architectural information. This includes architectural descriptions that are used for the following:<br />\n
          a) Expression of the system and its evolution<br />\n
          b) Communication among the system stakeholders<br />\n
          c) Evaluation and comparison of architectures in a consistent manner<br />\n
          d) Planning, managing, and executing the activities of system development<br />\n
          e) Expression of the persistent characteristics and supporting principles of a system to guide acceptable<br />\n
          change<br />\n
          f) Verification of a system implementation's compliance with an architectural description<br />\n
          g) Recording contributions to the body of knowledge of software-intensive systems architecture<br />\n
          The purpose of this recommended practice is to facilitate the expression and communication of architectures<br />\n
          and thereby lay a foundation for quality and cost gains through standardization of elements and practices for<br />\n
          architectural description.<br />\n
          Despite significant efforts to improve engineering practices and technologies, software-intensive systems<br />\n
          continue to present formidable risks and difficulties in their design, construction, deployment, and evolution.<br />\n
          Recent attempts to address these difficulties have focused on the earliest period of design decision-making<br />\n
          and evaluation, increasingly referred to as the<br />\n
          architectural level<br />\n
          of system development. The phrases<br />\n
          archi-tectural<br />\n
          level<br />\n
          and<br />\n
          architecture<br />\n
          are widely, if imprecisely, used. Their use reflects acceptance of an architectural<br />\n
          metaphor in the analysis and development of software-intensive systems. A key premise of this<br />\n
          metaphor is that important decisions may be made early in system development in a manner similar to the<br />\n
          early decision-making found in the development of civil architecture projects.<br />\n
          Many innovations are resulting from this attention to the architectural level, among them architectural<br />\n
          description languages and associated tools and environments; architectural frameworks, models, and<br />\n
          patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these<br />\n
          efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of<br />\n
          a recommended practice to codify their common elements.<br />\n
          These innovations are occurring, and maturing, rapidly within many research and application communities,<br />\n
          and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the<br />\n
          importance of the<br />\n
          architectural level of systems development<br />\n
          , and that that level consists of early decisionmaking<br />\n
          about overall design structure, goals, requirements, and development strategies. However, there has<br />\n
          not yet emerged any reliable consensus on a precise definition of a system's<br />\n
          , i.e., how it should<br />\n
          be described, what uses such a description may serve, or where and when it should be defined. The boundaries<br />\n
          and relationships between architectural trends and practices, and other practices; and between architectural<br />\n
          technology and other technology, are not yet widely recognized.<br />\n
          In such situations, progress often depends on mediating influences. Potential adopters of architectural<br />\n
          practices and technology need a frame of reference within which to address implementation and adoption<br />\n
          decisions. Technology developers need a frame of reference within which to communicate the motivating<br />\n
          concepts of their technology, and to accumulate and appreciate feedback from early adoption.<br />\n
          To these ends, this recommended practice is intended to reflect generally accepted trends in practices for<br />\n
          architectural description and to provide a technical framework for further evolution in this area.<br />\n
          Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future<br />\n
          developments in system architectural technology can be deployed. This recommended practice codifies<br />\n
          those elements on which there is consensus; specifically the use of multiple views, reusable specifications<br />\n
          for models within views, and the relation of architecture to system context.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems and Software Engineering - Recommended Practice for Architectural Description of Software-Intensive Systems"
        -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: "42010"
    -bookCollection: ""
    -pageCount: 24
    -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 {#93560
    #id: 11972
    #code: "IEEE00006846"
    #attributes: Doctrine\ORM\PersistentCollection {#93542 …}
    #variants: Doctrine\ORM\PersistentCollection {#93539 …}
    #options: Doctrine\ORM\PersistentCollection {#93535 …}
    #associations: Doctrine\ORM\PersistentCollection {#93537 …}
    #createdAt: DateTime @1751040111 {#93568
      date: 2025-06-27 18:01:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93547
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93553 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93588
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93560}
        #id: 42897
        #name: "IEEE/ISO/IEC 42010:2022"
        #slug: "ieee-iso-iec-42010-2022-ieee00006846-243624"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for the structure and expression of an architecture description (AD) for various entities, including software, systems, enterprises, systems of systems, families of systems, products (goods or services), product lines, service lines, technologies and business domains. This document distinguishes the architecture of an entity of interest from an AD expressing that architecture. Architectures are not the subject of this document. This document specifies requirements for use of the architectural concepts and their relationships as captured in an AD. It does not specify requirements for any entity of interest or its environment. This document specifies requirements for an architecture description framework (ADF), an architecture description language (ADL), architecture viewpoints and model kinds in order to usefully support the development and use of an AD. This document specifies conformance to the requirements for an AD, ADF, ADL, architecture viewpoint and model kind. This document does not specify the processes, architecting methods, models, notations, techniques or tools by which an AD is created, utilized or managed. This document does not specify any format or media for recording an AD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC International Standard for Software, systems and enterprise--Architecture description"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93551 …}
    #channels: Doctrine\ORM\PersistentCollection {#93544 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93549 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93546 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93561 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93531
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#93567
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#93566
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 74
    -documents: Doctrine\ORM\PersistentCollection {#93557 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93555 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106754
  +product: App\Entity\Product\Product {#93560
    #id: 11972
    #code: "IEEE00006846"
    #attributes: Doctrine\ORM\PersistentCollection {#93542 …}
    #variants: Doctrine\ORM\PersistentCollection {#93539 …}
    #options: Doctrine\ORM\PersistentCollection {#93535 …}
    #associations: Doctrine\ORM\PersistentCollection {#93537 …}
    #createdAt: DateTime @1751040111 {#93568
      date: 2025-06-27 18:01:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93547
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93553 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93588
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93560}
        #id: 42897
        #name: "IEEE/ISO/IEC 42010:2022"
        #slug: "ieee-iso-iec-42010-2022-ieee00006846-243624"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for the structure and expression of an architecture description (AD) for various entities, including software, systems, enterprises, systems of systems, families of systems, products (goods or services), product lines, service lines, technologies and business domains. This document distinguishes the architecture of an entity of interest from an AD expressing that architecture. Architectures are not the subject of this document. This document specifies requirements for use of the architectural concepts and their relationships as captured in an AD. It does not specify requirements for any entity of interest or its environment. This document specifies requirements for an architecture description framework (ADF), an architecture description language (ADL), architecture viewpoints and model kinds in order to usefully support the development and use of an AD. This document specifies conformance to the requirements for an AD, ADF, ADL, architecture viewpoint and model kind. This document does not specify the processes, architecting methods, models, notations, techniques or tools by which an AD is created, utilized or managed. This document does not specify any format or media for recording an AD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC International Standard for Software, systems and enterprise--Architecture description"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93551 …}
    #channels: Doctrine\ORM\PersistentCollection {#93544 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93549 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93546 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93561 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93531
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#93567
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#93566
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 74
    -documents: Doctrine\ORM\PersistentCollection {#93557 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93555 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93560
    #id: 11972
    #code: "IEEE00006846"
    #attributes: Doctrine\ORM\PersistentCollection {#93542 …}
    #variants: Doctrine\ORM\PersistentCollection {#93539 …}
    #options: Doctrine\ORM\PersistentCollection {#93535 …}
    #associations: Doctrine\ORM\PersistentCollection {#93537 …}
    #createdAt: DateTime @1751040111 {#93568
      date: 2025-06-27 18:01:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93547
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93553 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93588
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93560}
        #id: 42897
        #name: "IEEE/ISO/IEC 42010:2022"
        #slug: "ieee-iso-iec-42010-2022-ieee00006846-243624"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for the structure and expression of an architecture description (AD) for various entities, including software, systems, enterprises, systems of systems, families of systems, products (goods or services), product lines, service lines, technologies and business domains. This document distinguishes the architecture of an entity of interest from an AD expressing that architecture. Architectures are not the subject of this document. This document specifies requirements for use of the architectural concepts and their relationships as captured in an AD. It does not specify requirements for any entity of interest or its environment. This document specifies requirements for an architecture description framework (ADF), an architecture description language (ADL), architecture viewpoints and model kinds in order to usefully support the development and use of an AD. This document specifies conformance to the requirements for an AD, ADF, ADL, architecture viewpoint and model kind. This document does not specify the processes, architecting methods, models, notations, techniques or tools by which an AD is created, utilized or managed. This document does not specify any format or media for recording an AD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC International Standard for Software, systems and enterprise--Architecture description"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93551 …}
    #channels: Doctrine\ORM\PersistentCollection {#93544 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93549 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93546 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93561 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93531
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#93567
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#93566
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 74
    -documents: Doctrine\ORM\PersistentCollection {#93557 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93555 …}
  }
]

App\Twig\Components\ProductMostRecent {#106821
  +product: App\Entity\Product\Product {#93560
    #id: 11972
    #code: "IEEE00006846"
    #attributes: Doctrine\ORM\PersistentCollection {#93542 …}
    #variants: Doctrine\ORM\PersistentCollection {#93539 …}
    #options: Doctrine\ORM\PersistentCollection {#93535 …}
    #associations: Doctrine\ORM\PersistentCollection {#93537 …}
    #createdAt: DateTime @1751040111 {#93568
      date: 2025-06-27 18:01:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93547
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93553 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93588
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93560}
        #id: 42897
        #name: "IEEE/ISO/IEC 42010:2022"
        #slug: "ieee-iso-iec-42010-2022-ieee00006846-243624"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for the structure and expression of an architecture description (AD) for various entities, including software, systems, enterprises, systems of systems, families of systems, products (goods or services), product lines, service lines, technologies and business domains. This document distinguishes the architecture of an entity of interest from an AD expressing that architecture. Architectures are not the subject of this document. This document specifies requirements for use of the architectural concepts and their relationships as captured in an AD. It does not specify requirements for any entity of interest or its environment. This document specifies requirements for an architecture description framework (ADF), an architecture description language (ADL), architecture viewpoints and model kinds in order to usefully support the development and use of an AD. This document specifies conformance to the requirements for an AD, ADF, ADL, architecture viewpoint and model kind. This document does not specify the processes, architecting methods, models, notations, techniques or tools by which an AD is created, utilized or managed. This document does not specify any format or media for recording an AD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC International Standard for Software, systems and enterprise--Architecture description"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93551 …}
    #channels: Doctrine\ORM\PersistentCollection {#93544 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93549 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93546 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93561 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93531
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#93567
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#93566
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 74
    -documents: Doctrine\ORM\PersistentCollection {#93557 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93555 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106691
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#106672 …}
    #variants: Doctrine\ORM\PersistentCollection {#106669 …}
    #options: Doctrine\ORM\PersistentCollection {#106665 …}
    #associations: Doctrine\ORM\PersistentCollection {#106667 …}
    #createdAt: DateTime @1751039381 {#106658
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106671
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106682 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106892
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106691}
        #id: 38789
        #name: "IEEE/ISO/IEC 42010:2011"
        #slug: "ieee-iso-iec-42010-2011-ieee00005334-242597"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          ISO/IEC/IEEE 42010:2011 addresses the creation, analysis and sustainment of architectures of systems through the use of architecture descriptions. A conceptual model of architecture description is established. The required contents of an architecture description are specified. Architecture viewpoints, architecture frameworks and architecture description languages are introduced for codifying conventions and common practices of architecture description. The required content of architecture viewpoints, architecture frameworks and architecture description languages is specified. Annexes provide the motivation and background for key concepts and terminology and examples of applying ISO/IEC/IEEE 42010:2011.<br />\n
          \t\t\t\t<br />\n
          This International Standard specifies the manner in which architecture descriptions of systems are organized and expressed. This International Standard specifies architecture viewpoints, architecture frameworks and architecture description languages for use in architecture descriptions. This International Standard also provides motivations for terms and concepts used; presents guidance on specifying architecture viewpoints; and demonstrates the use of this International Standard with other standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Architecture description"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106680 …}
    #channels: Doctrine\ORM\PersistentCollection {#106674 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106678 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106676 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106689 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106698
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#106702
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#106656
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#106690
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#106687 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106685 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106907
  +product: App\Entity\Product\Product {#106691
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#106672 …}
    #variants: Doctrine\ORM\PersistentCollection {#106669 …}
    #options: Doctrine\ORM\PersistentCollection {#106665 …}
    #associations: Doctrine\ORM\PersistentCollection {#106667 …}
    #createdAt: DateTime @1751039381 {#106658
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106671
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106682 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106892
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106691}
        #id: 38789
        #name: "IEEE/ISO/IEC 42010:2011"
        #slug: "ieee-iso-iec-42010-2011-ieee00005334-242597"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          ISO/IEC/IEEE 42010:2011 addresses the creation, analysis and sustainment of architectures of systems through the use of architecture descriptions. A conceptual model of architecture description is established. The required contents of an architecture description are specified. Architecture viewpoints, architecture frameworks and architecture description languages are introduced for codifying conventions and common practices of architecture description. The required content of architecture viewpoints, architecture frameworks and architecture description languages is specified. Annexes provide the motivation and background for key concepts and terminology and examples of applying ISO/IEC/IEEE 42010:2011.<br />\n
          \t\t\t\t<br />\n
          This International Standard specifies the manner in which architecture descriptions of systems are organized and expressed. This International Standard specifies architecture viewpoints, architecture frameworks and architecture description languages for use in architecture descriptions. This International Standard also provides motivations for terms and concepts used; presents guidance on specifying architecture viewpoints; and demonstrates the use of this International Standard with other standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Architecture description"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106680 …}
    #channels: Doctrine\ORM\PersistentCollection {#106674 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106678 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106676 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106689 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106698
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#106702
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#106656
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#106690
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#106687 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106685 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106691
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#106672 …}
    #variants: Doctrine\ORM\PersistentCollection {#106669 …}
    #options: Doctrine\ORM\PersistentCollection {#106665 …}
    #associations: Doctrine\ORM\PersistentCollection {#106667 …}
    #createdAt: DateTime @1751039381 {#106658
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106671
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106682 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106892
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106691}
        #id: 38789
        #name: "IEEE/ISO/IEC 42010:2011"
        #slug: "ieee-iso-iec-42010-2011-ieee00005334-242597"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          ISO/IEC/IEEE 42010:2011 addresses the creation, analysis and sustainment of architectures of systems through the use of architecture descriptions. A conceptual model of architecture description is established. The required contents of an architecture description are specified. Architecture viewpoints, architecture frameworks and architecture description languages are introduced for codifying conventions and common practices of architecture description. The required content of architecture viewpoints, architecture frameworks and architecture description languages is specified. Annexes provide the motivation and background for key concepts and terminology and examples of applying ISO/IEC/IEEE 42010:2011.<br />\n
          \t\t\t\t<br />\n
          This International Standard specifies the manner in which architecture descriptions of systems are organized and expressed. This International Standard specifies architecture viewpoints, architecture frameworks and architecture description languages for use in architecture descriptions. This International Standard also provides motivations for terms and concepts used; presents guidance on specifying architecture viewpoints; and demonstrates the use of this International Standard with other standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Architecture description"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106680 …}
    #channels: Doctrine\ORM\PersistentCollection {#106674 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106678 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106676 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106689 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106698
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#106702
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#106656
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#106690
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#106687 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106685 …}
  }
]

App\Twig\Components\ProductMostRecent {#106959
  +product: App\Entity\Product\Product {#106691
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#106672 …}
    #variants: Doctrine\ORM\PersistentCollection {#106669 …}
    #options: Doctrine\ORM\PersistentCollection {#106665 …}
    #associations: Doctrine\ORM\PersistentCollection {#106667 …}
    #createdAt: DateTime @1751039381 {#106658
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106671
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106682 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106892
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106691}
        #id: 38789
        #name: "IEEE/ISO/IEC 42010:2011"
        #slug: "ieee-iso-iec-42010-2011-ieee00005334-242597"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          ISO/IEC/IEEE 42010:2011 addresses the creation, analysis and sustainment of architectures of systems through the use of architecture descriptions. A conceptual model of architecture description is established. The required contents of an architecture description are specified. Architecture viewpoints, architecture frameworks and architecture description languages are introduced for codifying conventions and common practices of architecture description. The required content of architecture viewpoints, architecture frameworks and architecture description languages is specified. Annexes provide the motivation and background for key concepts and terminology and examples of applying ISO/IEC/IEEE 42010:2011.<br />\n
          \t\t\t\t<br />\n
          This International Standard specifies the manner in which architecture descriptions of systems are organized and expressed. This International Standard specifies architecture viewpoints, architecture frameworks and architecture description languages for use in architecture descriptions. This International Standard also provides motivations for terms and concepts used; presents guidance on specifying architecture viewpoints; and demonstrates the use of this International Standard with other standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Systems and software engineering -- Architecture description"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106680 …}
    #channels: Doctrine\ORM\PersistentCollection {#106674 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106678 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106676 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106689 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106698
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#106702
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#106656
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#106690
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#106687 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106685 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039009 {#7274
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.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: 36425
        #name: "IEEE/ISO/IEC 42010:2007"
        #slug: "ieee-iso-iec-42010-2007-ieee00004228-242006"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This recommended practice addresses the activities of the creation, analysis, and sustainment<br />\n
          of architectures of software-intensive systems, and the recording of such architectures in<br />\n
          terms of<br />\n
          architectural descriptions<br />\n
          . A conceptual framework for architectural description is established.<br />\n
          The content of an architectural description is defined. Annexes provide the rationale for key<br />\n
          concepts and terminology, the relationships to other standards, and examples of usage.<br />\n
          \t\t\t\t<br />\n
          This recommended practice addresses the architectural description of software-intensive systems. A<br />\n
          software-intensive system<br />\n
          is any system where software contributes essential influences to the design,<br />\n
          construction, deployment, and evolution of the system as a whole.<br />\n
          The scope of this recommended practice encompasses those products of system development that capture<br />\n
          architectural information. This includes architectural descriptions that are used for the following:<br />\n
          a) Expression of the system and its evolution<br />\n
          b) Communication among the system stakeholders<br />\n
          c) Evaluation and comparison of architectures in a consistent manner<br />\n
          d) Planning, managing, and executing the activities of system development<br />\n
          e) Expression of the persistent characteristics and supporting principles of a system to guide acceptable<br />\n
          change<br />\n
          f) Verification of a system implementation's compliance with an architectural description<br />\n
          g) Recording contributions to the body of knowledge of software-intensive systems architecture<br />\n
          The purpose of this recommended practice is to facilitate the expression and communication of architectures<br />\n
          and thereby lay a foundation for quality and cost gains through standardization of elements and practices for<br />\n
          architectural description.<br />\n
          Despite significant efforts to improve engineering practices and technologies, software-intensive systems<br />\n
          continue to present formidable risks and difficulties in their design, construction, deployment, and evolution.<br />\n
          Recent attempts to address these difficulties have focused on the earliest period of design decision-making<br />\n
          and evaluation, increasingly referred to as the<br />\n
          architectural level<br />\n
          of system development. The phrases<br />\n
          archi-tectural<br />\n
          level<br />\n
          and<br />\n
          architecture<br />\n
          are widely, if imprecisely, used. Their use reflects acceptance of an architectural<br />\n
          metaphor in the analysis and development of software-intensive systems. A key premise of this<br />\n
          metaphor is that important decisions may be made early in system development in a manner similar to the<br />\n
          early decision-making found in the development of civil architecture projects.<br />\n
          Many innovations are resulting from this attention to the architectural level, among them architectural<br />\n
          description languages and associated tools and environments; architectural frameworks, models, and<br />\n
          patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these<br />\n
          efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of<br />\n
          a recommended practice to codify their common elements.<br />\n
          These innovations are occurring, and maturing, rapidly within many research and application communities,<br />\n
          and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the<br />\n
          importance of the<br />\n
          architectural level of systems development<br />\n
          , and that that level consists of early decisionmaking<br />\n
          about overall design structure, goals, requirements, and development strategies. However, there has<br />\n
          not yet emerged any reliable consensus on a precise definition of a system's<br />\n
          , i.e., how it should<br />\n
          be described, what uses such a description may serve, or where and when it should be defined. The boundaries<br />\n
          and relationships between architectural trends and practices, and other practices; and between architectural<br />\n
          technology and other technology, are not yet widely recognized.<br />\n
          In such situations, progress often depends on mediating influences. Potential adopters of architectural<br />\n
          practices and technology need a frame of reference within which to address implementation and adoption<br />\n
          decisions. Technology developers need a frame of reference within which to communicate the motivating<br />\n
          concepts of their technology, and to accumulate and appreciate feedback from early adoption.<br />\n
          To these ends, this recommended practice is intended to reflect generally accepted trends in practices for<br />\n
          architectural description and to provide a technical framework for further evolution in this area.<br />\n
          Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future<br />\n
          developments in system architectural technology can be deployed. This recommended practice codifies<br />\n
          those elements on which there is consensus; specifically the use of multiple views, reusable specifications<br />\n
          for models within views, and the relation of architecture to system context.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems and Software Engineering - Recommended Practice for Architectural Description of Software-Intensive Systems"
        -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: "42010"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#107023
  +product: App\Entity\Product\Product {#7310
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039009 {#7274
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.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: 36425
        #name: "IEEE/ISO/IEC 42010:2007"
        #slug: "ieee-iso-iec-42010-2007-ieee00004228-242006"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This recommended practice addresses the activities of the creation, analysis, and sustainment<br />\n
          of architectures of software-intensive systems, and the recording of such architectures in<br />\n
          terms of<br />\n
          architectural descriptions<br />\n
          . A conceptual framework for architectural description is established.<br />\n
          The content of an architectural description is defined. Annexes provide the rationale for key<br />\n
          concepts and terminology, the relationships to other standards, and examples of usage.<br />\n
          \t\t\t\t<br />\n
          This recommended practice addresses the architectural description of software-intensive systems. A<br />\n
          software-intensive system<br />\n
          is any system where software contributes essential influences to the design,<br />\n
          construction, deployment, and evolution of the system as a whole.<br />\n
          The scope of this recommended practice encompasses those products of system development that capture<br />\n
          architectural information. This includes architectural descriptions that are used for the following:<br />\n
          a) Expression of the system and its evolution<br />\n
          b) Communication among the system stakeholders<br />\n
          c) Evaluation and comparison of architectures in a consistent manner<br />\n
          d) Planning, managing, and executing the activities of system development<br />\n
          e) Expression of the persistent characteristics and supporting principles of a system to guide acceptable<br />\n
          change<br />\n
          f) Verification of a system implementation's compliance with an architectural description<br />\n
          g) Recording contributions to the body of knowledge of software-intensive systems architecture<br />\n
          The purpose of this recommended practice is to facilitate the expression and communication of architectures<br />\n
          and thereby lay a foundation for quality and cost gains through standardization of elements and practices for<br />\n
          architectural description.<br />\n
          Despite significant efforts to improve engineering practices and technologies, software-intensive systems<br />\n
          continue to present formidable risks and difficulties in their design, construction, deployment, and evolution.<br />\n
          Recent attempts to address these difficulties have focused on the earliest period of design decision-making<br />\n
          and evaluation, increasingly referred to as the<br />\n
          architectural level<br />\n
          of system development. The phrases<br />\n
          archi-tectural<br />\n
          level<br />\n
          and<br />\n
          architecture<br />\n
          are widely, if imprecisely, used. Their use reflects acceptance of an architectural<br />\n
          metaphor in the analysis and development of software-intensive systems. A key premise of this<br />\n
          metaphor is that important decisions may be made early in system development in a manner similar to the<br />\n
          early decision-making found in the development of civil architecture projects.<br />\n
          Many innovations are resulting from this attention to the architectural level, among them architectural<br />\n
          description languages and associated tools and environments; architectural frameworks, models, and<br />\n
          patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these<br />\n
          efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of<br />\n
          a recommended practice to codify their common elements.<br />\n
          These innovations are occurring, and maturing, rapidly within many research and application communities,<br />\n
          and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the<br />\n
          importance of the<br />\n
          architectural level of systems development<br />\n
          , and that that level consists of early decisionmaking<br />\n
          about overall design structure, goals, requirements, and development strategies. However, there has<br />\n
          not yet emerged any reliable consensus on a precise definition of a system's<br />\n
          , i.e., how it should<br />\n
          be described, what uses such a description may serve, or where and when it should be defined. The boundaries<br />\n
          and relationships between architectural trends and practices, and other practices; and between architectural<br />\n
          technology and other technology, are not yet widely recognized.<br />\n
          In such situations, progress often depends on mediating influences. Potential adopters of architectural<br />\n
          practices and technology need a frame of reference within which to address implementation and adoption<br />\n
          decisions. Technology developers need a frame of reference within which to communicate the motivating<br />\n
          concepts of their technology, and to accumulate and appreciate feedback from early adoption.<br />\n
          To these ends, this recommended practice is intended to reflect generally accepted trends in practices for<br />\n
          architectural description and to provide a technical framework for further evolution in this area.<br />\n
          Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future<br />\n
          developments in system architectural technology can be deployed. This recommended practice codifies<br />\n
          those elements on which there is consensus; specifically the use of multiple views, reusable specifications<br />\n
          for models within views, and the relation of architecture to system context.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems and Software Engineering - Recommended Practice for Architectural Description of Software-Intensive Systems"
        -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: "42010"
    -bookCollection: ""
    -pageCount: 24
    -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: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039009 {#7274
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.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: 36425
        #name: "IEEE/ISO/IEC 42010:2007"
        #slug: "ieee-iso-iec-42010-2007-ieee00004228-242006"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This recommended practice addresses the activities of the creation, analysis, and sustainment<br />\n
          of architectures of software-intensive systems, and the recording of such architectures in<br />\n
          terms of<br />\n
          architectural descriptions<br />\n
          . A conceptual framework for architectural description is established.<br />\n
          The content of an architectural description is defined. Annexes provide the rationale for key<br />\n
          concepts and terminology, the relationships to other standards, and examples of usage.<br />\n
          \t\t\t\t<br />\n
          This recommended practice addresses the architectural description of software-intensive systems. A<br />\n
          software-intensive system<br />\n
          is any system where software contributes essential influences to the design,<br />\n
          construction, deployment, and evolution of the system as a whole.<br />\n
          The scope of this recommended practice encompasses those products of system development that capture<br />\n
          architectural information. This includes architectural descriptions that are used for the following:<br />\n
          a) Expression of the system and its evolution<br />\n
          b) Communication among the system stakeholders<br />\n
          c) Evaluation and comparison of architectures in a consistent manner<br />\n
          d) Planning, managing, and executing the activities of system development<br />\n
          e) Expression of the persistent characteristics and supporting principles of a system to guide acceptable<br />\n
          change<br />\n
          f) Verification of a system implementation's compliance with an architectural description<br />\n
          g) Recording contributions to the body of knowledge of software-intensive systems architecture<br />\n
          The purpose of this recommended practice is to facilitate the expression and communication of architectures<br />\n
          and thereby lay a foundation for quality and cost gains through standardization of elements and practices for<br />\n
          architectural description.<br />\n
          Despite significant efforts to improve engineering practices and technologies, software-intensive systems<br />\n
          continue to present formidable risks and difficulties in their design, construction, deployment, and evolution.<br />\n
          Recent attempts to address these difficulties have focused on the earliest period of design decision-making<br />\n
          and evaluation, increasingly referred to as the<br />\n
          architectural level<br />\n
          of system development. The phrases<br />\n
          archi-tectural<br />\n
          level<br />\n
          and<br />\n
          architecture<br />\n
          are widely, if imprecisely, used. Their use reflects acceptance of an architectural<br />\n
          metaphor in the analysis and development of software-intensive systems. A key premise of this<br />\n
          metaphor is that important decisions may be made early in system development in a manner similar to the<br />\n
          early decision-making found in the development of civil architecture projects.<br />\n
          Many innovations are resulting from this attention to the architectural level, among them architectural<br />\n
          description languages and associated tools and environments; architectural frameworks, models, and<br />\n
          patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these<br />\n
          efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of<br />\n
          a recommended practice to codify their common elements.<br />\n
          These innovations are occurring, and maturing, rapidly within many research and application communities,<br />\n
          and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the<br />\n
          importance of the<br />\n
          architectural level of systems development<br />\n
          , and that that level consists of early decisionmaking<br />\n
          about overall design structure, goals, requirements, and development strategies. However, there has<br />\n
          not yet emerged any reliable consensus on a precise definition of a system's<br />\n
          , i.e., how it should<br />\n
          be described, what uses such a description may serve, or where and when it should be defined. The boundaries<br />\n
          and relationships between architectural trends and practices, and other practices; and between architectural<br />\n
          technology and other technology, are not yet widely recognized.<br />\n
          In such situations, progress often depends on mediating influences. Potential adopters of architectural<br />\n
          practices and technology need a frame of reference within which to address implementation and adoption<br />\n
          decisions. Technology developers need a frame of reference within which to communicate the motivating<br />\n
          concepts of their technology, and to accumulate and appreciate feedback from early adoption.<br />\n
          To these ends, this recommended practice is intended to reflect generally accepted trends in practices for<br />\n
          architectural description and to provide a technical framework for further evolution in this area.<br />\n
          Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future<br />\n
          developments in system architectural technology can be deployed. This recommended practice codifies<br />\n
          those elements on which there is consensus; specifically the use of multiple views, reusable specifications<br />\n
          for models within views, and the relation of architecture to system context.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems and Software Engineering - Recommended Practice for Architectural Description of Software-Intensive Systems"
        -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: "42010"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#107050
  +product: App\Entity\Product\Product {#7310
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039009 {#7274
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.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: 36425
        #name: "IEEE/ISO/IEC 42010:2007"
        #slug: "ieee-iso-iec-42010-2007-ieee00004228-242006"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This recommended practice addresses the activities of the creation, analysis, and sustainment<br />\n
          of architectures of software-intensive systems, and the recording of such architectures in<br />\n
          terms of<br />\n
          architectural descriptions<br />\n
          . A conceptual framework for architectural description is established.<br />\n
          The content of an architectural description is defined. Annexes provide the rationale for key<br />\n
          concepts and terminology, the relationships to other standards, and examples of usage.<br />\n
          \t\t\t\t<br />\n
          This recommended practice addresses the architectural description of software-intensive systems. A<br />\n
          software-intensive system<br />\n
          is any system where software contributes essential influences to the design,<br />\n
          construction, deployment, and evolution of the system as a whole.<br />\n
          The scope of this recommended practice encompasses those products of system development that capture<br />\n
          architectural information. This includes architectural descriptions that are used for the following:<br />\n
          a) Expression of the system and its evolution<br />\n
          b) Communication among the system stakeholders<br />\n
          c) Evaluation and comparison of architectures in a consistent manner<br />\n
          d) Planning, managing, and executing the activities of system development<br />\n
          e) Expression of the persistent characteristics and supporting principles of a system to guide acceptable<br />\n
          change<br />\n
          f) Verification of a system implementation's compliance with an architectural description<br />\n
          g) Recording contributions to the body of knowledge of software-intensive systems architecture<br />\n
          The purpose of this recommended practice is to facilitate the expression and communication of architectures<br />\n
          and thereby lay a foundation for quality and cost gains through standardization of elements and practices for<br />\n
          architectural description.<br />\n
          Despite significant efforts to improve engineering practices and technologies, software-intensive systems<br />\n
          continue to present formidable risks and difficulties in their design, construction, deployment, and evolution.<br />\n
          Recent attempts to address these difficulties have focused on the earliest period of design decision-making<br />\n
          and evaluation, increasingly referred to as the<br />\n
          architectural level<br />\n
          of system development. The phrases<br />\n
          archi-tectural<br />\n
          level<br />\n
          and<br />\n
          architecture<br />\n
          are widely, if imprecisely, used. Their use reflects acceptance of an architectural<br />\n
          metaphor in the analysis and development of software-intensive systems. A key premise of this<br />\n
          metaphor is that important decisions may be made early in system development in a manner similar to the<br />\n
          early decision-making found in the development of civil architecture projects.<br />\n
          Many innovations are resulting from this attention to the architectural level, among them architectural<br />\n
          description languages and associated tools and environments; architectural frameworks, models, and<br />\n
          patterns; and techniques for architectural analysis, evaluation, and architecture-based reuse. While these<br />\n
          efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of<br />\n
          a recommended practice to codify their common elements.<br />\n
          These innovations are occurring, and maturing, rapidly within many research and application communities,<br />\n
          and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the<br />\n
          importance of the<br />\n
          architectural level of systems development<br />\n
          , and that that level consists of early decisionmaking<br />\n
          about overall design structure, goals, requirements, and development strategies. However, there has<br />\n
          not yet emerged any reliable consensus on a precise definition of a system's<br />\n
          , i.e., how it should<br />\n
          be described, what uses such a description may serve, or where and when it should be defined. The boundaries<br />\n
          and relationships between architectural trends and practices, and other practices; and between architectural<br />\n
          technology and other technology, are not yet widely recognized.<br />\n
          In such situations, progress often depends on mediating influences. Potential adopters of architectural<br />\n
          practices and technology need a frame of reference within which to address implementation and adoption<br />\n
          decisions. Technology developers need a frame of reference within which to communicate the motivating<br />\n
          concepts of their technology, and to accumulate and appreciate feedback from early adoption.<br />\n
          To these ends, this recommended practice is intended to reflect generally accepted trends in practices for<br />\n
          architectural description and to provide a technical framework for further evolution in this area.<br />\n
          Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future<br />\n
          developments in system architectural technology can be deployed. This recommended practice codifies<br />\n
          those elements on which there is consensus; specifically the use of multiple views, reusable specifications<br />\n
          for models within views, and the relation of architecture to system context.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC Standard for Systems and Software Engineering - Recommended Practice for Architectural Description of Software-Intensive Systems"
        -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: "42010"
    -bookCollection: ""
    -pageCount: 24
    -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 {#128449
    #id: 9459
    #code: "IEEE00002375"
    #attributes: Doctrine\ORM\PersistentCollection {#128473 …}
    #variants: Doctrine\ORM\PersistentCollection {#128471 …}
    #options: Doctrine\ORM\PersistentCollection {#128466 …}
    #associations: Doctrine\ORM\PersistentCollection {#128469 …}
    #createdAt: DateTime @1751038281 {#128462
      date: 2025-06-27 17:31:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128455
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128484 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128449}
        #id: 32845
        #name: "IEEE 12207.0:1996"
        #slug: "ieee-12207-0-1996-ieee00002375-241111"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 12207:2008(E) (IEEE Std 12207-2008). ISO/IEC 12207 provides a common framework for developing and managing software. IEEE/EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Alliance (EIA) as formulated by a joint project of the two organizations. IEEE/EIA 12207.0 contains concepts and guidelines to foster better understanding and application of the standard. Thus this standard provides industry a basis for software practices that would be usable for both national and international business.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes software portion of firmware. The supplement will contain the in sum country foreward including compliance methodology, software life cycle process objectives, software life cycle data objectives, key concepts of understanding 12207, and errata. The project will contribute to a suite of standards consisting of three parts: ISO 12207, 12207.1, and 12207.2.<br />\n
          The base document provides a consistent framework and related methods for the supplier and acquirer of software to establish, understand, and communicate between the acquirer and the supplier their respective responsibilities and the requirements for the software. The supplement will add: (1) enhance compliance approach to fit a variety of situations. (2) provide clarification to the intent of ISO 12207, (3) provide additions to meet the conventions of the Software Engineering Standards for process standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/EIA Standard - Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology -- Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128482 …}
    #channels: Doctrine\ORM\PersistentCollection {#128475 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128479 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128477 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128489 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128448
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128497
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @891295200 {#128468
      date: 1998-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207.0"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#128488 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128486 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#128541
  +product: App\Entity\Product\Product {#128449
    #id: 9459
    #code: "IEEE00002375"
    #attributes: Doctrine\ORM\PersistentCollection {#128473 …}
    #variants: Doctrine\ORM\PersistentCollection {#128471 …}
    #options: Doctrine\ORM\PersistentCollection {#128466 …}
    #associations: Doctrine\ORM\PersistentCollection {#128469 …}
    #createdAt: DateTime @1751038281 {#128462
      date: 2025-06-27 17:31:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128455
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128484 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128449}
        #id: 32845
        #name: "IEEE 12207.0:1996"
        #slug: "ieee-12207-0-1996-ieee00002375-241111"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 12207:2008(E) (IEEE Std 12207-2008). ISO/IEC 12207 provides a common framework for developing and managing software. IEEE/EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Alliance (EIA) as formulated by a joint project of the two organizations. IEEE/EIA 12207.0 contains concepts and guidelines to foster better understanding and application of the standard. Thus this standard provides industry a basis for software practices that would be usable for both national and international business.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes software portion of firmware. The supplement will contain the in sum country foreward including compliance methodology, software life cycle process objectives, software life cycle data objectives, key concepts of understanding 12207, and errata. The project will contribute to a suite of standards consisting of three parts: ISO 12207, 12207.1, and 12207.2.<br />\n
          The base document provides a consistent framework and related methods for the supplier and acquirer of software to establish, understand, and communicate between the acquirer and the supplier their respective responsibilities and the requirements for the software. The supplement will add: (1) enhance compliance approach to fit a variety of situations. (2) provide clarification to the intent of ISO 12207, (3) provide additions to meet the conventions of the Software Engineering Standards for process standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/EIA Standard - Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology -- Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128482 …}
    #channels: Doctrine\ORM\PersistentCollection {#128475 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128479 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128477 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128489 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128448
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128497
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @891295200 {#128468
      date: 1998-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207.0"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#128488 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128486 …}
  }
  +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 {#128449
    #id: 9459
    #code: "IEEE00002375"
    #attributes: Doctrine\ORM\PersistentCollection {#128473 …}
    #variants: Doctrine\ORM\PersistentCollection {#128471 …}
    #options: Doctrine\ORM\PersistentCollection {#128466 …}
    #associations: Doctrine\ORM\PersistentCollection {#128469 …}
    #createdAt: DateTime @1751038281 {#128462
      date: 2025-06-27 17:31:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128455
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128484 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128449}
        #id: 32845
        #name: "IEEE 12207.0:1996"
        #slug: "ieee-12207-0-1996-ieee00002375-241111"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 12207:2008(E) (IEEE Std 12207-2008). ISO/IEC 12207 provides a common framework for developing and managing software. IEEE/EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Alliance (EIA) as formulated by a joint project of the two organizations. IEEE/EIA 12207.0 contains concepts and guidelines to foster better understanding and application of the standard. Thus this standard provides industry a basis for software practices that would be usable for both national and international business.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes software portion of firmware. The supplement will contain the in sum country foreward including compliance methodology, software life cycle process objectives, software life cycle data objectives, key concepts of understanding 12207, and errata. The project will contribute to a suite of standards consisting of three parts: ISO 12207, 12207.1, and 12207.2.<br />\n
          The base document provides a consistent framework and related methods for the supplier and acquirer of software to establish, understand, and communicate between the acquirer and the supplier their respective responsibilities and the requirements for the software. The supplement will add: (1) enhance compliance approach to fit a variety of situations. (2) provide clarification to the intent of ISO 12207, (3) provide additions to meet the conventions of the Software Engineering Standards for process standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/EIA Standard - Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology -- Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128482 …}
    #channels: Doctrine\ORM\PersistentCollection {#128475 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128479 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128477 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128489 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128448
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128497
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @891295200 {#128468
      date: 1998-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207.0"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#128488 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128486 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#128577
  +product: App\Entity\Product\Product {#128449
    #id: 9459
    #code: "IEEE00002375"
    #attributes: Doctrine\ORM\PersistentCollection {#128473 …}
    #variants: Doctrine\ORM\PersistentCollection {#128471 …}
    #options: Doctrine\ORM\PersistentCollection {#128466 …}
    #associations: Doctrine\ORM\PersistentCollection {#128469 …}
    #createdAt: DateTime @1751038281 {#128462
      date: 2025-06-27 17:31:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128455
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128484 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128449}
        #id: 32845
        #name: "IEEE 12207.0:1996"
        #slug: "ieee-12207-0-1996-ieee00002375-241111"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 12207:2008(E) (IEEE Std 12207-2008). ISO/IEC 12207 provides a common framework for developing and managing software. IEEE/EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Alliance (EIA) as formulated by a joint project of the two organizations. IEEE/EIA 12207.0 contains concepts and guidelines to foster better understanding and application of the standard. Thus this standard provides industry a basis for software practices that would be usable for both national and international business.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes software portion of firmware. The supplement will contain the in sum country foreward including compliance methodology, software life cycle process objectives, software life cycle data objectives, key concepts of understanding 12207, and errata. The project will contribute to a suite of standards consisting of three parts: ISO 12207, 12207.1, and 12207.2.<br />\n
          The base document provides a consistent framework and related methods for the supplier and acquirer of software to establish, understand, and communicate between the acquirer and the supplier their respective responsibilities and the requirements for the software. The supplement will add: (1) enhance compliance approach to fit a variety of situations. (2) provide clarification to the intent of ISO 12207, (3) provide additions to meet the conventions of the Software Engineering Standards for process standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/EIA Standard - Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology -- Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128482 …}
    #channels: Doctrine\ORM\PersistentCollection {#128475 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128479 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128477 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128489 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128448
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128497
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @891295200 {#128468
      date: 1998-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207.0"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#128488 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128486 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#128449
    #id: 9459
    #code: "IEEE00002375"
    #attributes: Doctrine\ORM\PersistentCollection {#128473 …}
    #variants: Doctrine\ORM\PersistentCollection {#128471 …}
    #options: Doctrine\ORM\PersistentCollection {#128466 …}
    #associations: Doctrine\ORM\PersistentCollection {#128469 …}
    #createdAt: DateTime @1751038281 {#128462
      date: 2025-06-27 17:31:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128455
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128484 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128449}
        #id: 32845
        #name: "IEEE 12207.0:1996"
        #slug: "ieee-12207-0-1996-ieee00002375-241111"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 12207:2008(E) (IEEE Std 12207-2008). ISO/IEC 12207 provides a common framework for developing and managing software. IEEE/EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Alliance (EIA) as formulated by a joint project of the two organizations. IEEE/EIA 12207.0 contains concepts and guidelines to foster better understanding and application of the standard. Thus this standard provides industry a basis for software practices that would be usable for both national and international business.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes software portion of firmware. The supplement will contain the in sum country foreward including compliance methodology, software life cycle process objectives, software life cycle data objectives, key concepts of understanding 12207, and errata. The project will contribute to a suite of standards consisting of three parts: ISO 12207, 12207.1, and 12207.2.<br />\n
          The base document provides a consistent framework and related methods for the supplier and acquirer of software to establish, understand, and communicate between the acquirer and the supplier their respective responsibilities and the requirements for the software. The supplement will add: (1) enhance compliance approach to fit a variety of situations. (2) provide clarification to the intent of ISO 12207, (3) provide additions to meet the conventions of the Software Engineering Standards for process standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/EIA Standard - Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology -- Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128482 …}
    #channels: Doctrine\ORM\PersistentCollection {#128475 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128479 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128477 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128489 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128448
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128497
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @891295200 {#128468
      date: 1998-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207.0"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#128488 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128486 …}
  }
]

App\Twig\Components\ProductMostRecent {#128655
  +product: App\Entity\Product\Product {#128449
    #id: 9459
    #code: "IEEE00002375"
    #attributes: Doctrine\ORM\PersistentCollection {#128473 …}
    #variants: Doctrine\ORM\PersistentCollection {#128471 …}
    #options: Doctrine\ORM\PersistentCollection {#128466 …}
    #associations: Doctrine\ORM\PersistentCollection {#128469 …}
    #createdAt: DateTime @1751038281 {#128462
      date: 2025-06-27 17:31:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128455
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128484 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128449}
        #id: 32845
        #name: "IEEE 12207.0:1996"
        #slug: "ieee-12207-0-1996-ieee00002375-241111"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by 12207:2008(E) (IEEE Std 12207-2008). ISO/IEC 12207 provides a common framework for developing and managing software. IEEE/EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Alliance (EIA) as formulated by a joint project of the two organizations. IEEE/EIA 12207.0 contains concepts and guidelines to foster better understanding and application of the standard. Thus this standard provides industry a basis for software practices that would be usable for both national and international business.<br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes software portion of firmware. The supplement will contain the in sum country foreward including compliance methodology, software life cycle process objectives, software life cycle data objectives, key concepts of understanding 12207, and errata. The project will contribute to a suite of standards consisting of three parts: ISO 12207, 12207.1, and 12207.2.<br />\n
          The base document provides a consistent framework and related methods for the supplier and acquirer of software to establish, understand, and communicate between the acquirer and the supplier their respective responsibilities and the requirements for the software. The supplement will add: (1) enhance compliance approach to fit a variety of situations. (2) provide clarification to the intent of ISO 12207, (3) provide additions to meet the conventions of the Software Engineering Standards for process standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/EIA Standard - Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology -- Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128482 …}
    #channels: Doctrine\ORM\PersistentCollection {#128475 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128479 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128477 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128489 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128448
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128497
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @891295200 {#128468
      date: 1998-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207.0"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#128488 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128486 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}