GET https://dev.normadoc.fr/_partial/products/10503/associations/11450/sort?fieldSort=%7B%22publishedAt%22%3A%22DESC%22%7D&isSubscriberDashboard=0&template=%40Syliu…

Response
200 OK
IP
150.40.235.242
Profiled on
Token
e11df9

Components

4 Twig Components
17 Render Count
16 ms Render Time
132.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		7 1.24ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		7 4.32ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		2 12.01ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.18ms

Render calls

ProductState App\Twig\Components\ProductState 132.0 MiB 0.33 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039102 {#7274
      date: 2025-06-27 17:45:02.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: 37021
        #name: "IEEE 1016:2009"
        #slug: "ieee-1016-2009-ieee00004502-242155"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard describes software designs and establishes the information content and organization of a software design description (SDD). An SDD is a representation of a software design to be used for recording design information and communicating that design information to key design stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software construction activities, when design leads to code, and “reverse engineering” situations when a design description is recovered from an existing implementation.<br />\n
          This standard can be applied to commercial, scientific, or military software that runs on digital computers. Applicability is not restricted by the size, complexity, or criticality of the software. This standard can be applied to the description of high-level and detailed designs.<br />\n
          This standard does not prescribe specific methodologies for design, configuration management, or quality assurance. This standard does not require the use of any particular design languages, but establishes requirements on the selection of design languages for use in an SDD. This standard can be applied to the preparation of SDDs captured as paper documents, automated databases, software development tools, or other media.<br />\n
          This standard specifies requirements on the information content and organization of SDDs. The standard specifies requirements for the selection of design languages to be used for SDD, and requirements for documenting design viewpoints to be used in organizing an SDD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Systems Design--Software Design Descriptions"
        -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 @1585692000 {#7292
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#7318
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#7316
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#93055
  +product: App\Entity\Product\Product {#7311
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039102 {#7274
      date: 2025-06-27 17:45:02.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: 37021
        #name: "IEEE 1016:2009"
        #slug: "ieee-1016-2009-ieee00004502-242155"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard describes software designs and establishes the information content and organization of a software design description (SDD). An SDD is a representation of a software design to be used for recording design information and communicating that design information to key design stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software construction activities, when design leads to code, and “reverse engineering” situations when a design description is recovered from an existing implementation.<br />\n
          This standard can be applied to commercial, scientific, or military software that runs on digital computers. Applicability is not restricted by the size, complexity, or criticality of the software. This standard can be applied to the description of high-level and detailed designs.<br />\n
          This standard does not prescribe specific methodologies for design, configuration management, or quality assurance. This standard does not require the use of any particular design languages, but establishes requirements on the selection of design languages for use in an SDD. This standard can be applied to the preparation of SDDs captured as paper documents, automated databases, software development tools, or other media.<br />\n
          This standard specifies requirements on the information content and organization of SDDs. The standard specifies requirements for the selection of design languages to be used for SDD, and requirements for documenting design viewpoints to be used in organizing an SDD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Systems Design--Software Design Descriptions"
        -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 @1585692000 {#7292
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#7318
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#7316
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -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 132.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039102 {#7274
      date: 2025-06-27 17:45:02.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: 37021
        #name: "IEEE 1016:2009"
        #slug: "ieee-1016-2009-ieee00004502-242155"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard describes software designs and establishes the information content and organization of a software design description (SDD). An SDD is a representation of a software design to be used for recording design information and communicating that design information to key design stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software construction activities, when design leads to code, and “reverse engineering” situations when a design description is recovered from an existing implementation.<br />\n
          This standard can be applied to commercial, scientific, or military software that runs on digital computers. Applicability is not restricted by the size, complexity, or criticality of the software. This standard can be applied to the description of high-level and detailed designs.<br />\n
          This standard does not prescribe specific methodologies for design, configuration management, or quality assurance. This standard does not require the use of any particular design languages, but establishes requirements on the selection of design languages for use in an SDD. This standard can be applied to the preparation of SDDs captured as paper documents, automated databases, software development tools, or other media.<br />\n
          This standard specifies requirements on the information content and organization of SDDs. The standard specifies requirements for the selection of design languages to be used for SDD, and requirements for documenting design viewpoints to be used in organizing an SDD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Systems Design--Software Design Descriptions"
        -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 @1585692000 {#7292
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#7318
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#7316
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93235
  +product: App\Entity\Product\Product {#7311
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039102 {#7274
      date: 2025-06-27 17:45:02.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: 37021
        #name: "IEEE 1016:2009"
        #slug: "ieee-1016-2009-ieee00004502-242155"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard describes software designs and establishes the information content and organization of a software design description (SDD). An SDD is a representation of a software design to be used for recording design information and communicating that design information to key design stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software construction activities, when design leads to code, and “reverse engineering” situations when a design description is recovered from an existing implementation.<br />\n
          This standard can be applied to commercial, scientific, or military software that runs on digital computers. Applicability is not restricted by the size, complexity, or criticality of the software. This standard can be applied to the description of high-level and detailed designs.<br />\n
          This standard does not prescribe specific methodologies for design, configuration management, or quality assurance. This standard does not require the use of any particular design languages, but establishes requirements on the selection of design languages for use in an SDD. This standard can be applied to the preparation of SDDs captured as paper documents, automated databases, software development tools, or other media.<br />\n
          This standard specifies requirements on the information content and organization of SDDs. The standard specifies requirements for the selection of design languages to be used for SDD, and requirements for documenting design viewpoints to be used in organizing an SDD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Systems Design--Software Design Descriptions"
        -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 @1585692000 {#7292
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#7318
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#7316
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -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 132.0 MiB 0.62 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039102 {#7274
      date: 2025-06-27 17:45:02.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: 37021
        #name: "IEEE 1016:2009"
        #slug: "ieee-1016-2009-ieee00004502-242155"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard describes software designs and establishes the information content and organization of a software design description (SDD). An SDD is a representation of a software design to be used for recording design information and communicating that design information to key design stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software construction activities, when design leads to code, and “reverse engineering” situations when a design description is recovered from an existing implementation.<br />\n
          This standard can be applied to commercial, scientific, or military software that runs on digital computers. Applicability is not restricted by the size, complexity, or criticality of the software. This standard can be applied to the description of high-level and detailed designs.<br />\n
          This standard does not prescribe specific methodologies for design, configuration management, or quality assurance. This standard does not require the use of any particular design languages, but establishes requirements on the selection of design languages for use in an SDD. This standard can be applied to the preparation of SDDs captured as paper documents, automated databases, software development tools, or other media.<br />\n
          This standard specifies requirements on the information content and organization of SDDs. The standard specifies requirements for the selection of design languages to be used for SDD, and requirements for documenting design viewpoints to be used in organizing an SDD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Systems Design--Software Design Descriptions"
        -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 @1585692000 {#7292
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#7318
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#7316
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93310
  +product: App\Entity\Product\Product {#7311
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039102 {#7274
      date: 2025-06-27 17:45:02.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: 37021
        #name: "IEEE 1016:2009"
        #slug: "ieee-1016-2009-ieee00004502-242155"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard describes software designs and establishes the information content and organization of a software design description (SDD). An SDD is a representation of a software design to be used for recording design information and communicating that design information to key design stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software construction activities, when design leads to code, and “reverse engineering” situations when a design description is recovered from an existing implementation.<br />\n
          This standard can be applied to commercial, scientific, or military software that runs on digital computers. Applicability is not restricted by the size, complexity, or criticality of the software. This standard can be applied to the description of high-level and detailed designs.<br />\n
          This standard does not prescribe specific methodologies for design, configuration management, or quality assurance. This standard does not require the use of any particular design languages, but establishes requirements on the selection of design languages for use in an SDD. This standard can be applied to the preparation of SDDs captured as paper documents, automated databases, software development tools, or other media.<br />\n
          This standard specifies requirements on the information content and organization of SDDs. The standard specifies requirements for the selection of design languages to be used for SDD, and requirements for documenting design viewpoints to be used in organizing an SDD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Systems Design--Software Design Descriptions"
        -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 @1585692000 {#7292
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#7318
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#7316
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -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 132.0 MiB 0.16 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100317
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#100300 …}
    #variants: Doctrine\ORM\PersistentCollection {#100297 …}
    #options: Doctrine\ORM\PersistentCollection {#100293 …}
    #associations: Doctrine\ORM\PersistentCollection {#100295 …}
    #createdAt: DateTime @1751037902 {#100325
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#100298
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100311 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100335
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100317}
        #id: 31077
        #name: "IEEE 1016:1998"
        #slug: "ieee-1016-1998-ieee00001478-240669"
        #description: """
          Revision Standard - Superseded.<br />\n
          This IEEE Standards product is part of the family on Software Engineering. The necessary information content and recommendations for an organization for Software Design Descriptions (SDDs) are described. An SDD is a representation of a software system that is used as a medium for communicating software design information. This recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.<br />\n
          \t\t\t\t<br />\n
          This is a Recommended Practice for describing software designs. It produces the necessary information content and recommended organization for a Software Design Description. A software design description is a representation of a software system that is used as medium for communicating software design information. The practice may be applied to commercial, scientific or military software which runs on any digital computer. Applicability is not restricted by the size of the the software. This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality of design information and changes to the design description will be managed by other project activities. Finally, this document does not support and is not limited to any particular description techniques. It may be applied to proper documents, automated databases, design description languages, or other means of description. In addition it will also establish a correlation between the content of software design descriptions as defined in 1016 and the content of such documents as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100308 …}
    #channels: Doctrine\ORM\PersistentCollection {#100302 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100306 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100304 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100318 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100285
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100324
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#100323
      date: 1998-12-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#100315 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100313 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100371
  +product: App\Entity\Product\Product {#100317
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#100300 …}
    #variants: Doctrine\ORM\PersistentCollection {#100297 …}
    #options: Doctrine\ORM\PersistentCollection {#100293 …}
    #associations: Doctrine\ORM\PersistentCollection {#100295 …}
    #createdAt: DateTime @1751037902 {#100325
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#100298
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100311 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100335
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100317}
        #id: 31077
        #name: "IEEE 1016:1998"
        #slug: "ieee-1016-1998-ieee00001478-240669"
        #description: """
          Revision Standard - Superseded.<br />\n
          This IEEE Standards product is part of the family on Software Engineering. The necessary information content and recommendations for an organization for Software Design Descriptions (SDDs) are described. An SDD is a representation of a software system that is used as a medium for communicating software design information. This recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.<br />\n
          \t\t\t\t<br />\n
          This is a Recommended Practice for describing software designs. It produces the necessary information content and recommended organization for a Software Design Description. A software design description is a representation of a software system that is used as medium for communicating software design information. The practice may be applied to commercial, scientific or military software which runs on any digital computer. Applicability is not restricted by the size of the the software. This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality of design information and changes to the design description will be managed by other project activities. Finally, this document does not support and is not limited to any particular description techniques. It may be applied to proper documents, automated databases, design description languages, or other means of description. In addition it will also establish a correlation between the content of software design descriptions as defined in 1016 and the content of such documents as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100308 …}
    #channels: Doctrine\ORM\PersistentCollection {#100302 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100306 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100304 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100318 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100285
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100324
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#100323
      date: 1998-12-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#100315 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100313 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 132.0 MiB 0.69 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100317
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#100300 …}
    #variants: Doctrine\ORM\PersistentCollection {#100297 …}
    #options: Doctrine\ORM\PersistentCollection {#100293 …}
    #associations: Doctrine\ORM\PersistentCollection {#100295 …}
    #createdAt: DateTime @1751037902 {#100325
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#100298
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100311 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100335
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100317}
        #id: 31077
        #name: "IEEE 1016:1998"
        #slug: "ieee-1016-1998-ieee00001478-240669"
        #description: """
          Revision Standard - Superseded.<br />\n
          This IEEE Standards product is part of the family on Software Engineering. The necessary information content and recommendations for an organization for Software Design Descriptions (SDDs) are described. An SDD is a representation of a software system that is used as a medium for communicating software design information. This recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.<br />\n
          \t\t\t\t<br />\n
          This is a Recommended Practice for describing software designs. It produces the necessary information content and recommended organization for a Software Design Description. A software design description is a representation of a software system that is used as medium for communicating software design information. The practice may be applied to commercial, scientific or military software which runs on any digital computer. Applicability is not restricted by the size of the the software. This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality of design information and changes to the design description will be managed by other project activities. Finally, this document does not support and is not limited to any particular description techniques. It may be applied to proper documents, automated databases, design description languages, or other means of description. In addition it will also establish a correlation between the content of software design descriptions as defined in 1016 and the content of such documents as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100308 …}
    #channels: Doctrine\ORM\PersistentCollection {#100302 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100306 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100304 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100318 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100285
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100324
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#100323
      date: 1998-12-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#100315 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100313 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100438
  +product: App\Entity\Product\Product {#100317
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#100300 …}
    #variants: Doctrine\ORM\PersistentCollection {#100297 …}
    #options: Doctrine\ORM\PersistentCollection {#100293 …}
    #associations: Doctrine\ORM\PersistentCollection {#100295 …}
    #createdAt: DateTime @1751037902 {#100325
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#100298
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100311 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100335
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100317}
        #id: 31077
        #name: "IEEE 1016:1998"
        #slug: "ieee-1016-1998-ieee00001478-240669"
        #description: """
          Revision Standard - Superseded.<br />\n
          This IEEE Standards product is part of the family on Software Engineering. The necessary information content and recommendations for an organization for Software Design Descriptions (SDDs) are described. An SDD is a representation of a software system that is used as a medium for communicating software design information. This recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.<br />\n
          \t\t\t\t<br />\n
          This is a Recommended Practice for describing software designs. It produces the necessary information content and recommended organization for a Software Design Description. A software design description is a representation of a software system that is used as medium for communicating software design information. The practice may be applied to commercial, scientific or military software which runs on any digital computer. Applicability is not restricted by the size of the the software. This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality of design information and changes to the design description will be managed by other project activities. Finally, this document does not support and is not limited to any particular description techniques. It may be applied to proper documents, automated databases, design description languages, or other means of description. In addition it will also establish a correlation between the content of software design descriptions as defined in 1016 and the content of such documents as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100308 …}
    #channels: Doctrine\ORM\PersistentCollection {#100302 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100306 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100304 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100318 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100285
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100324
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#100323
      date: 1998-12-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#100315 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100313 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 132.0 MiB 0.16 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039102 {#7274
      date: 2025-06-27 17:45:02.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: 37021
        #name: "IEEE 1016:2009"
        #slug: "ieee-1016-2009-ieee00004502-242155"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard describes software designs and establishes the information content and organization of a software design description (SDD). An SDD is a representation of a software design to be used for recording design information and communicating that design information to key design stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software construction activities, when design leads to code, and “reverse engineering” situations when a design description is recovered from an existing implementation.<br />\n
          This standard can be applied to commercial, scientific, or military software that runs on digital computers. Applicability is not restricted by the size, complexity, or criticality of the software. This standard can be applied to the description of high-level and detailed designs.<br />\n
          This standard does not prescribe specific methodologies for design, configuration management, or quality assurance. This standard does not require the use of any particular design languages, but establishes requirements on the selection of design languages for use in an SDD. This standard can be applied to the preparation of SDDs captured as paper documents, automated databases, software development tools, or other media.<br />\n
          This standard specifies requirements on the information content and organization of SDDs. The standard specifies requirements for the selection of design languages to be used for SDD, and requirements for documenting design viewpoints to be used in organizing an SDD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Systems Design--Software Design Descriptions"
        -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 @1585692000 {#7292
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#7318
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#7316
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#107058
  +product: App\Entity\Product\Product {#7311
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039102 {#7274
      date: 2025-06-27 17:45:02.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: 37021
        #name: "IEEE 1016:2009"
        #slug: "ieee-1016-2009-ieee00004502-242155"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard describes software designs and establishes the information content and organization of a software design description (SDD). An SDD is a representation of a software design to be used for recording design information and communicating that design information to key design stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software construction activities, when design leads to code, and “reverse engineering” situations when a design description is recovered from an existing implementation.<br />\n
          This standard can be applied to commercial, scientific, or military software that runs on digital computers. Applicability is not restricted by the size, complexity, or criticality of the software. This standard can be applied to the description of high-level and detailed designs.<br />\n
          This standard does not prescribe specific methodologies for design, configuration management, or quality assurance. This standard does not require the use of any particular design languages, but establishes requirements on the selection of design languages for use in an SDD. This standard can be applied to the preparation of SDDs captured as paper documents, automated databases, software development tools, or other media.<br />\n
          This standard specifies requirements on the information content and organization of SDDs. The standard specifies requirements for the selection of design languages to be used for SDD, and requirements for documenting design viewpoints to be used in organizing an SDD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Systems Design--Software Design Descriptions"
        -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 @1585692000 {#7292
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#7318
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#7316
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -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 132.0 MiB 0.66 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039102 {#7274
      date: 2025-06-27 17:45:02.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: 37021
        #name: "IEEE 1016:2009"
        #slug: "ieee-1016-2009-ieee00004502-242155"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard describes software designs and establishes the information content and organization of a software design description (SDD). An SDD is a representation of a software design to be used for recording design information and communicating that design information to key design stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software construction activities, when design leads to code, and “reverse engineering” situations when a design description is recovered from an existing implementation.<br />\n
          This standard can be applied to commercial, scientific, or military software that runs on digital computers. Applicability is not restricted by the size, complexity, or criticality of the software. This standard can be applied to the description of high-level and detailed designs.<br />\n
          This standard does not prescribe specific methodologies for design, configuration management, or quality assurance. This standard does not require the use of any particular design languages, but establishes requirements on the selection of design languages for use in an SDD. This standard can be applied to the preparation of SDDs captured as paper documents, automated databases, software development tools, or other media.<br />\n
          This standard specifies requirements on the information content and organization of SDDs. The standard specifies requirements for the selection of design languages to be used for SDD, and requirements for documenting design viewpoints to be used in organizing an SDD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Systems Design--Software Design Descriptions"
        -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 @1585692000 {#7292
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#7318
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#7316
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#107100
  +product: App\Entity\Product\Product {#7311
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751039102 {#7274
      date: 2025-06-27 17:45:02.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: 37021
        #name: "IEEE 1016:2009"
        #slug: "ieee-1016-2009-ieee00004502-242155"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard describes software designs and establishes the information content and organization of a software design description (SDD). An SDD is a representation of a software design to be used for recording design information and communicating that design information to key design stakeholders. This standard is intended for use in design situations in which an explicit SDD is to be prepared. These situations include traditional software construction activities, when design leads to code, and “reverse engineering” situations when a design description is recovered from an existing implementation.<br />\n
          This standard can be applied to commercial, scientific, or military software that runs on digital computers. Applicability is not restricted by the size, complexity, or criticality of the software. This standard can be applied to the description of high-level and detailed designs.<br />\n
          This standard does not prescribe specific methodologies for design, configuration management, or quality assurance. This standard does not require the use of any particular design languages, but establishes requirements on the selection of design languages for use in an SDD. This standard can be applied to the preparation of SDDs captured as paper documents, automated databases, software development tools, or other media.<br />\n
          This standard specifies requirements on the information content and organization of SDDs. The standard specifies requirements for the selection of design languages to be used for SDD, and requirements for documenting design viewpoints to be used in organizing an SDD.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Systems Design--Software Design Descriptions"
        -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 @1585692000 {#7292
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#7318
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#7316
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -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 132.0 MiB 0.14 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100317
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#100300 …}
    #variants: Doctrine\ORM\PersistentCollection {#100297 …}
    #options: Doctrine\ORM\PersistentCollection {#100293 …}
    #associations: Doctrine\ORM\PersistentCollection {#100295 …}
    #createdAt: DateTime @1751037902 {#100325
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#100298
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100311 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100335
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100317}
        #id: 31077
        #name: "IEEE 1016:1998"
        #slug: "ieee-1016-1998-ieee00001478-240669"
        #description: """
          Revision Standard - Superseded.<br />\n
          This IEEE Standards product is part of the family on Software Engineering. The necessary information content and recommendations for an organization for Software Design Descriptions (SDDs) are described. An SDD is a representation of a software system that is used as a medium for communicating software design information. This recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.<br />\n
          \t\t\t\t<br />\n
          This is a Recommended Practice for describing software designs. It produces the necessary information content and recommended organization for a Software Design Description. A software design description is a representation of a software system that is used as medium for communicating software design information. The practice may be applied to commercial, scientific or military software which runs on any digital computer. Applicability is not restricted by the size of the the software. This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality of design information and changes to the design description will be managed by other project activities. Finally, this document does not support and is not limited to any particular description techniques. It may be applied to proper documents, automated databases, design description languages, or other means of description. In addition it will also establish a correlation between the content of software design descriptions as defined in 1016 and the content of such documents as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100308 …}
    #channels: Doctrine\ORM\PersistentCollection {#100302 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100306 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100304 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100318 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100285
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100324
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#100323
      date: 1998-12-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#100315 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100313 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#107165
  +product: App\Entity\Product\Product {#100317
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#100300 …}
    #variants: Doctrine\ORM\PersistentCollection {#100297 …}
    #options: Doctrine\ORM\PersistentCollection {#100293 …}
    #associations: Doctrine\ORM\PersistentCollection {#100295 …}
    #createdAt: DateTime @1751037902 {#100325
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#100298
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100311 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100335
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100317}
        #id: 31077
        #name: "IEEE 1016:1998"
        #slug: "ieee-1016-1998-ieee00001478-240669"
        #description: """
          Revision Standard - Superseded.<br />\n
          This IEEE Standards product is part of the family on Software Engineering. The necessary information content and recommendations for an organization for Software Design Descriptions (SDDs) are described. An SDD is a representation of a software system that is used as a medium for communicating software design information. This recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.<br />\n
          \t\t\t\t<br />\n
          This is a Recommended Practice for describing software designs. It produces the necessary information content and recommended organization for a Software Design Description. A software design description is a representation of a software system that is used as medium for communicating software design information. The practice may be applied to commercial, scientific or military software which runs on any digital computer. Applicability is not restricted by the size of the the software. This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality of design information and changes to the design description will be managed by other project activities. Finally, this document does not support and is not limited to any particular description techniques. It may be applied to proper documents, automated databases, design description languages, or other means of description. In addition it will also establish a correlation between the content of software design descriptions as defined in 1016 and the content of such documents as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100308 …}
    #channels: Doctrine\ORM\PersistentCollection {#100302 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100306 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100304 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100318 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100285
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100324
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#100323
      date: 1998-12-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#100315 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100313 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 132.0 MiB 0.60 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100317
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#100300 …}
    #variants: Doctrine\ORM\PersistentCollection {#100297 …}
    #options: Doctrine\ORM\PersistentCollection {#100293 …}
    #associations: Doctrine\ORM\PersistentCollection {#100295 …}
    #createdAt: DateTime @1751037902 {#100325
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#100298
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100311 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100335
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100317}
        #id: 31077
        #name: "IEEE 1016:1998"
        #slug: "ieee-1016-1998-ieee00001478-240669"
        #description: """
          Revision Standard - Superseded.<br />\n
          This IEEE Standards product is part of the family on Software Engineering. The necessary information content and recommendations for an organization for Software Design Descriptions (SDDs) are described. An SDD is a representation of a software system that is used as a medium for communicating software design information. This recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.<br />\n
          \t\t\t\t<br />\n
          This is a Recommended Practice for describing software designs. It produces the necessary information content and recommended organization for a Software Design Description. A software design description is a representation of a software system that is used as medium for communicating software design information. The practice may be applied to commercial, scientific or military software which runs on any digital computer. Applicability is not restricted by the size of the the software. This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality of design information and changes to the design description will be managed by other project activities. Finally, this document does not support and is not limited to any particular description techniques. It may be applied to proper documents, automated databases, design description languages, or other means of description. In addition it will also establish a correlation between the content of software design descriptions as defined in 1016 and the content of such documents as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100308 …}
    #channels: Doctrine\ORM\PersistentCollection {#100302 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100306 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100304 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100318 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100285
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100324
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#100323
      date: 1998-12-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#100315 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100313 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#107192
  +product: App\Entity\Product\Product {#100317
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#100300 …}
    #variants: Doctrine\ORM\PersistentCollection {#100297 …}
    #options: Doctrine\ORM\PersistentCollection {#100293 …}
    #associations: Doctrine\ORM\PersistentCollection {#100295 …}
    #createdAt: DateTime @1751037902 {#100325
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#100298
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100311 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100335
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100317}
        #id: 31077
        #name: "IEEE 1016:1998"
        #slug: "ieee-1016-1998-ieee00001478-240669"
        #description: """
          Revision Standard - Superseded.<br />\n
          This IEEE Standards product is part of the family on Software Engineering. The necessary information content and recommendations for an organization for Software Design Descriptions (SDDs) are described. An SDD is a representation of a software system that is used as a medium for communicating software design information. This recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.<br />\n
          \t\t\t\t<br />\n
          This is a Recommended Practice for describing software designs. It produces the necessary information content and recommended organization for a Software Design Description. A software design description is a representation of a software system that is used as medium for communicating software design information. The practice may be applied to commercial, scientific or military software which runs on any digital computer. Applicability is not restricted by the size of the the software. This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality of design information and changes to the design description will be managed by other project activities. Finally, this document does not support and is not limited to any particular description techniques. It may be applied to proper documents, automated databases, design description languages, or other means of description. In addition it will also establish a correlation between the content of software design descriptions as defined in 1016 and the content of such documents as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100308 …}
    #channels: Doctrine\ORM\PersistentCollection {#100302 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100306 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100304 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100318 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100285
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100324
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#100323
      date: 1998-12-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#100315 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100313 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 132.0 MiB 0.15 ms
Input props 
[
  "product" => App\Entity\Product\Product {#107009
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#107027 …}
    #variants: Doctrine\ORM\PersistentCollection {#107029 …}
    #options: Doctrine\ORM\PersistentCollection {#107033 …}
    #associations: Doctrine\ORM\PersistentCollection {#107031 …}
    #createdAt: DateTime @1751037901 {#106999
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#107001
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#107017 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107258
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#107009}
        #id: 31073
        #name: "IEEE 1016:1987 (R1993)"
        #slug: "ieee-1016-1987-r1993-ieee00001477-240668"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The necessary information content and recommended organization for a software design description are specified. A software design description is a representation of a software system that is used as a medium for communicating software design information. The recommendations, which may be applied to commercial, scientific, or military software that runs on any digital computer, are not limited to specific methodologies for design, configuration management, or quality assurance, or to any particular descriptive technique. Applicability is not restricted by the size, complexity, or criticality of the software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for describing software designs. It specifies the necessary information content, and recommended organization for a software design description. A software design description is a representation of a software system that is used as a medium for communicating software design information.<br />\n
          The practice may be applied to commercial, scientific, or military software that runs on any digital computer. Applicability is not restricted by the size, complexity, or criticality of the software.<br />\n
          This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality design information and changes to the design of description will be managed by other project activities. Finally, this document does not support nor is it limited to any particular descriptive technique. It maybe applied to paper documents, automated databases, design description languages, or other means of description.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#107019 …}
    #channels: Doctrine\ORM\PersistentCollection {#107025 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#107021 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#107023 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#107011 …}
    -apiLastModifiedAt: DateTime @1754517600 {#107003
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#107004
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#107010
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106992
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#107013 …}
    -favorites: Doctrine\ORM\PersistentCollection {#107015 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#107273
  +product: App\Entity\Product\Product {#107009
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#107027 …}
    #variants: Doctrine\ORM\PersistentCollection {#107029 …}
    #options: Doctrine\ORM\PersistentCollection {#107033 …}
    #associations: Doctrine\ORM\PersistentCollection {#107031 …}
    #createdAt: DateTime @1751037901 {#106999
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#107001
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#107017 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107258
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#107009}
        #id: 31073
        #name: "IEEE 1016:1987 (R1993)"
        #slug: "ieee-1016-1987-r1993-ieee00001477-240668"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The necessary information content and recommended organization for a software design description are specified. A software design description is a representation of a software system that is used as a medium for communicating software design information. The recommendations, which may be applied to commercial, scientific, or military software that runs on any digital computer, are not limited to specific methodologies for design, configuration management, or quality assurance, or to any particular descriptive technique. Applicability is not restricted by the size, complexity, or criticality of the software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for describing software designs. It specifies the necessary information content, and recommended organization for a software design description. A software design description is a representation of a software system that is used as a medium for communicating software design information.<br />\n
          The practice may be applied to commercial, scientific, or military software that runs on any digital computer. Applicability is not restricted by the size, complexity, or criticality of the software.<br />\n
          This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality design information and changes to the design of description will be managed by other project activities. Finally, this document does not support nor is it limited to any particular descriptive technique. It maybe applied to paper documents, automated databases, design description languages, or other means of description.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#107019 …}
    #channels: Doctrine\ORM\PersistentCollection {#107025 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#107021 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#107023 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#107011 …}
    -apiLastModifiedAt: DateTime @1754517600 {#107003
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#107004
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#107010
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106992
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#107013 …}
    -favorites: Doctrine\ORM\PersistentCollection {#107015 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 132.0 MiB 0.55 ms
Input props 
[
  "product" => App\Entity\Product\Product {#107009
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#107027 …}
    #variants: Doctrine\ORM\PersistentCollection {#107029 …}
    #options: Doctrine\ORM\PersistentCollection {#107033 …}
    #associations: Doctrine\ORM\PersistentCollection {#107031 …}
    #createdAt: DateTime @1751037901 {#106999
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#107001
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#107017 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107258
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#107009}
        #id: 31073
        #name: "IEEE 1016:1987 (R1993)"
        #slug: "ieee-1016-1987-r1993-ieee00001477-240668"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The necessary information content and recommended organization for a software design description are specified. A software design description is a representation of a software system that is used as a medium for communicating software design information. The recommendations, which may be applied to commercial, scientific, or military software that runs on any digital computer, are not limited to specific methodologies for design, configuration management, or quality assurance, or to any particular descriptive technique. Applicability is not restricted by the size, complexity, or criticality of the software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for describing software designs. It specifies the necessary information content, and recommended organization for a software design description. A software design description is a representation of a software system that is used as a medium for communicating software design information.<br />\n
          The practice may be applied to commercial, scientific, or military software that runs on any digital computer. Applicability is not restricted by the size, complexity, or criticality of the software.<br />\n
          This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality design information and changes to the design of description will be managed by other project activities. Finally, this document does not support nor is it limited to any particular descriptive technique. It maybe applied to paper documents, automated databases, design description languages, or other means of description.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#107019 …}
    #channels: Doctrine\ORM\PersistentCollection {#107025 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#107021 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#107023 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#107011 …}
    -apiLastModifiedAt: DateTime @1754517600 {#107003
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#107004
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#107010
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106992
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#107013 …}
    -favorites: Doctrine\ORM\PersistentCollection {#107015 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#107329
  +product: App\Entity\Product\Product {#107009
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#107027 …}
    #variants: Doctrine\ORM\PersistentCollection {#107029 …}
    #options: Doctrine\ORM\PersistentCollection {#107033 …}
    #associations: Doctrine\ORM\PersistentCollection {#107031 …}
    #createdAt: DateTime @1751037901 {#106999
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#107001
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#107017 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107258
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#107009}
        #id: 31073
        #name: "IEEE 1016:1987 (R1993)"
        #slug: "ieee-1016-1987-r1993-ieee00001477-240668"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The necessary information content and recommended organization for a software design description are specified. A software design description is a representation of a software system that is used as a medium for communicating software design information. The recommendations, which may be applied to commercial, scientific, or military software that runs on any digital computer, are not limited to specific methodologies for design, configuration management, or quality assurance, or to any particular descriptive technique. Applicability is not restricted by the size, complexity, or criticality of the software.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for describing software designs. It specifies the necessary information content, and recommended organization for a software design description. A software design description is a representation of a software system that is used as a medium for communicating software design information.<br />\n
          The practice may be applied to commercial, scientific, or military software that runs on any digital computer. Applicability is not restricted by the size, complexity, or criticality of the software.<br />\n
          This practice is not limited to specific methodologies for design, configuration management, or quality assurance. It is assumed that the quality design information and changes to the design of description will be managed by other project activities. Finally, this document does not support nor is it limited to any particular descriptive technique. It maybe applied to paper documents, automated databases, design description languages, or other means of description.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Design Descriptions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#107019 …}
    #channels: Doctrine\ORM\PersistentCollection {#107025 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#107021 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#107023 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#107011 …}
    -apiLastModifiedAt: DateTime @1754517600 {#107003
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#107004
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#107010
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#106992
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#107013 …}
    -favorites: Doctrine\ORM\PersistentCollection {#107015 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 132.0 MiB 6.62 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128829
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128812 …}
    #variants: Doctrine\ORM\PersistentCollection {#128810 …}
    #options: Doctrine\ORM\PersistentCollection {#128805 …}
    #associations: Doctrine\ORM\PersistentCollection {#128807 …}
    #createdAt: DateTime @1751037622 {#128802
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128837
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128823 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128946
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128829}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128821 …}
    #channels: Doctrine\ORM\PersistentCollection {#128814 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128818 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128816 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128831 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128788
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128836
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128795
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128808
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128827 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128825 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#128863
  +product: App\Entity\Product\Product {#128829
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128812 …}
    #variants: Doctrine\ORM\PersistentCollection {#128810 …}
    #options: Doctrine\ORM\PersistentCollection {#128805 …}
    #associations: Doctrine\ORM\PersistentCollection {#128807 …}
    #createdAt: DateTime @1751037622 {#128802
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128837
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128823 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128946
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128829}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128821 …}
    #channels: Doctrine\ORM\PersistentCollection {#128814 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128818 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128816 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128831 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128788
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128836
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128795
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128808
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128827 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128825 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}
ProductState App\Twig\Components\ProductState 132.0 MiB 0.15 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128829
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128812 …}
    #variants: Doctrine\ORM\PersistentCollection {#128810 …}
    #options: Doctrine\ORM\PersistentCollection {#128805 …}
    #associations: Doctrine\ORM\PersistentCollection {#128807 …}
    #createdAt: DateTime @1751037622 {#128802
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128837
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128823 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128946
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128829}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128821 …}
    #channels: Doctrine\ORM\PersistentCollection {#128814 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128818 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128816 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128831 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128788
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128836
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128795
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128808
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128827 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128825 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#128950
  +product: App\Entity\Product\Product {#128829
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128812 …}
    #variants: Doctrine\ORM\PersistentCollection {#128810 …}
    #options: Doctrine\ORM\PersistentCollection {#128805 …}
    #associations: Doctrine\ORM\PersistentCollection {#128807 …}
    #createdAt: DateTime @1751037622 {#128802
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128837
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128823 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128946
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128829}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128821 …}
    #channels: Doctrine\ORM\PersistentCollection {#128814 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128818 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128816 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128831 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128788
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128836
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128795
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128808
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128827 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128825 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 132.0 MiB 0.64 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128829
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128812 …}
    #variants: Doctrine\ORM\PersistentCollection {#128810 …}
    #options: Doctrine\ORM\PersistentCollection {#128805 …}
    #associations: Doctrine\ORM\PersistentCollection {#128807 …}
    #createdAt: DateTime @1751037622 {#128802
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128837
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128823 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128946
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128829}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128821 …}
    #channels: Doctrine\ORM\PersistentCollection {#128814 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128818 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128816 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128831 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128788
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128836
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128795
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128808
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128827 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128825 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#129028
  +product: App\Entity\Product\Product {#128829
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128812 …}
    #variants: Doctrine\ORM\PersistentCollection {#128810 …}
    #options: Doctrine\ORM\PersistentCollection {#128805 …}
    #associations: Doctrine\ORM\PersistentCollection {#128807 …}
    #createdAt: DateTime @1751037622 {#128802
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128837
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128823 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128946
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128829}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128821 …}
    #channels: Doctrine\ORM\PersistentCollection {#128814 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128818 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128816 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128831 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128788
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128836
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128795
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128808
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128827 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128825 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 132.0 MiB 5.39 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128796
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#128880 …}
    #variants: Doctrine\ORM\PersistentCollection {#128879 …}
    #options: Doctrine\ORM\PersistentCollection {#128874 …}
    #associations: Doctrine\ORM\PersistentCollection {#128876 …}
    #createdAt: DateTime @1751037795 {#128803
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128801
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128877 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#129155
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128796}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128862 …}
    #channels: Doctrine\ORM\PersistentCollection {#128885 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128840 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128886 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128794 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128800
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#128799
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#128798
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#128797
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#128792 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128785 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#129116
  +product: App\Entity\Product\Product {#128796
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#128880 …}
    #variants: Doctrine\ORM\PersistentCollection {#128879 …}
    #options: Doctrine\ORM\PersistentCollection {#128874 …}
    #associations: Doctrine\ORM\PersistentCollection {#128876 …}
    #createdAt: DateTime @1751037795 {#128803
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128801
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128877 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#129155
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128796}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128862 …}
    #channels: Doctrine\ORM\PersistentCollection {#128885 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128840 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128886 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128794 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128800
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#128799
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#128798
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#128797
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#128792 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128785 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}
ProductState App\Twig\Components\ProductState 132.0 MiB 0.14 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128796
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#128880 …}
    #variants: Doctrine\ORM\PersistentCollection {#128879 …}
    #options: Doctrine\ORM\PersistentCollection {#128874 …}
    #associations: Doctrine\ORM\PersistentCollection {#128876 …}
    #createdAt: DateTime @1751037795 {#128803
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128801
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128877 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#129155
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128796}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128862 …}
    #channels: Doctrine\ORM\PersistentCollection {#128885 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128840 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128886 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128794 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128800
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#128799
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#128798
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#128797
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#128792 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128785 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#129169
  +product: App\Entity\Product\Product {#128796
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#128880 …}
    #variants: Doctrine\ORM\PersistentCollection {#128879 …}
    #options: Doctrine\ORM\PersistentCollection {#128874 …}
    #associations: Doctrine\ORM\PersistentCollection {#128876 …}
    #createdAt: DateTime @1751037795 {#128803
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128801
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128877 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#129155
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128796}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128862 …}
    #channels: Doctrine\ORM\PersistentCollection {#128885 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128840 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128886 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128794 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128800
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#128799
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#128798
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#128797
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#128792 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128785 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 132.0 MiB 0.55 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128796
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#128880 …}
    #variants: Doctrine\ORM\PersistentCollection {#128879 …}
    #options: Doctrine\ORM\PersistentCollection {#128874 …}
    #associations: Doctrine\ORM\PersistentCollection {#128876 …}
    #createdAt: DateTime @1751037795 {#128803
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128801
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128877 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#129155
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128796}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128862 …}
    #channels: Doctrine\ORM\PersistentCollection {#128885 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128840 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128886 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128794 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128800
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#128799
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#128798
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#128797
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#128792 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128785 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#129243
  +product: App\Entity\Product\Product {#128796
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#128880 …}
    #variants: Doctrine\ORM\PersistentCollection {#128879 …}
    #options: Doctrine\ORM\PersistentCollection {#128874 …}
    #associations: Doctrine\ORM\PersistentCollection {#128876 …}
    #createdAt: DateTime @1751037795 {#128803
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128801
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128877 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#129155
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128796}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128862 …}
    #channels: Doctrine\ORM\PersistentCollection {#128885 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128840 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128886 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128794 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128800
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#128799
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#128798
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#128797
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#128792 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128785 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}