GET https://dev.normadoc.fr/_partial/product/IEEE00005334/features

Response
200 OK
IP
216.73.216.149
Profiled on
Token
8f51de

Components

3 Twig Components
11 Render Count
7 ms Render Time
160.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		5 2.70ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		5 3.77ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.50ms

Render calls

ProductState App\Twig\Components\ProductState 160.0 MiB 1.94 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039381 {#7274
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#7292
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#7316
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#93076
  +product: App\Entity\Product\Product {#7311
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039381 {#7274
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#7292
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#7316
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 160.0 MiB 0.50 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039381 {#7274
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#7292
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#7316
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93247
  +product: App\Entity\Product\Product {#7311
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039381 {#7274
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#7292
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#7316
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 160.0 MiB 1.11 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039381 {#7274
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#7292
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#7316
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93322
  +product: App\Entity\Product\Product {#7311
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039381 {#7274
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#7292
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#7316
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 160.0 MiB 0.20 ms
Input props 
[
  "product" => App\Entity\Product\Product {#106749
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#106730 …}
    #variants: Doctrine\ORM\PersistentCollection {#106727 …}
    #options: Doctrine\ORM\PersistentCollection {#106723 …}
    #associations: Doctrine\ORM\PersistentCollection {#106725 …}
    #createdAt: DateTime @1751038212 {#106756
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#106729
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106740 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106779
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106749}
        #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 {#106738 …}
    #channels: Doctrine\ORM\PersistentCollection {#106732 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106736 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106734 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#106716
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106755
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#106754
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#106748
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#106745 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106743 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#106763
  +product: App\Entity\Product\Product {#106749
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#106730 …}
    #variants: Doctrine\ORM\PersistentCollection {#106727 …}
    #options: Doctrine\ORM\PersistentCollection {#106723 …}
    #associations: Doctrine\ORM\PersistentCollection {#106725 …}
    #createdAt: DateTime @1751038212 {#106756
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#106729
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106740 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106779
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106749}
        #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 {#106738 …}
    #channels: Doctrine\ORM\PersistentCollection {#106732 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106736 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106734 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#106716
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106755
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#106754
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#106748
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#106745 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106743 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 160.0 MiB 0.72 ms
Input props 
[
  "product" => App\Entity\Product\Product {#106749
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#106730 …}
    #variants: Doctrine\ORM\PersistentCollection {#106727 …}
    #options: Doctrine\ORM\PersistentCollection {#106723 …}
    #associations: Doctrine\ORM\PersistentCollection {#106725 …}
    #createdAt: DateTime @1751038212 {#106756
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#106729
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106740 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106779
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106749}
        #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 {#106738 …}
    #channels: Doctrine\ORM\PersistentCollection {#106732 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106736 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106734 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#106716
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106755
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#106754
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#106748
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#106745 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106743 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#106864
  +product: App\Entity\Product\Product {#106749
    #id: 9374
    #code: "IEEE00002187"
    #attributes: Doctrine\ORM\PersistentCollection {#106730 …}
    #variants: Doctrine\ORM\PersistentCollection {#106727 …}
    #options: Doctrine\ORM\PersistentCollection {#106723 …}
    #associations: Doctrine\ORM\PersistentCollection {#106725 …}
    #createdAt: DateTime @1751038212 {#106756
      date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#106729
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106740 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106779
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106749}
        #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 {#106738 …}
    #channels: Doctrine\ORM\PersistentCollection {#106732 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106736 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106734 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106747 …}
    -apiLastModifiedAt: DateTime @1745791200 {#106716
      date: 2025-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106755
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @971042400 {#106754
      date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1315519200 {#106748
      date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1471"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#106745 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106743 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 160.0 MiB 0.19 ms
Input props 
[
  "product" => App\Entity\Product\Product {#93749
    #id: 11972
    #code: "IEEE00006846"
    #attributes: Doctrine\ORM\PersistentCollection {#93731 …}
    #variants: Doctrine\ORM\PersistentCollection {#93728 …}
    #options: Doctrine\ORM\PersistentCollection {#93724 …}
    #associations: Doctrine\ORM\PersistentCollection {#93726 …}
    #createdAt: DateTime @1751040111 {#93757
      date: 2025-06-27 18:01:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93736
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93742 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93777
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93749}
        #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 {#93740 …}
    #channels: Doctrine\ORM\PersistentCollection {#93733 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93738 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93735 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93750 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93720
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#93756
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#93755
      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 {#93746 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93744 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#113514
  +product: App\Entity\Product\Product {#93749
    #id: 11972
    #code: "IEEE00006846"
    #attributes: Doctrine\ORM\PersistentCollection {#93731 …}
    #variants: Doctrine\ORM\PersistentCollection {#93728 …}
    #options: Doctrine\ORM\PersistentCollection {#93724 …}
    #associations: Doctrine\ORM\PersistentCollection {#93726 …}
    #createdAt: DateTime @1751040111 {#93757
      date: 2025-06-27 18:01:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93736
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93742 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93777
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93749}
        #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 {#93740 …}
    #channels: Doctrine\ORM\PersistentCollection {#93733 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93738 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93735 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93750 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93720
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#93756
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#93755
      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 {#93746 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93744 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 160.0 MiB 0.70 ms
Input props 
[
  "product" => App\Entity\Product\Product {#93749
    #id: 11972
    #code: "IEEE00006846"
    #attributes: Doctrine\ORM\PersistentCollection {#93731 …}
    #variants: Doctrine\ORM\PersistentCollection {#93728 …}
    #options: Doctrine\ORM\PersistentCollection {#93724 …}
    #associations: Doctrine\ORM\PersistentCollection {#93726 …}
    #createdAt: DateTime @1751040111 {#93757
      date: 2025-06-27 18:01:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93736
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93742 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93777
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93749}
        #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 {#93740 …}
    #channels: Doctrine\ORM\PersistentCollection {#93733 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93738 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93735 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93750 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93720
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#93756
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#93755
      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 {#93746 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93744 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#113581
  +product: App\Entity\Product\Product {#93749
    #id: 11972
    #code: "IEEE00006846"
    #attributes: Doctrine\ORM\PersistentCollection {#93731 …}
    #variants: Doctrine\ORM\PersistentCollection {#93728 …}
    #options: Doctrine\ORM\PersistentCollection {#93724 …}
    #associations: Doctrine\ORM\PersistentCollection {#93726 …}
    #createdAt: DateTime @1751040111 {#93757
      date: 2025-06-27 18:01:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93736
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93742 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93777
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93749}
        #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 {#93740 …}
    #channels: Doctrine\ORM\PersistentCollection {#93733 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93738 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93735 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93750 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93720
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#93756
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#93755
      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 {#93746 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93744 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 160.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039381 {#7274
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#7292
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#7316
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#113646
  +product: App\Entity\Product\Product {#7311
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039381 {#7274
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#7292
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#7316
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 160.0 MiB 0.62 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039381 {#7274
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#7292
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#7316
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#113673
  +product: App\Entity\Product\Product {#7311
    #id: 10945
    #code: "IEEE00005334"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039381 {#7274
      date: 2025-06-27 17:49:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#7322
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#7292
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#7316
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "42010"
    -bookCollection: ""
    -pageCount: 46
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 160.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#113441
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#113463 …}
    #variants: Doctrine\ORM\PersistentCollection {#113465 …}
    #options: Doctrine\ORM\PersistentCollection {#113469 …}
    #associations: Doctrine\ORM\PersistentCollection {#113467 …}
    #createdAt: DateTime @1751039009 {#113432
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#113439
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113453 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113739
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113441}
        #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 {#113455 …}
    #channels: Doctrine\ORM\PersistentCollection {#113461 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113457 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113459 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113446 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113436
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113438
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1184450400 {#113440
      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 {#113449 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113451 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#113754
  +product: App\Entity\Product\Product {#113441
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#113463 …}
    #variants: Doctrine\ORM\PersistentCollection {#113465 …}
    #options: Doctrine\ORM\PersistentCollection {#113469 …}
    #associations: Doctrine\ORM\PersistentCollection {#113467 …}
    #createdAt: DateTime @1751039009 {#113432
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#113439
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113453 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113739
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113441}
        #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 {#113455 …}
    #channels: Doctrine\ORM\PersistentCollection {#113461 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113457 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113459 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113446 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113436
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113438
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1184450400 {#113440
      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 {#113449 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113451 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 160.0 MiB 0.63 ms
Input props 
[
  "product" => App\Entity\Product\Product {#113441
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#113463 …}
    #variants: Doctrine\ORM\PersistentCollection {#113465 …}
    #options: Doctrine\ORM\PersistentCollection {#113469 …}
    #associations: Doctrine\ORM\PersistentCollection {#113467 …}
    #createdAt: DateTime @1751039009 {#113432
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#113439
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113453 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113739
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113441}
        #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 {#113455 …}
    #channels: Doctrine\ORM\PersistentCollection {#113461 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113457 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113459 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113446 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113436
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113438
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1184450400 {#113440
      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 {#113449 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113451 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#113806
  +product: App\Entity\Product\Product {#113441
    #id: 10354
    #code: "IEEE00004228"
    #attributes: Doctrine\ORM\PersistentCollection {#113463 …}
    #variants: Doctrine\ORM\PersistentCollection {#113465 …}
    #options: Doctrine\ORM\PersistentCollection {#113469 …}
    #associations: Doctrine\ORM\PersistentCollection {#113467 …}
    #createdAt: DateTime @1751039009 {#113432
      date: 2025-06-27 17:43:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#113439
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113453 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113739
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113441}
        #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 {#113455 …}
    #channels: Doctrine\ORM\PersistentCollection {#113461 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113457 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113459 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113446 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113436
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113438
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1184450400 {#113440
      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 {#113449 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113451 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}