GET https://dev.normadoc.fr/products/ieee-1016-1998-ieee00001478-240669

Response
200 OK
IP
216.73.216.9
Profiled on
Token
197cc1

Components

3 Twig Components
11 Render Count
5 ms Render Time
88.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		5 1.12ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		5 3.55ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.22ms

Render calls

ProductState App\Twig\Components\ProductState 68.0 MiB 0.34 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7520
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037902 {#7536
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#95002
  +product: App\Entity\Product\Product {#7520
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037902 {#7536
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 68.0 MiB 0.22 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7520
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037902 {#7536
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#95182
  +product: App\Entity\Product\Product {#7520
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037902 {#7536
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 68.0 MiB 0.77 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7520
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037902 {#7536
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#95257
  +product: App\Entity\Product\Product {#7520
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037902 {#7536
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 80.0 MiB 0.21 ms
Input props 
[
  "product" => App\Entity\Product\Product {#108818
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751037901 {#108825
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108798
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108809 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108848
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108818}
        #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 {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108816 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108785
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108824
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#108823
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#108817
      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 {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#108832
  +product: App\Entity\Product\Product {#108818
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751037901 {#108825
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108798
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108809 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108848
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108818}
        #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 {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108816 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108785
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108824
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#108823
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#108817
      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 {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 80.0 MiB 0.73 ms
Input props 
[
  "product" => App\Entity\Product\Product {#108818
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751037901 {#108825
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108798
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108809 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108848
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108818}
        #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 {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108816 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108785
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108824
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#108823
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#108817
      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 {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#108937
  +product: App\Entity\Product\Product {#108818
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751037901 {#108825
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108798
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108809 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108848
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108818}
        #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 {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108816 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108785
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108824
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#108823
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#108817
      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 {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 88.0 MiB 0.19 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95681
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#95661 …}
    #variants: Doctrine\ORM\PersistentCollection {#95658 …}
    #options: Doctrine\ORM\PersistentCollection {#95654 …}
    #associations: Doctrine\ORM\PersistentCollection {#95650 …}
    #createdAt: DateTime @1751039102 {#95688
      date: 2025-06-27 17:45:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95667
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95672 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95713
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95681}
        #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 {#95670 …}
    #channels: Doctrine\ORM\PersistentCollection {#95663 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95668 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95665 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95678 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95651
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1585692000 {#95687
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#95686
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#95680
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -documents: Doctrine\ORM\PersistentCollection {#95676 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95674 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#115549
  +product: App\Entity\Product\Product {#95681
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#95661 …}
    #variants: Doctrine\ORM\PersistentCollection {#95658 …}
    #options: Doctrine\ORM\PersistentCollection {#95654 …}
    #associations: Doctrine\ORM\PersistentCollection {#95650 …}
    #createdAt: DateTime @1751039102 {#95688
      date: 2025-06-27 17:45:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95667
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95672 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95713
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95681}
        #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 {#95670 …}
    #channels: Doctrine\ORM\PersistentCollection {#95663 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95668 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95665 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95678 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95651
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1585692000 {#95687
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#95686
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#95680
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -documents: Doctrine\ORM\PersistentCollection {#95676 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95674 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 88.0 MiB 0.76 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95681
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#95661 …}
    #variants: Doctrine\ORM\PersistentCollection {#95658 …}
    #options: Doctrine\ORM\PersistentCollection {#95654 …}
    #associations: Doctrine\ORM\PersistentCollection {#95650 …}
    #createdAt: DateTime @1751039102 {#95688
      date: 2025-06-27 17:45:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95667
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95672 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95713
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95681}
        #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 {#95670 …}
    #channels: Doctrine\ORM\PersistentCollection {#95663 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95668 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95665 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95678 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95651
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1585692000 {#95687
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#95686
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#95680
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -documents: Doctrine\ORM\PersistentCollection {#95676 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95674 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#115616
  +product: App\Entity\Product\Product {#95681
    #id: 10503
    #code: "IEEE00004502"
    #attributes: Doctrine\ORM\PersistentCollection {#95661 …}
    #variants: Doctrine\ORM\PersistentCollection {#95658 …}
    #options: Doctrine\ORM\PersistentCollection {#95654 …}
    #associations: Doctrine\ORM\PersistentCollection {#95650 …}
    #createdAt: DateTime @1751039102 {#95688
      date: 2025-06-27 17:45:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#95667
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95672 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95713
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95681}
        #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 {#95670 …}
    #channels: Doctrine\ORM\PersistentCollection {#95663 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95668 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95665 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95678 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95651
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1585692000 {#95687
      date: 2020-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1248040800 {#95686
      date: 2009-07-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#95680
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1016"
    -bookCollection: ""
    -pageCount: 35
    -documents: Doctrine\ORM\PersistentCollection {#95676 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95674 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 88.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7520
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037902 {#7536
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#115681
  +product: App\Entity\Product\Product {#7520
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037902 {#7536
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 88.0 MiB 0.63 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7520
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037902 {#7536
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#115708
  +product: App\Entity\Product\Product {#7520
    #id: 9017
    #code: "IEEE00001478"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037902 {#7536
      date: 2025-06-27 17:25:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #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 {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912726000 {#7531
      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 {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 88.0 MiB 0.20 ms
Input props 
[
  "product" => App\Entity\Product\Product {#108818
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751037901 {#108825
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108798
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108809 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108848
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108818}
        #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 {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108816 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108785
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108824
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#108823
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#108817
      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 {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#115772
  +product: App\Entity\Product\Product {#108818
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751037901 {#108825
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108798
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108809 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108848
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108818}
        #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 {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108816 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108785
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108824
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#108823
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#108817
      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 {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 88.0 MiB 0.66 ms
Input props 
[
  "product" => App\Entity\Product\Product {#108818
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751037901 {#108825
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108798
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108809 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108848
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108818}
        #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 {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108816 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108785
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108824
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#108823
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#108817
      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 {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#115799
  +product: App\Entity\Product\Product {#108818
    #id: 9016
    #code: "IEEE00001477"
    #attributes: Doctrine\ORM\PersistentCollection {#108799 …}
    #variants: Doctrine\ORM\PersistentCollection {#108796 …}
    #options: Doctrine\ORM\PersistentCollection {#108792 …}
    #associations: Doctrine\ORM\PersistentCollection {#108794 …}
    #createdAt: DateTime @1751037901 {#108825
      date: 2025-06-27 17:25:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108798
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108809 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#108848
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108818}
        #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 {#108807 …}
    #channels: Doctrine\ORM\PersistentCollection {#108801 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108805 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108803 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108816 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108785
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108824
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @553125600 {#108823
      date: 1987-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#108817
      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 {#108814 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108812 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}