Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10074
    #code: "IEEE00003580"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038795 {#7274
      date: 2025-06-27 17:39:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 35305
        #name: "IEEE 1074:2006"
        #slug: "ieee-1074-2006-ieee00003580-241726"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010<br />\n
          \t\t\t\t<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.<br />\n
          This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.<br />\n
          The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.<br />\n
          This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing a Software Project Life Cycle Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154037600 {#7318
      date: 2006-07-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#92877
  +product: App\Entity\Product\Product {#7310
    #id: 10074
    #code: "IEEE00003580"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038795 {#7274
      date: 2025-06-27 17:39:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 35305
        #name: "IEEE 1074:2006"
        #slug: "ieee-1074-2006-ieee00003580-241726"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010<br />\n
          \t\t\t\t<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.<br />\n
          This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.<br />\n
          The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.<br />\n
          This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing a Software Project Life Cycle Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154037600 {#7318
      date: 2006-07-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10074
    #code: "IEEE00003580"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038795 {#7274
      date: 2025-06-27 17:39:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 35305
        #name: "IEEE 1074:2006"
        #slug: "ieee-1074-2006-ieee00003580-241726"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010<br />\n
          \t\t\t\t<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.<br />\n
          This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.<br />\n
          The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.<br />\n
          This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing a Software Project Life Cycle Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154037600 {#7318
      date: 2006-07-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductType {#93057
  +product: App\Entity\Product\Product {#7310
    #id: 10074
    #code: "IEEE00003580"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038795 {#7274
      date: 2025-06-27 17:39:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 35305
        #name: "IEEE 1074:2006"
        #slug: "ieee-1074-2006-ieee00003580-241726"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010<br />\n
          \t\t\t\t<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.<br />\n
          This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.<br />\n
          The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.<br />\n
          This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing a Software Project Life Cycle Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154037600 {#7318
      date: 2006-07-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10074
    #code: "IEEE00003580"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038795 {#7274
      date: 2025-06-27 17:39:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 35305
        #name: "IEEE 1074:2006"
        #slug: "ieee-1074-2006-ieee00003580-241726"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010<br />\n
          \t\t\t\t<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.<br />\n
          This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.<br />\n
          The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.<br />\n
          This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing a Software Project Life Cycle Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154037600 {#7318
      date: 2006-07-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#93132
  +product: App\Entity\Product\Product {#7310
    #id: 10074
    #code: "IEEE00003580"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038795 {#7274
      date: 2025-06-27 17:39:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 35305
        #name: "IEEE 1074:2006"
        #slug: "ieee-1074-2006-ieee00003580-241726"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010<br />\n
          \t\t\t\t<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.<br />\n
          This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.<br />\n
          The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.<br />\n
          This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing a Software Project Life Cycle Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154037600 {#7318
      date: 2006-07-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#100122
    #id: 9089
    #code: "IEEE00001606"
    #attributes: Doctrine\ORM\PersistentCollection {#100105 …}
    #variants: Doctrine\ORM\PersistentCollection {#100102 …}
    #options: Doctrine\ORM\PersistentCollection {#100098 …}
    #associations: Doctrine\ORM\PersistentCollection {#100100 …}
    #createdAt: DateTime @1751037962 {#100130
      date: 2025-06-27 17:26:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100103
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100116 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100140
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100122}
        #id: 31365
        #name: "IEEE 1074:1997"
        #slug: "ieee-1074-1997-ieee00001606-240741"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by IEEE Std 1074-2006 A process for creating a software life cycle process is provided. Although this standardis directed primarily at the process architect, it is useful to any organization that is responsible formanaging and performing software projects.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes for the development and maintenance of software, whether stand-alone or part of a system. (Non-software activities, such as hardware development and purchasing, are outside the scope of this standard). This standard also provides associated Input and Output information. The proposed revision will differ from the original as follows: (1) The word process will be downplayed, or order to better focus attention on the Activities. Collections of Activities will now be called Activity Groups. (2) All Planning Activities will now be collected into a single Activity Group called Project Planning Activities. (3) The Verification and Validation Process will be replaced by a new Activity Group entitled &quot;Evaluation Activities&quot;, which will include specific V&amp;V Activities such as reviews, audits, testing.<br />\n
          To better enable software organizations to develop and/or maintain software on time and within budget. It is envisioned that the primary user of the revised standard will be the Process Architect for a software project. This is the individual whose function is to select a Software Life Cycle Model (SLCM) for the project, create the project Software Life Cycle (SLC), and ensure that this SLC is properly followed throughout the lifetime of the project. The revised standard will benefit the Process Architect by clearly defining his or her role, and the steps necessary to fulfilll that role.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100113 …}
    #channels: Doctrine\ORM\PersistentCollection {#100107 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100111 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100109 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100123 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100090
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100129
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912553200 {#100128
      date: 1998-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 96
    -documents: Doctrine\ORM\PersistentCollection {#100120 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100118 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#100176
  +product: App\Entity\Product\Product {#100122
    #id: 9089
    #code: "IEEE00001606"
    #attributes: Doctrine\ORM\PersistentCollection {#100105 …}
    #variants: Doctrine\ORM\PersistentCollection {#100102 …}
    #options: Doctrine\ORM\PersistentCollection {#100098 …}
    #associations: Doctrine\ORM\PersistentCollection {#100100 …}
    #createdAt: DateTime @1751037962 {#100130
      date: 2025-06-27 17:26:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100103
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100116 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100140
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100122}
        #id: 31365
        #name: "IEEE 1074:1997"
        #slug: "ieee-1074-1997-ieee00001606-240741"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by IEEE Std 1074-2006 A process for creating a software life cycle process is provided. Although this standardis directed primarily at the process architect, it is useful to any organization that is responsible formanaging and performing software projects.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes for the development and maintenance of software, whether stand-alone or part of a system. (Non-software activities, such as hardware development and purchasing, are outside the scope of this standard). This standard also provides associated Input and Output information. The proposed revision will differ from the original as follows: (1) The word process will be downplayed, or order to better focus attention on the Activities. Collections of Activities will now be called Activity Groups. (2) All Planning Activities will now be collected into a single Activity Group called Project Planning Activities. (3) The Verification and Validation Process will be replaced by a new Activity Group entitled &quot;Evaluation Activities&quot;, which will include specific V&amp;V Activities such as reviews, audits, testing.<br />\n
          To better enable software organizations to develop and/or maintain software on time and within budget. It is envisioned that the primary user of the revised standard will be the Process Architect for a software project. This is the individual whose function is to select a Software Life Cycle Model (SLCM) for the project, create the project Software Life Cycle (SLC), and ensure that this SLC is properly followed throughout the lifetime of the project. The revised standard will benefit the Process Architect by clearly defining his or her role, and the steps necessary to fulfilll that role.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100113 …}
    #channels: Doctrine\ORM\PersistentCollection {#100107 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100111 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100109 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100123 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100090
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100129
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912553200 {#100128
      date: 1998-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 96
    -documents: Doctrine\ORM\PersistentCollection {#100120 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100118 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#100122
    #id: 9089
    #code: "IEEE00001606"
    #attributes: Doctrine\ORM\PersistentCollection {#100105 …}
    #variants: Doctrine\ORM\PersistentCollection {#100102 …}
    #options: Doctrine\ORM\PersistentCollection {#100098 …}
    #associations: Doctrine\ORM\PersistentCollection {#100100 …}
    #createdAt: DateTime @1751037962 {#100130
      date: 2025-06-27 17:26:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100103
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100116 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100140
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100122}
        #id: 31365
        #name: "IEEE 1074:1997"
        #slug: "ieee-1074-1997-ieee00001606-240741"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by IEEE Std 1074-2006 A process for creating a software life cycle process is provided. Although this standardis directed primarily at the process architect, it is useful to any organization that is responsible formanaging and performing software projects.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes for the development and maintenance of software, whether stand-alone or part of a system. (Non-software activities, such as hardware development and purchasing, are outside the scope of this standard). This standard also provides associated Input and Output information. The proposed revision will differ from the original as follows: (1) The word process will be downplayed, or order to better focus attention on the Activities. Collections of Activities will now be called Activity Groups. (2) All Planning Activities will now be collected into a single Activity Group called Project Planning Activities. (3) The Verification and Validation Process will be replaced by a new Activity Group entitled &quot;Evaluation Activities&quot;, which will include specific V&amp;V Activities such as reviews, audits, testing.<br />\n
          To better enable software organizations to develop and/or maintain software on time and within budget. It is envisioned that the primary user of the revised standard will be the Process Architect for a software project. This is the individual whose function is to select a Software Life Cycle Model (SLCM) for the project, create the project Software Life Cycle (SLC), and ensure that this SLC is properly followed throughout the lifetime of the project. The revised standard will benefit the Process Architect by clearly defining his or her role, and the steps necessary to fulfilll that role.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100113 …}
    #channels: Doctrine\ORM\PersistentCollection {#100107 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100111 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100109 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100123 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100090
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100129
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912553200 {#100128
      date: 1998-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 96
    -documents: Doctrine\ORM\PersistentCollection {#100120 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100118 …}
  }
]

App\Twig\Components\ProductMostRecent {#100243
  +product: App\Entity\Product\Product {#100122
    #id: 9089
    #code: "IEEE00001606"
    #attributes: Doctrine\ORM\PersistentCollection {#100105 …}
    #variants: Doctrine\ORM\PersistentCollection {#100102 …}
    #options: Doctrine\ORM\PersistentCollection {#100098 …}
    #associations: Doctrine\ORM\PersistentCollection {#100100 …}
    #createdAt: DateTime @1751037962 {#100130
      date: 2025-06-27 17:26:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100103
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100116 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100140
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100122}
        #id: 31365
        #name: "IEEE 1074:1997"
        #slug: "ieee-1074-1997-ieee00001606-240741"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by IEEE Std 1074-2006 A process for creating a software life cycle process is provided. Although this standardis directed primarily at the process architect, it is useful to any organization that is responsible formanaging and performing software projects.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes for the development and maintenance of software, whether stand-alone or part of a system. (Non-software activities, such as hardware development and purchasing, are outside the scope of this standard). This standard also provides associated Input and Output information. The proposed revision will differ from the original as follows: (1) The word process will be downplayed, or order to better focus attention on the Activities. Collections of Activities will now be called Activity Groups. (2) All Planning Activities will now be collected into a single Activity Group called Project Planning Activities. (3) The Verification and Validation Process will be replaced by a new Activity Group entitled &quot;Evaluation Activities&quot;, which will include specific V&amp;V Activities such as reviews, audits, testing.<br />\n
          To better enable software organizations to develop and/or maintain software on time and within budget. It is envisioned that the primary user of the revised standard will be the Process Architect for a software project. This is the individual whose function is to select a Software Life Cycle Model (SLCM) for the project, create the project Software Life Cycle (SLC), and ensure that this SLC is properly followed throughout the lifetime of the project. The revised standard will benefit the Process Architect by clearly defining his or her role, and the steps necessary to fulfilll that role.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100113 …}
    #channels: Doctrine\ORM\PersistentCollection {#100107 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100111 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100109 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100123 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100090
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100129
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912553200 {#100128
      date: 1998-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 96
    -documents: Doctrine\ORM\PersistentCollection {#100120 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100118 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10074
    #code: "IEEE00003580"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038795 {#7274
      date: 2025-06-27 17:39:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 35305
        #name: "IEEE 1074:2006"
        #slug: "ieee-1074-2006-ieee00003580-241726"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010<br />\n
          \t\t\t\t<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.<br />\n
          This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.<br />\n
          The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.<br />\n
          This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing a Software Project Life Cycle Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154037600 {#7318
      date: 2006-07-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106886
  +product: App\Entity\Product\Product {#7310
    #id: 10074
    #code: "IEEE00003580"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038795 {#7274
      date: 2025-06-27 17:39:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 35305
        #name: "IEEE 1074:2006"
        #slug: "ieee-1074-2006-ieee00003580-241726"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010<br />\n
          \t\t\t\t<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.<br />\n
          This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.<br />\n
          The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.<br />\n
          This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing a Software Project Life Cycle Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154037600 {#7318
      date: 2006-07-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10074
    #code: "IEEE00003580"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038795 {#7274
      date: 2025-06-27 17:39:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 35305
        #name: "IEEE 1074:2006"
        #slug: "ieee-1074-2006-ieee00003580-241726"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010<br />\n
          \t\t\t\t<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.<br />\n
          This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.<br />\n
          The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.<br />\n
          This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing a Software Project Life Cycle Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154037600 {#7318
      date: 2006-07-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#106928
  +product: App\Entity\Product\Product {#7310
    #id: 10074
    #code: "IEEE00003580"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038795 {#7274
      date: 2025-06-27 17:39:55.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 35305
        #name: "IEEE 1074:2006"
        #slug: "ieee-1074-2006-ieee00003580-241726"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. (Replaced by ISO/IEC TR 24774:2010<br />\n
          \t\t\t\t<br />\n
          This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.<br />\n
          This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.<br />\n
          The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.<br />\n
          This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing a Software Project Life Cycle Process"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154037600 {#7318
      date: 2006-07-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 110
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#100122
    #id: 9089
    #code: "IEEE00001606"
    #attributes: Doctrine\ORM\PersistentCollection {#100105 …}
    #variants: Doctrine\ORM\PersistentCollection {#100102 …}
    #options: Doctrine\ORM\PersistentCollection {#100098 …}
    #associations: Doctrine\ORM\PersistentCollection {#100100 …}
    #createdAt: DateTime @1751037962 {#100130
      date: 2025-06-27 17:26:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100103
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100116 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100140
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100122}
        #id: 31365
        #name: "IEEE 1074:1997"
        #slug: "ieee-1074-1997-ieee00001606-240741"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by IEEE Std 1074-2006 A process for creating a software life cycle process is provided. Although this standardis directed primarily at the process architect, it is useful to any organization that is responsible formanaging and performing software projects.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes for the development and maintenance of software, whether stand-alone or part of a system. (Non-software activities, such as hardware development and purchasing, are outside the scope of this standard). This standard also provides associated Input and Output information. The proposed revision will differ from the original as follows: (1) The word process will be downplayed, or order to better focus attention on the Activities. Collections of Activities will now be called Activity Groups. (2) All Planning Activities will now be collected into a single Activity Group called Project Planning Activities. (3) The Verification and Validation Process will be replaced by a new Activity Group entitled &quot;Evaluation Activities&quot;, which will include specific V&amp;V Activities such as reviews, audits, testing.<br />\n
          To better enable software organizations to develop and/or maintain software on time and within budget. It is envisioned that the primary user of the revised standard will be the Process Architect for a software project. This is the individual whose function is to select a Software Life Cycle Model (SLCM) for the project, create the project Software Life Cycle (SLC), and ensure that this SLC is properly followed throughout the lifetime of the project. The revised standard will benefit the Process Architect by clearly defining his or her role, and the steps necessary to fulfilll that role.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100113 …}
    #channels: Doctrine\ORM\PersistentCollection {#100107 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100111 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100109 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100123 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100090
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100129
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912553200 {#100128
      date: 1998-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 96
    -documents: Doctrine\ORM\PersistentCollection {#100120 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100118 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106993
  +product: App\Entity\Product\Product {#100122
    #id: 9089
    #code: "IEEE00001606"
    #attributes: Doctrine\ORM\PersistentCollection {#100105 …}
    #variants: Doctrine\ORM\PersistentCollection {#100102 …}
    #options: Doctrine\ORM\PersistentCollection {#100098 …}
    #associations: Doctrine\ORM\PersistentCollection {#100100 …}
    #createdAt: DateTime @1751037962 {#100130
      date: 2025-06-27 17:26:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100103
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100116 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100140
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100122}
        #id: 31365
        #name: "IEEE 1074:1997"
        #slug: "ieee-1074-1997-ieee00001606-240741"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by IEEE Std 1074-2006 A process for creating a software life cycle process is provided. Although this standardis directed primarily at the process architect, it is useful to any organization that is responsible formanaging and performing software projects.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes for the development and maintenance of software, whether stand-alone or part of a system. (Non-software activities, such as hardware development and purchasing, are outside the scope of this standard). This standard also provides associated Input and Output information. The proposed revision will differ from the original as follows: (1) The word process will be downplayed, or order to better focus attention on the Activities. Collections of Activities will now be called Activity Groups. (2) All Planning Activities will now be collected into a single Activity Group called Project Planning Activities. (3) The Verification and Validation Process will be replaced by a new Activity Group entitled &quot;Evaluation Activities&quot;, which will include specific V&amp;V Activities such as reviews, audits, testing.<br />\n
          To better enable software organizations to develop and/or maintain software on time and within budget. It is envisioned that the primary user of the revised standard will be the Process Architect for a software project. This is the individual whose function is to select a Software Life Cycle Model (SLCM) for the project, create the project Software Life Cycle (SLC), and ensure that this SLC is properly followed throughout the lifetime of the project. The revised standard will benefit the Process Architect by clearly defining his or her role, and the steps necessary to fulfilll that role.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100113 …}
    #channels: Doctrine\ORM\PersistentCollection {#100107 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100111 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100109 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100123 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100090
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100129
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912553200 {#100128
      date: 1998-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 96
    -documents: Doctrine\ORM\PersistentCollection {#100120 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100118 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#100122
    #id: 9089
    #code: "IEEE00001606"
    #attributes: Doctrine\ORM\PersistentCollection {#100105 …}
    #variants: Doctrine\ORM\PersistentCollection {#100102 …}
    #options: Doctrine\ORM\PersistentCollection {#100098 …}
    #associations: Doctrine\ORM\PersistentCollection {#100100 …}
    #createdAt: DateTime @1751037962 {#100130
      date: 2025-06-27 17:26:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100103
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100116 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100140
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100122}
        #id: 31365
        #name: "IEEE 1074:1997"
        #slug: "ieee-1074-1997-ieee00001606-240741"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by IEEE Std 1074-2006 A process for creating a software life cycle process is provided. Although this standardis directed primarily at the process architect, it is useful to any organization that is responsible formanaging and performing software projects.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes for the development and maintenance of software, whether stand-alone or part of a system. (Non-software activities, such as hardware development and purchasing, are outside the scope of this standard). This standard also provides associated Input and Output information. The proposed revision will differ from the original as follows: (1) The word process will be downplayed, or order to better focus attention on the Activities. Collections of Activities will now be called Activity Groups. (2) All Planning Activities will now be collected into a single Activity Group called Project Planning Activities. (3) The Verification and Validation Process will be replaced by a new Activity Group entitled &quot;Evaluation Activities&quot;, which will include specific V&amp;V Activities such as reviews, audits, testing.<br />\n
          To better enable software organizations to develop and/or maintain software on time and within budget. It is envisioned that the primary user of the revised standard will be the Process Architect for a software project. This is the individual whose function is to select a Software Life Cycle Model (SLCM) for the project, create the project Software Life Cycle (SLC), and ensure that this SLC is properly followed throughout the lifetime of the project. The revised standard will benefit the Process Architect by clearly defining his or her role, and the steps necessary to fulfilll that role.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100113 …}
    #channels: Doctrine\ORM\PersistentCollection {#100107 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100111 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100109 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100123 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100090
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100129
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912553200 {#100128
      date: 1998-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 96
    -documents: Doctrine\ORM\PersistentCollection {#100120 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100118 …}
  }
]

App\Twig\Components\ProductMostRecent {#107020
  +product: App\Entity\Product\Product {#100122
    #id: 9089
    #code: "IEEE00001606"
    #attributes: Doctrine\ORM\PersistentCollection {#100105 …}
    #variants: Doctrine\ORM\PersistentCollection {#100102 …}
    #options: Doctrine\ORM\PersistentCollection {#100098 …}
    #associations: Doctrine\ORM\PersistentCollection {#100100 …}
    #createdAt: DateTime @1751037962 {#100130
      date: 2025-06-27 17:26:02.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100103
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100116 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100140
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100122}
        #id: 31365
        #name: "IEEE 1074:1997"
        #slug: "ieee-1074-1997-ieee00001606-240741"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by IEEE Std 1074-2006 A process for creating a software life cycle process is provided. Although this standardis directed primarily at the process architect, it is useful to any organization that is responsible formanaging and performing software projects.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes for the development and maintenance of software, whether stand-alone or part of a system. (Non-software activities, such as hardware development and purchasing, are outside the scope of this standard). This standard also provides associated Input and Output information. The proposed revision will differ from the original as follows: (1) The word process will be downplayed, or order to better focus attention on the Activities. Collections of Activities will now be called Activity Groups. (2) All Planning Activities will now be collected into a single Activity Group called Project Planning Activities. (3) The Verification and Validation Process will be replaced by a new Activity Group entitled &quot;Evaluation Activities&quot;, which will include specific V&amp;V Activities such as reviews, audits, testing.<br />\n
          To better enable software organizations to develop and/or maintain software on time and within budget. It is envisioned that the primary user of the revised standard will be the Process Architect for a software project. This is the individual whose function is to select a Software Life Cycle Model (SLCM) for the project, create the project Software Life Cycle (SLC), and ensure that this SLC is properly followed throughout the lifetime of the project. The revised standard will benefit the Process Architect by clearly defining his or her role, and the steps necessary to fulfilll that role.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100113 …}
    #channels: Doctrine\ORM\PersistentCollection {#100107 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100111 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100109 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100123 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100090
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100129
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @912553200 {#100128
      date: 1998-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 96
    -documents: Doctrine\ORM\PersistentCollection {#100120 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100118 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106808
    #id: 9088
    #code: "IEEE00001605"
    #attributes: Doctrine\ORM\PersistentCollection {#106824 …}
    #variants: Doctrine\ORM\PersistentCollection {#106826 …}
    #options: Doctrine\ORM\PersistentCollection {#106830 …}
    #associations: Doctrine\ORM\PersistentCollection {#106828 …}
    #createdAt: DateTime @1751037961 {#106800
      date: 2025-06-27 17:26:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106797
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106814 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107086
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106808}
        #id: 31361
        #name: "IEEE 1074:1995"
        #slug: "ieee-1074-1995-ieee00001605-240740"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by 1074-1997. The set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system, is provided. Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard. Also provided is associated Input and Output Information.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system. (Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard.) This standard also provides associated Input and Output Information.<br />\n
          For convenience, Activities are listed and described under specific Processes. In practice, the Activities may be performed by persons whose organizational titles or job descriptions do not clearly convey that a Process is part of their job. The Process under which an Activity is listed in this standard may be transparent in practice.<br />\n
          This standard does not prescribe a specific software life cycle model (SLCM). Each using organization must map the activities specified in the standard into its own software life cycle (SLC). If an organization has not yet defined an SLC, it will be necessary for them to select or define one before attempting to follow this standard. Further, this standard does not presume the use of any specific software development methodology nor the creation of specific documents.<br />\n
          For software already developed, it is recommended that these requirements, or a subset there of, be applied. The existence of this standard should not be construed to prohibit the imposition of additional or more stringent requirements where the need exists, e.g., critical software.<br />\n
          Compliance with this standard is defined in 1.5.1 .
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106816 …}
    #channels: Doctrine\ORM\PersistentCollection {#106822 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106818 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106820 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106807 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106799
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106801
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @830469600 {#106802
      date: 1996-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 106
    -documents: Doctrine\ORM\PersistentCollection {#106810 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106812 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#107101
  +product: App\Entity\Product\Product {#106808
    #id: 9088
    #code: "IEEE00001605"
    #attributes: Doctrine\ORM\PersistentCollection {#106824 …}
    #variants: Doctrine\ORM\PersistentCollection {#106826 …}
    #options: Doctrine\ORM\PersistentCollection {#106830 …}
    #associations: Doctrine\ORM\PersistentCollection {#106828 …}
    #createdAt: DateTime @1751037961 {#106800
      date: 2025-06-27 17:26:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106797
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106814 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107086
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106808}
        #id: 31361
        #name: "IEEE 1074:1995"
        #slug: "ieee-1074-1995-ieee00001605-240740"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by 1074-1997. The set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system, is provided. Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard. Also provided is associated Input and Output Information.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system. (Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard.) This standard also provides associated Input and Output Information.<br />\n
          For convenience, Activities are listed and described under specific Processes. In practice, the Activities may be performed by persons whose organizational titles or job descriptions do not clearly convey that a Process is part of their job. The Process under which an Activity is listed in this standard may be transparent in practice.<br />\n
          This standard does not prescribe a specific software life cycle model (SLCM). Each using organization must map the activities specified in the standard into its own software life cycle (SLC). If an organization has not yet defined an SLC, it will be necessary for them to select or define one before attempting to follow this standard. Further, this standard does not presume the use of any specific software development methodology nor the creation of specific documents.<br />\n
          For software already developed, it is recommended that these requirements, or a subset there of, be applied. The existence of this standard should not be construed to prohibit the imposition of additional or more stringent requirements where the need exists, e.g., critical software.<br />\n
          Compliance with this standard is defined in 1.5.1 .
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106816 …}
    #channels: Doctrine\ORM\PersistentCollection {#106822 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106818 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106820 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106807 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106799
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106801
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @830469600 {#106802
      date: 1996-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 106
    -documents: Doctrine\ORM\PersistentCollection {#106810 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106812 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106808
    #id: 9088
    #code: "IEEE00001605"
    #attributes: Doctrine\ORM\PersistentCollection {#106824 …}
    #variants: Doctrine\ORM\PersistentCollection {#106826 …}
    #options: Doctrine\ORM\PersistentCollection {#106830 …}
    #associations: Doctrine\ORM\PersistentCollection {#106828 …}
    #createdAt: DateTime @1751037961 {#106800
      date: 2025-06-27 17:26:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106797
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106814 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107086
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106808}
        #id: 31361
        #name: "IEEE 1074:1995"
        #slug: "ieee-1074-1995-ieee00001605-240740"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by 1074-1997. The set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system, is provided. Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard. Also provided is associated Input and Output Information.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system. (Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard.) This standard also provides associated Input and Output Information.<br />\n
          For convenience, Activities are listed and described under specific Processes. In practice, the Activities may be performed by persons whose organizational titles or job descriptions do not clearly convey that a Process is part of their job. The Process under which an Activity is listed in this standard may be transparent in practice.<br />\n
          This standard does not prescribe a specific software life cycle model (SLCM). Each using organization must map the activities specified in the standard into its own software life cycle (SLC). If an organization has not yet defined an SLC, it will be necessary for them to select or define one before attempting to follow this standard. Further, this standard does not presume the use of any specific software development methodology nor the creation of specific documents.<br />\n
          For software already developed, it is recommended that these requirements, or a subset there of, be applied. The existence of this standard should not be construed to prohibit the imposition of additional or more stringent requirements where the need exists, e.g., critical software.<br />\n
          Compliance with this standard is defined in 1.5.1 .
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106816 …}
    #channels: Doctrine\ORM\PersistentCollection {#106822 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106818 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106820 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106807 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106799
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106801
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @830469600 {#106802
      date: 1996-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 106
    -documents: Doctrine\ORM\PersistentCollection {#106810 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106812 …}
  }
]

App\Twig\Components\ProductMostRecent {#107153
  +product: App\Entity\Product\Product {#106808
    #id: 9088
    #code: "IEEE00001605"
    #attributes: Doctrine\ORM\PersistentCollection {#106824 …}
    #variants: Doctrine\ORM\PersistentCollection {#106826 …}
    #options: Doctrine\ORM\PersistentCollection {#106830 …}
    #associations: Doctrine\ORM\PersistentCollection {#106828 …}
    #createdAt: DateTime @1751037961 {#106800
      date: 2025-06-27 17:26:01.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106797
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106814 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107086
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106808}
        #id: 31361
        #name: "IEEE 1074:1995"
        #slug: "ieee-1074-1995-ieee00001605-240740"
        #description: """
          Revision Standard - Superseded.<br />\n
          Superseded by 1074-1997. The set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system, is provided. Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard. Also provided is associated Input and Output Information.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system. (Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard.) This standard also provides associated Input and Output Information.<br />\n
          For convenience, Activities are listed and described under specific Processes. In practice, the Activities may be performed by persons whose organizational titles or job descriptions do not clearly convey that a Process is part of their job. The Process under which an Activity is listed in this standard may be transparent in practice.<br />\n
          This standard does not prescribe a specific software life cycle model (SLCM). Each using organization must map the activities specified in the standard into its own software life cycle (SLC). If an organization has not yet defined an SLC, it will be necessary for them to select or define one before attempting to follow this standard. Further, this standard does not presume the use of any specific software development methodology nor the creation of specific documents.<br />\n
          For software already developed, it is recommended that these requirements, or a subset there of, be applied. The existence of this standard should not be construed to prohibit the imposition of additional or more stringent requirements where the need exists, e.g., critical software.<br />\n
          Compliance with this standard is defined in 1.5.1 .
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106816 …}
    #channels: Doctrine\ORM\PersistentCollection {#106822 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106818 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106820 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106807 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106799
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106801
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @830469600 {#106802
      date: 1996-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 106
    -documents: Doctrine\ORM\PersistentCollection {#106810 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106812 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106837
    #id: 9087
    #code: "IEEE00001604"
    #attributes: Doctrine\ORM\PersistentCollection {#106854 …}
    #variants: Doctrine\ORM\PersistentCollection {#106856 …}
    #options: Doctrine\ORM\PersistentCollection {#106860 …}
    #associations: Doctrine\ORM\PersistentCollection {#106858 …}
    #createdAt: DateTime @1751037960 {#106832
      date: 2025-06-27 17:26:00.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106833
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106844 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107219
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106837}
        #id: 31357
        #name: "IEEE 1074:1991"
        #slug: "ieee-1074-1991-ieee00001604-240739"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The set of activities that constitute the processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system, is set forth. The management and support processes that continue throughout the entire life cycle, as well as all aspects of the software life cycle from concept exploration through retirement, are covered. Associated input and output information is also provided. Utilization of the processes and their component activities maximizes the benefits to the user when the use of this standard is initiated early in the software life cycle. This standard requires definition of a user’s software life cycle and shows its mapping into typical software life cycles; it is not intended to define or imply a software life cycle of its own.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system. (Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard.) This standard also provides associated Input and Output Information.<br />\n
          For convenience, Activities are listed and described under specific Processes. In practice, the Activities may be performed by persons whose organizational titles or job descriptions do not clearly convey that a Process is part of their job. The Process under which an Activity is listed in this standard may be transparent in practice.<br />\n
          This standard does not prescribe a specific software life cycle model (SLCM). Each using organization must map the activities specified in the standard into its own software life cycle (SLC). If an organization has not yet defined an SLC, it will be necessary for them to select or define one before attempting to follow this standard. Further, this standard does not presume the use of any specific software development methodology nor the creation of specific documents.<br />\n
          For software already developed, it is recommended that these requirements, or a subset thereof, be applied. The existence of this standard should not be construed to prohibit the imposition of additional or more stringent requirements where the need exists, e.g., critical software. Compliance with this standard is defined in 1.5.1.<br />\n
          This is a standard for the Processes of software development and maintenance. This standard requires definition of a user's software life cycle and shows mapping into typical software life cycles, but it is not intended to define or imply a software life cycle of its own. This standard applies to the management and support Processes that continue throughout the entire life cycle, as well as all aspects of the software life cycle from concept exploration through retirement. Utilization of these Processes, and their component Activities, maximizes the benefits to the user when the use of this standard is initiated early in the software life cycle.<br />\n
          Software that has proceeded past the initialization phase when this standard is invoked should gradually comply with the standard.<br />\n
          This standard was written for any organization responsible for managing and developing software. It will be useful to project managers, software developers, quality assurance organizations, purchasers, users, and maintainers. Since it was written to consider both software and its operating environment, it can be used where software is the total system or where software is embedded in a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106846 …}
    #channels: Doctrine\ORM\PersistentCollection {#106852 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106848 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106850 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106838 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106834
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106835
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @696639600 {#106836
      date: 1992-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 112
    -documents: Doctrine\ORM\PersistentCollection {#106840 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106842 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#107234
  +product: App\Entity\Product\Product {#106837
    #id: 9087
    #code: "IEEE00001604"
    #attributes: Doctrine\ORM\PersistentCollection {#106854 …}
    #variants: Doctrine\ORM\PersistentCollection {#106856 …}
    #options: Doctrine\ORM\PersistentCollection {#106860 …}
    #associations: Doctrine\ORM\PersistentCollection {#106858 …}
    #createdAt: DateTime @1751037960 {#106832
      date: 2025-06-27 17:26:00.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106833
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106844 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107219
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106837}
        #id: 31357
        #name: "IEEE 1074:1991"
        #slug: "ieee-1074-1991-ieee00001604-240739"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The set of activities that constitute the processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system, is set forth. The management and support processes that continue throughout the entire life cycle, as well as all aspects of the software life cycle from concept exploration through retirement, are covered. Associated input and output information is also provided. Utilization of the processes and their component activities maximizes the benefits to the user when the use of this standard is initiated early in the software life cycle. This standard requires definition of a user’s software life cycle and shows its mapping into typical software life cycles; it is not intended to define or imply a software life cycle of its own.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system. (Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard.) This standard also provides associated Input and Output Information.<br />\n
          For convenience, Activities are listed and described under specific Processes. In practice, the Activities may be performed by persons whose organizational titles or job descriptions do not clearly convey that a Process is part of their job. The Process under which an Activity is listed in this standard may be transparent in practice.<br />\n
          This standard does not prescribe a specific software life cycle model (SLCM). Each using organization must map the activities specified in the standard into its own software life cycle (SLC). If an organization has not yet defined an SLC, it will be necessary for them to select or define one before attempting to follow this standard. Further, this standard does not presume the use of any specific software development methodology nor the creation of specific documents.<br />\n
          For software already developed, it is recommended that these requirements, or a subset thereof, be applied. The existence of this standard should not be construed to prohibit the imposition of additional or more stringent requirements where the need exists, e.g., critical software. Compliance with this standard is defined in 1.5.1.<br />\n
          This is a standard for the Processes of software development and maintenance. This standard requires definition of a user's software life cycle and shows mapping into typical software life cycles, but it is not intended to define or imply a software life cycle of its own. This standard applies to the management and support Processes that continue throughout the entire life cycle, as well as all aspects of the software life cycle from concept exploration through retirement. Utilization of these Processes, and their component Activities, maximizes the benefits to the user when the use of this standard is initiated early in the software life cycle.<br />\n
          Software that has proceeded past the initialization phase when this standard is invoked should gradually comply with the standard.<br />\n
          This standard was written for any organization responsible for managing and developing software. It will be useful to project managers, software developers, quality assurance organizations, purchasers, users, and maintainers. Since it was written to consider both software and its operating environment, it can be used where software is the total system or where software is embedded in a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106846 …}
    #channels: Doctrine\ORM\PersistentCollection {#106852 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106848 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106850 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106838 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106834
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106835
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @696639600 {#106836
      date: 1992-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 112
    -documents: Doctrine\ORM\PersistentCollection {#106840 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106842 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106837
    #id: 9087
    #code: "IEEE00001604"
    #attributes: Doctrine\ORM\PersistentCollection {#106854 …}
    #variants: Doctrine\ORM\PersistentCollection {#106856 …}
    #options: Doctrine\ORM\PersistentCollection {#106860 …}
    #associations: Doctrine\ORM\PersistentCollection {#106858 …}
    #createdAt: DateTime @1751037960 {#106832
      date: 2025-06-27 17:26:00.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106833
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106844 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107219
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106837}
        #id: 31357
        #name: "IEEE 1074:1991"
        #slug: "ieee-1074-1991-ieee00001604-240739"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The set of activities that constitute the processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system, is set forth. The management and support processes that continue throughout the entire life cycle, as well as all aspects of the software life cycle from concept exploration through retirement, are covered. Associated input and output information is also provided. Utilization of the processes and their component activities maximizes the benefits to the user when the use of this standard is initiated early in the software life cycle. This standard requires definition of a user’s software life cycle and shows its mapping into typical software life cycles; it is not intended to define or imply a software life cycle of its own.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system. (Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard.) This standard also provides associated Input and Output Information.<br />\n
          For convenience, Activities are listed and described under specific Processes. In practice, the Activities may be performed by persons whose organizational titles or job descriptions do not clearly convey that a Process is part of their job. The Process under which an Activity is listed in this standard may be transparent in practice.<br />\n
          This standard does not prescribe a specific software life cycle model (SLCM). Each using organization must map the activities specified in the standard into its own software life cycle (SLC). If an organization has not yet defined an SLC, it will be necessary for them to select or define one before attempting to follow this standard. Further, this standard does not presume the use of any specific software development methodology nor the creation of specific documents.<br />\n
          For software already developed, it is recommended that these requirements, or a subset thereof, be applied. The existence of this standard should not be construed to prohibit the imposition of additional or more stringent requirements where the need exists, e.g., critical software. Compliance with this standard is defined in 1.5.1.<br />\n
          This is a standard for the Processes of software development and maintenance. This standard requires definition of a user's software life cycle and shows mapping into typical software life cycles, but it is not intended to define or imply a software life cycle of its own. This standard applies to the management and support Processes that continue throughout the entire life cycle, as well as all aspects of the software life cycle from concept exploration through retirement. Utilization of these Processes, and their component Activities, maximizes the benefits to the user when the use of this standard is initiated early in the software life cycle.<br />\n
          Software that has proceeded past the initialization phase when this standard is invoked should gradually comply with the standard.<br />\n
          This standard was written for any organization responsible for managing and developing software. It will be useful to project managers, software developers, quality assurance organizations, purchasers, users, and maintainers. Since it was written to consider both software and its operating environment, it can be used where software is the total system or where software is embedded in a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106846 …}
    #channels: Doctrine\ORM\PersistentCollection {#106852 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106848 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106850 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106838 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106834
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106835
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @696639600 {#106836
      date: 1992-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 112
    -documents: Doctrine\ORM\PersistentCollection {#106840 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106842 …}
  }
]

App\Twig\Components\ProductMostRecent {#107286
  +product: App\Entity\Product\Product {#106837
    #id: 9087
    #code: "IEEE00001604"
    #attributes: Doctrine\ORM\PersistentCollection {#106854 …}
    #variants: Doctrine\ORM\PersistentCollection {#106856 …}
    #options: Doctrine\ORM\PersistentCollection {#106860 …}
    #associations: Doctrine\ORM\PersistentCollection {#106858 …}
    #createdAt: DateTime @1751037960 {#106832
      date: 2025-06-27 17:26:00.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#106833
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106844 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107219
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106837}
        #id: 31357
        #name: "IEEE 1074:1991"
        #slug: "ieee-1074-1991-ieee00001604-240739"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The set of activities that constitute the processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system, is set forth. The management and support processes that continue throughout the entire life cycle, as well as all aspects of the software life cycle from concept exploration through retirement, are covered. Associated input and output information is also provided. Utilization of the processes and their component activities maximizes the benefits to the user when the use of this standard is initiated early in the software life cycle. This standard requires definition of a user’s software life cycle and shows its mapping into typical software life cycles; it is not intended to define or imply a software life cycle of its own.<br />\n
          \t\t\t\t<br />\n
          This standard provides the set of Activities that constitute the Processes that are mandatory for the development and maintenance of software, whether stand-alone or part of a system. (Non-software Activities, such as hardware development and purchasing, are outside of the scope of this standard.) This standard also provides associated Input and Output Information.<br />\n
          For convenience, Activities are listed and described under specific Processes. In practice, the Activities may be performed by persons whose organizational titles or job descriptions do not clearly convey that a Process is part of their job. The Process under which an Activity is listed in this standard may be transparent in practice.<br />\n
          This standard does not prescribe a specific software life cycle model (SLCM). Each using organization must map the activities specified in the standard into its own software life cycle (SLC). If an organization has not yet defined an SLC, it will be necessary for them to select or define one before attempting to follow this standard. Further, this standard does not presume the use of any specific software development methodology nor the creation of specific documents.<br />\n
          For software already developed, it is recommended that these requirements, or a subset thereof, be applied. The existence of this standard should not be construed to prohibit the imposition of additional or more stringent requirements where the need exists, e.g., critical software. Compliance with this standard is defined in 1.5.1.<br />\n
          This is a standard for the Processes of software development and maintenance. This standard requires definition of a user's software life cycle and shows mapping into typical software life cycles, but it is not intended to define or imply a software life cycle of its own. This standard applies to the management and support Processes that continue throughout the entire life cycle, as well as all aspects of the software life cycle from concept exploration through retirement. Utilization of these Processes, and their component Activities, maximizes the benefits to the user when the use of this standard is initiated early in the software life cycle.<br />\n
          Software that has proceeded past the initialization phase when this standard is invoked should gradually comply with the standard.<br />\n
          This standard was written for any organization responsible for managing and developing software. It will be useful to project managers, software developers, quality assurance organizations, purchasers, users, and maintainers. Since it was written to consider both software and its operating environment, it can be used where software is the total system or where software is embedded in a larger system.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Developing Software Life Cycle Processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106846 …}
    #channels: Doctrine\ORM\PersistentCollection {#106852 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106848 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106850 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106838 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106834
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106835
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @696639600 {#106836
      date: 1992-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1074"
    -bookCollection: ""
    -pageCount: 112
    -documents: Doctrine\ORM\PersistentCollection {#106840 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106842 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}