GET https://dev.normadoc.fr/_partial/cart/summary?template=%40SyliusShop%2FCart%2F_widget.html.twig

Response
200 OK
IP
216.73.216.131
Profiled on
Token
9b3633

Components

3 Twig Components
5 Render Count
3 ms Render Time
74.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		2 0.63ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		2 1.72ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.22ms

Render calls

ProductState App\Twig\Components\ProductState 68.0 MiB 0.34 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751038212 {#7536
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7535
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 32505
        #name: "IEEE 1471:2000"
        #slug: "ieee-1471-2000-ieee00002187-241026"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
          An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#7530
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#7531
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#7521
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#95003
  +product: App\Entity\Product\Product {#7519
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751038212 {#7536
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7535
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 32505
        #name: "IEEE 1471:2000"
        #slug: "ieee-1471-2000-ieee00002187-241026"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
          An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#7530
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#7531
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#7521
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 68.0 MiB 0.22 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751038212 {#7536
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7535
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 32505
        #name: "IEEE 1471:2000"
        #slug: "ieee-1471-2000-ieee00002187-241026"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
          An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#7530
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#7531
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#7521
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#95183
  +product: App\Entity\Product\Product {#7519
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751038212 {#7536
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7535
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 32505
        #name: "IEEE 1471:2000"
        #slug: "ieee-1471-2000-ieee00002187-241026"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
          An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#7530
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#7531
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#7521
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 68.0 MiB 0.73 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751038212 {#7536
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7535
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 32505
        #name: "IEEE 1471:2000"
        #slug: "ieee-1471-2000-ieee00002187-241026"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
          An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#7530
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#7531
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#7521
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#95258
  +product: App\Entity\Product\Product {#7519
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751038212 {#7536
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7535
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 32505
        #name: "IEEE 1471:2000"
        #slug: "ieee-1471-2000-ieee00002187-241026"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
          An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#7530
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#7531
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#7521
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 74.0 MiB 0.29 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751038212 {#7536
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7535
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 32505
        #name: "IEEE 1471:2000"
        #slug: "ieee-1471-2000-ieee00002187-241026"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
          An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#7530
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#7531
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#7521
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#102197
  +product: App\Entity\Product\Product {#7519
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751038212 {#7536
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7535
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 32505
        #name: "IEEE 1471:2000"
        #slug: "ieee-1471-2000-ieee00002187-241026"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
          An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#7530
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#7531
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#7521
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 74.0 MiB 0.99 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751038212 {#7536
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7535
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 32505
        #name: "IEEE 1471:2000"
        #slug: "ieee-1471-2000-ieee00002187-241026"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
          An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#7530
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#7531
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#7521
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#102281
  +product: App\Entity\Product\Product {#7519
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751038212 {#7536
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7535
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 32505
        #name: "IEEE 1471:2000"
        #slug: "ieee-1471-2000-ieee00002187-241026"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
          An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#7530
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#7531
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#7521
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}