Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7520
    #id: 8887
    #code: "IEEE00001220"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037793 {#7536
      date: 2025-06-27 17:23:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #id: 30557
        #name: "IEEE 830:1984"
        #slug: "ieee-830-1984-ieee00001220-240539"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a guide for writing software requirements specifications. It describer; the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.<br />\n
          This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.<br />\n
          This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.<br />\n
          This guide is applicable to in-house and commercial software products. Special care, however,<br />\n
          should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.<br />\n
          (2) This guide does not cover the specification of requirements for software being developed<br />\n
          using the techniques of rapid prototyping.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @445215600 {#7531
      date: 1984-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 26
    -documents: Doctrine\ORM\PersistentCollection {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#95002
  +product: App\Entity\Product\Product {#7520
    #id: 8887
    #code: "IEEE00001220"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037793 {#7536
      date: 2025-06-27 17:23:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #id: 30557
        #name: "IEEE 830:1984"
        #slug: "ieee-830-1984-ieee00001220-240539"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a guide for writing software requirements specifications. It describer; the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.<br />\n
          This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.<br />\n
          This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.<br />\n
          This guide is applicable to in-house and commercial software products. Special care, however,<br />\n
          should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.<br />\n
          (2) This guide does not cover the specification of requirements for software being developed<br />\n
          using the techniques of rapid prototyping.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @445215600 {#7531
      date: 1984-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 26
    -documents: Doctrine\ORM\PersistentCollection {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7520
    #id: 8887
    #code: "IEEE00001220"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037793 {#7536
      date: 2025-06-27 17:23:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #id: 30557
        #name: "IEEE 830:1984"
        #slug: "ieee-830-1984-ieee00001220-240539"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a guide for writing software requirements specifications. It describer; the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.<br />\n
          This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.<br />\n
          This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.<br />\n
          This guide is applicable to in-house and commercial software products. Special care, however,<br />\n
          should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.<br />\n
          (2) This guide does not cover the specification of requirements for software being developed<br />\n
          using the techniques of rapid prototyping.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @445215600 {#7531
      date: 1984-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 26
    -documents: Doctrine\ORM\PersistentCollection {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
]

App\Twig\Components\ProductType {#95182
  +product: App\Entity\Product\Product {#7520
    #id: 8887
    #code: "IEEE00001220"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037793 {#7536
      date: 2025-06-27 17:23:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #id: 30557
        #name: "IEEE 830:1984"
        #slug: "ieee-830-1984-ieee00001220-240539"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a guide for writing software requirements specifications. It describer; the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.<br />\n
          This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.<br />\n
          This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.<br />\n
          This guide is applicable to in-house and commercial software products. Special care, however,<br />\n
          should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.<br />\n
          (2) This guide does not cover the specification of requirements for software being developed<br />\n
          using the techniques of rapid prototyping.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @445215600 {#7531
      date: 1984-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 26
    -documents: Doctrine\ORM\PersistentCollection {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7520
    #id: 8887
    #code: "IEEE00001220"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037793 {#7536
      date: 2025-06-27 17:23:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #id: 30557
        #name: "IEEE 830:1984"
        #slug: "ieee-830-1984-ieee00001220-240539"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a guide for writing software requirements specifications. It describer; the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.<br />\n
          This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.<br />\n
          This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.<br />\n
          This guide is applicable to in-house and commercial software products. Special care, however,<br />\n
          should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.<br />\n
          (2) This guide does not cover the specification of requirements for software being developed<br />\n
          using the techniques of rapid prototyping.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @445215600 {#7531
      date: 1984-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 26
    -documents: Doctrine\ORM\PersistentCollection {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
]

App\Twig\Components\ProductMostRecent {#95257
  +product: App\Entity\Product\Product {#7520
    #id: 8887
    #code: "IEEE00001220"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037793 {#7536
      date: 2025-06-27 17:23:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #id: 30557
        #name: "IEEE 830:1984"
        #slug: "ieee-830-1984-ieee00001220-240539"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a guide for writing software requirements specifications. It describer; the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.<br />\n
          This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.<br />\n
          This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.<br />\n
          This guide is applicable to in-house and commercial software products. Special care, however,<br />\n
          should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.<br />\n
          (2) This guide does not cover the specification of requirements for software being developed<br />\n
          using the techniques of rapid prototyping.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @445215600 {#7531
      date: 1984-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 26
    -documents: Doctrine\ORM\PersistentCollection {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95681
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#95661 …}
    #variants: Doctrine\ORM\PersistentCollection {#95658 …}
    #options: Doctrine\ORM\PersistentCollection {#95654 …}
    #associations: Doctrine\ORM\PersistentCollection {#95650 …}
    #createdAt: DateTime @1751037795 {#95688
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#95667
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95672 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95713
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95681}
        #id: 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 {#95670 …}
    #channels: Doctrine\ORM\PersistentCollection {#95663 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95668 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95665 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95678 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95651
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#95687
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#95686
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#95680
      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 {#95676 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95674 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#108874
  +product: App\Entity\Product\Product {#95681
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#95661 …}
    #variants: Doctrine\ORM\PersistentCollection {#95658 …}
    #options: Doctrine\ORM\PersistentCollection {#95654 …}
    #associations: Doctrine\ORM\PersistentCollection {#95650 …}
    #createdAt: DateTime @1751037795 {#95688
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#95667
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95672 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95713
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95681}
        #id: 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 {#95670 …}
    #channels: Doctrine\ORM\PersistentCollection {#95663 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95668 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95665 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95678 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95651
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#95687
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#95686
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#95680
      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 {#95676 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95674 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95681
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#95661 …}
    #variants: Doctrine\ORM\PersistentCollection {#95658 …}
    #options: Doctrine\ORM\PersistentCollection {#95654 …}
    #associations: Doctrine\ORM\PersistentCollection {#95650 …}
    #createdAt: DateTime @1751037795 {#95688
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#95667
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95672 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95713
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95681}
        #id: 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 {#95670 …}
    #channels: Doctrine\ORM\PersistentCollection {#95663 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95668 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95665 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95678 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95651
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#95687
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#95686
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#95680
      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 {#95676 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95674 …}
  }
]

App\Twig\Components\ProductMostRecent {#108945
  +product: App\Entity\Product\Product {#95681
    #id: 8889
    #code: "IEEE00001222"
    #attributes: Doctrine\ORM\PersistentCollection {#95661 …}
    #variants: Doctrine\ORM\PersistentCollection {#95658 …}
    #options: Doctrine\ORM\PersistentCollection {#95654 …}
    #associations: Doctrine\ORM\PersistentCollection {#95650 …}
    #createdAt: DateTime @1751037795 {#95688
      date: 2025-06-27 17:23:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#95667
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95672 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95713
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95681}
        #id: 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 {#95670 …}
    #channels: Doctrine\ORM\PersistentCollection {#95663 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95668 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95665 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95678 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95651
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1719266400 {#95687
      date: 2024-06-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @908834400 {#95686
      date: 1998-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#95680
      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 {#95676 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95674 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108777
    #id: 8888
    #code: "IEEE00001221"
    #attributes: Doctrine\ORM\PersistentCollection {#108794 …}
    #variants: Doctrine\ORM\PersistentCollection {#108791 …}
    #options: Doctrine\ORM\PersistentCollection {#108787 …}
    #associations: Doctrine\ORM\PersistentCollection {#108789 …}
    #createdAt: DateTime @1751037794 {#108818
      date: 2025-06-27 17:23:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108779
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108805 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109012
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108777}
        #id: 30561
        #name: "IEEE 830:1993"
        #slug: "ieee-830-1993-ieee00001221-240540"
        #description: """
          Revision Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for writing software requirements specifications. It describes the<br />\n
          content and qualities of a good software requirements specification (SRS) and presents several sample SRS outlines.<br />\n
          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. However, application to already-developed software could be counterproductive.<br />\n
          When software is embedded in some larger system, such as medical equipment, then issues beyond those<br />\n
          identified in this standard may have to be addressed.<br />\n
          This recommended practice describes the process of creating a product and the content of the product. The product is a software requirements specification. This recommended practice can be used to create such software requirements specification directly or can be used as a model for a more specific standard.<br />\n
          This recommended practice does not identify any specific method, nomenclature, or tool for preparing<br />\n
          an SRS.<br />\n
          This recommended practice describes recommended approaches for the specification of software requirements. It is divided into five clauses. Clause 1 explains the scope of this recommended practice. Clause 2 lists the references made to other standards. Clause 3 provides definitions of specific terms used. Clause 4 provides background information for writing a good SRS. Clause 5 discusses each of the essential parts of an SRS. This recommended practice also has an annex, which provides alternate format templates.
          """
        #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 {#108802 …}
    #channels: Doctrine\ORM\PersistentCollection {#108796 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108800 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108798 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108812 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108792
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108819
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @765756000 {#108823
      date: 1994-04-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#108809 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108807 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#109027
  +product: App\Entity\Product\Product {#108777
    #id: 8888
    #code: "IEEE00001221"
    #attributes: Doctrine\ORM\PersistentCollection {#108794 …}
    #variants: Doctrine\ORM\PersistentCollection {#108791 …}
    #options: Doctrine\ORM\PersistentCollection {#108787 …}
    #associations: Doctrine\ORM\PersistentCollection {#108789 …}
    #createdAt: DateTime @1751037794 {#108818
      date: 2025-06-27 17:23:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108779
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108805 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109012
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108777}
        #id: 30561
        #name: "IEEE 830:1993"
        #slug: "ieee-830-1993-ieee00001221-240540"
        #description: """
          Revision Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for writing software requirements specifications. It describes the<br />\n
          content and qualities of a good software requirements specification (SRS) and presents several sample SRS outlines.<br />\n
          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. However, application to already-developed software could be counterproductive.<br />\n
          When software is embedded in some larger system, such as medical equipment, then issues beyond those<br />\n
          identified in this standard may have to be addressed.<br />\n
          This recommended practice describes the process of creating a product and the content of the product. The product is a software requirements specification. This recommended practice can be used to create such software requirements specification directly or can be used as a model for a more specific standard.<br />\n
          This recommended practice does not identify any specific method, nomenclature, or tool for preparing<br />\n
          an SRS.<br />\n
          This recommended practice describes recommended approaches for the specification of software requirements. It is divided into five clauses. Clause 1 explains the scope of this recommended practice. Clause 2 lists the references made to other standards. Clause 3 provides definitions of specific terms used. Clause 4 provides background information for writing a good SRS. Clause 5 discusses each of the essential parts of an SRS. This recommended practice also has an annex, which provides alternate format templates.
          """
        #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 {#108802 …}
    #channels: Doctrine\ORM\PersistentCollection {#108796 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108800 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108798 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108812 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108792
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108819
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @765756000 {#108823
      date: 1994-04-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#108809 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108807 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#108777
    #id: 8888
    #code: "IEEE00001221"
    #attributes: Doctrine\ORM\PersistentCollection {#108794 …}
    #variants: Doctrine\ORM\PersistentCollection {#108791 …}
    #options: Doctrine\ORM\PersistentCollection {#108787 …}
    #associations: Doctrine\ORM\PersistentCollection {#108789 …}
    #createdAt: DateTime @1751037794 {#108818
      date: 2025-06-27 17:23:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108779
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108805 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109012
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108777}
        #id: 30561
        #name: "IEEE 830:1993"
        #slug: "ieee-830-1993-ieee00001221-240540"
        #description: """
          Revision Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for writing software requirements specifications. It describes the<br />\n
          content and qualities of a good software requirements specification (SRS) and presents several sample SRS outlines.<br />\n
          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. However, application to already-developed software could be counterproductive.<br />\n
          When software is embedded in some larger system, such as medical equipment, then issues beyond those<br />\n
          identified in this standard may have to be addressed.<br />\n
          This recommended practice describes the process of creating a product and the content of the product. The product is a software requirements specification. This recommended practice can be used to create such software requirements specification directly or can be used as a model for a more specific standard.<br />\n
          This recommended practice does not identify any specific method, nomenclature, or tool for preparing<br />\n
          an SRS.<br />\n
          This recommended practice describes recommended approaches for the specification of software requirements. It is divided into five clauses. Clause 1 explains the scope of this recommended practice. Clause 2 lists the references made to other standards. Clause 3 provides definitions of specific terms used. Clause 4 provides background information for writing a good SRS. Clause 5 discusses each of the essential parts of an SRS. This recommended practice also has an annex, which provides alternate format templates.
          """
        #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 {#108802 …}
    #channels: Doctrine\ORM\PersistentCollection {#108796 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108800 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108798 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108812 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108792
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108819
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @765756000 {#108823
      date: 1994-04-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#108809 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108807 …}
  }
]

App\Twig\Components\ProductMostRecent {#109079
  +product: App\Entity\Product\Product {#108777
    #id: 8888
    #code: "IEEE00001221"
    #attributes: Doctrine\ORM\PersistentCollection {#108794 …}
    #variants: Doctrine\ORM\PersistentCollection {#108791 …}
    #options: Doctrine\ORM\PersistentCollection {#108787 …}
    #associations: Doctrine\ORM\PersistentCollection {#108789 …}
    #createdAt: DateTime @1751037794 {#108818
      date: 2025-06-27 17:23:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#108779
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#108805 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#109012
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#108777}
        #id: 30561
        #name: "IEEE 830:1993"
        #slug: "ieee-830-1993-ieee00001221-240540"
        #description: """
          Revision Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a recommended practice for writing software requirements specifications. It describes the<br />\n
          content and qualities of a good software requirements specification (SRS) and presents several sample SRS outlines.<br />\n
          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. However, application to already-developed software could be counterproductive.<br />\n
          When software is embedded in some larger system, such as medical equipment, then issues beyond those<br />\n
          identified in this standard may have to be addressed.<br />\n
          This recommended practice describes the process of creating a product and the content of the product. The product is a software requirements specification. This recommended practice can be used to create such software requirements specification directly or can be used as a model for a more specific standard.<br />\n
          This recommended practice does not identify any specific method, nomenclature, or tool for preparing<br />\n
          an SRS.<br />\n
          This recommended practice describes recommended approaches for the specification of software requirements. It is divided into five clauses. Clause 1 explains the scope of this recommended practice. Clause 2 lists the references made to other standards. Clause 3 provides definitions of specific terms used. Clause 4 provides background information for writing a good SRS. Clause 5 discusses each of the essential parts of an SRS. This recommended practice also has an annex, which provides alternate format templates.
          """
        #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 {#108802 …}
    #channels: Doctrine\ORM\PersistentCollection {#108796 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#108800 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#108798 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#108812 …}
    -apiLastModifiedAt: DateTime @1754517600 {#108792
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#108819
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @765756000 {#108823
      date: 1994-04-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#108809 …}
    -favorites: Doctrine\ORM\PersistentCollection {#108807 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7520
    #id: 8887
    #code: "IEEE00001220"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037793 {#7536
      date: 2025-06-27 17:23:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #id: 30557
        #name: "IEEE 830:1984"
        #slug: "ieee-830-1984-ieee00001220-240539"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a guide for writing software requirements specifications. It describer; the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.<br />\n
          This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.<br />\n
          This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.<br />\n
          This guide is applicable to in-house and commercial software products. Special care, however,<br />\n
          should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.<br />\n
          (2) This guide does not cover the specification of requirements for software being developed<br />\n
          using the techniques of rapid prototyping.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @445215600 {#7531
      date: 1984-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 26
    -documents: Doctrine\ORM\PersistentCollection {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#109143
  +product: App\Entity\Product\Product {#7520
    #id: 8887
    #code: "IEEE00001220"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037793 {#7536
      date: 2025-06-27 17:23:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #id: 30557
        #name: "IEEE 830:1984"
        #slug: "ieee-830-1984-ieee00001220-240539"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a guide for writing software requirements specifications. It describer; the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.<br />\n
          This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.<br />\n
          This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.<br />\n
          This guide is applicable to in-house and commercial software products. Special care, however,<br />\n
          should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.<br />\n
          (2) This guide does not cover the specification of requirements for software being developed<br />\n
          using the techniques of rapid prototyping.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @445215600 {#7531
      date: 1984-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 26
    -documents: Doctrine\ORM\PersistentCollection {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7520
    #id: 8887
    #code: "IEEE00001220"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037793 {#7536
      date: 2025-06-27 17:23:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #id: 30557
        #name: "IEEE 830:1984"
        #slug: "ieee-830-1984-ieee00001220-240539"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a guide for writing software requirements specifications. It describer; the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.<br />\n
          This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.<br />\n
          This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.<br />\n
          This guide is applicable to in-house and commercial software products. Special care, however,<br />\n
          should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.<br />\n
          (2) This guide does not cover the specification of requirements for software being developed<br />\n
          using the techniques of rapid prototyping.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @445215600 {#7531
      date: 1984-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 26
    -documents: Doctrine\ORM\PersistentCollection {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
]

App\Twig\Components\ProductMostRecent {#109170
  +product: App\Entity\Product\Product {#7520
    #id: 8887
    #code: "IEEE00001220"
    #attributes: Doctrine\ORM\PersistentCollection {#8207 …}
    #variants: Doctrine\ORM\PersistentCollection {#8289 …}
    #options: Doctrine\ORM\PersistentCollection {#8628 …}
    #associations: Doctrine\ORM\PersistentCollection {#8585 …}
    #createdAt: DateTime @1751037793 {#7536
      date: 2025-06-27 17:23:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7535
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8627 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8612
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7520}
        #id: 30557
        #name: "IEEE 830:1984"
        #slug: "ieee-830-1984-ieee00001220-240539"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          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.<br />\n
          \t\t\t\t<br />\n
          This is a guide for writing software requirements specifications. It describer; the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.<br />\n
          This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.<br />\n
          This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.<br />\n
          This guide is applicable to in-house and commercial software products. Special care, however,<br />\n
          should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.<br />\n
          (2) This guide does not cover the specification of requirements for software being developed<br />\n
          using the techniques of rapid prototyping.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Software Requirements Specifications"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7943 …}
    #channels: Doctrine\ORM\PersistentCollection {#8104 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8066 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8118 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7746 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @445215600 {#7531
      date: 1984-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "830"
    -bookCollection: ""
    -pageCount: 26
    -documents: Doctrine\ORM\PersistentCollection {#7786 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7928 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#130443
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#130467 …}
    #variants: Doctrine\ORM\PersistentCollection {#130465 …}
    #options: Doctrine\ORM\PersistentCollection {#130460 …}
    #associations: Doctrine\ORM\PersistentCollection {#130463 …}
    #createdAt: DateTime @1751037679 {#130456
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#130449
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#130478 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#130567
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#130443}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#130476 …}
    #channels: Doctrine\ORM\PersistentCollection {#130469 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#130473 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#130471 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#130483 …}
    -apiLastModifiedAt: DateTime @1754517600 {#130442
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#130491
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#130462
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#130482 …}
    -favorites: Doctrine\ORM\PersistentCollection {#130480 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#130535
  +product: App\Entity\Product\Product {#130443
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#130467 …}
    #variants: Doctrine\ORM\PersistentCollection {#130465 …}
    #options: Doctrine\ORM\PersistentCollection {#130460 …}
    #associations: Doctrine\ORM\PersistentCollection {#130463 …}
    #createdAt: DateTime @1751037679 {#130456
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#130449
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#130478 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#130567
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#130443}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#130476 …}
    #channels: Doctrine\ORM\PersistentCollection {#130469 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#130473 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#130471 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#130483 …}
    -apiLastModifiedAt: DateTime @1754517600 {#130442
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#130491
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#130462
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#130482 …}
    -favorites: Doctrine\ORM\PersistentCollection {#130480 …}
  }
  +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 {#130443
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#130467 …}
    #variants: Doctrine\ORM\PersistentCollection {#130465 …}
    #options: Doctrine\ORM\PersistentCollection {#130460 …}
    #associations: Doctrine\ORM\PersistentCollection {#130463 …}
    #createdAt: DateTime @1751037679 {#130456
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#130449
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#130478 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#130567
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#130443}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#130476 …}
    #channels: Doctrine\ORM\PersistentCollection {#130469 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#130473 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#130471 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#130483 …}
    -apiLastModifiedAt: DateTime @1754517600 {#130442
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#130491
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#130462
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#130482 …}
    -favorites: Doctrine\ORM\PersistentCollection {#130480 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#130571
  +product: App\Entity\Product\Product {#130443
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#130467 …}
    #variants: Doctrine\ORM\PersistentCollection {#130465 …}
    #options: Doctrine\ORM\PersistentCollection {#130460 …}
    #associations: Doctrine\ORM\PersistentCollection {#130463 …}
    #createdAt: DateTime @1751037679 {#130456
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#130449
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#130478 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#130567
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#130443}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#130476 …}
    #channels: Doctrine\ORM\PersistentCollection {#130469 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#130473 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#130471 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#130483 …}
    -apiLastModifiedAt: DateTime @1754517600 {#130442
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#130491
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#130462
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#130482 …}
    -favorites: Doctrine\ORM\PersistentCollection {#130480 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#130443
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#130467 …}
    #variants: Doctrine\ORM\PersistentCollection {#130465 …}
    #options: Doctrine\ORM\PersistentCollection {#130460 …}
    #associations: Doctrine\ORM\PersistentCollection {#130463 …}
    #createdAt: DateTime @1751037679 {#130456
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#130449
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#130478 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#130567
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#130443}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#130476 …}
    #channels: Doctrine\ORM\PersistentCollection {#130469 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#130473 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#130471 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#130483 …}
    -apiLastModifiedAt: DateTime @1754517600 {#130442
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#130491
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#130462
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#130482 …}
    -favorites: Doctrine\ORM\PersistentCollection {#130480 …}
  }
]

App\Twig\Components\ProductMostRecent {#130649
  +product: App\Entity\Product\Product {#130443
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#130467 …}
    #variants: Doctrine\ORM\PersistentCollection {#130465 …}
    #options: Doctrine\ORM\PersistentCollection {#130460 …}
    #associations: Doctrine\ORM\PersistentCollection {#130463 …}
    #createdAt: DateTime @1751037679 {#130456
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#130449
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#130478 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#130567
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#130443}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#130476 …}
    #channels: Doctrine\ORM\PersistentCollection {#130469 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7519 …}
    #reviews: Doctrine\ORM\PersistentCollection {#130473 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#130471 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7681 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#130483 …}
    -apiLastModifiedAt: DateTime @1754517600 {#130442
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#130491
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#130462
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#130482 …}
    -favorites: Doctrine\ORM\PersistentCollection {#130480 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}