Symfony Profiler

[
  "paddingClasses" => "p-2 px-lg-5 py-lg-0"
  "searchPlaceholder" => "sylius.ui.search"
  "showSearch" => "true"
  "searchValue" => "IEEE/ISO/IEC 15068-2:1999"
  "title" => "Search results"
]

App\Twig\Components\PageBanner {#94652
  +supTitle: null
  +title: "Search results"
  +subTitle: null
  +backUrl: null
  +backLabel: null
  +customClasses: null
  +backgroundType: null
  +centered: true
  +showSearch: true
  +searchPlaceholder: "sylius.ui.search"
  +searchValue: "IEEE/ISO/IEC 15068-2:1999"
  +paddingClasses: "p-2 px-lg-5 py-lg-0"
}

[
  "product" => App\Entity\Product\Product {#95565
    #id: 11415
    #code: "IEEE00006082"
    #attributes: Doctrine\ORM\PersistentCollection {#95582 …}
    #variants: Doctrine\ORM\PersistentCollection {#95584 …}
    #options: Doctrine\ORM\PersistentCollection {#95588 …}
    #associations: Doctrine\ORM\PersistentCollection {#95586 …}
    #createdAt: DateTime @1751039690 {#95560
      date: 2025-06-27 17:54:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95561
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95572 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95980
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95565}
        #id: 40669
        #name: "IEEE/ISO/IEC 26513:2017"
        #slug: "ieee-iso-iec-26513-2017-ieee00006082-243067"
        #description: """
          Revision Standard - Active.<br />\n
          This document supports the need for software users to receive consistent, complete, accurate, and usable documentation. This document was developed to assist those who review, assess, and test software user documentation as part of the software lifecycle process. It is not limited to the review and test phase of the software lifecycle, but includes activities throughout the information management and documentation management processes. This document applies to printed and electronic documentation such as user manuals, online help, instructions, user assistance, tutorials, websites, and user reference documentation. Much of its guidance is applicable to user documentation for systems as well as the software used to control machinery or hardware devices. It applies to both initial development and subsequent releases of the software and user documentation. This document is intended for use by all types of organizations, whether or not a dedicated documentation department is present. Readers are assumed to have experience with or general knowledge of reviewing and testing processes.<br />\n
          \t\t\t\t<br />\n
          This document supports the interest of software users in receiving consistent, complete, accurate, and usable documentation and specifies processes for use in testing and reviewing of user documentation (Clause 6). It is not limited to the test and review stage of the lifecycle, but includes activities throughout the information management and documentation management process. This document is intended for use in all types of organizations, whether or not a dedicated documentation department is present. In all cases, it can be used as a basis for local standards and procedures. Readers are assumed to have experience or general knowledge of testing or reviewing processes. This document deals with the evaluation of end-user content only, and not with the evaluation of the software it supports.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for testers and reviewers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95574 …}
    #channels: Doctrine\ORM\PersistentCollection {#95580 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95576 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95578 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95566 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95562
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#95563
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508968800 {#95564
      date: 2017-10-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26513"
    -bookCollection: ""
    -pageCount: 49
    -documents: Doctrine\ORM\PersistentCollection {#95568 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95570 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#95860
  +product: App\Entity\Product\Product {#95565
    #id: 11415
    #code: "IEEE00006082"
    #attributes: Doctrine\ORM\PersistentCollection {#95582 …}
    #variants: Doctrine\ORM\PersistentCollection {#95584 …}
    #options: Doctrine\ORM\PersistentCollection {#95588 …}
    #associations: Doctrine\ORM\PersistentCollection {#95586 …}
    #createdAt: DateTime @1751039690 {#95560
      date: 2025-06-27 17:54:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95561
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95572 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95980
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95565}
        #id: 40669
        #name: "IEEE/ISO/IEC 26513:2017"
        #slug: "ieee-iso-iec-26513-2017-ieee00006082-243067"
        #description: """
          Revision Standard - Active.<br />\n
          This document supports the need for software users to receive consistent, complete, accurate, and usable documentation. This document was developed to assist those who review, assess, and test software user documentation as part of the software lifecycle process. It is not limited to the review and test phase of the software lifecycle, but includes activities throughout the information management and documentation management processes. This document applies to printed and electronic documentation such as user manuals, online help, instructions, user assistance, tutorials, websites, and user reference documentation. Much of its guidance is applicable to user documentation for systems as well as the software used to control machinery or hardware devices. It applies to both initial development and subsequent releases of the software and user documentation. This document is intended for use by all types of organizations, whether or not a dedicated documentation department is present. Readers are assumed to have experience with or general knowledge of reviewing and testing processes.<br />\n
          \t\t\t\t<br />\n
          This document supports the interest of software users in receiving consistent, complete, accurate, and usable documentation and specifies processes for use in testing and reviewing of user documentation (Clause 6). It is not limited to the test and review stage of the lifecycle, but includes activities throughout the information management and documentation management process. This document is intended for use in all types of organizations, whether or not a dedicated documentation department is present. In all cases, it can be used as a basis for local standards and procedures. Readers are assumed to have experience or general knowledge of testing or reviewing processes. This document deals with the evaluation of end-user content only, and not with the evaluation of the software it supports.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for testers and reviewers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95574 …}
    #channels: Doctrine\ORM\PersistentCollection {#95580 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95576 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95578 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95566 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95562
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#95563
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508968800 {#95564
      date: 2017-10-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26513"
    -bookCollection: ""
    -pageCount: 49
    -documents: Doctrine\ORM\PersistentCollection {#95568 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95570 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95565
    #id: 11415
    #code: "IEEE00006082"
    #attributes: Doctrine\ORM\PersistentCollection {#95582 …}
    #variants: Doctrine\ORM\PersistentCollection {#95584 …}
    #options: Doctrine\ORM\PersistentCollection {#95588 …}
    #associations: Doctrine\ORM\PersistentCollection {#95586 …}
    #createdAt: DateTime @1751039690 {#95560
      date: 2025-06-27 17:54:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95561
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95572 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95980
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95565}
        #id: 40669
        #name: "IEEE/ISO/IEC 26513:2017"
        #slug: "ieee-iso-iec-26513-2017-ieee00006082-243067"
        #description: """
          Revision Standard - Active.<br />\n
          This document supports the need for software users to receive consistent, complete, accurate, and usable documentation. This document was developed to assist those who review, assess, and test software user documentation as part of the software lifecycle process. It is not limited to the review and test phase of the software lifecycle, but includes activities throughout the information management and documentation management processes. This document applies to printed and electronic documentation such as user manuals, online help, instructions, user assistance, tutorials, websites, and user reference documentation. Much of its guidance is applicable to user documentation for systems as well as the software used to control machinery or hardware devices. It applies to both initial development and subsequent releases of the software and user documentation. This document is intended for use by all types of organizations, whether or not a dedicated documentation department is present. Readers are assumed to have experience with or general knowledge of reviewing and testing processes.<br />\n
          \t\t\t\t<br />\n
          This document supports the interest of software users in receiving consistent, complete, accurate, and usable documentation and specifies processes for use in testing and reviewing of user documentation (Clause 6). It is not limited to the test and review stage of the lifecycle, but includes activities throughout the information management and documentation management process. This document is intended for use in all types of organizations, whether or not a dedicated documentation department is present. In all cases, it can be used as a basis for local standards and procedures. Readers are assumed to have experience or general knowledge of testing or reviewing processes. This document deals with the evaluation of end-user content only, and not with the evaluation of the software it supports.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for testers and reviewers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95574 …}
    #channels: Doctrine\ORM\PersistentCollection {#95580 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95576 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95578 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95566 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95562
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#95563
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508968800 {#95564
      date: 2017-10-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26513"
    -bookCollection: ""
    -pageCount: 49
    -documents: Doctrine\ORM\PersistentCollection {#95568 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95570 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#95987
  +product: App\Entity\Product\Product {#95565
    #id: 11415
    #code: "IEEE00006082"
    #attributes: Doctrine\ORM\PersistentCollection {#95582 …}
    #variants: Doctrine\ORM\PersistentCollection {#95584 …}
    #options: Doctrine\ORM\PersistentCollection {#95588 …}
    #associations: Doctrine\ORM\PersistentCollection {#95586 …}
    #createdAt: DateTime @1751039690 {#95560
      date: 2025-06-27 17:54:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95561
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95572 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95980
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95565}
        #id: 40669
        #name: "IEEE/ISO/IEC 26513:2017"
        #slug: "ieee-iso-iec-26513-2017-ieee00006082-243067"
        #description: """
          Revision Standard - Active.<br />\n
          This document supports the need for software users to receive consistent, complete, accurate, and usable documentation. This document was developed to assist those who review, assess, and test software user documentation as part of the software lifecycle process. It is not limited to the review and test phase of the software lifecycle, but includes activities throughout the information management and documentation management processes. This document applies to printed and electronic documentation such as user manuals, online help, instructions, user assistance, tutorials, websites, and user reference documentation. Much of its guidance is applicable to user documentation for systems as well as the software used to control machinery or hardware devices. It applies to both initial development and subsequent releases of the software and user documentation. This document is intended for use by all types of organizations, whether or not a dedicated documentation department is present. Readers are assumed to have experience with or general knowledge of reviewing and testing processes.<br />\n
          \t\t\t\t<br />\n
          This document supports the interest of software users in receiving consistent, complete, accurate, and usable documentation and specifies processes for use in testing and reviewing of user documentation (Clause 6). It is not limited to the test and review stage of the lifecycle, but includes activities throughout the information management and documentation management process. This document is intended for use in all types of organizations, whether or not a dedicated documentation department is present. In all cases, it can be used as a basis for local standards and procedures. Readers are assumed to have experience or general knowledge of testing or reviewing processes. This document deals with the evaluation of end-user content only, and not with the evaluation of the software it supports.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for testers and reviewers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95574 …}
    #channels: Doctrine\ORM\PersistentCollection {#95580 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95576 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95578 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95566 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95562
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#95563
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508968800 {#95564
      date: 2017-10-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26513"
    -bookCollection: ""
    -pageCount: 49
    -documents: Doctrine\ORM\PersistentCollection {#95568 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95570 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95565
    #id: 11415
    #code: "IEEE00006082"
    #attributes: Doctrine\ORM\PersistentCollection {#95582 …}
    #variants: Doctrine\ORM\PersistentCollection {#95584 …}
    #options: Doctrine\ORM\PersistentCollection {#95588 …}
    #associations: Doctrine\ORM\PersistentCollection {#95586 …}
    #createdAt: DateTime @1751039690 {#95560
      date: 2025-06-27 17:54:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95561
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95572 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95980
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95565}
        #id: 40669
        #name: "IEEE/ISO/IEC 26513:2017"
        #slug: "ieee-iso-iec-26513-2017-ieee00006082-243067"
        #description: """
          Revision Standard - Active.<br />\n
          This document supports the need for software users to receive consistent, complete, accurate, and usable documentation. This document was developed to assist those who review, assess, and test software user documentation as part of the software lifecycle process. It is not limited to the review and test phase of the software lifecycle, but includes activities throughout the information management and documentation management processes. This document applies to printed and electronic documentation such as user manuals, online help, instructions, user assistance, tutorials, websites, and user reference documentation. Much of its guidance is applicable to user documentation for systems as well as the software used to control machinery or hardware devices. It applies to both initial development and subsequent releases of the software and user documentation. This document is intended for use by all types of organizations, whether or not a dedicated documentation department is present. Readers are assumed to have experience with or general knowledge of reviewing and testing processes.<br />\n
          \t\t\t\t<br />\n
          This document supports the interest of software users in receiving consistent, complete, accurate, and usable documentation and specifies processes for use in testing and reviewing of user documentation (Clause 6). It is not limited to the test and review stage of the lifecycle, but includes activities throughout the information management and documentation management process. This document is intended for use in all types of organizations, whether or not a dedicated documentation department is present. In all cases, it can be used as a basis for local standards and procedures. Readers are assumed to have experience or general knowledge of testing or reviewing processes. This document deals with the evaluation of end-user content only, and not with the evaluation of the software it supports.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for testers and reviewers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95574 …}
    #channels: Doctrine\ORM\PersistentCollection {#95580 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95576 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95578 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95566 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95562
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#95563
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508968800 {#95564
      date: 2017-10-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26513"
    -bookCollection: ""
    -pageCount: 49
    -documents: Doctrine\ORM\PersistentCollection {#95568 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95570 …}
  }
]

App\Twig\Components\ProductMostRecent {#96081
  +product: App\Entity\Product\Product {#95565
    #id: 11415
    #code: "IEEE00006082"
    #attributes: Doctrine\ORM\PersistentCollection {#95582 …}
    #variants: Doctrine\ORM\PersistentCollection {#95584 …}
    #options: Doctrine\ORM\PersistentCollection {#95588 …}
    #associations: Doctrine\ORM\PersistentCollection {#95586 …}
    #createdAt: DateTime @1751039690 {#95560
      date: 2025-06-27 17:54:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95561
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95572 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95980
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95565}
        #id: 40669
        #name: "IEEE/ISO/IEC 26513:2017"
        #slug: "ieee-iso-iec-26513-2017-ieee00006082-243067"
        #description: """
          Revision Standard - Active.<br />\n
          This document supports the need for software users to receive consistent, complete, accurate, and usable documentation. This document was developed to assist those who review, assess, and test software user documentation as part of the software lifecycle process. It is not limited to the review and test phase of the software lifecycle, but includes activities throughout the information management and documentation management processes. This document applies to printed and electronic documentation such as user manuals, online help, instructions, user assistance, tutorials, websites, and user reference documentation. Much of its guidance is applicable to user documentation for systems as well as the software used to control machinery or hardware devices. It applies to both initial development and subsequent releases of the software and user documentation. This document is intended for use by all types of organizations, whether or not a dedicated documentation department is present. Readers are assumed to have experience with or general knowledge of reviewing and testing processes.<br />\n
          \t\t\t\t<br />\n
          This document supports the interest of software users in receiving consistent, complete, accurate, and usable documentation and specifies processes for use in testing and reviewing of user documentation (Clause 6). It is not limited to the test and review stage of the lifecycle, but includes activities throughout the information management and documentation management process. This document is intended for use in all types of organizations, whether or not a dedicated documentation department is present. In all cases, it can be used as a basis for local standards and procedures. Readers are assumed to have experience or general knowledge of testing or reviewing processes. This document deals with the evaluation of end-user content only, and not with the evaluation of the software it supports.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for testers and reviewers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95574 …}
    #channels: Doctrine\ORM\PersistentCollection {#95580 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95576 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95578 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95566 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95562
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1743116400 {#95563
      date: 2025-03-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508968800 {#95564
      date: 2017-10-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26513"
    -bookCollection: ""
    -pageCount: 49
    -documents: Doctrine\ORM\PersistentCollection {#95568 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95570 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95625
    #id: 11971
    #code: "IEEE00006845"
    #attributes: Doctrine\ORM\PersistentCollection {#95642 …}
    #variants: Doctrine\ORM\PersistentCollection {#95644 …}
    #options: Doctrine\ORM\PersistentCollection {#95648 …}
    #associations: Doctrine\ORM\PersistentCollection {#95646 …}
    #createdAt: DateTime @1751040110 {#95620
      date: 2025-06-27 18:01:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95621
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95632 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96312
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95625}
        #id: 42893
        #name: "IEEE/ISO/IEC 26512:2017"
        #slug: "ieee-iso-iec-26512-2017-ieee00006845-243623"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.<br />\n
          As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:<br />\n
          — information management;<br />\n
          — information design and development;<br />\n
          — information editing and review coordination;<br />\n
          — information testing, particularly usability testing;<br />\n
          — information production and packaging;<br />\n
          — information distribution and delivery;<br />\n
          — advice on the selection and implementation of information development tools and supporting systems; and<br />\n
          — information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information.<br />\n
          These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95634 …}
    #channels: Doctrine\ORM\PersistentCollection {#95640 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95638 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95626 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95622
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95623
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1509490800 {#95624
      date: 2017-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 47
    -documents: Doctrine\ORM\PersistentCollection {#95628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95630 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96290
  +product: App\Entity\Product\Product {#95625
    #id: 11971
    #code: "IEEE00006845"
    #attributes: Doctrine\ORM\PersistentCollection {#95642 …}
    #variants: Doctrine\ORM\PersistentCollection {#95644 …}
    #options: Doctrine\ORM\PersistentCollection {#95648 …}
    #associations: Doctrine\ORM\PersistentCollection {#95646 …}
    #createdAt: DateTime @1751040110 {#95620
      date: 2025-06-27 18:01:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95621
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95632 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96312
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95625}
        #id: 42893
        #name: "IEEE/ISO/IEC 26512:2017"
        #slug: "ieee-iso-iec-26512-2017-ieee00006845-243623"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.<br />\n
          As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:<br />\n
          — information management;<br />\n
          — information design and development;<br />\n
          — information editing and review coordination;<br />\n
          — information testing, particularly usability testing;<br />\n
          — information production and packaging;<br />\n
          — information distribution and delivery;<br />\n
          — advice on the selection and implementation of information development tools and supporting systems; and<br />\n
          — information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information.<br />\n
          These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95634 …}
    #channels: Doctrine\ORM\PersistentCollection {#95640 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95638 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95626 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95622
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95623
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1509490800 {#95624
      date: 2017-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 47
    -documents: Doctrine\ORM\PersistentCollection {#95628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95630 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95625
    #id: 11971
    #code: "IEEE00006845"
    #attributes: Doctrine\ORM\PersistentCollection {#95642 …}
    #variants: Doctrine\ORM\PersistentCollection {#95644 …}
    #options: Doctrine\ORM\PersistentCollection {#95648 …}
    #associations: Doctrine\ORM\PersistentCollection {#95646 …}
    #createdAt: DateTime @1751040110 {#95620
      date: 2025-06-27 18:01:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95621
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95632 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96312
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95625}
        #id: 42893
        #name: "IEEE/ISO/IEC 26512:2017"
        #slug: "ieee-iso-iec-26512-2017-ieee00006845-243623"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.<br />\n
          As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:<br />\n
          — information management;<br />\n
          — information design and development;<br />\n
          — information editing and review coordination;<br />\n
          — information testing, particularly usability testing;<br />\n
          — information production and packaging;<br />\n
          — information distribution and delivery;<br />\n
          — advice on the selection and implementation of information development tools and supporting systems; and<br />\n
          — information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information.<br />\n
          These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95634 …}
    #channels: Doctrine\ORM\PersistentCollection {#95640 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95638 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95626 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95622
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95623
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1509490800 {#95624
      date: 2017-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 47
    -documents: Doctrine\ORM\PersistentCollection {#95628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95630 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96326
  +product: App\Entity\Product\Product {#95625
    #id: 11971
    #code: "IEEE00006845"
    #attributes: Doctrine\ORM\PersistentCollection {#95642 …}
    #variants: Doctrine\ORM\PersistentCollection {#95644 …}
    #options: Doctrine\ORM\PersistentCollection {#95648 …}
    #associations: Doctrine\ORM\PersistentCollection {#95646 …}
    #createdAt: DateTime @1751040110 {#95620
      date: 2025-06-27 18:01:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95621
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95632 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96312
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95625}
        #id: 42893
        #name: "IEEE/ISO/IEC 26512:2017"
        #slug: "ieee-iso-iec-26512-2017-ieee00006845-243623"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.<br />\n
          As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:<br />\n
          — information management;<br />\n
          — information design and development;<br />\n
          — information editing and review coordination;<br />\n
          — information testing, particularly usability testing;<br />\n
          — information production and packaging;<br />\n
          — information distribution and delivery;<br />\n
          — advice on the selection and implementation of information development tools and supporting systems; and<br />\n
          — information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information.<br />\n
          These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95634 …}
    #channels: Doctrine\ORM\PersistentCollection {#95640 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95638 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95626 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95622
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95623
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1509490800 {#95624
      date: 2017-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 47
    -documents: Doctrine\ORM\PersistentCollection {#95628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95630 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95625
    #id: 11971
    #code: "IEEE00006845"
    #attributes: Doctrine\ORM\PersistentCollection {#95642 …}
    #variants: Doctrine\ORM\PersistentCollection {#95644 …}
    #options: Doctrine\ORM\PersistentCollection {#95648 …}
    #associations: Doctrine\ORM\PersistentCollection {#95646 …}
    #createdAt: DateTime @1751040110 {#95620
      date: 2025-06-27 18:01:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95621
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95632 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96312
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95625}
        #id: 42893
        #name: "IEEE/ISO/IEC 26512:2017"
        #slug: "ieee-iso-iec-26512-2017-ieee00006845-243623"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.<br />\n
          As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:<br />\n
          — information management;<br />\n
          — information design and development;<br />\n
          — information editing and review coordination;<br />\n
          — information testing, particularly usability testing;<br />\n
          — information production and packaging;<br />\n
          — information distribution and delivery;<br />\n
          — advice on the selection and implementation of information development tools and supporting systems; and<br />\n
          — information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information.<br />\n
          These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95634 …}
    #channels: Doctrine\ORM\PersistentCollection {#95640 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95638 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95626 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95622
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95623
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1509490800 {#95624
      date: 2017-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 47
    -documents: Doctrine\ORM\PersistentCollection {#95628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95630 …}
  }
]

App\Twig\Components\ProductMostRecent {#96400
  +product: App\Entity\Product\Product {#95625
    #id: 11971
    #code: "IEEE00006845"
    #attributes: Doctrine\ORM\PersistentCollection {#95642 …}
    #variants: Doctrine\ORM\PersistentCollection {#95644 …}
    #options: Doctrine\ORM\PersistentCollection {#95648 …}
    #associations: Doctrine\ORM\PersistentCollection {#95646 …}
    #createdAt: DateTime @1751040110 {#95620
      date: 2025-06-27 18:01:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95621
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95632 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96312
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95625}
        #id: 42893
        #name: "IEEE/ISO/IEC 26512:2017"
        #slug: "ieee-iso-iec-26512-2017-ieee00006845-243623"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information.<br />\n
          As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following:<br />\n
          — information management;<br />\n
          — information design and development;<br />\n
          — information editing and review coordination;<br />\n
          — information testing, particularly usability testing;<br />\n
          — information production and packaging;<br />\n
          — information distribution and delivery;<br />\n
          — advice on the selection and implementation of information development tools and supporting systems; and<br />\n
          — information development process improvement.<br />\n
          This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information.<br />\n
          These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95634 …}
    #channels: Doctrine\ORM\PersistentCollection {#95640 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95636 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95638 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95626 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95622
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95623
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1509490800 {#95624
      date: 2017-11-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26512"
    -bookCollection: ""
    -pageCount: 47
    -documents: Doctrine\ORM\PersistentCollection {#95628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95630 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95655
    #id: 12348
    #code: "IEEE00007497"
    #attributes: Doctrine\ORM\PersistentCollection {#95672 …}
    #variants: Doctrine\ORM\PersistentCollection {#95674 …}
    #options: Doctrine\ORM\PersistentCollection {#95678 …}
    #associations: Doctrine\ORM\PersistentCollection {#95676 …}
    #createdAt: DateTime @1751040374 {#95650
      date: 2025-06-27 18:06:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95651
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95662 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96542
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95655}
        #id: 44401
        #name: "IEEE/ISO/IEC P29119-1"
        #slug: "ieee-iso-iec-p29119-1-ieee00007497-244001"
        #description: """
          Revision Standard - Superseded - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC/IEEE 29119 specifies definitions and concepts in software testing. It provides definitions of testing terms and discussion of concepts key to the understanding of the ISO/IEC/IEEE 29119 series of software testing international standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Approved Draft International Standard - Software and systems engineering--Software testing--Part 1: Concepts and definitions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95664 …}
    #channels: Doctrine\ORM\PersistentCollection {#95670 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95666 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95668 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95652
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708556400 {#95653
      date: 2024-02-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1643583600 {#95654
      date: 2022-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29119-1"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#95658 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95660 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96522
  +product: App\Entity\Product\Product {#95655
    #id: 12348
    #code: "IEEE00007497"
    #attributes: Doctrine\ORM\PersistentCollection {#95672 …}
    #variants: Doctrine\ORM\PersistentCollection {#95674 …}
    #options: Doctrine\ORM\PersistentCollection {#95678 …}
    #associations: Doctrine\ORM\PersistentCollection {#95676 …}
    #createdAt: DateTime @1751040374 {#95650
      date: 2025-06-27 18:06:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95651
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95662 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96542
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95655}
        #id: 44401
        #name: "IEEE/ISO/IEC P29119-1"
        #slug: "ieee-iso-iec-p29119-1-ieee00007497-244001"
        #description: """
          Revision Standard - Superseded - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC/IEEE 29119 specifies definitions and concepts in software testing. It provides definitions of testing terms and discussion of concepts key to the understanding of the ISO/IEC/IEEE 29119 series of software testing international standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Approved Draft International Standard - Software and systems engineering--Software testing--Part 1: Concepts and definitions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95664 …}
    #channels: Doctrine\ORM\PersistentCollection {#95670 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95666 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95668 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95652
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708556400 {#95653
      date: 2024-02-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1643583600 {#95654
      date: 2022-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29119-1"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#95658 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95660 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95655
    #id: 12348
    #code: "IEEE00007497"
    #attributes: Doctrine\ORM\PersistentCollection {#95672 …}
    #variants: Doctrine\ORM\PersistentCollection {#95674 …}
    #options: Doctrine\ORM\PersistentCollection {#95678 …}
    #associations: Doctrine\ORM\PersistentCollection {#95676 …}
    #createdAt: DateTime @1751040374 {#95650
      date: 2025-06-27 18:06:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95651
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95662 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96542
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95655}
        #id: 44401
        #name: "IEEE/ISO/IEC P29119-1"
        #slug: "ieee-iso-iec-p29119-1-ieee00007497-244001"
        #description: """
          Revision Standard - Superseded - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC/IEEE 29119 specifies definitions and concepts in software testing. It provides definitions of testing terms and discussion of concepts key to the understanding of the ISO/IEC/IEEE 29119 series of software testing international standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Approved Draft International Standard - Software and systems engineering--Software testing--Part 1: Concepts and definitions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95664 …}
    #channels: Doctrine\ORM\PersistentCollection {#95670 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95666 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95668 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95652
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708556400 {#95653
      date: 2024-02-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1643583600 {#95654
      date: 2022-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29119-1"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#95658 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95660 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96549
  +product: App\Entity\Product\Product {#95655
    #id: 12348
    #code: "IEEE00007497"
    #attributes: Doctrine\ORM\PersistentCollection {#95672 …}
    #variants: Doctrine\ORM\PersistentCollection {#95674 …}
    #options: Doctrine\ORM\PersistentCollection {#95678 …}
    #associations: Doctrine\ORM\PersistentCollection {#95676 …}
    #createdAt: DateTime @1751040374 {#95650
      date: 2025-06-27 18:06:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95651
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95662 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96542
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95655}
        #id: 44401
        #name: "IEEE/ISO/IEC P29119-1"
        #slug: "ieee-iso-iec-p29119-1-ieee00007497-244001"
        #description: """
          Revision Standard - Superseded - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC/IEEE 29119 specifies definitions and concepts in software testing. It provides definitions of testing terms and discussion of concepts key to the understanding of the ISO/IEC/IEEE 29119 series of software testing international standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Approved Draft International Standard - Software and systems engineering--Software testing--Part 1: Concepts and definitions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95664 …}
    #channels: Doctrine\ORM\PersistentCollection {#95670 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95666 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95668 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95652
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708556400 {#95653
      date: 2024-02-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1643583600 {#95654
      date: 2022-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29119-1"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#95658 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95660 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95655
    #id: 12348
    #code: "IEEE00007497"
    #attributes: Doctrine\ORM\PersistentCollection {#95672 …}
    #variants: Doctrine\ORM\PersistentCollection {#95674 …}
    #options: Doctrine\ORM\PersistentCollection {#95678 …}
    #associations: Doctrine\ORM\PersistentCollection {#95676 …}
    #createdAt: DateTime @1751040374 {#95650
      date: 2025-06-27 18:06:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95651
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95662 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96542
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95655}
        #id: 44401
        #name: "IEEE/ISO/IEC P29119-1"
        #slug: "ieee-iso-iec-p29119-1-ieee00007497-244001"
        #description: """
          Revision Standard - Superseded - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC/IEEE 29119 specifies definitions and concepts in software testing. It provides definitions of testing terms and discussion of concepts key to the understanding of the ISO/IEC/IEEE 29119 series of software testing international standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Approved Draft International Standard - Software and systems engineering--Software testing--Part 1: Concepts and definitions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95664 …}
    #channels: Doctrine\ORM\PersistentCollection {#95670 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95666 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95668 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95652
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708556400 {#95653
      date: 2024-02-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1643583600 {#95654
      date: 2022-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29119-1"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#95658 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95660 …}
  }
]

App\Twig\Components\ProductMostRecent {#96626
  +product: App\Entity\Product\Product {#95655
    #id: 12348
    #code: "IEEE00007497"
    #attributes: Doctrine\ORM\PersistentCollection {#95672 …}
    #variants: Doctrine\ORM\PersistentCollection {#95674 …}
    #options: Doctrine\ORM\PersistentCollection {#95678 …}
    #associations: Doctrine\ORM\PersistentCollection {#95676 …}
    #createdAt: DateTime @1751040374 {#95650
      date: 2025-06-27 18:06:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95651
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95662 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96542
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95655}
        #id: 44401
        #name: "IEEE/ISO/IEC P29119-1"
        #slug: "ieee-iso-iec-p29119-1-ieee00007497-244001"
        #description: """
          Revision Standard - Superseded - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC/IEEE 29119 specifies definitions and concepts in software testing. It provides definitions of testing terms and discussion of concepts key to the understanding of the ISO/IEC/IEEE 29119 series of software testing international standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Approved Draft International Standard - Software and systems engineering--Software testing--Part 1: Concepts and definitions"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95664 …}
    #channels: Doctrine\ORM\PersistentCollection {#95670 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95666 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95668 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95652
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708556400 {#95653
      date: 2024-02-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1643583600 {#95654
      date: 2022-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "29119-1"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#95658 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95660 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95685
    #id: 12546
    #code: "IEEE00010139"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040504 {#95680
      date: 2025-06-27 18:08:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95681
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96751
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45193
        #name: "IEEE/ISO/IEC 24641:2023"
        #slug: "ieee-iso-iec-24641-2023-ieee00010139-244201"
        #description: """
          New IEEE Standard - Active.<br />\n
          This International Standard, within the context of methods and tools for MBSSE: • Provides terms and definitions related to MBSSE; • Defines MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, tasks, and outcomes; • Defines methods to support the defined tasks of each process; • Defines tool capabilities to automate/semi-automate tasks or methods. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects. These processes are applicable for managing and performing the systems engineering activities based on models within any stage in the life cycle of a system of interest. Annex D (informative) Relationship with other standards describes the relationships between this document and other standards.<br />\n
          \t\t\t\t<br />\n
          This document deals with the tool capabilities and methods for model-based systems and software engineering (MBSSE). This document:--specifies a reference model for the overall structure and processes of MBSSE-specific processes, and describes how the components of the reference model fit together;--specifies interrelationships between the components of the reference model;--specifies MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, outcomes and tasks;--specifies methods to support the defined tasks of each process;--specifies tool capabilities to automate or semi-automate tasks or methods. This document does not bring any additional life cycle processes for system and software but specifies an MBSSE reference model considered as activities, not only from the life cycle perspectives of systems engineering problem solving and the system-of-interest evolution, but also from the cognitive perspectives of modelling and model management, which can sustain and facilitate the system and software life cycle processes during digital transformation and in the digital age. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects or an enterprise. These processes are applicable for managing and performing the systems and software engineering activities based on models within any stage in the life cycle of a system-of-interest.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and Software engineering--Methods and tools for model-based systems and software engineering"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95682
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#95683
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1684188000 {#95684
      date: 2023-05-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24641"
    -bookCollection: ""
    -pageCount: 98
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96731
  +product: App\Entity\Product\Product {#95685
    #id: 12546
    #code: "IEEE00010139"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040504 {#95680
      date: 2025-06-27 18:08:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95681
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96751
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45193
        #name: "IEEE/ISO/IEC 24641:2023"
        #slug: "ieee-iso-iec-24641-2023-ieee00010139-244201"
        #description: """
          New IEEE Standard - Active.<br />\n
          This International Standard, within the context of methods and tools for MBSSE: • Provides terms and definitions related to MBSSE; • Defines MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, tasks, and outcomes; • Defines methods to support the defined tasks of each process; • Defines tool capabilities to automate/semi-automate tasks or methods. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects. These processes are applicable for managing and performing the systems engineering activities based on models within any stage in the life cycle of a system of interest. Annex D (informative) Relationship with other standards describes the relationships between this document and other standards.<br />\n
          \t\t\t\t<br />\n
          This document deals with the tool capabilities and methods for model-based systems and software engineering (MBSSE). This document:--specifies a reference model for the overall structure and processes of MBSSE-specific processes, and describes how the components of the reference model fit together;--specifies interrelationships between the components of the reference model;--specifies MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, outcomes and tasks;--specifies methods to support the defined tasks of each process;--specifies tool capabilities to automate or semi-automate tasks or methods. This document does not bring any additional life cycle processes for system and software but specifies an MBSSE reference model considered as activities, not only from the life cycle perspectives of systems engineering problem solving and the system-of-interest evolution, but also from the cognitive perspectives of modelling and model management, which can sustain and facilitate the system and software life cycle processes during digital transformation and in the digital age. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects or an enterprise. These processes are applicable for managing and performing the systems and software engineering activities based on models within any stage in the life cycle of a system-of-interest.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and Software engineering--Methods and tools for model-based systems and software engineering"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95682
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#95683
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1684188000 {#95684
      date: 2023-05-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24641"
    -bookCollection: ""
    -pageCount: 98
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95685
    #id: 12546
    #code: "IEEE00010139"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040504 {#95680
      date: 2025-06-27 18:08:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95681
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96751
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45193
        #name: "IEEE/ISO/IEC 24641:2023"
        #slug: "ieee-iso-iec-24641-2023-ieee00010139-244201"
        #description: """
          New IEEE Standard - Active.<br />\n
          This International Standard, within the context of methods and tools for MBSSE: • Provides terms and definitions related to MBSSE; • Defines MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, tasks, and outcomes; • Defines methods to support the defined tasks of each process; • Defines tool capabilities to automate/semi-automate tasks or methods. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects. These processes are applicable for managing and performing the systems engineering activities based on models within any stage in the life cycle of a system of interest. Annex D (informative) Relationship with other standards describes the relationships between this document and other standards.<br />\n
          \t\t\t\t<br />\n
          This document deals with the tool capabilities and methods for model-based systems and software engineering (MBSSE). This document:--specifies a reference model for the overall structure and processes of MBSSE-specific processes, and describes how the components of the reference model fit together;--specifies interrelationships between the components of the reference model;--specifies MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, outcomes and tasks;--specifies methods to support the defined tasks of each process;--specifies tool capabilities to automate or semi-automate tasks or methods. This document does not bring any additional life cycle processes for system and software but specifies an MBSSE reference model considered as activities, not only from the life cycle perspectives of systems engineering problem solving and the system-of-interest evolution, but also from the cognitive perspectives of modelling and model management, which can sustain and facilitate the system and software life cycle processes during digital transformation and in the digital age. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects or an enterprise. These processes are applicable for managing and performing the systems and software engineering activities based on models within any stage in the life cycle of a system-of-interest.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and Software engineering--Methods and tools for model-based systems and software engineering"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95682
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#95683
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1684188000 {#95684
      date: 2023-05-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24641"
    -bookCollection: ""
    -pageCount: 98
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96765
  +product: App\Entity\Product\Product {#95685
    #id: 12546
    #code: "IEEE00010139"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040504 {#95680
      date: 2025-06-27 18:08:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95681
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96751
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45193
        #name: "IEEE/ISO/IEC 24641:2023"
        #slug: "ieee-iso-iec-24641-2023-ieee00010139-244201"
        #description: """
          New IEEE Standard - Active.<br />\n
          This International Standard, within the context of methods and tools for MBSSE: • Provides terms and definitions related to MBSSE; • Defines MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, tasks, and outcomes; • Defines methods to support the defined tasks of each process; • Defines tool capabilities to automate/semi-automate tasks or methods. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects. These processes are applicable for managing and performing the systems engineering activities based on models within any stage in the life cycle of a system of interest. Annex D (informative) Relationship with other standards describes the relationships between this document and other standards.<br />\n
          \t\t\t\t<br />\n
          This document deals with the tool capabilities and methods for model-based systems and software engineering (MBSSE). This document:--specifies a reference model for the overall structure and processes of MBSSE-specific processes, and describes how the components of the reference model fit together;--specifies interrelationships between the components of the reference model;--specifies MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, outcomes and tasks;--specifies methods to support the defined tasks of each process;--specifies tool capabilities to automate or semi-automate tasks or methods. This document does not bring any additional life cycle processes for system and software but specifies an MBSSE reference model considered as activities, not only from the life cycle perspectives of systems engineering problem solving and the system-of-interest evolution, but also from the cognitive perspectives of modelling and model management, which can sustain and facilitate the system and software life cycle processes during digital transformation and in the digital age. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects or an enterprise. These processes are applicable for managing and performing the systems and software engineering activities based on models within any stage in the life cycle of a system-of-interest.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and Software engineering--Methods and tools for model-based systems and software engineering"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95682
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#95683
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1684188000 {#95684
      date: 2023-05-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24641"
    -bookCollection: ""
    -pageCount: 98
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95685
    #id: 12546
    #code: "IEEE00010139"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040504 {#95680
      date: 2025-06-27 18:08:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95681
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96751
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45193
        #name: "IEEE/ISO/IEC 24641:2023"
        #slug: "ieee-iso-iec-24641-2023-ieee00010139-244201"
        #description: """
          New IEEE Standard - Active.<br />\n
          This International Standard, within the context of methods and tools for MBSSE: • Provides terms and definitions related to MBSSE; • Defines MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, tasks, and outcomes; • Defines methods to support the defined tasks of each process; • Defines tool capabilities to automate/semi-automate tasks or methods. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects. These processes are applicable for managing and performing the systems engineering activities based on models within any stage in the life cycle of a system of interest. Annex D (informative) Relationship with other standards describes the relationships between this document and other standards.<br />\n
          \t\t\t\t<br />\n
          This document deals with the tool capabilities and methods for model-based systems and software engineering (MBSSE). This document:--specifies a reference model for the overall structure and processes of MBSSE-specific processes, and describes how the components of the reference model fit together;--specifies interrelationships between the components of the reference model;--specifies MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, outcomes and tasks;--specifies methods to support the defined tasks of each process;--specifies tool capabilities to automate or semi-automate tasks or methods. This document does not bring any additional life cycle processes for system and software but specifies an MBSSE reference model considered as activities, not only from the life cycle perspectives of systems engineering problem solving and the system-of-interest evolution, but also from the cognitive perspectives of modelling and model management, which can sustain and facilitate the system and software life cycle processes during digital transformation and in the digital age. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects or an enterprise. These processes are applicable for managing and performing the systems and software engineering activities based on models within any stage in the life cycle of a system-of-interest.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and Software engineering--Methods and tools for model-based systems and software engineering"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95682
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#95683
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1684188000 {#95684
      date: 2023-05-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24641"
    -bookCollection: ""
    -pageCount: 98
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
]

App\Twig\Components\ProductMostRecent {#96839
  +product: App\Entity\Product\Product {#95685
    #id: 12546
    #code: "IEEE00010139"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040504 {#95680
      date: 2025-06-27 18:08:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95681
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96751
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45193
        #name: "IEEE/ISO/IEC 24641:2023"
        #slug: "ieee-iso-iec-24641-2023-ieee00010139-244201"
        #description: """
          New IEEE Standard - Active.<br />\n
          This International Standard, within the context of methods and tools for MBSSE: • Provides terms and definitions related to MBSSE; • Defines MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, tasks, and outcomes; • Defines methods to support the defined tasks of each process; • Defines tool capabilities to automate/semi-automate tasks or methods. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects. These processes are applicable for managing and performing the systems engineering activities based on models within any stage in the life cycle of a system of interest. Annex D (informative) Relationship with other standards describes the relationships between this document and other standards.<br />\n
          \t\t\t\t<br />\n
          This document deals with the tool capabilities and methods for model-based systems and software engineering (MBSSE). This document:--specifies a reference model for the overall structure and processes of MBSSE-specific processes, and describes how the components of the reference model fit together;--specifies interrelationships between the components of the reference model;--specifies MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, outcomes and tasks;--specifies methods to support the defined tasks of each process;--specifies tool capabilities to automate or semi-automate tasks or methods. This document does not bring any additional life cycle processes for system and software but specifies an MBSSE reference model considered as activities, not only from the life cycle perspectives of systems engineering problem solving and the system-of-interest evolution, but also from the cognitive perspectives of modelling and model management, which can sustain and facilitate the system and software life cycle processes during digital transformation and in the digital age. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects or an enterprise. These processes are applicable for managing and performing the systems and software engineering activities based on models within any stage in the life cycle of a system-of-interest.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and Software engineering--Methods and tools for model-based systems and software engineering"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95682
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#95683
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1684188000 {#95684
      date: 2023-05-16 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24641"
    -bookCollection: ""
    -pageCount: 98
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95775
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#95792 …}
    #variants: Doctrine\ORM\PersistentCollection {#95794 …}
    #options: Doctrine\ORM\PersistentCollection {#95798 …}
    #associations: Doctrine\ORM\PersistentCollection {#95796 …}
    #createdAt: DateTime @1751040752 {#95770
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95771
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95782 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96981
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95775}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95784 …}
    #channels: Doctrine\ORM\PersistentCollection {#95790 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95786 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95788 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95776 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#95773
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#95774
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#95778 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95780 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96961
  +product: App\Entity\Product\Product {#95775
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#95792 …}
    #variants: Doctrine\ORM\PersistentCollection {#95794 …}
    #options: Doctrine\ORM\PersistentCollection {#95798 …}
    #associations: Doctrine\ORM\PersistentCollection {#95796 …}
    #createdAt: DateTime @1751040752 {#95770
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95771
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95782 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96981
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95775}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95784 …}
    #channels: Doctrine\ORM\PersistentCollection {#95790 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95786 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95788 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95776 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#95773
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#95774
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#95778 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95780 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95775
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#95792 …}
    #variants: Doctrine\ORM\PersistentCollection {#95794 …}
    #options: Doctrine\ORM\PersistentCollection {#95798 …}
    #associations: Doctrine\ORM\PersistentCollection {#95796 …}
    #createdAt: DateTime @1751040752 {#95770
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95771
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95782 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96981
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95775}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95784 …}
    #channels: Doctrine\ORM\PersistentCollection {#95790 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95786 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95788 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95776 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#95773
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#95774
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#95778 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95780 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96995
  +product: App\Entity\Product\Product {#95775
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#95792 …}
    #variants: Doctrine\ORM\PersistentCollection {#95794 …}
    #options: Doctrine\ORM\PersistentCollection {#95798 …}
    #associations: Doctrine\ORM\PersistentCollection {#95796 …}
    #createdAt: DateTime @1751040752 {#95770
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95771
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95782 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96981
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95775}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95784 …}
    #channels: Doctrine\ORM\PersistentCollection {#95790 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95786 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95788 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95776 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#95773
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#95774
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#95778 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95780 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95775
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#95792 …}
    #variants: Doctrine\ORM\PersistentCollection {#95794 …}
    #options: Doctrine\ORM\PersistentCollection {#95798 …}
    #associations: Doctrine\ORM\PersistentCollection {#95796 …}
    #createdAt: DateTime @1751040752 {#95770
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95771
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95782 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96981
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95775}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95784 …}
    #channels: Doctrine\ORM\PersistentCollection {#95790 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95786 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95788 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95776 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#95773
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#95774
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#95778 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95780 …}
  }
]

App\Twig\Components\ProductMostRecent {#97069
  +product: App\Entity\Product\Product {#95775
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#95792 …}
    #variants: Doctrine\ORM\PersistentCollection {#95794 …}
    #options: Doctrine\ORM\PersistentCollection {#95798 …}
    #associations: Doctrine\ORM\PersistentCollection {#95796 …}
    #createdAt: DateTime @1751040752 {#95770
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95771
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95782 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96981
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95775}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95784 …}
    #channels: Doctrine\ORM\PersistentCollection {#95790 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95786 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95788 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95776 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#95773
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#95774
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#95778 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95780 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95805
    #id: 13104
    #code: "IEEE00011506"
    #attributes: Doctrine\ORM\PersistentCollection {#95822 …}
    #variants: Doctrine\ORM\PersistentCollection {#95824 …}
    #options: Doctrine\ORM\PersistentCollection {#95828 …}
    #associations: Doctrine\ORM\PersistentCollection {#95826 …}
    #createdAt: DateTime @1751040866 {#95800
      date: 2025-06-27 18:14:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95801
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95812 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97219
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95805}
        #id: 47425
        #name: "IEEE/ISO/IEC P24748-4"
        #slug: "ieee-iso-iec-p24748-4-ieee00011506-273047"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          ISO/IEC/IEEE 15288, Systems and software engineering -- System life cycle processes, provides a common process framework covering the life cycle of human-made systems, from the conception of ideas through to the retirement of a system. It provides the processes for acquiring and supplying systems. In addition, this framework provides for the assessment and improvement of the life cycle processes. This common framework improves communication and cooperation among the parties that create, utilize, and manage modern systems in order that they can work in an integrated, coherent fashion.<br />\n
          The acquisition or supply of a system is usually done within a project. A project prepares and implements the technical planning, resources and schedules necessary to guide the project toward accomplishment of its objectives and proper conclusion. The project’s authorization and objectives are documented in an information item identified as a Systems Engineering Management Plan (SEMP).<br />\n
          This document defines a SEMP as the key vehicle for representing a project&#039;s application of systems life cycle processes. In this document, the terms technical planning and systems engineering planning are used interchangeably to emphasize or differentiate technical contributions in the processes under discussion.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC/IEEE 24748 - specifies the processes from ISO/IEC/IEEE 15288 that implement systems engineering management for the life cycles of technical solutions, - describes a required information item, termed the Systems Engineering Management Plan (SEMP) for the technical management and execution of the systems engineering of technical solutions, - provides requirements and guidance for the content of the required information item.<br />\n
          ISO/IEC/IEEE 24748-4 provides unified and consolidated requirements and guidance on systems engineering management planning. Its purpose is to help ensure consistency in the planning and control related to system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation, and use in various domains. ISO/IEC/IEEE 24748-4 should help systems and software engineers to plan for and manage progress on a project.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Draft International Standard - Systems and Software Engineering -- Life Cycle Management -- Part 4: Systems Engineering Management Planning"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95814 …}
    #channels: Doctrine\ORM\PersistentCollection {#95820 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95816 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95818 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95806 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95802
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1742511600 {#95803
      date: 2025-03-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1719957600 {#95804
      date: 2024-07-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-4"
    -bookCollection: ""
    -pageCount: 62
    -documents: Doctrine\ORM\PersistentCollection {#95808 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95810 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#97199
  +product: App\Entity\Product\Product {#95805
    #id: 13104
    #code: "IEEE00011506"
    #attributes: Doctrine\ORM\PersistentCollection {#95822 …}
    #variants: Doctrine\ORM\PersistentCollection {#95824 …}
    #options: Doctrine\ORM\PersistentCollection {#95828 …}
    #associations: Doctrine\ORM\PersistentCollection {#95826 …}
    #createdAt: DateTime @1751040866 {#95800
      date: 2025-06-27 18:14:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95801
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95812 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97219
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95805}
        #id: 47425
        #name: "IEEE/ISO/IEC P24748-4"
        #slug: "ieee-iso-iec-p24748-4-ieee00011506-273047"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          ISO/IEC/IEEE 15288, Systems and software engineering -- System life cycle processes, provides a common process framework covering the life cycle of human-made systems, from the conception of ideas through to the retirement of a system. It provides the processes for acquiring and supplying systems. In addition, this framework provides for the assessment and improvement of the life cycle processes. This common framework improves communication and cooperation among the parties that create, utilize, and manage modern systems in order that they can work in an integrated, coherent fashion.<br />\n
          The acquisition or supply of a system is usually done within a project. A project prepares and implements the technical planning, resources and schedules necessary to guide the project toward accomplishment of its objectives and proper conclusion. The project’s authorization and objectives are documented in an information item identified as a Systems Engineering Management Plan (SEMP).<br />\n
          This document defines a SEMP as the key vehicle for representing a project&#039;s application of systems life cycle processes. In this document, the terms technical planning and systems engineering planning are used interchangeably to emphasize or differentiate technical contributions in the processes under discussion.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC/IEEE 24748 - specifies the processes from ISO/IEC/IEEE 15288 that implement systems engineering management for the life cycles of technical solutions, - describes a required information item, termed the Systems Engineering Management Plan (SEMP) for the technical management and execution of the systems engineering of technical solutions, - provides requirements and guidance for the content of the required information item.<br />\n
          ISO/IEC/IEEE 24748-4 provides unified and consolidated requirements and guidance on systems engineering management planning. Its purpose is to help ensure consistency in the planning and control related to system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation, and use in various domains. ISO/IEC/IEEE 24748-4 should help systems and software engineers to plan for and manage progress on a project.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Draft International Standard - Systems and Software Engineering -- Life Cycle Management -- Part 4: Systems Engineering Management Planning"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95814 …}
    #channels: Doctrine\ORM\PersistentCollection {#95820 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95816 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95818 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95806 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95802
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1742511600 {#95803
      date: 2025-03-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1719957600 {#95804
      date: 2024-07-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-4"
    -bookCollection: ""
    -pageCount: 62
    -documents: Doctrine\ORM\PersistentCollection {#95808 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95810 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95805
    #id: 13104
    #code: "IEEE00011506"
    #attributes: Doctrine\ORM\PersistentCollection {#95822 …}
    #variants: Doctrine\ORM\PersistentCollection {#95824 …}
    #options: Doctrine\ORM\PersistentCollection {#95828 …}
    #associations: Doctrine\ORM\PersistentCollection {#95826 …}
    #createdAt: DateTime @1751040866 {#95800
      date: 2025-06-27 18:14:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95801
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95812 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97219
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95805}
        #id: 47425
        #name: "IEEE/ISO/IEC P24748-4"
        #slug: "ieee-iso-iec-p24748-4-ieee00011506-273047"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          ISO/IEC/IEEE 15288, Systems and software engineering -- System life cycle processes, provides a common process framework covering the life cycle of human-made systems, from the conception of ideas through to the retirement of a system. It provides the processes for acquiring and supplying systems. In addition, this framework provides for the assessment and improvement of the life cycle processes. This common framework improves communication and cooperation among the parties that create, utilize, and manage modern systems in order that they can work in an integrated, coherent fashion.<br />\n
          The acquisition or supply of a system is usually done within a project. A project prepares and implements the technical planning, resources and schedules necessary to guide the project toward accomplishment of its objectives and proper conclusion. The project’s authorization and objectives are documented in an information item identified as a Systems Engineering Management Plan (SEMP).<br />\n
          This document defines a SEMP as the key vehicle for representing a project&#039;s application of systems life cycle processes. In this document, the terms technical planning and systems engineering planning are used interchangeably to emphasize or differentiate technical contributions in the processes under discussion.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC/IEEE 24748 - specifies the processes from ISO/IEC/IEEE 15288 that implement systems engineering management for the life cycles of technical solutions, - describes a required information item, termed the Systems Engineering Management Plan (SEMP) for the technical management and execution of the systems engineering of technical solutions, - provides requirements and guidance for the content of the required information item.<br />\n
          ISO/IEC/IEEE 24748-4 provides unified and consolidated requirements and guidance on systems engineering management planning. Its purpose is to help ensure consistency in the planning and control related to system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation, and use in various domains. ISO/IEC/IEEE 24748-4 should help systems and software engineers to plan for and manage progress on a project.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE Draft International Standard - Systems and Software Engineering -- Life Cycle Management -- Part 4: Systems Engineering Management Planning"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95814 …}
    #channels: Doctrine\ORM\PersistentCollection {#95820 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95816 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95818 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95466 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95806 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95802
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1742511600 {#95803
      date: 2025-03-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1719957600 {#95804
      date: 2024-07-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-4"
    -bookCollection: ""
    -pageCount: 62
    -documents: Doctrine\ORM\PersistentCollection {#95808 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95810 …}
  }
]