Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7311
    #id: 12814
    #code: "IEEE00010731"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040678 {#7274
      date: 2025-06-27 18:11:18.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 {#7311}
        #id: 46265
        #name: "IEEE/ISO/IEC 32430:2021"
        #slug: "ieee-iso-iec-32430-2021-ieee00010731-244470"
        #description: """
          Adoption Standard - Active.<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/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740524400 {#7292
      date: 2025-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1633989600 {#7318
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1633989600 {#7316
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#93055
  +product: App\Entity\Product\Product {#7311
    #id: 12814
    #code: "IEEE00010731"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040678 {#7274
      date: 2025-06-27 18:11:18.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 {#7311}
        #id: 46265
        #name: "IEEE/ISO/IEC 32430:2021"
        #slug: "ieee-iso-iec-32430-2021-ieee00010731-244470"
        #description: """
          Adoption Standard - Active.<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/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740524400 {#7292
      date: 2025-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1633989600 {#7318
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1633989600 {#7316
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 12814
    #code: "IEEE00010731"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040678 {#7274
      date: 2025-06-27 18:11:18.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 {#7311}
        #id: 46265
        #name: "IEEE/ISO/IEC 32430:2021"
        #slug: "ieee-iso-iec-32430-2021-ieee00010731-244470"
        #description: """
          Adoption Standard - Active.<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/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740524400 {#7292
      date: 2025-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1633989600 {#7318
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1633989600 {#7316
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductType {#93235
  +product: App\Entity\Product\Product {#7311
    #id: 12814
    #code: "IEEE00010731"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040678 {#7274
      date: 2025-06-27 18:11:18.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 {#7311}
        #id: 46265
        #name: "IEEE/ISO/IEC 32430:2021"
        #slug: "ieee-iso-iec-32430-2021-ieee00010731-244470"
        #description: """
          Adoption Standard - Active.<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/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740524400 {#7292
      date: 2025-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1633989600 {#7318
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1633989600 {#7316
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 12814
    #code: "IEEE00010731"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040678 {#7274
      date: 2025-06-27 18:11:18.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 {#7311}
        #id: 46265
        #name: "IEEE/ISO/IEC 32430:2021"
        #slug: "ieee-iso-iec-32430-2021-ieee00010731-244470"
        #description: """
          Adoption Standard - Active.<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/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740524400 {#7292
      date: 2025-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1633989600 {#7318
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1633989600 {#7316
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#93310
  +product: App\Entity\Product\Product {#7311
    #id: 12814
    #code: "IEEE00010731"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040678 {#7274
      date: 2025-06-27 18:11:18.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 {#7311}
        #id: 46265
        #name: "IEEE/ISO/IEC 32430:2021"
        #slug: "ieee-iso-iec-32430-2021-ieee00010731-244470"
        #description: """
          Adoption Standard - Active.<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/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740524400 {#7292
      date: 2025-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1633989600 {#7318
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1633989600 {#7316
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93737
    #id: 13074
    #code: "IEEE00011514"
    #attributes: Doctrine\ORM\PersistentCollection {#93719 …}
    #variants: Doctrine\ORM\PersistentCollection {#93716 …}
    #options: Doctrine\ORM\PersistentCollection {#93712 …}
    #associations: Doctrine\ORM\PersistentCollection {#93714 …}
    #createdAt: DateTime @1751040843 {#93745
      date: 2025-06-27 18:14:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#93724
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93730 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93765
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93737}
        #id: 47305
        #name: "IEEE/ISO/IEC 32430:2024"
        #slug: "ieee-iso-iec-32430-2024-ieee00011514-244733"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          The IEEE-2430 standard specifies the set of definitions, rules and steps for applying the IFPUG (International Function Point Users Group) nonfunctional size measurement method SNAP (Software Non-functional Assessment Process) and provides guideline and examples of how to use the size measurements in software projects.<br />\n
          IEEE 2430 is complementary to ISO/IEC 20926:2009 “Software and systems engineering — Software measurement — IFPUG functional size measurement method”. Having both the functional size (ISO/IEC 20926:2009) and the non-functional size (IEEE 2430-2019) provides a complete view of the functional requirements and the non-functional requirements.<br />\n
          Providing quantifiable measures for the functional and the nonfunctional requirements allows organizations to build historical data repositories that can be referenced to assist in decision making for better planning and estimating cost and schedule of software projects, measure productivity and quality of software projects and analyze improvement trends.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Software engineering - Software Non-Functional Sizing Measurement"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93728 …}
    #channels: Doctrine\ORM\PersistentCollection {#93721 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93726 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93723 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93738 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93708
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740351600 {#93744
      date: 2025-02-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1738796400 {#93743
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 82
    -documents: Doctrine\ORM\PersistentCollection {#93734 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93732 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106930
  +product: App\Entity\Product\Product {#93737
    #id: 13074
    #code: "IEEE00011514"
    #attributes: Doctrine\ORM\PersistentCollection {#93719 …}
    #variants: Doctrine\ORM\PersistentCollection {#93716 …}
    #options: Doctrine\ORM\PersistentCollection {#93712 …}
    #associations: Doctrine\ORM\PersistentCollection {#93714 …}
    #createdAt: DateTime @1751040843 {#93745
      date: 2025-06-27 18:14:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#93724
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93730 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93765
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93737}
        #id: 47305
        #name: "IEEE/ISO/IEC 32430:2024"
        #slug: "ieee-iso-iec-32430-2024-ieee00011514-244733"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          The IEEE-2430 standard specifies the set of definitions, rules and steps for applying the IFPUG (International Function Point Users Group) nonfunctional size measurement method SNAP (Software Non-functional Assessment Process) and provides guideline and examples of how to use the size measurements in software projects.<br />\n
          IEEE 2430 is complementary to ISO/IEC 20926:2009 “Software and systems engineering — Software measurement — IFPUG functional size measurement method”. Having both the functional size (ISO/IEC 20926:2009) and the non-functional size (IEEE 2430-2019) provides a complete view of the functional requirements and the non-functional requirements.<br />\n
          Providing quantifiable measures for the functional and the nonfunctional requirements allows organizations to build historical data repositories that can be referenced to assist in decision making for better planning and estimating cost and schedule of software projects, measure productivity and quality of software projects and analyze improvement trends.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Software engineering - Software Non-Functional Sizing Measurement"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93728 …}
    #channels: Doctrine\ORM\PersistentCollection {#93721 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93726 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93723 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93738 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93708
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740351600 {#93744
      date: 2025-02-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1738796400 {#93743
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 82
    -documents: Doctrine\ORM\PersistentCollection {#93734 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93732 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93737
    #id: 13074
    #code: "IEEE00011514"
    #attributes: Doctrine\ORM\PersistentCollection {#93719 …}
    #variants: Doctrine\ORM\PersistentCollection {#93716 …}
    #options: Doctrine\ORM\PersistentCollection {#93712 …}
    #associations: Doctrine\ORM\PersistentCollection {#93714 …}
    #createdAt: DateTime @1751040843 {#93745
      date: 2025-06-27 18:14:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#93724
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93730 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93765
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93737}
        #id: 47305
        #name: "IEEE/ISO/IEC 32430:2024"
        #slug: "ieee-iso-iec-32430-2024-ieee00011514-244733"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          The IEEE-2430 standard specifies the set of definitions, rules and steps for applying the IFPUG (International Function Point Users Group) nonfunctional size measurement method SNAP (Software Non-functional Assessment Process) and provides guideline and examples of how to use the size measurements in software projects.<br />\n
          IEEE 2430 is complementary to ISO/IEC 20926:2009 “Software and systems engineering — Software measurement — IFPUG functional size measurement method”. Having both the functional size (ISO/IEC 20926:2009) and the non-functional size (IEEE 2430-2019) provides a complete view of the functional requirements and the non-functional requirements.<br />\n
          Providing quantifiable measures for the functional and the nonfunctional requirements allows organizations to build historical data repositories that can be referenced to assist in decision making for better planning and estimating cost and schedule of software projects, measure productivity and quality of software projects and analyze improvement trends.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Software engineering - Software Non-Functional Sizing Measurement"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93728 …}
    #channels: Doctrine\ORM\PersistentCollection {#93721 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93726 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93723 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93738 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93708
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740351600 {#93744
      date: 2025-02-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1738796400 {#93743
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 82
    -documents: Doctrine\ORM\PersistentCollection {#93734 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93732 …}
  }
]

App\Twig\Components\ProductMostRecent {#106996
  +product: App\Entity\Product\Product {#93737
    #id: 13074
    #code: "IEEE00011514"
    #attributes: Doctrine\ORM\PersistentCollection {#93719 …}
    #variants: Doctrine\ORM\PersistentCollection {#93716 …}
    #options: Doctrine\ORM\PersistentCollection {#93712 …}
    #associations: Doctrine\ORM\PersistentCollection {#93714 …}
    #createdAt: DateTime @1751040843 {#93745
      date: 2025-06-27 18:14:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#93724
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93730 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93765
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93737}
        #id: 47305
        #name: "IEEE/ISO/IEC 32430:2024"
        #slug: "ieee-iso-iec-32430-2024-ieee00011514-244733"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          The IEEE-2430 standard specifies the set of definitions, rules and steps for applying the IFPUG (International Function Point Users Group) nonfunctional size measurement method SNAP (Software Non-functional Assessment Process) and provides guideline and examples of how to use the size measurements in software projects.<br />\n
          IEEE 2430 is complementary to ISO/IEC 20926:2009 “Software and systems engineering — Software measurement — IFPUG functional size measurement method”. Having both the functional size (ISO/IEC 20926:2009) and the non-functional size (IEEE 2430-2019) provides a complete view of the functional requirements and the non-functional requirements.<br />\n
          Providing quantifiable measures for the functional and the nonfunctional requirements allows organizations to build historical data repositories that can be referenced to assist in decision making for better planning and estimating cost and schedule of software projects, measure productivity and quality of software projects and analyze improvement trends.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Software engineering - Software Non-Functional Sizing Measurement"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93728 …}
    #channels: Doctrine\ORM\PersistentCollection {#93721 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93726 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93723 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93738 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93708
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740351600 {#93744
      date: 2025-02-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1738796400 {#93743
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 82
    -documents: Doctrine\ORM\PersistentCollection {#93734 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93732 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106871
    #id: 12806
    #code: "IEEE00010716"
    #attributes: Doctrine\ORM\PersistentCollection {#106854 …}
    #variants: Doctrine\ORM\PersistentCollection {#106851 …}
    #options: Doctrine\ORM\PersistentCollection {#106847 …}
    #associations: Doctrine\ORM\PersistentCollection {#106849 …}
    #createdAt: DateTime @1751040672 {#106839
      date: 2025-06-27 18:11:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#106852
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106865 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107063
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106871}
        #id: 46233
        #name: "IEEE P32430"
        #slug: "ieee-p32430-ieee00010716-244462"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          The IEEE-2430 standard specifies the set of definitions, rules and steps for applying the IFPUG (International Function Point Users Group) nonfunctional size measurement method (SNAP) and provides guideline and examples of how to use the size measurements in software projects.<br />\n
          IEEE 2430 is complementary to ISO/IEC 20926:2009 &quot;Software and systems engineering -- Software measurement -- IFPUG functional size measurement method&quot;. Having both the functional size (ISO/IEC 20926:2009) and the non-functional size (IEEE 2430-2019) provides a complete view of the functional requirements and the non-functional requirements.<br />\n
          Providing quantifiable measures for the functional and the nonfunctional requirements allows organizations to build historical data repositories that can be referenced to assist in decision making for better planning and estimating cost and schedule of software projects, measure productivity and quality of software projects and analyze improvement trends.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft International Standard for Software Engineering -- Standard for Software Non-Functional Sizing Measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106862 …}
    #channels: Doctrine\ORM\PersistentCollection {#106856 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106860 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106858 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106872 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106879
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1694037600 {#106883
      date: 2023-09-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1663711200 {#106837
      date: 2022-09-21 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#106869 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106867 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#107078
  +product: App\Entity\Product\Product {#106871
    #id: 12806
    #code: "IEEE00010716"
    #attributes: Doctrine\ORM\PersistentCollection {#106854 …}
    #variants: Doctrine\ORM\PersistentCollection {#106851 …}
    #options: Doctrine\ORM\PersistentCollection {#106847 …}
    #associations: Doctrine\ORM\PersistentCollection {#106849 …}
    #createdAt: DateTime @1751040672 {#106839
      date: 2025-06-27 18:11:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#106852
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106865 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107063
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106871}
        #id: 46233
        #name: "IEEE P32430"
        #slug: "ieee-p32430-ieee00010716-244462"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          The IEEE-2430 standard specifies the set of definitions, rules and steps for applying the IFPUG (International Function Point Users Group) nonfunctional size measurement method (SNAP) and provides guideline and examples of how to use the size measurements in software projects.<br />\n
          IEEE 2430 is complementary to ISO/IEC 20926:2009 &quot;Software and systems engineering -- Software measurement -- IFPUG functional size measurement method&quot;. Having both the functional size (ISO/IEC 20926:2009) and the non-functional size (IEEE 2430-2019) provides a complete view of the functional requirements and the non-functional requirements.<br />\n
          Providing quantifiable measures for the functional and the nonfunctional requirements allows organizations to build historical data repositories that can be referenced to assist in decision making for better planning and estimating cost and schedule of software projects, measure productivity and quality of software projects and analyze improvement trends.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft International Standard for Software Engineering -- Standard for Software Non-Functional Sizing Measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106862 …}
    #channels: Doctrine\ORM\PersistentCollection {#106856 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106860 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106858 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106872 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106879
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1694037600 {#106883
      date: 2023-09-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1663711200 {#106837
      date: 2022-09-21 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#106869 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106867 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106871
    #id: 12806
    #code: "IEEE00010716"
    #attributes: Doctrine\ORM\PersistentCollection {#106854 …}
    #variants: Doctrine\ORM\PersistentCollection {#106851 …}
    #options: Doctrine\ORM\PersistentCollection {#106847 …}
    #associations: Doctrine\ORM\PersistentCollection {#106849 …}
    #createdAt: DateTime @1751040672 {#106839
      date: 2025-06-27 18:11:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#106852
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106865 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107063
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106871}
        #id: 46233
        #name: "IEEE P32430"
        #slug: "ieee-p32430-ieee00010716-244462"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          The IEEE-2430 standard specifies the set of definitions, rules and steps for applying the IFPUG (International Function Point Users Group) nonfunctional size measurement method (SNAP) and provides guideline and examples of how to use the size measurements in software projects.<br />\n
          IEEE 2430 is complementary to ISO/IEC 20926:2009 &quot;Software and systems engineering -- Software measurement -- IFPUG functional size measurement method&quot;. Having both the functional size (ISO/IEC 20926:2009) and the non-functional size (IEEE 2430-2019) provides a complete view of the functional requirements and the non-functional requirements.<br />\n
          Providing quantifiable measures for the functional and the nonfunctional requirements allows organizations to build historical data repositories that can be referenced to assist in decision making for better planning and estimating cost and schedule of software projects, measure productivity and quality of software projects and analyze improvement trends.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft International Standard for Software Engineering -- Standard for Software Non-Functional Sizing Measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106862 …}
    #channels: Doctrine\ORM\PersistentCollection {#106856 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106860 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106858 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106872 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106879
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1694037600 {#106883
      date: 2023-09-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1663711200 {#106837
      date: 2022-09-21 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#106869 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106867 …}
  }
]

App\Twig\Components\ProductMostRecent {#107130
  +product: App\Entity\Product\Product {#106871
    #id: 12806
    #code: "IEEE00010716"
    #attributes: Doctrine\ORM\PersistentCollection {#106854 …}
    #variants: Doctrine\ORM\PersistentCollection {#106851 …}
    #options: Doctrine\ORM\PersistentCollection {#106847 …}
    #associations: Doctrine\ORM\PersistentCollection {#106849 …}
    #createdAt: DateTime @1751040672 {#106839
      date: 2025-06-27 18:11:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#106852
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106865 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107063
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106871}
        #id: 46233
        #name: "IEEE P32430"
        #slug: "ieee-p32430-ieee00010716-244462"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          The IEEE-2430 standard specifies the set of definitions, rules and steps for applying the IFPUG (International Function Point Users Group) nonfunctional size measurement method (SNAP) and provides guideline and examples of how to use the size measurements in software projects.<br />\n
          IEEE 2430 is complementary to ISO/IEC 20926:2009 &quot;Software and systems engineering -- Software measurement -- IFPUG functional size measurement method&quot;. Having both the functional size (ISO/IEC 20926:2009) and the non-functional size (IEEE 2430-2019) provides a complete view of the functional requirements and the non-functional requirements.<br />\n
          Providing quantifiable measures for the functional and the nonfunctional requirements allows organizations to build historical data repositories that can be referenced to assist in decision making for better planning and estimating cost and schedule of software projects, measure productivity and quality of software projects and analyze improvement trends.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft International Standard for Software Engineering -- Standard for Software Non-Functional Sizing Measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106862 …}
    #channels: Doctrine\ORM\PersistentCollection {#106856 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106860 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106858 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106872 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106879
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1694037600 {#106883
      date: 2023-09-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1663711200 {#106837
      date: 2022-09-21 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#106869 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106867 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 12814
    #code: "IEEE00010731"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040678 {#7274
      date: 2025-06-27 18:11:18.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 {#7311}
        #id: 46265
        #name: "IEEE/ISO/IEC 32430:2021"
        #slug: "ieee-iso-iec-32430-2021-ieee00010731-244470"
        #description: """
          Adoption Standard - Active.<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/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740524400 {#7292
      date: 2025-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1633989600 {#7318
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1633989600 {#7316
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#107194
  +product: App\Entity\Product\Product {#7311
    #id: 12814
    #code: "IEEE00010731"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040678 {#7274
      date: 2025-06-27 18:11:18.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 {#7311}
        #id: 46265
        #name: "IEEE/ISO/IEC 32430:2021"
        #slug: "ieee-iso-iec-32430-2021-ieee00010731-244470"
        #description: """
          Adoption Standard - Active.<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/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740524400 {#7292
      date: 2025-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1633989600 {#7318
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1633989600 {#7316
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 12814
    #code: "IEEE00010731"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040678 {#7274
      date: 2025-06-27 18:11:18.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 {#7311}
        #id: 46265
        #name: "IEEE/ISO/IEC 32430:2021"
        #slug: "ieee-iso-iec-32430-2021-ieee00010731-244470"
        #description: """
          Adoption Standard - Active.<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/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740524400 {#7292
      date: 2025-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1633989600 {#7318
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1633989600 {#7316
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#107221
  +product: App\Entity\Product\Product {#7311
    #id: 12814
    #code: "IEEE00010731"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040678 {#7274
      date: 2025-06-27 18:11:18.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 {#7311}
        #id: 46265
        #name: "IEEE/ISO/IEC 32430:2021"
        #slug: "ieee-iso-iec-32430-2021-ieee00010731-244470"
        #description: """
          Adoption Standard - Active.<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/ISO/IEC International Standard--Software engineering--Trial use standard for software non-functional sizing measurements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740524400 {#7292
      date: 2025-02-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1633989600 {#7318
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1633989600 {#7316
      date: 2021-10-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "32430"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#128531
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#128536 …}
    #variants: Doctrine\ORM\PersistentCollection {#128534 …}
    #options: Doctrine\ORM\PersistentCollection {#128529 …}
    #associations: Doctrine\ORM\PersistentCollection {#128532 …}
    #createdAt: DateTime @1751040087 {#128525
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128560
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128643
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128531}
        #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 {#128545 …}
    #channels: Doctrine\ORM\PersistentCollection {#128538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128552 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128511
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128559
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#128518
      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 {#128551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128549 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#128604
  +product: App\Entity\Product\Product {#128531
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#128536 …}
    #variants: Doctrine\ORM\PersistentCollection {#128534 …}
    #options: Doctrine\ORM\PersistentCollection {#128529 …}
    #associations: Doctrine\ORM\PersistentCollection {#128532 …}
    #createdAt: DateTime @1751040087 {#128525
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128560
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128643
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128531}
        #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 {#128545 …}
    #channels: Doctrine\ORM\PersistentCollection {#128538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128552 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128511
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128559
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#128518
      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 {#128551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128549 …}
  }
  +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 {#128531
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#128536 …}
    #variants: Doctrine\ORM\PersistentCollection {#128534 …}
    #options: Doctrine\ORM\PersistentCollection {#128529 …}
    #associations: Doctrine\ORM\PersistentCollection {#128532 …}
    #createdAt: DateTime @1751040087 {#128525
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128560
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128643
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128531}
        #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 {#128545 …}
    #channels: Doctrine\ORM\PersistentCollection {#128538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128552 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128511
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128559
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#128518
      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 {#128551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128549 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#128645
  +product: App\Entity\Product\Product {#128531
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#128536 …}
    #variants: Doctrine\ORM\PersistentCollection {#128534 …}
    #options: Doctrine\ORM\PersistentCollection {#128529 …}
    #associations: Doctrine\ORM\PersistentCollection {#128532 …}
    #createdAt: DateTime @1751040087 {#128525
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128560
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128643
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128531}
        #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 {#128545 …}
    #channels: Doctrine\ORM\PersistentCollection {#128538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128552 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128511
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128559
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#128518
      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 {#128551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128549 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#128531
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#128536 …}
    #variants: Doctrine\ORM\PersistentCollection {#128534 …}
    #options: Doctrine\ORM\PersistentCollection {#128529 …}
    #associations: Doctrine\ORM\PersistentCollection {#128532 …}
    #createdAt: DateTime @1751040087 {#128525
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128560
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128643
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128531}
        #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 {#128545 …}
    #channels: Doctrine\ORM\PersistentCollection {#128538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128552 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128511
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128559
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#128518
      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 {#128551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128549 …}
  }
]

App\Twig\Components\ProductMostRecent {#128722
  +product: App\Entity\Product\Product {#128531
    #id: 11936
    #code: "IEEE00006800"
    #attributes: Doctrine\ORM\PersistentCollection {#128536 …}
    #variants: Doctrine\ORM\PersistentCollection {#128534 …}
    #options: Doctrine\ORM\PersistentCollection {#128529 …}
    #associations: Doctrine\ORM\PersistentCollection {#128532 …}
    #createdAt: DateTime @1751040087 {#128525
      date: 2025-06-27 18:01:27.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128560
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128547 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128643
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128531}
        #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 {#128545 …}
    #channels: Doctrine\ORM\PersistentCollection {#128538 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128542 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128540 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128552 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128511
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128559
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1503871200 {#128518
      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 {#128551 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128549 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}