Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7272
    #id: 12081
    #code: "IEEE00007045"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040185 {#7306
      date: 2025-06-27 18:03:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7272}
        #id: 43333
        #name: "IEEE 2430:2019"
        #slug: "ieee-2430-2019-ieee00007045-243733"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines a method for the sizing of non-functional software requirements. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR). This standard also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use. This standard covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence. Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.<br />\n
          The purpose of this standard is to define the method of sizing of NFR and describe how to use this size, alongside with the functional size.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1683151200 {#7287
      date: 2023-05-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1571176800 {#7318
      date: 2019-10-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1680127200 {#7314
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2430"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#92951
  +product: App\Entity\Product\Product {#7272
    #id: 12081
    #code: "IEEE00007045"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040185 {#7306
      date: 2025-06-27 18:03:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7272}
        #id: 43333
        #name: "IEEE 2430:2019"
        #slug: "ieee-2430-2019-ieee00007045-243733"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines a method for the sizing of non-functional software requirements. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR). This standard also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use. This standard covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence. Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.<br />\n
          The purpose of this standard is to define the method of sizing of NFR and describe how to use this size, alongside with the functional size.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1683151200 {#7287
      date: 2023-05-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1571176800 {#7318
      date: 2019-10-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1680127200 {#7314
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2430"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7272
    #id: 12081
    #code: "IEEE00007045"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040185 {#7306
      date: 2025-06-27 18:03:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7272}
        #id: 43333
        #name: "IEEE 2430:2019"
        #slug: "ieee-2430-2019-ieee00007045-243733"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines a method for the sizing of non-functional software requirements. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR). This standard also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use. This standard covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence. Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.<br />\n
          The purpose of this standard is to define the method of sizing of NFR and describe how to use this size, alongside with the functional size.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1683151200 {#7287
      date: 2023-05-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1571176800 {#7318
      date: 2019-10-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1680127200 {#7314
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2430"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductType {#93122
  +product: App\Entity\Product\Product {#7272
    #id: 12081
    #code: "IEEE00007045"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040185 {#7306
      date: 2025-06-27 18:03:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7272}
        #id: 43333
        #name: "IEEE 2430:2019"
        #slug: "ieee-2430-2019-ieee00007045-243733"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines a method for the sizing of non-functional software requirements. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR). This standard also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use. This standard covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence. Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.<br />\n
          The purpose of this standard is to define the method of sizing of NFR and describe how to use this size, alongside with the functional size.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1683151200 {#7287
      date: 2023-05-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1571176800 {#7318
      date: 2019-10-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1680127200 {#7314
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2430"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7272
    #id: 12081
    #code: "IEEE00007045"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040185 {#7306
      date: 2025-06-27 18:03:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7272}
        #id: 43333
        #name: "IEEE 2430:2019"
        #slug: "ieee-2430-2019-ieee00007045-243733"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines a method for the sizing of non-functional software requirements. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR). This standard also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use. This standard covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence. Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.<br />\n
          The purpose of this standard is to define the method of sizing of NFR and describe how to use this size, alongside with the functional size.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1683151200 {#7287
      date: 2023-05-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1571176800 {#7318
      date: 2019-10-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1680127200 {#7314
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2430"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#93197
  +product: App\Entity\Product\Product {#7272
    #id: 12081
    #code: "IEEE00007045"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040185 {#7306
      date: 2025-06-27 18:03:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7272}
        #id: 43333
        #name: "IEEE 2430:2019"
        #slug: "ieee-2430-2019-ieee00007045-243733"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines a method for the sizing of non-functional software requirements. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR). This standard also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use. This standard covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence. Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.<br />\n
          The purpose of this standard is to define the method of sizing of NFR and describe how to use this size, alongside with the functional size.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1683151200 {#7287
      date: 2023-05-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1571176800 {#7318
      date: 2019-10-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1680127200 {#7314
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2430"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7272
    #id: 12081
    #code: "IEEE00007045"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040185 {#7306
      date: 2025-06-27 18:03:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7272}
        #id: 43333
        #name: "IEEE 2430:2019"
        #slug: "ieee-2430-2019-ieee00007045-243733"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines a method for the sizing of non-functional software requirements. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR). This standard also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use. This standard covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence. Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.<br />\n
          The purpose of this standard is to define the method of sizing of NFR and describe how to use this size, alongside with the functional size.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1683151200 {#7287
      date: 2023-05-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1571176800 {#7318
      date: 2019-10-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1680127200 {#7314
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2430"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#100140
  +product: App\Entity\Product\Product {#7272
    #id: 12081
    #code: "IEEE00007045"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040185 {#7306
      date: 2025-06-27 18:03:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7272}
        #id: 43333
        #name: "IEEE 2430:2019"
        #slug: "ieee-2430-2019-ieee00007045-243733"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines a method for the sizing of non-functional software requirements. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR). This standard also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use. This standard covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence. Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.<br />\n
          The purpose of this standard is to define the method of sizing of NFR and describe how to use this size, alongside with the functional size.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1683151200 {#7287
      date: 2023-05-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1571176800 {#7318
      date: 2019-10-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1680127200 {#7314
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2430"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7272
    #id: 12081
    #code: "IEEE00007045"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040185 {#7306
      date: 2025-06-27 18:03:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7272}
        #id: 43333
        #name: "IEEE 2430:2019"
        #slug: "ieee-2430-2019-ieee00007045-243733"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines a method for the sizing of non-functional software requirements. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR). This standard also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use. This standard covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence. Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.<br />\n
          The purpose of this standard is to define the method of sizing of NFR and describe how to use this size, alongside with the functional size.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1683151200 {#7287
      date: 2023-05-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1571176800 {#7318
      date: 2019-10-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1680127200 {#7314
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2430"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#100224
  +product: App\Entity\Product\Product {#7272
    #id: 12081
    #code: "IEEE00007045"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040185 {#7306
      date: 2025-06-27 18:03:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7272}
        #id: 43333
        #name: "IEEE 2430:2019"
        #slug: "ieee-2430-2019-ieee00007045-243733"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          A method for the sizing of nonfunctional software requirements is defined in this standard. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. Non-functional categories for data operations, interface design, technical environment, and architecture software are included in this standard.Steps to determine and calculate the non-functional size are also included. Handling requirements involving both functional and non-functional requirements are explained in this standard, which also covers how to apply non-functional sizing estimates in terms of cost, project duration and quality, and considerations of software performance in terms of productivity and quality. The combination of functional and nonfunctional size should correspond to the total size necessary to produce the software. The functional size and non-functional size are orthogonal, and both are needed when sizing the software. The complementarity of the functional and the non-functional sizes, to avoid overlaps or gaps between the two size methods, are described in this standard. Calculating the implementation work effort and duration of the non-functional requirements is outside the scope of this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines a method for the sizing of non-functional software requirements. It complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements (FUR). This standard also describes the complementarity of functional and non-functional sizes, so that sizing both functional and non-functional requirements (NFR) do not overlap. It also describes how non-functional size, together with functional size, should be used for measuring the performance of software projects, setting benchmarks, and estimating the cost and duration of software projects. In general, there are many types of non-functional software requirements. Moreover, non-functional aspects evolve over time and may include additional aspects in the as technology advances. This standard does not intend to define the type of NFR for a given context. Users may choose ISO 25010:2011 or any other standard for the definition of NFR. It is assumed that users will size the NFR based on the definitions they use. This standard covers a subset of non-functional types. It is expected that, with time, the state of the art can improve and that potential future versions of this standard can define an extended coverage. The ultimate goal is a version that, together with ISO/IEC 20926:2009, covers every aspect that may be required of any prospective piece of software, including aspects such as process and project directives that are hard or impossible to trace to the software's algorithm or data. The combination of functional and non-functional size would then correspond to the total size necessary to bring the software into existence. Calculating the effort and duration of the implementation of the NFR is outside the scope of this standard.<br />\n
          The purpose of this standard is to define the method of sizing of NFR and describe how to use this size, alongside with the functional size.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Software Non-Functional Sizing Measurements"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1683151200 {#7287
      date: 2023-05-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1571176800 {#7318
      date: 2019-10-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1680127200 {#7314
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2430"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#121625
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#121630 …}
    #variants: Doctrine\ORM\PersistentCollection {#121628 …}
    #options: Doctrine\ORM\PersistentCollection {#121623 …}
    #associations: Doctrine\ORM\PersistentCollection {#121626 …}
    #createdAt: DateTime @1751040087 {#121619
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#121654
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121641 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121743
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121625}
        #id: 42753
        #name: "IEEE/ISO/IEC 24765:2017"
        #slug: "ieee-iso-iec-24765-2017-ieee00006800-243588"
        #description: """
          Revision Standard - Active.<br />\n
          This document provides a common vocabulary applicable to all systems and software engineering work. It was prepared to collect and standardize terminology. This document is intended to serve as a useful reference for those in the information technology field, and to encourage the use of systems and software engineering standards prepared by ISO and liaison organizations IEEE Computer Society and Project Management Institute. This document includes references to the active source standards for definitions so that systems and software engineering concepts and requirements can be further explored.<br />\n
          \t\t\t\t<br />\n
          Consistent with ISO vocabulary standards, each technical committee is responsible for standard terminology in its area of specialization. This document provides a common vocabulary applicable to all systems and software engineering work falling within the scope of ISO/IEC JTC 1/SC 7, Software and systems engineering, and the IEEE Computer Society Systems and Software Engineering Standards Committee (IEEE-CS S2ESC). The scope of each concept defined has been chosen to provide a definition that is suitable for general application. In those circumstances where a restricted application is concerned, a more specific definition might be needed. Terms have been excluded if they were: considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; and terms whose meaning in the information technology (IT) field could be directly inferred from their common English dictionary meaning.<br />\n
          document will not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121639 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121634 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121646 …}
    -apiLastModifiedAt: DateTime @1743289200 {#121605
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121653
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#121612
      date: 2017-08-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24765"
    -bookCollection: ""
    -pageCount: 541
    -documents: Doctrine\ORM\PersistentCollection {#121645 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121643 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#121698
  +product: App\Entity\Product\Product {#121625
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#121630 …}
    #variants: Doctrine\ORM\PersistentCollection {#121628 …}
    #options: Doctrine\ORM\PersistentCollection {#121623 …}
    #associations: Doctrine\ORM\PersistentCollection {#121626 …}
    #createdAt: DateTime @1751040087 {#121619
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#121654
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121641 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121743
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121625}
        #id: 42753
        #name: "IEEE/ISO/IEC 24765:2017"
        #slug: "ieee-iso-iec-24765-2017-ieee00006800-243588"
        #description: """
          Revision Standard - Active.<br />\n
          This document provides a common vocabulary applicable to all systems and software engineering work. It was prepared to collect and standardize terminology. This document is intended to serve as a useful reference for those in the information technology field, and to encourage the use of systems and software engineering standards prepared by ISO and liaison organizations IEEE Computer Society and Project Management Institute. This document includes references to the active source standards for definitions so that systems and software engineering concepts and requirements can be further explored.<br />\n
          \t\t\t\t<br />\n
          Consistent with ISO vocabulary standards, each technical committee is responsible for standard terminology in its area of specialization. This document provides a common vocabulary applicable to all systems and software engineering work falling within the scope of ISO/IEC JTC 1/SC 7, Software and systems engineering, and the IEEE Computer Society Systems and Software Engineering Standards Committee (IEEE-CS S2ESC). The scope of each concept defined has been chosen to provide a definition that is suitable for general application. In those circumstances where a restricted application is concerned, a more specific definition might be needed. Terms have been excluded if they were: considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; and terms whose meaning in the information technology (IT) field could be directly inferred from their common English dictionary meaning.<br />\n
          document will not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121639 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121634 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121646 …}
    -apiLastModifiedAt: DateTime @1743289200 {#121605
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121653
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#121612
      date: 2017-08-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24765"
    -bookCollection: ""
    -pageCount: 541
    -documents: Doctrine\ORM\PersistentCollection {#121645 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121643 …}
  }
  +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 {#121625
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#121630 …}
    #variants: Doctrine\ORM\PersistentCollection {#121628 …}
    #options: Doctrine\ORM\PersistentCollection {#121623 …}
    #associations: Doctrine\ORM\PersistentCollection {#121626 …}
    #createdAt: DateTime @1751040087 {#121619
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#121654
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121641 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121743
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121625}
        #id: 42753
        #name: "IEEE/ISO/IEC 24765:2017"
        #slug: "ieee-iso-iec-24765-2017-ieee00006800-243588"
        #description: """
          Revision Standard - Active.<br />\n
          This document provides a common vocabulary applicable to all systems and software engineering work. It was prepared to collect and standardize terminology. This document is intended to serve as a useful reference for those in the information technology field, and to encourage the use of systems and software engineering standards prepared by ISO and liaison organizations IEEE Computer Society and Project Management Institute. This document includes references to the active source standards for definitions so that systems and software engineering concepts and requirements can be further explored.<br />\n
          \t\t\t\t<br />\n
          Consistent with ISO vocabulary standards, each technical committee is responsible for standard terminology in its area of specialization. This document provides a common vocabulary applicable to all systems and software engineering work falling within the scope of ISO/IEC JTC 1/SC 7, Software and systems engineering, and the IEEE Computer Society Systems and Software Engineering Standards Committee (IEEE-CS S2ESC). The scope of each concept defined has been chosen to provide a definition that is suitable for general application. In those circumstances where a restricted application is concerned, a more specific definition might be needed. Terms have been excluded if they were: considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; and terms whose meaning in the information technology (IT) field could be directly inferred from their common English dictionary meaning.<br />\n
          document will not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121639 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121634 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121646 …}
    -apiLastModifiedAt: DateTime @1743289200 {#121605
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121653
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#121612
      date: 2017-08-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24765"
    -bookCollection: ""
    -pageCount: 541
    -documents: Doctrine\ORM\PersistentCollection {#121645 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121643 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#121745
  +product: App\Entity\Product\Product {#121625
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#121630 …}
    #variants: Doctrine\ORM\PersistentCollection {#121628 …}
    #options: Doctrine\ORM\PersistentCollection {#121623 …}
    #associations: Doctrine\ORM\PersistentCollection {#121626 …}
    #createdAt: DateTime @1751040087 {#121619
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#121654
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121641 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121743
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121625}
        #id: 42753
        #name: "IEEE/ISO/IEC 24765:2017"
        #slug: "ieee-iso-iec-24765-2017-ieee00006800-243588"
        #description: """
          Revision Standard - Active.<br />\n
          This document provides a common vocabulary applicable to all systems and software engineering work. It was prepared to collect and standardize terminology. This document is intended to serve as a useful reference for those in the information technology field, and to encourage the use of systems and software engineering standards prepared by ISO and liaison organizations IEEE Computer Society and Project Management Institute. This document includes references to the active source standards for definitions so that systems and software engineering concepts and requirements can be further explored.<br />\n
          \t\t\t\t<br />\n
          Consistent with ISO vocabulary standards, each technical committee is responsible for standard terminology in its area of specialization. This document provides a common vocabulary applicable to all systems and software engineering work falling within the scope of ISO/IEC JTC 1/SC 7, Software and systems engineering, and the IEEE Computer Society Systems and Software Engineering Standards Committee (IEEE-CS S2ESC). The scope of each concept defined has been chosen to provide a definition that is suitable for general application. In those circumstances where a restricted application is concerned, a more specific definition might be needed. Terms have been excluded if they were: considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; and terms whose meaning in the information technology (IT) field could be directly inferred from their common English dictionary meaning.<br />\n
          document will not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121639 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121634 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121646 …}
    -apiLastModifiedAt: DateTime @1743289200 {#121605
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121653
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#121612
      date: 2017-08-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24765"
    -bookCollection: ""
    -pageCount: 541
    -documents: Doctrine\ORM\PersistentCollection {#121645 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121643 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#121625
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#121630 …}
    #variants: Doctrine\ORM\PersistentCollection {#121628 …}
    #options: Doctrine\ORM\PersistentCollection {#121623 …}
    #associations: Doctrine\ORM\PersistentCollection {#121626 …}
    #createdAt: DateTime @1751040087 {#121619
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#121654
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121641 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121743
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121625}
        #id: 42753
        #name: "IEEE/ISO/IEC 24765:2017"
        #slug: "ieee-iso-iec-24765-2017-ieee00006800-243588"
        #description: """
          Revision Standard - Active.<br />\n
          This document provides a common vocabulary applicable to all systems and software engineering work. It was prepared to collect and standardize terminology. This document is intended to serve as a useful reference for those in the information technology field, and to encourage the use of systems and software engineering standards prepared by ISO and liaison organizations IEEE Computer Society and Project Management Institute. This document includes references to the active source standards for definitions so that systems and software engineering concepts and requirements can be further explored.<br />\n
          \t\t\t\t<br />\n
          Consistent with ISO vocabulary standards, each technical committee is responsible for standard terminology in its area of specialization. This document provides a common vocabulary applicable to all systems and software engineering work falling within the scope of ISO/IEC JTC 1/SC 7, Software and systems engineering, and the IEEE Computer Society Systems and Software Engineering Standards Committee (IEEE-CS S2ESC). The scope of each concept defined has been chosen to provide a definition that is suitable for general application. In those circumstances where a restricted application is concerned, a more specific definition might be needed. Terms have been excluded if they were: considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; and terms whose meaning in the information technology (IT) field could be directly inferred from their common English dictionary meaning.<br />\n
          document will not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121639 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121634 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121646 …}
    -apiLastModifiedAt: DateTime @1743289200 {#121605
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121653
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#121612
      date: 2017-08-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24765"
    -bookCollection: ""
    -pageCount: 541
    -documents: Doctrine\ORM\PersistentCollection {#121645 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121643 …}
  }
]

App\Twig\Components\ProductMostRecent {#121822
  +product: App\Entity\Product\Product {#121625
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#121630 …}
    #variants: Doctrine\ORM\PersistentCollection {#121628 …}
    #options: Doctrine\ORM\PersistentCollection {#121623 …}
    #associations: Doctrine\ORM\PersistentCollection {#121626 …}
    #createdAt: DateTime @1751040087 {#121619
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#121654
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121641 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121743
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121625}
        #id: 42753
        #name: "IEEE/ISO/IEC 24765:2017"
        #slug: "ieee-iso-iec-24765-2017-ieee00006800-243588"
        #description: """
          Revision Standard - Active.<br />\n
          This document provides a common vocabulary applicable to all systems and software engineering work. It was prepared to collect and standardize terminology. This document is intended to serve as a useful reference for those in the information technology field, and to encourage the use of systems and software engineering standards prepared by ISO and liaison organizations IEEE Computer Society and Project Management Institute. This document includes references to the active source standards for definitions so that systems and software engineering concepts and requirements can be further explored.<br />\n
          \t\t\t\t<br />\n
          Consistent with ISO vocabulary standards, each technical committee is responsible for standard terminology in its area of specialization. This document provides a common vocabulary applicable to all systems and software engineering work falling within the scope of ISO/IEC JTC 1/SC 7, Software and systems engineering, and the IEEE Computer Society Systems and Software Engineering Standards Committee (IEEE-CS S2ESC). The scope of each concept defined has been chosen to provide a definition that is suitable for general application. In those circumstances where a restricted application is concerned, a more specific definition might be needed. Terms have been excluded if they were: considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; and terms whose meaning in the information technology (IT) field could be directly inferred from their common English dictionary meaning.<br />\n
          document will not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121639 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7276 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121634 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121646 …}
    -apiLastModifiedAt: DateTime @1743289200 {#121605
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121653
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#121612
      date: 2017-08-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24765"
    -bookCollection: ""
    -pageCount: 541
    -documents: Doctrine\ORM\PersistentCollection {#121645 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121643 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}