GET https://dev.normadoc.fr/_fragment?_path=_format%3Dhtml%26_locale%3Den_US%26_controller%3Dsylius.controller.shop.locale_switch%253A%253ArenderAction

Response
200 OK
IP
216.73.216.131
Profiled on
Token
f28cf2

Components

4 Twig Components
8 Render Count
17 ms Render Time
484.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		3 1.14ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		3 3.09ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.28ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		1 14.17ms

Render calls

ProductState App\Twig\Components\ProductState 484.0 MiB 0.56 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12724
    #code: "IEEE00010528"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040620 {#7274
      date: 2025-06-27 18:10:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 45905
        #name: "IEEE/ISO/IEC 24748-9:2023"
        #slug: "ieee-iso-iec-24748-9-2023-ieee00010528-244379"
        #description: """
          New IEEE Standard - Active.<br />\n
          Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle management -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems"
        -notes: "Active"
      }
    ]
    #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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#7292
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1685484000 {#7318
      date: 2023-05-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-9"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#93054
  +product: App\Entity\Product\Product {#7310
    #id: 12724
    #code: "IEEE00010528"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040620 {#7274
      date: 2025-06-27 18:10:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 45905
        #name: "IEEE/ISO/IEC 24748-9:2023"
        #slug: "ieee-iso-iec-24748-9-2023-ieee00010528-244379"
        #description: """
          New IEEE Standard - Active.<br />\n
          Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle management -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems"
        -notes: "Active"
      }
    ]
    #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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#7292
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1685484000 {#7318
      date: 2023-05-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-9"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 484.0 MiB 0.28 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12724
    #code: "IEEE00010528"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040620 {#7274
      date: 2025-06-27 18:10:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 45905
        #name: "IEEE/ISO/IEC 24748-9:2023"
        #slug: "ieee-iso-iec-24748-9-2023-ieee00010528-244379"
        #description: """
          New IEEE Standard - Active.<br />\n
          Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle management -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems"
        -notes: "Active"
      }
    ]
    #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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#7292
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1685484000 {#7318
      date: 2023-05-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-9"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93234
  +product: App\Entity\Product\Product {#7310
    #id: 12724
    #code: "IEEE00010528"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040620 {#7274
      date: 2025-06-27 18:10:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 45905
        #name: "IEEE/ISO/IEC 24748-9:2023"
        #slug: "ieee-iso-iec-24748-9-2023-ieee00010528-244379"
        #description: """
          New IEEE Standard - Active.<br />\n
          Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle management -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems"
        -notes: "Active"
      }
    ]
    #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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#7292
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1685484000 {#7318
      date: 2023-05-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-9"
    -bookCollection: ""
    -pageCount: 52
    -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 484.0 MiB 1.04 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12724
    #code: "IEEE00010528"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040620 {#7274
      date: 2025-06-27 18:10:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 45905
        #name: "IEEE/ISO/IEC 24748-9:2023"
        #slug: "ieee-iso-iec-24748-9-2023-ieee00010528-244379"
        #description: """
          New IEEE Standard - Active.<br />\n
          Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle management -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems"
        -notes: "Active"
      }
    ]
    #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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#7292
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1685484000 {#7318
      date: 2023-05-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-9"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93309
  +product: App\Entity\Product\Product {#7310
    #id: 12724
    #code: "IEEE00010528"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040620 {#7274
      date: 2025-06-27 18:10:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 45905
        #name: "IEEE/ISO/IEC 24748-9:2023"
        #slug: "ieee-iso-iec-24748-9-2023-ieee00010528-244379"
        #description: """
          New IEEE Standard - Active.<br />\n
          Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle management -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems"
        -notes: "Active"
      }
    ]
    #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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#7292
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1685484000 {#7318
      date: 2023-05-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-9"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 484.0 MiB 0.27 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12724
    #code: "IEEE00010528"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040620 {#7274
      date: 2025-06-27 18:10:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 45905
        #name: "IEEE/ISO/IEC 24748-9:2023"
        #slug: "ieee-iso-iec-24748-9-2023-ieee00010528-244379"
        #description: """
          New IEEE Standard - Active.<br />\n
          Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle management -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems"
        -notes: "Active"
      }
    ]
    #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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#7292
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1685484000 {#7318
      date: 2023-05-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-9"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100265
  +product: App\Entity\Product\Product {#7310
    #id: 12724
    #code: "IEEE00010528"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040620 {#7274
      date: 2025-06-27 18:10:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 45905
        #name: "IEEE/ISO/IEC 24748-9:2023"
        #slug: "ieee-iso-iec-24748-9-2023-ieee00010528-244379"
        #description: """
          New IEEE Standard - Active.<br />\n
          Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle management -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems"
        -notes: "Active"
      }
    ]
    #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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#7292
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1685484000 {#7318
      date: 2023-05-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-9"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 484.0 MiB 0.93 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12724
    #code: "IEEE00010528"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040620 {#7274
      date: 2025-06-27 18:10:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 45905
        #name: "IEEE/ISO/IEC 24748-9:2023"
        #slug: "ieee-iso-iec-24748-9-2023-ieee00010528-244379"
        #description: """
          New IEEE Standard - Active.<br />\n
          Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle management -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems"
        -notes: "Active"
      }
    ]
    #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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#7292
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1685484000 {#7318
      date: 2023-05-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-9"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100349
  +product: App\Entity\Product\Product {#7310
    #id: 12724
    #code: "IEEE00010528"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040620 {#7274
      date: 2025-06-27 18:10:20.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 45905
        #name: "IEEE/ISO/IEC 24748-9:2023"
        #slug: "ieee-iso-iec-24748-9-2023-ieee00010528-244379"
        #description: """
          New IEEE Standard - Active.<br />\n
          Many countries have adopted information-based prevention and control measures during the epidemic, and have developed numerous epidemic prevention and control systems and software. Most of the processes in the entire life cycle of the epidemic prevention and control systems are most likely to be completed in the event of an epidemic. Compared with the normal state, there will be special situations such as poor communication caused by the need for personnel to maintain a safe distance; limited transportation and logistics, resulting in insufficient infrastructure protection; short delivery cycles and frequent iterative upgrades; and special requirements such as accuracy, disaster tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture. In this case, it is believed that in the development process of epidemic prevention and control systems, the application of the life cycle process method specified in the ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207 standards can effectively help guide the process management and application of the epidemic prevention and control systems.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle management -- Part 9: Application of system and software life cycle processes in epidemic prevention and control systems"
        -notes: "Active"
      }
    ]
    #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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1687730400 {#7292
      date: 2023-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1685484000 {#7318
      date: 2023-05-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "24748-9"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 484.0 MiB 14.17 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121733
    #id: 11171
    #code: "IEEE00005672"
    #attributes: Doctrine\ORM\PersistentCollection {#121757 …}
    #variants: Doctrine\ORM\PersistentCollection {#121755 …}
    #options: Doctrine\ORM\PersistentCollection {#121750 …}
    #associations: Doctrine\ORM\PersistentCollection {#121753 …}
    #createdAt: DateTime @1751039524 {#121746
      date: 2025-06-27 17:52:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121739
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121768 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121874
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121733}
        #id: 39693
        #name: "IEEE/ISO/IEC 12207:2017"
        #slug: "ieee-iso-iec-12207-2017-ieee00005672-242823"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction.<br />\n
          This International Standard applies to the acquisition of software systems, products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of any system, whether performed internally or externally to an organization. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project.<br />\n
          The processes, activities and tasks of this International Standard may also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288, Systems and software engineering—System life cycle processes.<br />\n
          In the context of this International Standard and ISO/IEC/IEEE 15288, it is recognized that there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system of interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this International Standard for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering-System life cycle processes, depends on the system of interest. Processes in both standards have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software system.<br />\n
          This International Standard is written for acquirers of software systems, products and services and for suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, and users of software systems and products. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations and the situation can range from an informal agreement to a formal contract.<br />\n
          The processes in this International Standard can be used as a basis for establishing business environments, e.g., methods, procedures, techniques, tools and trained personnel. Annex A provides normative direction regarding the tailoring of these software life cycle processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121766 …}
    #channels: Doctrine\ORM\PersistentCollection {#121759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121763 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121761 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121773 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121732
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121781
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1510700400 {#121752
      date: 2017-11-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 157
    -documents: Doctrine\ORM\PersistentCollection {#121772 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121770 …}
  }
  "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 {#121825
  +product: App\Entity\Product\Product {#121733
    #id: 11171
    #code: "IEEE00005672"
    #attributes: Doctrine\ORM\PersistentCollection {#121757 …}
    #variants: Doctrine\ORM\PersistentCollection {#121755 …}
    #options: Doctrine\ORM\PersistentCollection {#121750 …}
    #associations: Doctrine\ORM\PersistentCollection {#121753 …}
    #createdAt: DateTime @1751039524 {#121746
      date: 2025-06-27 17:52:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121739
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121768 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121874
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121733}
        #id: 39693
        #name: "IEEE/ISO/IEC 12207:2017"
        #slug: "ieee-iso-iec-12207-2017-ieee00005672-242823"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction.<br />\n
          This International Standard applies to the acquisition of software systems, products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of any system, whether performed internally or externally to an organization. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project.<br />\n
          The processes, activities and tasks of this International Standard may also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288, Systems and software engineering—System life cycle processes.<br />\n
          In the context of this International Standard and ISO/IEC/IEEE 15288, it is recognized that there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system of interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this International Standard for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering-System life cycle processes, depends on the system of interest. Processes in both standards have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software system.<br />\n
          This International Standard is written for acquirers of software systems, products and services and for suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, and users of software systems and products. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations and the situation can range from an informal agreement to a formal contract.<br />\n
          The processes in this International Standard can be used as a basis for establishing business environments, e.g., methods, procedures, techniques, tools and trained personnel. Annex A provides normative direction regarding the tailoring of these software life cycle processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121766 …}
    #channels: Doctrine\ORM\PersistentCollection {#121759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121763 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121761 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121773 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121732
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121781
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1510700400 {#121752
      date: 2017-11-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 157
    -documents: Doctrine\ORM\PersistentCollection {#121772 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121770 …}
  }
  +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 484.0 MiB 0.30 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121733
    #id: 11171
    #code: "IEEE00005672"
    #attributes: Doctrine\ORM\PersistentCollection {#121757 …}
    #variants: Doctrine\ORM\PersistentCollection {#121755 …}
    #options: Doctrine\ORM\PersistentCollection {#121750 …}
    #associations: Doctrine\ORM\PersistentCollection {#121753 …}
    #createdAt: DateTime @1751039524 {#121746
      date: 2025-06-27 17:52:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121739
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121768 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121874
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121733}
        #id: 39693
        #name: "IEEE/ISO/IEC 12207:2017"
        #slug: "ieee-iso-iec-12207-2017-ieee00005672-242823"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction.<br />\n
          This International Standard applies to the acquisition of software systems, products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of any system, whether performed internally or externally to an organization. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project.<br />\n
          The processes, activities and tasks of this International Standard may also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288, Systems and software engineering—System life cycle processes.<br />\n
          In the context of this International Standard and ISO/IEC/IEEE 15288, it is recognized that there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system of interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this International Standard for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering-System life cycle processes, depends on the system of interest. Processes in both standards have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software system.<br />\n
          This International Standard is written for acquirers of software systems, products and services and for suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, and users of software systems and products. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations and the situation can range from an informal agreement to a formal contract.<br />\n
          The processes in this International Standard can be used as a basis for establishing business environments, e.g., methods, procedures, techniques, tools and trained personnel. Annex A provides normative direction regarding the tailoring of these software life cycle processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121766 …}
    #channels: Doctrine\ORM\PersistentCollection {#121759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121763 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121761 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121773 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121732
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121781
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1510700400 {#121752
      date: 2017-11-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 157
    -documents: Doctrine\ORM\PersistentCollection {#121772 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121770 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#121876
  +product: App\Entity\Product\Product {#121733
    #id: 11171
    #code: "IEEE00005672"
    #attributes: Doctrine\ORM\PersistentCollection {#121757 …}
    #variants: Doctrine\ORM\PersistentCollection {#121755 …}
    #options: Doctrine\ORM\PersistentCollection {#121750 …}
    #associations: Doctrine\ORM\PersistentCollection {#121753 …}
    #createdAt: DateTime @1751039524 {#121746
      date: 2025-06-27 17:52:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121739
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121768 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121874
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121733}
        #id: 39693
        #name: "IEEE/ISO/IEC 12207:2017"
        #slug: "ieee-iso-iec-12207-2017-ieee00005672-242823"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction.<br />\n
          This International Standard applies to the acquisition of software systems, products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of any system, whether performed internally or externally to an organization. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project.<br />\n
          The processes, activities and tasks of this International Standard may also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288, Systems and software engineering—System life cycle processes.<br />\n
          In the context of this International Standard and ISO/IEC/IEEE 15288, it is recognized that there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system of interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this International Standard for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering-System life cycle processes, depends on the system of interest. Processes in both standards have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software system.<br />\n
          This International Standard is written for acquirers of software systems, products and services and for suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, and users of software systems and products. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations and the situation can range from an informal agreement to a formal contract.<br />\n
          The processes in this International Standard can be used as a basis for establishing business environments, e.g., methods, procedures, techniques, tools and trained personnel. Annex A provides normative direction regarding the tailoring of these software life cycle processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121766 …}
    #channels: Doctrine\ORM\PersistentCollection {#121759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121763 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121761 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121773 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121732
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121781
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1510700400 {#121752
      date: 2017-11-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 157
    -documents: Doctrine\ORM\PersistentCollection {#121772 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121770 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 484.0 MiB 1.13 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121733
    #id: 11171
    #code: "IEEE00005672"
    #attributes: Doctrine\ORM\PersistentCollection {#121757 …}
    #variants: Doctrine\ORM\PersistentCollection {#121755 …}
    #options: Doctrine\ORM\PersistentCollection {#121750 …}
    #associations: Doctrine\ORM\PersistentCollection {#121753 …}
    #createdAt: DateTime @1751039524 {#121746
      date: 2025-06-27 17:52:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121739
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121768 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121874
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121733}
        #id: 39693
        #name: "IEEE/ISO/IEC 12207:2017"
        #slug: "ieee-iso-iec-12207-2017-ieee00005672-242823"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction.<br />\n
          This International Standard applies to the acquisition of software systems, products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of any system, whether performed internally or externally to an organization. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project.<br />\n
          The processes, activities and tasks of this International Standard may also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288, Systems and software engineering—System life cycle processes.<br />\n
          In the context of this International Standard and ISO/IEC/IEEE 15288, it is recognized that there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system of interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this International Standard for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering-System life cycle processes, depends on the system of interest. Processes in both standards have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software system.<br />\n
          This International Standard is written for acquirers of software systems, products and services and for suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, and users of software systems and products. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations and the situation can range from an informal agreement to a formal contract.<br />\n
          The processes in this International Standard can be used as a basis for establishing business environments, e.g., methods, procedures, techniques, tools and trained personnel. Annex A provides normative direction regarding the tailoring of these software life cycle processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121766 …}
    #channels: Doctrine\ORM\PersistentCollection {#121759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121763 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121761 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121773 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121732
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121781
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1510700400 {#121752
      date: 2017-11-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 157
    -documents: Doctrine\ORM\PersistentCollection {#121772 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121770 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#121953
  +product: App\Entity\Product\Product {#121733
    #id: 11171
    #code: "IEEE00005672"
    #attributes: Doctrine\ORM\PersistentCollection {#121757 …}
    #variants: Doctrine\ORM\PersistentCollection {#121755 …}
    #options: Doctrine\ORM\PersistentCollection {#121750 …}
    #associations: Doctrine\ORM\PersistentCollection {#121753 …}
    #createdAt: DateTime @1751039524 {#121746
      date: 2025-06-27 17:52:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121739
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121768 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121874
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121733}
        #id: 39693
        #name: "IEEE/ISO/IEC 12207:2017"
        #slug: "ieee-iso-iec-12207-2017-ieee00005672-242823"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction.<br />\n
          This International Standard applies to the acquisition of software systems, products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of any system, whether performed internally or externally to an organization. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project.<br />\n
          The processes, activities and tasks of this International Standard may also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288, Systems and software engineering—System life cycle processes.<br />\n
          In the context of this International Standard and ISO/IEC/IEEE 15288, it is recognized that there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system of interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this International Standard for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering-System life cycle processes, depends on the system of interest. Processes in both standards have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.<br />\n
          The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software system.<br />\n
          This International Standard is written for acquirers of software systems, products and services and for suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, and users of software systems and products. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations and the situation can range from an informal agreement to a formal contract.<br />\n
          The processes in this International Standard can be used as a basis for establishing business environments, e.g., methods, procedures, techniques, tools and trained personnel. Annex A provides normative direction regarding the tailoring of these software life cycle processes.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121766 …}
    #channels: Doctrine\ORM\PersistentCollection {#121759 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121763 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121761 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121773 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121732
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121781
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1510700400 {#121752
      date: 2017-11-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 157
    -documents: Doctrine\ORM\PersistentCollection {#121772 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121770 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}