Components
4
Twig Components
15
Render Count
18
ms
Render Time
102.0
MiB
Memory Usage
Components
| Name | Metadata | Render Count | Render Time |
|---|---|---|---|
| ProductState |
"App\Twig\Components\ProductState"components/ProductState.html.twig |
6 | 1.30ms |
| ProductMostRecent |
"App\Twig\Components\ProductMostRecent"components/ProductMostRecent.html.twig |
6 | 4.06ms |
| ProductCard |
"App\Twig\Components\ProductCard"components/ProductCard.html.twig |
2 | 13.99ms |
| ProductType |
"App\Twig\Components\ProductType"components/ProductType.html.twig |
1 | 0.22ms |
Render calls
| ProductState | App\Twig\Components\ProductState | 76.0 MiB | 0.31 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#7310 #id: 10824 #code: "IEEE00005065" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039305 {#7274 : 2025-06-27 17:48:25.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#7322 : 2025-08-08 01:09:50.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: 38305 #name: "IEEE 24748-1:2011" #slug: "ieee-24748-1-2011-ieee00005065-242476" #description: """ New IEEE Standard - Superseded.<br />\n This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties.<br />\n ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.<br />\n \t\t\t\t<br />\n This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:<br />\n - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains;<br />\n - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services; defines the concept and terminology of a life cycle;<br />\n - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;<br />\n - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;<br />\n - describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects);<br />\n - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;<br />\n - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management;<br />\n - complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.<br />\n NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management" -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 @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1307052000 {#7318 : 2011-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 96 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } "showFullLabel" => "true" ] |
|||
| Attributes | [ "showFullLabel" => "true" ] |
|||
| Component | App\Twig\Components\ProductState {#93007 +product: App\Entity\Product\Product {#7310 #id: 10824 #code: "IEEE00005065" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039305 {#7274 : 2025-06-27 17:48:25.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#7322 : 2025-08-08 01:09:50.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: 38305 #name: "IEEE 24748-1:2011" #slug: "ieee-24748-1-2011-ieee00005065-242476" #description: """ New IEEE Standard - Superseded.<br />\n This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties.<br />\n ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.<br />\n \t\t\t\t<br />\n This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:<br />\n - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains;<br />\n - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services; defines the concept and terminology of a life cycle;<br />\n - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;<br />\n - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;<br />\n - describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects);<br />\n - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;<br />\n - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management;<br />\n - complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.<br />\n NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management" -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 @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1307052000 {#7318 : 2011-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 96 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductType | App\Twig\Components\ProductType | 76.0 MiB | 0.22 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#7310 #id: 10824 #code: "IEEE00005065" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039305 {#7274 : 2025-06-27 17:48:25.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#7322 : 2025-08-08 01:09:50.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: 38305 #name: "IEEE 24748-1:2011" #slug: "ieee-24748-1-2011-ieee00005065-242476" #description: """ New IEEE Standard - Superseded.<br />\n This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties.<br />\n ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.<br />\n \t\t\t\t<br />\n This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:<br />\n - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains;<br />\n - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services; defines the concept and terminology of a life cycle;<br />\n - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;<br />\n - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;<br />\n - describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects);<br />\n - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;<br />\n - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management;<br />\n - complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.<br />\n NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management" -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 @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1307052000 {#7318 : 2011-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 96 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductType {#93187 +product: App\Entity\Product\Product {#7310 #id: 10824 #code: "IEEE00005065" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039305 {#7274 : 2025-06-27 17:48:25.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#7322 : 2025-08-08 01:09:50.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: 38305 #name: "IEEE 24748-1:2011" #slug: "ieee-24748-1-2011-ieee00005065-242476" #description: """ New IEEE Standard - Superseded.<br />\n This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties.<br />\n ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.<br />\n \t\t\t\t<br />\n This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:<br />\n - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains;<br />\n - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services; defines the concept and terminology of a life cycle;<br />\n - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;<br />\n - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;<br />\n - describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects);<br />\n - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;<br />\n - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management;<br />\n - complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.<br />\n NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management" -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 @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1307052000 {#7318 : 2011-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 96 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +label: "Standard" -typeAttributeCode: "type" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 76.0 MiB | 0.66 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#7310 #id: 10824 #code: "IEEE00005065" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039305 {#7274 : 2025-06-27 17:48:25.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#7322 : 2025-08-08 01:09:50.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: 38305 #name: "IEEE 24748-1:2011" #slug: "ieee-24748-1-2011-ieee00005065-242476" #description: """ New IEEE Standard - Superseded.<br />\n This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties.<br />\n ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.<br />\n \t\t\t\t<br />\n This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:<br />\n - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains;<br />\n - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services; defines the concept and terminology of a life cycle;<br />\n - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;<br />\n - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;<br />\n - describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects);<br />\n - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;<br />\n - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management;<br />\n - complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.<br />\n NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management" -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 @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1307052000 {#7318 : 2011-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 96 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#93262 +product: App\Entity\Product\Product {#7310 #id: 10824 #code: "IEEE00005065" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039305 {#7274 : 2025-06-27 17:48:25.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#7322 : 2025-08-08 01:09:50.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: 38305 #name: "IEEE 24748-1:2011" #slug: "ieee-24748-1-2011-ieee00005065-242476" #description: """ New IEEE Standard - Superseded.<br />\n This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties.<br />\n ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.<br />\n \t\t\t\t<br />\n This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:<br />\n - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains;<br />\n - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services; defines the concept and terminology of a life cycle;<br />\n - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;<br />\n - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;<br />\n - describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects);<br />\n - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;<br />\n - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management;<br />\n - complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.<br />\n NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management" -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 @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1307052000 {#7318 : 2011-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 96 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductState | App\Twig\Components\ProductState | 80.0 MiB | 0.19 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#93685 #id: 12911 #code: "IEEE00010942" #attributes: Doctrine\ORM\PersistentCollection {#93667 …} #variants: Doctrine\ORM\PersistentCollection {#93664 …} #options: Doctrine\ORM\PersistentCollection {#93660 …} #associations: Doctrine\ORM\PersistentCollection {#93662 …} #createdAt: DateTime @1751040739 {#93693 : 2025-06-27 18:12:19.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#93672 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93678 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93713 #locale: "en_US" #translatable: App\Entity\Product\Product {#93685} #id: 46653 #name: "IEEE/ISO/IEC 24748-1:2024" #slug: "ieee-iso-iec-24748-1-2024-ieee00010942-244569" #description: """ Revision Standard - Active.<br />\n <br />\n \t\t\t\t<br />\n This document provides guidance for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document:--addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines;--establishes a common framework for describing life cycles, including their individual stages, for the management of projects that provide or acquire either products or services;--defines the concept of a life cycle;--supports the use of the life cycle processes within an organization or a project; organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;--provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;--describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software systems aspects);--shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;--describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management, risk management and model-based systems and software engineering.<br />\n The purpose of this document is to facilitate the joint usage of the process content of the latest revisions of both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, by providing unified and consolidated guidance on life cycle management of systems and software. This is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains as the two International Standards are used in combination. That will in turn help a project team design a life cycle model for managing the progress of their project. Hence, ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 are the documents that apply the concepts found in this document to specific processes. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Life cycle management--Part 1: Guidelines for life cycle management" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93676 …} #channels: Doctrine\ORM\PersistentCollection {#93669 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93674 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93671 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93686 …} -apiLastModifiedAt: DateTime @1754517600 {#93656 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1745272800 {#93692 : 2025-04-22 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1711062000 {#93691 : 2024-03-22 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 90 -documents: Doctrine\ORM\PersistentCollection {#93682 …} -favorites: Doctrine\ORM\PersistentCollection {#93680 …} } "showFullLabel" => "true" ] |
|||
| Attributes | [ "showFullLabel" => "true" ] |
|||
| Component | App\Twig\Components\ProductState {#106878 +product: App\Entity\Product\Product {#93685 #id: 12911 #code: "IEEE00010942" #attributes: Doctrine\ORM\PersistentCollection {#93667 …} #variants: Doctrine\ORM\PersistentCollection {#93664 …} #options: Doctrine\ORM\PersistentCollection {#93660 …} #associations: Doctrine\ORM\PersistentCollection {#93662 …} #createdAt: DateTime @1751040739 {#93693 : 2025-06-27 18:12:19.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#93672 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93678 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93713 #locale: "en_US" #translatable: App\Entity\Product\Product {#93685} #id: 46653 #name: "IEEE/ISO/IEC 24748-1:2024" #slug: "ieee-iso-iec-24748-1-2024-ieee00010942-244569" #description: """ Revision Standard - Active.<br />\n <br />\n \t\t\t\t<br />\n This document provides guidance for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document:--addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines;--establishes a common framework for describing life cycles, including their individual stages, for the management of projects that provide or acquire either products or services;--defines the concept of a life cycle;--supports the use of the life cycle processes within an organization or a project; organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;--provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;--describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software systems aspects);--shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;--describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management, risk management and model-based systems and software engineering.<br />\n The purpose of this document is to facilitate the joint usage of the process content of the latest revisions of both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, by providing unified and consolidated guidance on life cycle management of systems and software. This is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains as the two International Standards are used in combination. That will in turn help a project team design a life cycle model for managing the progress of their project. Hence, ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 are the documents that apply the concepts found in this document to specific processes. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Life cycle management--Part 1: Guidelines for life cycle management" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93676 …} #channels: Doctrine\ORM\PersistentCollection {#93669 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93674 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93671 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93686 …} -apiLastModifiedAt: DateTime @1754517600 {#93656 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1745272800 {#93692 : 2025-04-22 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1711062000 {#93691 : 2024-03-22 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 90 -documents: Doctrine\ORM\PersistentCollection {#93682 …} -favorites: Doctrine\ORM\PersistentCollection {#93680 …} } +appearance: "state-active" +labels: [ "Active" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 80.0 MiB | 0.78 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#93685 #id: 12911 #code: "IEEE00010942" #attributes: Doctrine\ORM\PersistentCollection {#93667 …} #variants: Doctrine\ORM\PersistentCollection {#93664 …} #options: Doctrine\ORM\PersistentCollection {#93660 …} #associations: Doctrine\ORM\PersistentCollection {#93662 …} #createdAt: DateTime @1751040739 {#93693 : 2025-06-27 18:12:19.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#93672 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93678 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93713 #locale: "en_US" #translatable: App\Entity\Product\Product {#93685} #id: 46653 #name: "IEEE/ISO/IEC 24748-1:2024" #slug: "ieee-iso-iec-24748-1-2024-ieee00010942-244569" #description: """ Revision Standard - Active.<br />\n <br />\n \t\t\t\t<br />\n This document provides guidance for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document:--addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines;--establishes a common framework for describing life cycles, including their individual stages, for the management of projects that provide or acquire either products or services;--defines the concept of a life cycle;--supports the use of the life cycle processes within an organization or a project; organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;--provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;--describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software systems aspects);--shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;--describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management, risk management and model-based systems and software engineering.<br />\n The purpose of this document is to facilitate the joint usage of the process content of the latest revisions of both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, by providing unified and consolidated guidance on life cycle management of systems and software. This is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains as the two International Standards are used in combination. That will in turn help a project team design a life cycle model for managing the progress of their project. Hence, ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 are the documents that apply the concepts found in this document to specific processes. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Life cycle management--Part 1: Guidelines for life cycle management" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93676 …} #channels: Doctrine\ORM\PersistentCollection {#93669 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93674 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93671 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93686 …} -apiLastModifiedAt: DateTime @1754517600 {#93656 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1745272800 {#93692 : 2025-04-22 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1711062000 {#93691 : 2024-03-22 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 90 -documents: Doctrine\ORM\PersistentCollection {#93682 …} -favorites: Doctrine\ORM\PersistentCollection {#93680 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#106945 +product: App\Entity\Product\Product {#93685 #id: 12911 #code: "IEEE00010942" #attributes: Doctrine\ORM\PersistentCollection {#93667 …} #variants: Doctrine\ORM\PersistentCollection {#93664 …} #options: Doctrine\ORM\PersistentCollection {#93660 …} #associations: Doctrine\ORM\PersistentCollection {#93662 …} #createdAt: DateTime @1751040739 {#93693 : 2025-06-27 18:12:19.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#93672 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93678 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93713 #locale: "en_US" #translatable: App\Entity\Product\Product {#93685} #id: 46653 #name: "IEEE/ISO/IEC 24748-1:2024" #slug: "ieee-iso-iec-24748-1-2024-ieee00010942-244569" #description: """ Revision Standard - Active.<br />\n <br />\n \t\t\t\t<br />\n This document provides guidance for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document:--addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines;--establishes a common framework for describing life cycles, including their individual stages, for the management of projects that provide or acquire either products or services;--defines the concept of a life cycle;--supports the use of the life cycle processes within an organization or a project; organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;--provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;--describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software systems aspects);--shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;--describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management, risk management and model-based systems and software engineering.<br />\n The purpose of this document is to facilitate the joint usage of the process content of the latest revisions of both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, by providing unified and consolidated guidance on life cycle management of systems and software. This is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains as the two International Standards are used in combination. That will in turn help a project team design a life cycle model for managing the progress of their project. Hence, ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 are the documents that apply the concepts found in this document to specific processes. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Life cycle management--Part 1: Guidelines for life cycle management" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93676 …} #channels: Doctrine\ORM\PersistentCollection {#93669 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93674 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93671 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93686 …} -apiLastModifiedAt: DateTime @1754517600 {#93656 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1745272800 {#93692 : 2025-04-22 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1711062000 {#93691 : 2024-03-22 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 90 -documents: Doctrine\ORM\PersistentCollection {#93682 …} -favorites: Doctrine\ORM\PersistentCollection {#93680 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductState | App\Twig\Components\ProductState | 80.0 MiB | 0.19 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#106815 #id: 12014 #code: "IEEE00006934" #attributes: Doctrine\ORM\PersistentCollection {#106798 …} #variants: Doctrine\ORM\PersistentCollection {#106795 …} #options: Doctrine\ORM\PersistentCollection {#106791 …} #associations: Doctrine\ORM\PersistentCollection {#106793 …} #createdAt: DateTime @1751040138 {#106783 : 2025-06-27 18:02:18.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#106796 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106809 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#107016 #locale: "en_US" #translatable: App\Entity\Product\Product {#106815} #id: 43065 #name: "IEEE/ISO/IEC 24748-1:2018" #slug: "ieee-iso-iec-24748-1-2018-ieee00006934-243666" #description: """ Revision Standard - Superseded.<br />\n The purpose of this document is to facilitate the joint usage of the process content of the latest revisions of both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, by providing unified and consolidated guidance on life cycle management of systems and software. This is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains as the two International Standards are used in combination. That will in turn help a project team design a life cycle model for managing the progress of their project. Hence, ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 are the documents that apply the concepts found in this document to specific processes.<br />\n \t\t\t\t<br />\n This document provides guidelines for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document: - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines; - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide, or acquire either products or services; - defines the concept and terminology of a life cycle; - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services; - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle; - describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software aspects); - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects; and - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Life cycle management - Part 1:Guidelines for life cycle management" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106806 …} #channels: Doctrine\ORM\PersistentCollection {#106800 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#106804 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106802 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106816 …} -apiLastModifiedAt: DateTime @1754517600 {#106823 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1710716400 {#106827 : 2024-03-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1541026800 {#106781 : 2018-11-01 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 82 -documents: Doctrine\ORM\PersistentCollection {#106813 …} -favorites: Doctrine\ORM\PersistentCollection {#106811 …} } "showFullLabel" => "true" ] |
|||
| Attributes | [ "showFullLabel" => "true" ] |
|||
| Component | App\Twig\Components\ProductState {#107031 +product: App\Entity\Product\Product {#106815 #id: 12014 #code: "IEEE00006934" #attributes: Doctrine\ORM\PersistentCollection {#106798 …} #variants: Doctrine\ORM\PersistentCollection {#106795 …} #options: Doctrine\ORM\PersistentCollection {#106791 …} #associations: Doctrine\ORM\PersistentCollection {#106793 …} #createdAt: DateTime @1751040138 {#106783 : 2025-06-27 18:02:18.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#106796 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106809 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#107016 #locale: "en_US" #translatable: App\Entity\Product\Product {#106815} #id: 43065 #name: "IEEE/ISO/IEC 24748-1:2018" #slug: "ieee-iso-iec-24748-1-2018-ieee00006934-243666" #description: """ Revision Standard - Superseded.<br />\n The purpose of this document is to facilitate the joint usage of the process content of the latest revisions of both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, by providing unified and consolidated guidance on life cycle management of systems and software. This is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains as the two International Standards are used in combination. That will in turn help a project team design a life cycle model for managing the progress of their project. Hence, ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 are the documents that apply the concepts found in this document to specific processes.<br />\n \t\t\t\t<br />\n This document provides guidelines for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document: - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines; - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide, or acquire either products or services; - defines the concept and terminology of a life cycle; - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services; - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle; - describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software aspects); - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects; and - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Life cycle management - Part 1:Guidelines for life cycle management" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106806 …} #channels: Doctrine\ORM\PersistentCollection {#106800 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#106804 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106802 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106816 …} -apiLastModifiedAt: DateTime @1754517600 {#106823 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1710716400 {#106827 : 2024-03-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1541026800 {#106781 : 2018-11-01 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 82 -documents: Doctrine\ORM\PersistentCollection {#106813 …} -favorites: Doctrine\ORM\PersistentCollection {#106811 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 80.0 MiB | 0.61 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#106815 #id: 12014 #code: "IEEE00006934" #attributes: Doctrine\ORM\PersistentCollection {#106798 …} #variants: Doctrine\ORM\PersistentCollection {#106795 …} #options: Doctrine\ORM\PersistentCollection {#106791 …} #associations: Doctrine\ORM\PersistentCollection {#106793 …} #createdAt: DateTime @1751040138 {#106783 : 2025-06-27 18:02:18.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#106796 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106809 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#107016 #locale: "en_US" #translatable: App\Entity\Product\Product {#106815} #id: 43065 #name: "IEEE/ISO/IEC 24748-1:2018" #slug: "ieee-iso-iec-24748-1-2018-ieee00006934-243666" #description: """ Revision Standard - Superseded.<br />\n The purpose of this document is to facilitate the joint usage of the process content of the latest revisions of both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, by providing unified and consolidated guidance on life cycle management of systems and software. This is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains as the two International Standards are used in combination. That will in turn help a project team design a life cycle model for managing the progress of their project. Hence, ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 are the documents that apply the concepts found in this document to specific processes.<br />\n \t\t\t\t<br />\n This document provides guidelines for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document: - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines; - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide, or acquire either products or services; - defines the concept and terminology of a life cycle; - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services; - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle; - describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software aspects); - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects; and - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Life cycle management - Part 1:Guidelines for life cycle management" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106806 …} #channels: Doctrine\ORM\PersistentCollection {#106800 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#106804 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106802 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106816 …} -apiLastModifiedAt: DateTime @1754517600 {#106823 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1710716400 {#106827 : 2024-03-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1541026800 {#106781 : 2018-11-01 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 82 -documents: Doctrine\ORM\PersistentCollection {#106813 …} -favorites: Doctrine\ORM\PersistentCollection {#106811 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#107083 +product: App\Entity\Product\Product {#106815 #id: 12014 #code: "IEEE00006934" #attributes: Doctrine\ORM\PersistentCollection {#106798 …} #variants: Doctrine\ORM\PersistentCollection {#106795 …} #options: Doctrine\ORM\PersistentCollection {#106791 …} #associations: Doctrine\ORM\PersistentCollection {#106793 …} #createdAt: DateTime @1751040138 {#106783 : 2025-06-27 18:02:18.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#106796 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106809 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#107016 #locale: "en_US" #translatable: App\Entity\Product\Product {#106815} #id: 43065 #name: "IEEE/ISO/IEC 24748-1:2018" #slug: "ieee-iso-iec-24748-1-2018-ieee00006934-243666" #description: """ Revision Standard - Superseded.<br />\n The purpose of this document is to facilitate the joint usage of the process content of the latest revisions of both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, by providing unified and consolidated guidance on life cycle management of systems and software. This is to help ensure consistency in system concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains as the two International Standards are used in combination. That will in turn help a project team design a life cycle model for managing the progress of their project. Hence, ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 are the documents that apply the concepts found in this document to specific processes.<br />\n \t\t\t\t<br />\n This document provides guidelines for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document: - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines; - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide, or acquire either products or services; - defines the concept and terminology of a life cycle; - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services; - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle; - describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software aspects); - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects; and - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Life cycle management - Part 1:Guidelines for life cycle management" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106806 …} #channels: Doctrine\ORM\PersistentCollection {#106800 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#106804 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106802 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106816 …} -apiLastModifiedAt: DateTime @1754517600 {#106823 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1710716400 {#106827 : 2024-03-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1541026800 {#106781 : 2018-11-01 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 82 -documents: Doctrine\ORM\PersistentCollection {#106813 …} -favorites: Doctrine\ORM\PersistentCollection {#106811 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductState | App\Twig\Components\ProductState | 80.0 MiB | 0.17 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#7310 #id: 10824 #code: "IEEE00005065" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039305 {#7274 : 2025-06-27 17:48:25.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#7322 : 2025-08-08 01:09:50.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: 38305 #name: "IEEE 24748-1:2011" #slug: "ieee-24748-1-2011-ieee00005065-242476" #description: """ New IEEE Standard - Superseded.<br />\n This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties.<br />\n ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.<br />\n \t\t\t\t<br />\n This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:<br />\n - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains;<br />\n - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services; defines the concept and terminology of a life cycle;<br />\n - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;<br />\n - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;<br />\n - describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects);<br />\n - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;<br />\n - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management;<br />\n - complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.<br />\n NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management" -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 @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1307052000 {#7318 : 2011-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 96 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } "showFullLabel" => "true" ] |
|||
| Attributes | [ "showFullLabel" => "true" ] |
|||
| Component | App\Twig\Components\ProductState {#107147 +product: App\Entity\Product\Product {#7310 #id: 10824 #code: "IEEE00005065" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039305 {#7274 : 2025-06-27 17:48:25.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#7322 : 2025-08-08 01:09:50.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: 38305 #name: "IEEE 24748-1:2011" #slug: "ieee-24748-1-2011-ieee00005065-242476" #description: """ New IEEE Standard - Superseded.<br />\n This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties.<br />\n ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.<br />\n \t\t\t\t<br />\n This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:<br />\n - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains;<br />\n - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services; defines the concept and terminology of a life cycle;<br />\n - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;<br />\n - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;<br />\n - describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects);<br />\n - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;<br />\n - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management;<br />\n - complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.<br />\n NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management" -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 @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1307052000 {#7318 : 2011-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 96 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 80.0 MiB | 0.60 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#7310 #id: 10824 #code: "IEEE00005065" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039305 {#7274 : 2025-06-27 17:48:25.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#7322 : 2025-08-08 01:09:50.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: 38305 #name: "IEEE 24748-1:2011" #slug: "ieee-24748-1-2011-ieee00005065-242476" #description: """ New IEEE Standard - Superseded.<br />\n This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties.<br />\n ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.<br />\n \t\t\t\t<br />\n This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:<br />\n - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains;<br />\n - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services; defines the concept and terminology of a life cycle;<br />\n - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;<br />\n - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;<br />\n - describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects);<br />\n - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;<br />\n - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management;<br />\n - complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.<br />\n NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management" -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 @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1307052000 {#7318 : 2011-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 96 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#107174 +product: App\Entity\Product\Product {#7310 #id: 10824 #code: "IEEE00005065" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039305 {#7274 : 2025-06-27 17:48:25.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#7322 : 2025-08-08 01:09:50.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: 38305 #name: "IEEE 24748-1:2011" #slug: "ieee-24748-1-2011-ieee00005065-242476" #description: """ New IEEE Standard - Superseded.<br />\n This guide adopts ISO/IEC TR 24748-1:2010, which provides information on life cycle concepts and descriptions of the purposes and outcomes of representative life cycle stages. It also illustrates the use of a life cycle model for systems in the context of ISO/IEC 15288 and provides a corresponding illustration of the use of a life cycle model for software in the context of ISO/IEC 12207. ISO/IEC TR 24748-1:2010 additionally provides detailed discussion and advice on adapting a life cycle model for use in a specific project and organizational environment. It further provides guidance on life cycle model use by domains, disciplines and specialties.<br />\n ISO/IEC TR 24748-1:2010 gives a detailed comparison between prior and current versions of ISO/IEC 12207 and ISO/IEC 15288, as well as advice on transitioning from prior to current versions and on using their application guides. The discussion and advice are intended to provide a reference model for life cycle models, facilitate use of the updated ISO/IEC 15288 and ISO/IEC 12207, and provide a framework for the development of updated application guides for those International Standards. ISO/IEC TR 24748-1:2010 is a result of the alignment stage of the harmonization of ISO/IEC 12207 and ISO/IEC 15288.<br />\n \t\t\t\t<br />\n This Technical Report is a guide for the life cycle management of systems and software based on ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:<br />\n - addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains;<br />\n - establishes a common framework for describing life cycles, including their individual stages, for the management of projects to provide or acquire either products or services; defines the concept and terminology of a life cycle;<br />\n - supports the use of the life cycle processes within an organization or a project. Organizations and projects can use these life cycle concepts when acquiring and supplying either products or services;<br />\n - provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle;<br />\n - describes the relationship between life cycles and their use in ISO/IEC 15288 (systems aspects) and ISO/IEC 12207 (software aspects);<br />\n - shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects;<br />\n - describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management and risk management;<br />\n - complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.<br />\n NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Guide--Adoption of ISO/IEC TR 24748-1:2010 Systems and Software Engineering--Life Cycle Management--Part 1: Guide for Life Cycle Management" -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 @1754517600 {#7317 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1307052000 {#7318 : 2011-06-03 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "24748-1" -bookCollection: "" -pageCount: 96 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductCard | App\Twig\Components\ProductCard | 102.0 MiB | 8.26 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#128486 #id: 9038 #code: "IEEE00001502" #attributes: Doctrine\ORM\PersistentCollection {#128469 …} #variants: Doctrine\ORM\PersistentCollection {#128467 …} #options: Doctrine\ORM\PersistentCollection {#128462 …} #associations: Doctrine\ORM\PersistentCollection {#128464 …} #createdAt: DateTime @1751037919 {#128459 : 2025-06-27 17:25:19.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128452 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128480 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128603 #locale: "en_US" #translatable: App\Entity\Product\Product {#128486} #id: 31161 #name: "IEEE 1028:1998 (R2002)" #slug: "ieee-1028-1998-r2002-ieee00001502-240690" #description: """ Revision Standard - Superseded.<br />\n This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n \t\t\t\t<br />\n Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Software Reviews" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128478 …} #channels: Doctrine\ORM\PersistentCollection {#128471 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128475 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128473 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128488 …} -apiLastModifiedAt: DateTime @1754517600 {#128445 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128494 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @883609200 {#128465 : 1998-01-01 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128446 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1028" -bookCollection: "" -pageCount: 48 -documents: Doctrine\ORM\PersistentCollection {#128484 …} -favorites: Doctrine\ORM\PersistentCollection {#128482 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "additionalClasses" => "product__teaser--with-grey-border" "hasStretchedLink" => true "hoverType" => "shadow" "linkLabel" => "See more" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#128520 +product: App\Entity\Product\Product {#128486 #id: 9038 #code: "IEEE00001502" #attributes: Doctrine\ORM\PersistentCollection {#128469 …} #variants: Doctrine\ORM\PersistentCollection {#128467 …} #options: Doctrine\ORM\PersistentCollection {#128462 …} #associations: Doctrine\ORM\PersistentCollection {#128464 …} #createdAt: DateTime @1751037919 {#128459 : 2025-06-27 17:25:19.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128452 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128480 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128603 #locale: "en_US" #translatable: App\Entity\Product\Product {#128486} #id: 31161 #name: "IEEE 1028:1998 (R2002)" #slug: "ieee-1028-1998-r2002-ieee00001502-240690" #description: """ Revision Standard - Superseded.<br />\n This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n \t\t\t\t<br />\n Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Software Reviews" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128478 …} #channels: Doctrine\ORM\PersistentCollection {#128471 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128475 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128473 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128488 …} -apiLastModifiedAt: DateTime @1754517600 {#128445 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128494 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @883609200 {#128465 : 1998-01-01 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128446 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1028" -bookCollection: "" -pageCount: 48 -documents: Doctrine\ORM\PersistentCollection {#128484 …} -favorites: Doctrine\ORM\PersistentCollection {#128482 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "product__teaser--with-grey-border" +linkLabel: "See more" +imageFilter: "product_thumbnail_teaser" +hasStretchedLink: true +backgroundColor: "white" +hoverType: "shadow" } |
|||
| ProductState | App\Twig\Components\ProductState | 102.0 MiB | 0.27 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#128486 #id: 9038 #code: "IEEE00001502" #attributes: Doctrine\ORM\PersistentCollection {#128469 …} #variants: Doctrine\ORM\PersistentCollection {#128467 …} #options: Doctrine\ORM\PersistentCollection {#128462 …} #associations: Doctrine\ORM\PersistentCollection {#128464 …} #createdAt: DateTime @1751037919 {#128459 : 2025-06-27 17:25:19.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128452 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128480 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128603 #locale: "en_US" #translatable: App\Entity\Product\Product {#128486} #id: 31161 #name: "IEEE 1028:1998 (R2002)" #slug: "ieee-1028-1998-r2002-ieee00001502-240690" #description: """ Revision Standard - Superseded.<br />\n This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n \t\t\t\t<br />\n Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Software Reviews" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128478 …} #channels: Doctrine\ORM\PersistentCollection {#128471 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128475 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128473 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128488 …} -apiLastModifiedAt: DateTime @1754517600 {#128445 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128494 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @883609200 {#128465 : 1998-01-01 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128446 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1028" -bookCollection: "" -pageCount: 48 -documents: Doctrine\ORM\PersistentCollection {#128484 …} -favorites: Doctrine\ORM\PersistentCollection {#128482 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#128607 +product: App\Entity\Product\Product {#128486 #id: 9038 #code: "IEEE00001502" #attributes: Doctrine\ORM\PersistentCollection {#128469 …} #variants: Doctrine\ORM\PersistentCollection {#128467 …} #options: Doctrine\ORM\PersistentCollection {#128462 …} #associations: Doctrine\ORM\PersistentCollection {#128464 …} #createdAt: DateTime @1751037919 {#128459 : 2025-06-27 17:25:19.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128452 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128480 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128603 #locale: "en_US" #translatable: App\Entity\Product\Product {#128486} #id: 31161 #name: "IEEE 1028:1998 (R2002)" #slug: "ieee-1028-1998-r2002-ieee00001502-240690" #description: """ Revision Standard - Superseded.<br />\n This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n \t\t\t\t<br />\n Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Software Reviews" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128478 …} #channels: Doctrine\ORM\PersistentCollection {#128471 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128475 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128473 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128488 …} -apiLastModifiedAt: DateTime @1754517600 {#128445 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128494 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @883609200 {#128465 : 1998-01-01 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128446 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1028" -bookCollection: "" -pageCount: 48 -documents: Doctrine\ORM\PersistentCollection {#128484 …} -favorites: Doctrine\ORM\PersistentCollection {#128482 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 102.0 MiB | 0.76 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#128486 #id: 9038 #code: "IEEE00001502" #attributes: Doctrine\ORM\PersistentCollection {#128469 …} #variants: Doctrine\ORM\PersistentCollection {#128467 …} #options: Doctrine\ORM\PersistentCollection {#128462 …} #associations: Doctrine\ORM\PersistentCollection {#128464 …} #createdAt: DateTime @1751037919 {#128459 : 2025-06-27 17:25:19.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128452 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128480 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128603 #locale: "en_US" #translatable: App\Entity\Product\Product {#128486} #id: 31161 #name: "IEEE 1028:1998 (R2002)" #slug: "ieee-1028-1998-r2002-ieee00001502-240690" #description: """ Revision Standard - Superseded.<br />\n This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n \t\t\t\t<br />\n Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Software Reviews" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128478 …} #channels: Doctrine\ORM\PersistentCollection {#128471 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128475 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128473 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128488 …} -apiLastModifiedAt: DateTime @1754517600 {#128445 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128494 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @883609200 {#128465 : 1998-01-01 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128446 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1028" -bookCollection: "" -pageCount: 48 -documents: Doctrine\ORM\PersistentCollection {#128484 …} -favorites: Doctrine\ORM\PersistentCollection {#128482 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#128685 +product: App\Entity\Product\Product {#128486 #id: 9038 #code: "IEEE00001502" #attributes: Doctrine\ORM\PersistentCollection {#128469 …} #variants: Doctrine\ORM\PersistentCollection {#128467 …} #options: Doctrine\ORM\PersistentCollection {#128462 …} #associations: Doctrine\ORM\PersistentCollection {#128464 …} #createdAt: DateTime @1751037919 {#128459 : 2025-06-27 17:25:19.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128452 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128480 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128603 #locale: "en_US" #translatable: App\Entity\Product\Product {#128486} #id: 31161 #name: "IEEE 1028:1998 (R2002)" #slug: "ieee-1028-1998-r2002-ieee00001502-240690" #description: """ Revision Standard - Superseded.<br />\n This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.<br />\n \t\t\t\t<br />\n Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.<br />\n Software is employed in most equipment and business systems. To achieve the expectations of the users of the software, it is essential to have disciplined methods for evaluating of software products as they pass along the software development life-cycle. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Software Reviews" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128478 …} #channels: Doctrine\ORM\PersistentCollection {#128471 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128475 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128473 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128488 …} -apiLastModifiedAt: DateTime @1754517600 {#128445 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128494 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @883609200 {#128465 : 1998-01-01 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128446 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1028" -bookCollection: "" -pageCount: 48 -documents: Doctrine\ORM\PersistentCollection {#128484 …} -favorites: Doctrine\ORM\PersistentCollection {#128482 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductCard | App\Twig\Components\ProductCard | 102.0 MiB | 5.73 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#128453 #id: 9051 #code: "IEEE00001526" #attributes: Doctrine\ORM\PersistentCollection {#128537 …} #variants: Doctrine\ORM\PersistentCollection {#128536 …} #options: Doctrine\ORM\PersistentCollection {#128531 …} #associations: Doctrine\ORM\PersistentCollection {#128533 …} #createdAt: DateTime @1751037930 {#128460 : 2025-06-27 17:25:30.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128458 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128534 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128802 #locale: "en_US" #translatable: App\Entity\Product\Product {#128453} #id: 31213 #name: "IEEE 1044:1993 (R2002)" #slug: "ieee-1044-1993-r2002-ieee00001526-240703" #description: """ New IEEE Standard - Superseded.<br />\n A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n \t\t\t\t<br />\n This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard Classification for Software Anomalies" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128519 …} #channels: Doctrine\ORM\PersistentCollection {#128542 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128497 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128543 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128451 …} -apiLastModifiedAt: DateTime @1754517600 {#128457 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128456 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @754614000 {#128455 : 1993-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128454 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1044" -bookCollection: "" -pageCount: 32 -documents: Doctrine\ORM\PersistentCollection {#128449 …} -favorites: Doctrine\ORM\PersistentCollection {#128442 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "additionalClasses" => "product__teaser--with-grey-border" "hasStretchedLink" => true "hoverType" => "shadow" "linkLabel" => "See more" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#128760 +product: App\Entity\Product\Product {#128453 #id: 9051 #code: "IEEE00001526" #attributes: Doctrine\ORM\PersistentCollection {#128537 …} #variants: Doctrine\ORM\PersistentCollection {#128536 …} #options: Doctrine\ORM\PersistentCollection {#128531 …} #associations: Doctrine\ORM\PersistentCollection {#128533 …} #createdAt: DateTime @1751037930 {#128460 : 2025-06-27 17:25:30.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128458 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128534 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128802 #locale: "en_US" #translatable: App\Entity\Product\Product {#128453} #id: 31213 #name: "IEEE 1044:1993 (R2002)" #slug: "ieee-1044-1993-r2002-ieee00001526-240703" #description: """ New IEEE Standard - Superseded.<br />\n A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n \t\t\t\t<br />\n This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard Classification for Software Anomalies" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128519 …} #channels: Doctrine\ORM\PersistentCollection {#128542 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128497 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128543 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128451 …} -apiLastModifiedAt: DateTime @1754517600 {#128457 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128456 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @754614000 {#128455 : 1993-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128454 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1044" -bookCollection: "" -pageCount: 32 -documents: Doctrine\ORM\PersistentCollection {#128449 …} -favorites: Doctrine\ORM\PersistentCollection {#128442 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "product__teaser--with-grey-border" +linkLabel: "See more" +imageFilter: "product_thumbnail_teaser" +hasStretchedLink: true +backgroundColor: "white" +hoverType: "shadow" } |
|||
| ProductState | App\Twig\Components\ProductState | 102.0 MiB | 0.18 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#128453 #id: 9051 #code: "IEEE00001526" #attributes: Doctrine\ORM\PersistentCollection {#128537 …} #variants: Doctrine\ORM\PersistentCollection {#128536 …} #options: Doctrine\ORM\PersistentCollection {#128531 …} #associations: Doctrine\ORM\PersistentCollection {#128533 …} #createdAt: DateTime @1751037930 {#128460 : 2025-06-27 17:25:30.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128458 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128534 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128802 #locale: "en_US" #translatable: App\Entity\Product\Product {#128453} #id: 31213 #name: "IEEE 1044:1993 (R2002)" #slug: "ieee-1044-1993-r2002-ieee00001526-240703" #description: """ New IEEE Standard - Superseded.<br />\n A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n \t\t\t\t<br />\n This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard Classification for Software Anomalies" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128519 …} #channels: Doctrine\ORM\PersistentCollection {#128542 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128497 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128543 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128451 …} -apiLastModifiedAt: DateTime @1754517600 {#128457 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128456 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @754614000 {#128455 : 1993-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128454 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1044" -bookCollection: "" -pageCount: 32 -documents: Doctrine\ORM\PersistentCollection {#128449 …} -favorites: Doctrine\ORM\PersistentCollection {#128442 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#128809 +product: App\Entity\Product\Product {#128453 #id: 9051 #code: "IEEE00001526" #attributes: Doctrine\ORM\PersistentCollection {#128537 …} #variants: Doctrine\ORM\PersistentCollection {#128536 …} #options: Doctrine\ORM\PersistentCollection {#128531 …} #associations: Doctrine\ORM\PersistentCollection {#128533 …} #createdAt: DateTime @1751037930 {#128460 : 2025-06-27 17:25:30.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128458 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128534 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128802 #locale: "en_US" #translatable: App\Entity\Product\Product {#128453} #id: 31213 #name: "IEEE 1044:1993 (R2002)" #slug: "ieee-1044-1993-r2002-ieee00001526-240703" #description: """ New IEEE Standard - Superseded.<br />\n A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n \t\t\t\t<br />\n This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard Classification for Software Anomalies" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128519 …} #channels: Doctrine\ORM\PersistentCollection {#128542 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128497 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128543 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128451 …} -apiLastModifiedAt: DateTime @1754517600 {#128457 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128456 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @754614000 {#128455 : 1993-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128454 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1044" -bookCollection: "" -pageCount: 32 -documents: Doctrine\ORM\PersistentCollection {#128449 …} -favorites: Doctrine\ORM\PersistentCollection {#128442 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 102.0 MiB | 0.64 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#128453 #id: 9051 #code: "IEEE00001526" #attributes: Doctrine\ORM\PersistentCollection {#128537 …} #variants: Doctrine\ORM\PersistentCollection {#128536 …} #options: Doctrine\ORM\PersistentCollection {#128531 …} #associations: Doctrine\ORM\PersistentCollection {#128533 …} #createdAt: DateTime @1751037930 {#128460 : 2025-06-27 17:25:30.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128458 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128534 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128802 #locale: "en_US" #translatable: App\Entity\Product\Product {#128453} #id: 31213 #name: "IEEE 1044:1993 (R2002)" #slug: "ieee-1044-1993-r2002-ieee00001526-240703" #description: """ New IEEE Standard - Superseded.<br />\n A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n \t\t\t\t<br />\n This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard Classification for Software Anomalies" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128519 …} #channels: Doctrine\ORM\PersistentCollection {#128542 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128497 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128543 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128451 …} -apiLastModifiedAt: DateTime @1754517600 {#128457 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128456 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @754614000 {#128455 : 1993-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128454 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1044" -bookCollection: "" -pageCount: 32 -documents: Doctrine\ORM\PersistentCollection {#128449 …} -favorites: Doctrine\ORM\PersistentCollection {#128442 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#128886 +product: App\Entity\Product\Product {#128453 #id: 9051 #code: "IEEE00001526" #attributes: Doctrine\ORM\PersistentCollection {#128537 …} #variants: Doctrine\ORM\PersistentCollection {#128536 …} #options: Doctrine\ORM\PersistentCollection {#128531 …} #associations: Doctrine\ORM\PersistentCollection {#128533 …} #createdAt: DateTime @1751037930 {#128460 : 2025-06-27 17:25:30.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#128458 : 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#128534 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#128802 #locale: "en_US" #translatable: App\Entity\Product\Product {#128453} #id: 31213 #name: "IEEE 1044:1993 (R2002)" #slug: "ieee-1044-1993-r2002-ieee00001526-240703" #description: """ New IEEE Standard - Superseded.<br />\n A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n \t\t\t\t<br />\n This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard Classification for Software Anomalies" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#128519 …} #channels: Doctrine\ORM\PersistentCollection {#128542 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#128497 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#128543 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128451 …} -apiLastModifiedAt: DateTime @1754517600 {#128457 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#128456 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @754614000 {#128455 : 1993-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1031781600 {#128454 : 2002-09-12 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1044" -bookCollection: "" -pageCount: 32 -documents: Doctrine\ORM\PersistentCollection {#128449 …} -favorites: Doctrine\ORM\PersistentCollection {#128442 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||