Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10919
    #code: "IEEE00005289"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039365 {#7274
      date: 2025-06-27 17:49:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 38685
        #name: "IEEE/ISO/IEC 29148:2011"
        #slug: "ieee-iso-iec-29148-2011-ieee00005289-242571"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This International Standard<br />\n
          - specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,<br />\n
          - gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008),<br />\n
          - specifies the required information items that are to be produced through the implementation of the requirements processes,<br />\n
          - specifies the required contents of the required information items, and<br />\n
          - gives guidelines for the format of the required and related information items.<br />\n
          This International Standard is applicable to<br />\n
          - those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008),<br />\n
          - those who use or plan to use ISO/IEC/IEEE 15289:2011 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, and<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#93007
  +product: App\Entity\Product\Product {#7310
    #id: 10919
    #code: "IEEE00005289"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039365 {#7274
      date: 2025-06-27 17:49:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 38685
        #name: "IEEE/ISO/IEC 29148:2011"
        #slug: "ieee-iso-iec-29148-2011-ieee00005289-242571"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This International Standard<br />\n
          - specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,<br />\n
          - gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008),<br />\n
          - specifies the required information items that are to be produced through the implementation of the requirements processes,<br />\n
          - specifies the required contents of the required information items, and<br />\n
          - gives guidelines for the format of the required and related information items.<br />\n
          This International Standard is applicable to<br />\n
          - those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008),<br />\n
          - those who use or plan to use ISO/IEC/IEEE 15289:2011 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, and<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10919
    #code: "IEEE00005289"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039365 {#7274
      date: 2025-06-27 17:49:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 38685
        #name: "IEEE/ISO/IEC 29148:2011"
        #slug: "ieee-iso-iec-29148-2011-ieee00005289-242571"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This International Standard<br />\n
          - specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,<br />\n
          - gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008),<br />\n
          - specifies the required information items that are to be produced through the implementation of the requirements processes,<br />\n
          - specifies the required contents of the required information items, and<br />\n
          - gives guidelines for the format of the required and related information items.<br />\n
          This International Standard is applicable to<br />\n
          - those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008),<br />\n
          - those who use or plan to use ISO/IEC/IEEE 15289:2011 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, and<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductType {#93187
  +product: App\Entity\Product\Product {#7310
    #id: 10919
    #code: "IEEE00005289"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039365 {#7274
      date: 2025-06-27 17:49:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 38685
        #name: "IEEE/ISO/IEC 29148:2011"
        #slug: "ieee-iso-iec-29148-2011-ieee00005289-242571"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This International Standard<br />\n
          - specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,<br />\n
          - gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008),<br />\n
          - specifies the required information items that are to be produced through the implementation of the requirements processes,<br />\n
          - specifies the required contents of the required information items, and<br />\n
          - gives guidelines for the format of the required and related information items.<br />\n
          This International Standard is applicable to<br />\n
          - those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008),<br />\n
          - those who use or plan to use ISO/IEC/IEEE 15289:2011 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, and<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10919
    #code: "IEEE00005289"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039365 {#7274
      date: 2025-06-27 17:49:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 38685
        #name: "IEEE/ISO/IEC 29148:2011"
        #slug: "ieee-iso-iec-29148-2011-ieee00005289-242571"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This International Standard<br />\n
          - specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,<br />\n
          - gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008),<br />\n
          - specifies the required information items that are to be produced through the implementation of the requirements processes,<br />\n
          - specifies the required contents of the required information items, and<br />\n
          - gives guidelines for the format of the required and related information items.<br />\n
          This International Standard is applicable to<br />\n
          - those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008),<br />\n
          - those who use or plan to use ISO/IEC/IEEE 15289:2011 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, and<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#93262
  +product: App\Entity\Product\Product {#7310
    #id: 10919
    #code: "IEEE00005289"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039365 {#7274
      date: 2025-06-27 17:49:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 38685
        #name: "IEEE/ISO/IEC 29148:2011"
        #slug: "ieee-iso-iec-29148-2011-ieee00005289-242571"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This International Standard<br />\n
          - specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,<br />\n
          - gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008),<br />\n
          - specifies the required information items that are to be produced through the implementation of the requirements processes,<br />\n
          - specifies the required contents of the required information items, and<br />\n
          - gives guidelines for the format of the required and related information items.<br />\n
          This International Standard is applicable to<br />\n
          - those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008),<br />\n
          - those who use or plan to use ISO/IEC/IEEE 15289:2011 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, and<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106698
    #id: 9225
    #code: "IEEE00001879"
    #attributes: Doctrine\ORM\PersistentCollection {#106681 …}
    #variants: Doctrine\ORM\PersistentCollection {#106678 …}
    #options: Doctrine\ORM\PersistentCollection {#106674 …}
    #associations: Doctrine\ORM\PersistentCollection {#106676 …}
    #createdAt: DateTime @1751038076 {#106706
      date: 2025-06-27 17:27:56.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106679
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106797
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106698}
        #id: 31909
        #name: "IEEE 1233:1998"
        #slug: "ieee-1233-1998-ieee00001879-240877"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. Guidance for the development of the set of requirements, System Requirements Specification (SyRS), that will satisfy an expressed need is provided. Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. Also addressed are the conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also covers the necessary characteristics and qualities of individual requirements and the set of all requirements.<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for the development of a set of requirements that, when realized, will satisfy an expressed need. In this guide that set of requirements will be called the System Requirements Specification (SyRS). Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. This guide addresses conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also addresses the necessary characteristics and qualities of individual requirements and the set of all requirements. This guide does not specify industry-wide system specification standards nor state a mandatory System Requirements Specification. This guide is written under the premise that the current state of the art of system development does not warrant or support a formal standards document.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Developing System Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106689 …}
    #channels: Doctrine\ORM\PersistentCollection {#106683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106687 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106699 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106666
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1604358000 {#106705
      date: 2020-11-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914886000 {#106704
      date: 1998-12-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1233"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106694 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106810
  +product: App\Entity\Product\Product {#106698
    #id: 9225
    #code: "IEEE00001879"
    #attributes: Doctrine\ORM\PersistentCollection {#106681 …}
    #variants: Doctrine\ORM\PersistentCollection {#106678 …}
    #options: Doctrine\ORM\PersistentCollection {#106674 …}
    #associations: Doctrine\ORM\PersistentCollection {#106676 …}
    #createdAt: DateTime @1751038076 {#106706
      date: 2025-06-27 17:27:56.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106679
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106797
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106698}
        #id: 31909
        #name: "IEEE 1233:1998"
        #slug: "ieee-1233-1998-ieee00001879-240877"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. Guidance for the development of the set of requirements, System Requirements Specification (SyRS), that will satisfy an expressed need is provided. Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. Also addressed are the conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also covers the necessary characteristics and qualities of individual requirements and the set of all requirements.<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for the development of a set of requirements that, when realized, will satisfy an expressed need. In this guide that set of requirements will be called the System Requirements Specification (SyRS). Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. This guide addresses conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also addresses the necessary characteristics and qualities of individual requirements and the set of all requirements. This guide does not specify industry-wide system specification standards nor state a mandatory System Requirements Specification. This guide is written under the premise that the current state of the art of system development does not warrant or support a formal standards document.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Developing System Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106689 …}
    #channels: Doctrine\ORM\PersistentCollection {#106683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106687 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106699 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106666
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1604358000 {#106705
      date: 2020-11-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914886000 {#106704
      date: 1998-12-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1233"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106694 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106698
    #id: 9225
    #code: "IEEE00001879"
    #attributes: Doctrine\ORM\PersistentCollection {#106681 …}
    #variants: Doctrine\ORM\PersistentCollection {#106678 …}
    #options: Doctrine\ORM\PersistentCollection {#106674 …}
    #associations: Doctrine\ORM\PersistentCollection {#106676 …}
    #createdAt: DateTime @1751038076 {#106706
      date: 2025-06-27 17:27:56.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106679
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106797
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106698}
        #id: 31909
        #name: "IEEE 1233:1998"
        #slug: "ieee-1233-1998-ieee00001879-240877"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. Guidance for the development of the set of requirements, System Requirements Specification (SyRS), that will satisfy an expressed need is provided. Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. Also addressed are the conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also covers the necessary characteristics and qualities of individual requirements and the set of all requirements.<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for the development of a set of requirements that, when realized, will satisfy an expressed need. In this guide that set of requirements will be called the System Requirements Specification (SyRS). Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. This guide addresses conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also addresses the necessary characteristics and qualities of individual requirements and the set of all requirements. This guide does not specify industry-wide system specification standards nor state a mandatory System Requirements Specification. This guide is written under the premise that the current state of the art of system development does not warrant or support a formal standards document.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Developing System Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106689 …}
    #channels: Doctrine\ORM\PersistentCollection {#106683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106687 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106699 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106666
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1604358000 {#106705
      date: 2020-11-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914886000 {#106704
      date: 1998-12-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1233"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106694 …}
  }
]

App\Twig\Components\ProductMostRecent {#106877
  +product: App\Entity\Product\Product {#106698
    #id: 9225
    #code: "IEEE00001879"
    #attributes: Doctrine\ORM\PersistentCollection {#106681 …}
    #variants: Doctrine\ORM\PersistentCollection {#106678 …}
    #options: Doctrine\ORM\PersistentCollection {#106674 …}
    #associations: Doctrine\ORM\PersistentCollection {#106676 …}
    #createdAt: DateTime @1751038076 {#106706
      date: 2025-06-27 17:27:56.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106679
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106797
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106698}
        #id: 31909
        #name: "IEEE 1233:1998"
        #slug: "ieee-1233-1998-ieee00001879-240877"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. Guidance for the development of the set of requirements, System Requirements Specification (SyRS), that will satisfy an expressed need is provided. Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. Also addressed are the conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also covers the necessary characteristics and qualities of individual requirements and the set of all requirements.<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for the development of a set of requirements that, when realized, will satisfy an expressed need. In this guide that set of requirements will be called the System Requirements Specification (SyRS). Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. This guide addresses conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also addresses the necessary characteristics and qualities of individual requirements and the set of all requirements. This guide does not specify industry-wide system specification standards nor state a mandatory System Requirements Specification. This guide is written under the premise that the current state of the art of system development does not warrant or support a formal standards document.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Developing System Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106689 …}
    #channels: Doctrine\ORM\PersistentCollection {#106683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106687 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106699 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106666
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1604358000 {#106705
      date: 2020-11-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914886000 {#106704
      date: 1998-12-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1233"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106694 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106741
    #id: 9314
    #code: "IEEE00002047"
    #attributes: Doctrine\ORM\PersistentCollection {#106732 …}
    #variants: Doctrine\ORM\PersistentCollection {#106726 …}
    #options: Doctrine\ORM\PersistentCollection {#106727 …}
    #associations: Doctrine\ORM\PersistentCollection {#106729 …}
    #createdAt: DateTime @1751038161 {#106671
      date: 2025-06-27 17:29:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106670
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106744 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106944
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106741}
        #id: 32265
        #name: "IEEE 1362:1998 (R2007)"
        #slug: "ieee-1362-1998-r2007-ieee00002047-240966"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The format and contents of a concept of operations (ConOps) document are described. AConOps is a user-oriented document that describes system characteristics for a proposed system from theusersO viewpoint. The ConOps document is used to communicate overall quantitative and qualitativesystem characteristics to the user, buyer, developer, and other organizational elements (for example,training, facilities, staffing, and maintenance). It is used to describe the user organization(s), mission(s), andorganizational objectives from an integrated systems point of view.<br />\n
          \t\t\t\t<br />\n
          To prescribe the format and contents of concept of operation document.<br />\n
          To provide a uniform scheme for preparing and presenting a concept of operations document. A concept of operations (CONOPS) document describes the mission of the system and its operational and support environments. The CONOPS describes the functions and characteristics of the computer system within the overall system. The CONOPS represent a consensus among development, support and user organizations on the operational concept of the system being developed. The CONOPS provides the basis for the system requirements document.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Information Technology - System Definition - Concept of Operations (ConOps) Document"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106742 …}
    #channels: Doctrine\ORM\PersistentCollection {#106736 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106735 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106738 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106737 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106669
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106668
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914281200 {#106662
      date: 1998-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1196809200 {#106667
      date: 2007-12-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1362"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#106719 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106749 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106959
  +product: App\Entity\Product\Product {#106741
    #id: 9314
    #code: "IEEE00002047"
    #attributes: Doctrine\ORM\PersistentCollection {#106732 …}
    #variants: Doctrine\ORM\PersistentCollection {#106726 …}
    #options: Doctrine\ORM\PersistentCollection {#106727 …}
    #associations: Doctrine\ORM\PersistentCollection {#106729 …}
    #createdAt: DateTime @1751038161 {#106671
      date: 2025-06-27 17:29:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106670
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106744 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106944
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106741}
        #id: 32265
        #name: "IEEE 1362:1998 (R2007)"
        #slug: "ieee-1362-1998-r2007-ieee00002047-240966"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The format and contents of a concept of operations (ConOps) document are described. AConOps is a user-oriented document that describes system characteristics for a proposed system from theusersO viewpoint. The ConOps document is used to communicate overall quantitative and qualitativesystem characteristics to the user, buyer, developer, and other organizational elements (for example,training, facilities, staffing, and maintenance). It is used to describe the user organization(s), mission(s), andorganizational objectives from an integrated systems point of view.<br />\n
          \t\t\t\t<br />\n
          To prescribe the format and contents of concept of operation document.<br />\n
          To provide a uniform scheme for preparing and presenting a concept of operations document. A concept of operations (CONOPS) document describes the mission of the system and its operational and support environments. The CONOPS describes the functions and characteristics of the computer system within the overall system. The CONOPS represent a consensus among development, support and user organizations on the operational concept of the system being developed. The CONOPS provides the basis for the system requirements document.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Information Technology - System Definition - Concept of Operations (ConOps) Document"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106742 …}
    #channels: Doctrine\ORM\PersistentCollection {#106736 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106735 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106738 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106737 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106669
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106668
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914281200 {#106662
      date: 1998-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1196809200 {#106667
      date: 2007-12-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1362"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#106719 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106749 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106741
    #id: 9314
    #code: "IEEE00002047"
    #attributes: Doctrine\ORM\PersistentCollection {#106732 …}
    #variants: Doctrine\ORM\PersistentCollection {#106726 …}
    #options: Doctrine\ORM\PersistentCollection {#106727 …}
    #associations: Doctrine\ORM\PersistentCollection {#106729 …}
    #createdAt: DateTime @1751038161 {#106671
      date: 2025-06-27 17:29:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106670
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106744 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106944
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106741}
        #id: 32265
        #name: "IEEE 1362:1998 (R2007)"
        #slug: "ieee-1362-1998-r2007-ieee00002047-240966"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The format and contents of a concept of operations (ConOps) document are described. AConOps is a user-oriented document that describes system characteristics for a proposed system from theusersO viewpoint. The ConOps document is used to communicate overall quantitative and qualitativesystem characteristics to the user, buyer, developer, and other organizational elements (for example,training, facilities, staffing, and maintenance). It is used to describe the user organization(s), mission(s), andorganizational objectives from an integrated systems point of view.<br />\n
          \t\t\t\t<br />\n
          To prescribe the format and contents of concept of operation document.<br />\n
          To provide a uniform scheme for preparing and presenting a concept of operations document. A concept of operations (CONOPS) document describes the mission of the system and its operational and support environments. The CONOPS describes the functions and characteristics of the computer system within the overall system. The CONOPS represent a consensus among development, support and user organizations on the operational concept of the system being developed. The CONOPS provides the basis for the system requirements document.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Information Technology - System Definition - Concept of Operations (ConOps) Document"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106742 …}
    #channels: Doctrine\ORM\PersistentCollection {#106736 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106735 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106738 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106737 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106669
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106668
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914281200 {#106662
      date: 1998-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1196809200 {#106667
      date: 2007-12-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1362"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#106719 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106749 …}
  }
]

App\Twig\Components\ProductMostRecent {#107015
  +product: App\Entity\Product\Product {#106741
    #id: 9314
    #code: "IEEE00002047"
    #attributes: Doctrine\ORM\PersistentCollection {#106732 …}
    #variants: Doctrine\ORM\PersistentCollection {#106726 …}
    #options: Doctrine\ORM\PersistentCollection {#106727 …}
    #associations: Doctrine\ORM\PersistentCollection {#106729 …}
    #createdAt: DateTime @1751038161 {#106671
      date: 2025-06-27 17:29:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106670
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106744 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106944
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106741}
        #id: 32265
        #name: "IEEE 1362:1998 (R2007)"
        #slug: "ieee-1362-1998-r2007-ieee00002047-240966"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The format and contents of a concept of operations (ConOps) document are described. AConOps is a user-oriented document that describes system characteristics for a proposed system from theusersO viewpoint. The ConOps document is used to communicate overall quantitative and qualitativesystem characteristics to the user, buyer, developer, and other organizational elements (for example,training, facilities, staffing, and maintenance). It is used to describe the user organization(s), mission(s), andorganizational objectives from an integrated systems point of view.<br />\n
          \t\t\t\t<br />\n
          To prescribe the format and contents of concept of operation document.<br />\n
          To provide a uniform scheme for preparing and presenting a concept of operations document. A concept of operations (CONOPS) document describes the mission of the system and its operational and support environments. The CONOPS describes the functions and characteristics of the computer system within the overall system. The CONOPS represent a consensus among development, support and user organizations on the operational concept of the system being developed. The CONOPS provides the basis for the system requirements document.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Information Technology - System Definition - Concept of Operations (ConOps) Document"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106742 …}
    #channels: Doctrine\ORM\PersistentCollection {#106736 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106735 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106738 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106737 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106669
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106668
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914281200 {#106662
      date: 1998-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1196809200 {#106667
      date: 2007-12-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1362"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#106719 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106749 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106718
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#106761 …}
    #variants: Doctrine\ORM\PersistentCollection {#106763 …}
    #options: Doctrine\ORM\PersistentCollection {#106767 …}
    #associations: Doctrine\ORM\PersistentCollection {#106765 …}
    #createdAt: DateTime @1751037795 {#106723
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106716
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106751 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107085
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106718}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106753 …}
    #channels: Doctrine\ORM\PersistentCollection {#106759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106755 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106757 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106715 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106717
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#106722
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#106720
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#106721
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#106713 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106745 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#107100
  +product: App\Entity\Product\Product {#106718
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#106761 …}
    #variants: Doctrine\ORM\PersistentCollection {#106763 …}
    #options: Doctrine\ORM\PersistentCollection {#106767 …}
    #associations: Doctrine\ORM\PersistentCollection {#106765 …}
    #createdAt: DateTime @1751037795 {#106723
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106716
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106751 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107085
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106718}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106753 …}
    #channels: Doctrine\ORM\PersistentCollection {#106759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106755 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106757 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106715 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106717
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#106722
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#106720
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#106721
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#106713 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106745 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106718
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#106761 …}
    #variants: Doctrine\ORM\PersistentCollection {#106763 …}
    #options: Doctrine\ORM\PersistentCollection {#106767 …}
    #associations: Doctrine\ORM\PersistentCollection {#106765 …}
    #createdAt: DateTime @1751037795 {#106723
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106716
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106751 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107085
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106718}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106753 …}
    #channels: Doctrine\ORM\PersistentCollection {#106759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106755 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106757 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106715 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106717
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#106722
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#106720
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#106721
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#106713 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106745 …}
  }
]

App\Twig\Components\ProductMostRecent {#107152
  +product: App\Entity\Product\Product {#106718
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#106761 …}
    #variants: Doctrine\ORM\PersistentCollection {#106763 …}
    #options: Doctrine\ORM\PersistentCollection {#106767 …}
    #associations: Doctrine\ORM\PersistentCollection {#106765 …}
    #createdAt: DateTime @1751037795 {#106723
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106716
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106751 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107085
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106718}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106753 …}
    #channels: Doctrine\ORM\PersistentCollection {#106759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106755 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106757 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106715 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106717
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#106722
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#106720
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#106721
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#106713 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106745 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93699
    #id: 12017
    #code: "IEEE00006937"
    #attributes: Doctrine\ORM\PersistentCollection {#93681 …}
    #variants: Doctrine\ORM\PersistentCollection {#93678 …}
    #options: Doctrine\ORM\PersistentCollection {#93674 …}
    #associations: Doctrine\ORM\PersistentCollection {#93676 …}
    #createdAt: DateTime @1751040140 {#93707
      date: 2025-06-27 18:02:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93686
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93727
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 43077
        #name: "IEEE/ISO/IEC 29148:2018"
        #slug: "ieee-iso-iec-29148-2018-ieee00006937-243669"
        #description: """
          Revision Standard - Active.<br />\n
          This document contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. This document provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288. Information items applicable to the engineering of requirements and their content are defined. The content of this document can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This document: specifies the required processes implemented in the engineering activities that result in requirements for systems and software products (including services) throughout the life cycle; provides guidelines for applying the requirements and requirements-related processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207; specifies the required information items produced through the implementation of the requirements processes; specifies the required contents of the required information items; provides guidelines for the format of the required and related information items. This document is applicable to: those who use or plan to use ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of the project scope, product(s), methodology,size or complexity; anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC/IEEE 15288 and/or ISO/IEC/IEEE 12207; those who use or plan to use ISO/IEC/IEEE 15289 on projects dealing with man-made systems, software-intensive systems, software and hardware products and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity; anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conforms to ISO/IEC/IEEE 15289.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes -- Requirements engineering"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …}
    #channels: Doctrine\ORM\PersistentCollection {#93683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93688 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93670
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1631829600 {#93706
      date: 2021-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1543532400 {#93705
      date: 2018-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#93696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93694 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113769
  +product: App\Entity\Product\Product {#93699
    #id: 12017
    #code: "IEEE00006937"
    #attributes: Doctrine\ORM\PersistentCollection {#93681 …}
    #variants: Doctrine\ORM\PersistentCollection {#93678 …}
    #options: Doctrine\ORM\PersistentCollection {#93674 …}
    #associations: Doctrine\ORM\PersistentCollection {#93676 …}
    #createdAt: DateTime @1751040140 {#93707
      date: 2025-06-27 18:02:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93686
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93727
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 43077
        #name: "IEEE/ISO/IEC 29148:2018"
        #slug: "ieee-iso-iec-29148-2018-ieee00006937-243669"
        #description: """
          Revision Standard - Active.<br />\n
          This document contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. This document provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288. Information items applicable to the engineering of requirements and their content are defined. The content of this document can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This document: specifies the required processes implemented in the engineering activities that result in requirements for systems and software products (including services) throughout the life cycle; provides guidelines for applying the requirements and requirements-related processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207; specifies the required information items produced through the implementation of the requirements processes; specifies the required contents of the required information items; provides guidelines for the format of the required and related information items. This document is applicable to: those who use or plan to use ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of the project scope, product(s), methodology,size or complexity; anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC/IEEE 15288 and/or ISO/IEC/IEEE 12207; those who use or plan to use ISO/IEC/IEEE 15289 on projects dealing with man-made systems, software-intensive systems, software and hardware products and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity; anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conforms to ISO/IEC/IEEE 15289.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes -- Requirements engineering"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …}
    #channels: Doctrine\ORM\PersistentCollection {#93683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93688 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93670
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1631829600 {#93706
      date: 2021-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1543532400 {#93705
      date: 2018-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#93696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93694 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93699
    #id: 12017
    #code: "IEEE00006937"
    #attributes: Doctrine\ORM\PersistentCollection {#93681 …}
    #variants: Doctrine\ORM\PersistentCollection {#93678 …}
    #options: Doctrine\ORM\PersistentCollection {#93674 …}
    #associations: Doctrine\ORM\PersistentCollection {#93676 …}
    #createdAt: DateTime @1751040140 {#93707
      date: 2025-06-27 18:02:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93686
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93727
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 43077
        #name: "IEEE/ISO/IEC 29148:2018"
        #slug: "ieee-iso-iec-29148-2018-ieee00006937-243669"
        #description: """
          Revision Standard - Active.<br />\n
          This document contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. This document provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288. Information items applicable to the engineering of requirements and their content are defined. The content of this document can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This document: specifies the required processes implemented in the engineering activities that result in requirements for systems and software products (including services) throughout the life cycle; provides guidelines for applying the requirements and requirements-related processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207; specifies the required information items produced through the implementation of the requirements processes; specifies the required contents of the required information items; provides guidelines for the format of the required and related information items. This document is applicable to: those who use or plan to use ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of the project scope, product(s), methodology,size or complexity; anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC/IEEE 15288 and/or ISO/IEC/IEEE 12207; those who use or plan to use ISO/IEC/IEEE 15289 on projects dealing with man-made systems, software-intensive systems, software and hardware products and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity; anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conforms to ISO/IEC/IEEE 15289.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes -- Requirements engineering"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …}
    #channels: Doctrine\ORM\PersistentCollection {#93683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93688 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93670
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1631829600 {#93706
      date: 2021-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1543532400 {#93705
      date: 2018-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#93696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93694 …}
  }
]

App\Twig\Components\ProductMostRecent {#113836
  +product: App\Entity\Product\Product {#93699
    #id: 12017
    #code: "IEEE00006937"
    #attributes: Doctrine\ORM\PersistentCollection {#93681 …}
    #variants: Doctrine\ORM\PersistentCollection {#93678 …}
    #options: Doctrine\ORM\PersistentCollection {#93674 …}
    #associations: Doctrine\ORM\PersistentCollection {#93676 …}
    #createdAt: DateTime @1751040140 {#93707
      date: 2025-06-27 18:02:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93686
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93727
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 43077
        #name: "IEEE/ISO/IEC 29148:2018"
        #slug: "ieee-iso-iec-29148-2018-ieee00006937-243669"
        #description: """
          Revision Standard - Active.<br />\n
          This document contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. This document provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288. Information items applicable to the engineering of requirements and their content are defined. The content of this document can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This document: specifies the required processes implemented in the engineering activities that result in requirements for systems and software products (including services) throughout the life cycle; provides guidelines for applying the requirements and requirements-related processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207; specifies the required information items produced through the implementation of the requirements processes; specifies the required contents of the required information items; provides guidelines for the format of the required and related information items. This document is applicable to: those who use or plan to use ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of the project scope, product(s), methodology,size or complexity; anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC/IEEE 15288 and/or ISO/IEC/IEEE 12207; those who use or plan to use ISO/IEC/IEEE 15289 on projects dealing with man-made systems, software-intensive systems, software and hardware products and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity; anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conforms to ISO/IEC/IEEE 15289.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes -- Requirements engineering"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …}
    #channels: Doctrine\ORM\PersistentCollection {#93683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93688 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93670
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1631829600 {#93706
      date: 2021-09-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1543532400 {#93705
      date: 2018-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#93696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93694 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10919
    #code: "IEEE00005289"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039365 {#7274
      date: 2025-06-27 17:49:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 38685
        #name: "IEEE/ISO/IEC 29148:2011"
        #slug: "ieee-iso-iec-29148-2011-ieee00005289-242571"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This International Standard<br />\n
          - specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,<br />\n
          - gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008),<br />\n
          - specifies the required information items that are to be produced through the implementation of the requirements processes,<br />\n
          - specifies the required contents of the required information items, and<br />\n
          - gives guidelines for the format of the required and related information items.<br />\n
          This International Standard is applicable to<br />\n
          - those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008),<br />\n
          - those who use or plan to use ISO/IEC/IEEE 15289:2011 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, and<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113901
  +product: App\Entity\Product\Product {#7310
    #id: 10919
    #code: "IEEE00005289"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039365 {#7274
      date: 2025-06-27 17:49:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 38685
        #name: "IEEE/ISO/IEC 29148:2011"
        #slug: "ieee-iso-iec-29148-2011-ieee00005289-242571"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This International Standard<br />\n
          - specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,<br />\n
          - gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008),<br />\n
          - specifies the required information items that are to be produced through the implementation of the requirements processes,<br />\n
          - specifies the required contents of the required information items, and<br />\n
          - gives guidelines for the format of the required and related information items.<br />\n
          This International Standard is applicable to<br />\n
          - those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008),<br />\n
          - those who use or plan to use ISO/IEC/IEEE 15289:2011 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, and<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10919
    #code: "IEEE00005289"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039365 {#7274
      date: 2025-06-27 17:49:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 38685
        #name: "IEEE/ISO/IEC 29148:2011"
        #slug: "ieee-iso-iec-29148-2011-ieee00005289-242571"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This International Standard<br />\n
          - specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,<br />\n
          - gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008),<br />\n
          - specifies the required information items that are to be produced through the implementation of the requirements processes,<br />\n
          - specifies the required contents of the required information items, and<br />\n
          - gives guidelines for the format of the required and related information items.<br />\n
          This International Standard is applicable to<br />\n
          - those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008),<br />\n
          - those who use or plan to use ISO/IEC/IEEE 15289:2011 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, and<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#113928
  +product: App\Entity\Product\Product {#7310
    #id: 10919
    #code: "IEEE00005289"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039365 {#7274
      date: 2025-06-27 17:49:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 38685
        #name: "IEEE/ISO/IEC 29148:2011"
        #slug: "ieee-iso-iec-29148-2011-ieee00005289-242571"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998. ISO/IEC/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO/IEC/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC 12207 and ISO/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO/IEC/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC 12207 or ISO/IEC 15288, or can be used independently.<br />\n
          \t\t\t\t<br />\n
          This International Standard<br />\n
          - specifies the required processes that are to be implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,<br />\n
          - gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008),<br />\n
          - specifies the required information items that are to be produced through the implementation of the requirements processes,<br />\n
          - specifies the required contents of the required information items, and<br />\n
          - gives guidelines for the format of the required and related information items.<br />\n
          This International Standard is applicable to<br />\n
          - those who use or plan to use ISO/IEC 15288 and ISO/IEC 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity,<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO/IEC 15288:2008 (IEEE Std 15288-2008) and/or ISO/IEC 12207:2008 (IEEE Std 12207-2008),<br />\n
          - those who use or plan to use ISO/IEC/IEEE 15289:2011 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of project scope, product(s), methodology, size or complexity, and<br />\n
          - anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conform to ISO/IEC/IEEE 15289:2011.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1322694000 {#7318
      date: 2011-12-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29148"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106718
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#106761 …}
    #variants: Doctrine\ORM\PersistentCollection {#106763 …}
    #options: Doctrine\ORM\PersistentCollection {#106767 …}
    #associations: Doctrine\ORM\PersistentCollection {#106765 …}
    #createdAt: DateTime @1751037795 {#106723
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106716
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106751 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107085
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106718}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106753 …}
    #channels: Doctrine\ORM\PersistentCollection {#106759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106755 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106757 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106715 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106717
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#106722
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#106720
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#106721
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#106713 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106745 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#135515
  +product: App\Entity\Product\Product {#106718
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#106761 …}
    #variants: Doctrine\ORM\PersistentCollection {#106763 …}
    #options: Doctrine\ORM\PersistentCollection {#106767 …}
    #associations: Doctrine\ORM\PersistentCollection {#106765 …}
    #createdAt: DateTime @1751037795 {#106723
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106716
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106751 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107085
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106718}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106753 …}
    #channels: Doctrine\ORM\PersistentCollection {#106759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106755 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106757 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106715 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106717
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#106722
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#106720
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#106721
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#106713 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106745 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}

[
  "product" => App\Entity\Product\Product {#106718
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#106761 …}
    #variants: Doctrine\ORM\PersistentCollection {#106763 …}
    #options: Doctrine\ORM\PersistentCollection {#106767 …}
    #associations: Doctrine\ORM\PersistentCollection {#106765 …}
    #createdAt: DateTime @1751037795 {#106723
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106716
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106751 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107085
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106718}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106753 …}
    #channels: Doctrine\ORM\PersistentCollection {#106759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106755 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106757 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106715 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106717
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#106722
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#106720
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#106721
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#106713 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106745 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#135600
  +product: App\Entity\Product\Product {#106718
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#106761 …}
    #variants: Doctrine\ORM\PersistentCollection {#106763 …}
    #options: Doctrine\ORM\PersistentCollection {#106767 …}
    #associations: Doctrine\ORM\PersistentCollection {#106765 …}
    #createdAt: DateTime @1751037795 {#106723
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106716
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106751 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107085
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106718}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106753 …}
    #channels: Doctrine\ORM\PersistentCollection {#106759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106755 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106757 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106715 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106717
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#106722
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#106720
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#106721
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#106713 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106745 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106718
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#106761 …}
    #variants: Doctrine\ORM\PersistentCollection {#106763 …}
    #options: Doctrine\ORM\PersistentCollection {#106767 …}
    #associations: Doctrine\ORM\PersistentCollection {#106765 …}
    #createdAt: DateTime @1751037795 {#106723
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106716
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106751 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107085
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106718}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106753 …}
    #channels: Doctrine\ORM\PersistentCollection {#106759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106755 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106757 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106715 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106717
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#106722
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#106720
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#106721
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#106713 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106745 …}
  }
]

App\Twig\Components\ProductMostRecent {#135645
  +product: App\Entity\Product\Product {#106718
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#106761 …}
    #variants: Doctrine\ORM\PersistentCollection {#106763 …}
    #options: Doctrine\ORM\PersistentCollection {#106767 …}
    #associations: Doctrine\ORM\PersistentCollection {#106765 …}
    #createdAt: DateTime @1751037795 {#106723
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106716
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106751 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107085
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106718}
        #id: 30565
        #name: "IEEE 830:1998 (R2009)"
        #slug: "ieee-830-1998-r2009-ieee00001222-240541"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/ EIA12207.1- 1997 are also provided.<br />\n
          \t\t\t\t<br />\n
          The general area of requirements for software systems as specified by either potential customers/users or designers/producers and constituting the substance of an agreement between them. To establish a correlation between the content of software requirements specifications as defined in 830 and the content of such documentation as defined in IEEE 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data by adding an annex which will correlate the assumptions relating to content of the two documents and trace content between subject documentation<br />\n
          To achieve harmonization of the content definition for software life cycle process results among the IEEE software engineering standards and with related international standards. This will help users to produce results consistent with the international standard for software life cycle processes, ISO/IEC 12207.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106753 …}
    #channels: Doctrine\ORM\PersistentCollection {#106759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106755 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106757 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106715 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106717
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#106722
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#106720
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#106721
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#106713 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106745 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106698
    #id: 9225
    #code: "IEEE00001879"
    #attributes: Doctrine\ORM\PersistentCollection {#106681 …}
    #variants: Doctrine\ORM\PersistentCollection {#106678 …}
    #options: Doctrine\ORM\PersistentCollection {#106674 …}
    #associations: Doctrine\ORM\PersistentCollection {#106676 …}
    #createdAt: DateTime @1751038076 {#106706
      date: 2025-06-27 17:27:56.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106679
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106797
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106698}
        #id: 31909
        #name: "IEEE 1233:1998"
        #slug: "ieee-1233-1998-ieee00001879-240877"
        #description: """
          Revision Standard - Superseded.<br />\n
          Replaced by ISO/IEC/IEEE 29148:2011. Guidance for the development of the set of requirements, System Requirements Specification (SyRS), that will satisfy an expressed need is provided. Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. Also addressed are the conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also covers the necessary characteristics and qualities of individual requirements and the set of all requirements.<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for the development of a set of requirements that, when realized, will satisfy an expressed need. In this guide that set of requirements will be called the System Requirements Specification (SyRS). Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. This guide addresses conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also addresses the necessary characteristics and qualities of individual requirements and the set of all requirements. This guide does not specify industry-wide system specification standards nor state a mandatory System Requirements Specification. This guide is written under the premise that the current state of the art of system development does not warrant or support a formal standards document.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Developing System Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106689 …}
    #channels: Doctrine\ORM\PersistentCollection {#106683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106687 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106699 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106666
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1604358000 {#106705
      date: 2020-11-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @914886000 {#106704
      date: 1998-12-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1233"
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#106696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106694 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]