Symfony Profiler

Components

4 Twig Components

12 Render Count

14 ms Render Time

134.0 MiB Memory Usage

Components

Name	Metadata	Render Count	Render Time
ProductState	"App\Twig\Components\ProductState" components/ProductState.html.twig	5	2.65ms
ProductMostRecent	"App\Twig\Components\ProductMostRecent" components/ProductMostRecent.html.twig	5	3.88ms
ProductType	"App\Twig\Components\ProductType" components/ProductType.html.twig	1	0.53ms
ProductCard	"App\Twig\Components\ProductCard" components/ProductCard.html.twig	1	8.03ms

Render calls

ProductState	App\Twig\Components\ProductState	132.0 MiB	1.85 ms
Input props	["product" => App\Entity\Product\Product {#7310 #id: 10995 #code: "IEEE00005408" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039414 {#7274 date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#7322 date: 2025-08-08 01:00:11.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: 38989 #name: "IEEE/ISO/IEC 26511:2012" #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647" #description: """ Revision Standard - Superseded.<br />\n ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n \t\t\t\t<br />\n This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n team;<br />\n * measurements and estimates needed for management control;<br />\n * the application of management control to user documentation work;<br />\n * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n * managers of the software development process;<br />\n * acquirers of documentation prepared by suppliers;<br />\n * experienced writers who develop the written content for user documentation;<br />\n * developers of tools for creating on-screen documentation;<br />\n * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n * graphic designers with expertise in electronic media;<br />\n * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n and development, based on reuse of user documentation topics;<br />\n * documentation of products other than software;<br />\n * multimedia marketing presentations using animation, video, and sound;<br />\n * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n * maintenance documentation describing the internal operation of systems software.<br />\n NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n does not contain a purpose statement """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation" -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 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1331766000 {#7318 date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 54 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#93016+product: App\Entity\Product\Product {#7310 #id: 10995 #code: "IEEE00005408" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039414 {#7274 date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#7322 date: 2025-08-08 01:00:11.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: 38989 #name: "IEEE/ISO/IEC 26511:2012" #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647" #description: """ Revision Standard - Superseded.<br />\n ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n \t\t\t\t<br />\n This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n team;<br />\n * measurements and estimates needed for management control;<br />\n * the application of management control to user documentation work;<br />\n * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n * managers of the software development process;<br />\n * acquirers of documentation prepared by suppliers;<br />\n * experienced writers who develop the written content for user documentation;<br />\n * developers of tools for creating on-screen documentation;<br />\n * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n * graphic designers with expertise in electronic media;<br />\n * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n and development, based on reuse of user documentation topics;<br />\n * documentation of products other than software;<br />\n * multimedia marketing presentations using animation, video, and sound;<br />\n * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n * maintenance documentation describing the internal operation of systems software.<br />\n NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n does not contain a purpose statement """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation" -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 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1331766000 {#7318 date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 54 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

132.0 MiB

1.85 ms

Input props

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039414 {#7274
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.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: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#7318
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#93016
  +product: App\Entity\Product\Product {#7310
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039414 {#7274
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.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: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#7318
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -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	132.0 MiB	0.53 ms
Input props	["product" => App\Entity\Product\Product {#7310 #id: 10995 #code: "IEEE00005408" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039414 {#7274 date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#7322 date: 2025-08-08 01:00:11.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: 38989 #name: "IEEE/ISO/IEC 26511:2012" #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647" #description: """ Revision Standard - Superseded.<br />\n ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n \t\t\t\t<br />\n This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n team;<br />\n * measurements and estimates needed for management control;<br />\n * the application of management control to user documentation work;<br />\n * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n * managers of the software development process;<br />\n * acquirers of documentation prepared by suppliers;<br />\n * experienced writers who develop the written content for user documentation;<br />\n * developers of tools for creating on-screen documentation;<br />\n * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n * graphic designers with expertise in electronic media;<br />\n * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n and development, based on reuse of user documentation topics;<br />\n * documentation of products other than software;<br />\n * multimedia marketing presentations using animation, video, and sound;<br />\n * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n * maintenance documentation describing the internal operation of systems software.<br />\n NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n does not contain a purpose statement """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation" -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 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1331766000 {#7318 date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 54 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} }]
Attributes	[]
Component	App\Twig\Components\ProductType {#93187+product: App\Entity\Product\Product {#7310 #id: 10995 #code: "IEEE00005408" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039414 {#7274 date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#7322 date: 2025-08-08 01:00:11.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: 38989 #name: "IEEE/ISO/IEC 26511:2012" #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647" #description: """ Revision Standard - Superseded.<br />\n ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n \t\t\t\t<br />\n This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n team;<br />\n * measurements and estimates needed for management control;<br />\n * the application of management control to user documentation work;<br />\n * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n * managers of the software development process;<br />\n * acquirers of documentation prepared by suppliers;<br />\n * experienced writers who develop the written content for user documentation;<br />\n * developers of tools for creating on-screen documentation;<br />\n * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n * graphic designers with expertise in electronic media;<br />\n * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n and development, based on reuse of user documentation topics;<br />\n * documentation of products other than software;<br />\n * multimedia marketing presentations using animation, video, and sound;<br />\n * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n * maintenance documentation describing the internal operation of systems software.<br />\n NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n does not contain a purpose statement """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation" -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 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1331766000 {#7318 date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 54 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +label: "Standard" -typeAttributeCode: "type" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductType

App\Twig\Components\ProductType

132.0 MiB

0.53 ms

Input props

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039414 {#7274
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.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: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#7318
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductType {#93187
  +product: App\Entity\Product\Product {#7310
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039414 {#7274
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.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: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#7318
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -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	132.0 MiB	1.07 ms
Input props	["product" => App\Entity\Product\Product {#7310 #id: 10995 #code: "IEEE00005408" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039414 {#7274 date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#7322 date: 2025-08-08 01:00:11.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: 38989 #name: "IEEE/ISO/IEC 26511:2012" #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647" #description: """ Revision Standard - Superseded.<br />\n ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n \t\t\t\t<br />\n This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n team;<br />\n * measurements and estimates needed for management control;<br />\n * the application of management control to user documentation work;<br />\n * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n * managers of the software development process;<br />\n * acquirers of documentation prepared by suppliers;<br />\n * experienced writers who develop the written content for user documentation;<br />\n * developers of tools for creating on-screen documentation;<br />\n * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n * graphic designers with expertise in electronic media;<br />\n * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n and development, based on reuse of user documentation topics;<br />\n * documentation of products other than software;<br />\n * multimedia marketing presentations using animation, video, and sound;<br />\n * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n * maintenance documentation describing the internal operation of systems software.<br />\n NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n does not contain a purpose statement """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation" -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 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1331766000 {#7318 date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 54 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#93262+product: App\Entity\Product\Product {#7310 #id: 10995 #code: "IEEE00005408" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039414 {#7274 date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#7322 date: 2025-08-08 01:00:11.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: 38989 #name: "IEEE/ISO/IEC 26511:2012" #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647" #description: """ Revision Standard - Superseded.<br />\n ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n \t\t\t\t<br />\n This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n team;<br />\n * measurements and estimates needed for management control;<br />\n * the application of management control to user documentation work;<br />\n * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n * managers of the software development process;<br />\n * acquirers of documentation prepared by suppliers;<br />\n * experienced writers who develop the written content for user documentation;<br />\n * developers of tools for creating on-screen documentation;<br />\n * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n * graphic designers with expertise in electronic media;<br />\n * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n and development, based on reuse of user documentation topics;<br />\n * documentation of products other than software;<br />\n * multimedia marketing presentations using animation, video, and sound;<br />\n * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n * maintenance documentation describing the internal operation of systems software.<br />\n NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n does not contain a purpose statement """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation" -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 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1331766000 {#7318 date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 54 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

132.0 MiB

1.07 ms

Input props

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039414 {#7274
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.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: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#7318
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#93262
  +product: App\Entity\Product\Product {#7310
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039414 {#7274
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.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: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#7318
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -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	132.0 MiB	0.21 ms
Input props	["product" => App\Entity\Product\Product {#106699 #id: 9071 #code: "IEEE00001554" #attributes: Doctrine\ORM\PersistentCollection {#106680 …} #variants: Doctrine\ORM\PersistentCollection {#106677 …} #options: Doctrine\ORM\PersistentCollection {#106673 …} #associations: Doctrine\ORM\PersistentCollection {#106675 …} #createdAt: DateTime @1751037947 {#106706 date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754606304 {#106679 date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106690 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106729 #locale: "en_US" #translatable: App\Entity\Product\Product {#106699} #id: 31293 #name: "IEEE 1063:2001 (R2007)" #slug: "ieee-1063-2001-r2007-ieee00001554-240723" #description: """ Revision Standard - Superseded.<br />\n Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n \t\t\t\t<br />\n This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Software User Documentation" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106688 …} #channels: Doctrine\ORM\PersistentCollection {#106682 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#106686 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106684 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106697 …} -apiLastModifiedAt: DateTime @1754517600 {#106666 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106705 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1008802800 {#106704 date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1190844000 {#106698 date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1063" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#106695 …} -favorites: Doctrine\ORM\PersistentCollection {#106693 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#106713+product: App\Entity\Product\Product {#106699 #id: 9071 #code: "IEEE00001554" #attributes: Doctrine\ORM\PersistentCollection {#106680 …} #variants: Doctrine\ORM\PersistentCollection {#106677 …} #options: Doctrine\ORM\PersistentCollection {#106673 …} #associations: Doctrine\ORM\PersistentCollection {#106675 …} #createdAt: DateTime @1751037947 {#106706 date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754606304 {#106679 date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106690 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106729 #locale: "en_US" #translatable: App\Entity\Product\Product {#106699} #id: 31293 #name: "IEEE 1063:2001 (R2007)" #slug: "ieee-1063-2001-r2007-ieee00001554-240723" #description: """ Revision Standard - Superseded.<br />\n Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n \t\t\t\t<br />\n This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Software User Documentation" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106688 …} #channels: Doctrine\ORM\PersistentCollection {#106682 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#106686 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106684 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106697 …} -apiLastModifiedAt: DateTime @1754517600 {#106666 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106705 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1008802800 {#106704 date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1190844000 {#106698 date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1063" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#106695 …} -favorites: Doctrine\ORM\PersistentCollection {#106693 …} } +appearance: "state-suspended" +labels: [ "Superseded" "Confirmed" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

132.0 MiB

0.21 ms

Input props

[
  "product" => App\Entity\Product\Product {#106699
    #id: 9071
    #code: "IEEE00001554"
    #attributes: Doctrine\ORM\PersistentCollection {#106680 …}
    #variants: Doctrine\ORM\PersistentCollection {#106677 …}
    #options: Doctrine\ORM\PersistentCollection {#106673 …}
    #associations: Doctrine\ORM\PersistentCollection {#106675 …}
    #createdAt: DateTime @1751037947 {#106706
      date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106679
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106729
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106699}
        #id: 31293
        #name: "IEEE 1063:2001 (R2007)"
        #slug: "ieee-1063-2001-r2007-ieee00001554-240723"
        #description: """
          Revision Standard - Superseded.<br />\n
          Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n
          A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software User Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106688 …}
    #channels: Doctrine\ORM\PersistentCollection {#106682 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106684 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106697 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106666
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106705
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1008802800 {#106704
      date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1190844000 {#106698
      date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1063"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#106695 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106693 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#106713
  +product: App\Entity\Product\Product {#106699
    #id: 9071
    #code: "IEEE00001554"
    #attributes: Doctrine\ORM\PersistentCollection {#106680 …}
    #variants: Doctrine\ORM\PersistentCollection {#106677 …}
    #options: Doctrine\ORM\PersistentCollection {#106673 …}
    #associations: Doctrine\ORM\PersistentCollection {#106675 …}
    #createdAt: DateTime @1751037947 {#106706
      date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106679
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106729
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106699}
        #id: 31293
        #name: "IEEE 1063:2001 (R2007)"
        #slug: "ieee-1063-2001-r2007-ieee00001554-240723"
        #description: """
          Revision Standard - Superseded.<br />\n
          Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n
          A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software User Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106688 …}
    #channels: Doctrine\ORM\PersistentCollection {#106682 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106684 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106697 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106666
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106705
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1008802800 {#106704
      date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1190844000 {#106698
      date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1063"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#106695 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106693 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	132.0 MiB	0.70 ms
Input props	["product" => App\Entity\Product\Product {#106699 #id: 9071 #code: "IEEE00001554" #attributes: Doctrine\ORM\PersistentCollection {#106680 …} #variants: Doctrine\ORM\PersistentCollection {#106677 …} #options: Doctrine\ORM\PersistentCollection {#106673 …} #associations: Doctrine\ORM\PersistentCollection {#106675 …} #createdAt: DateTime @1751037947 {#106706 date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754606304 {#106679 date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106690 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106729 #locale: "en_US" #translatable: App\Entity\Product\Product {#106699} #id: 31293 #name: "IEEE 1063:2001 (R2007)" #slug: "ieee-1063-2001-r2007-ieee00001554-240723" #description: """ Revision Standard - Superseded.<br />\n Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n \t\t\t\t<br />\n This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Software User Documentation" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106688 …} #channels: Doctrine\ORM\PersistentCollection {#106682 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#106686 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106684 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106697 …} -apiLastModifiedAt: DateTime @1754517600 {#106666 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106705 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1008802800 {#106704 date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1190844000 {#106698 date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1063" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#106695 …} -favorites: Doctrine\ORM\PersistentCollection {#106693 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#106818+product: App\Entity\Product\Product {#106699 #id: 9071 #code: "IEEE00001554" #attributes: Doctrine\ORM\PersistentCollection {#106680 …} #variants: Doctrine\ORM\PersistentCollection {#106677 …} #options: Doctrine\ORM\PersistentCollection {#106673 …} #associations: Doctrine\ORM\PersistentCollection {#106675 …} #createdAt: DateTime @1751037947 {#106706 date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754606304 {#106679 date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106690 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106729 #locale: "en_US" #translatable: App\Entity\Product\Product {#106699} #id: 31293 #name: "IEEE 1063:2001 (R2007)" #slug: "ieee-1063-2001-r2007-ieee00001554-240723" #description: """ Revision Standard - Superseded.<br />\n Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n \t\t\t\t<br />\n This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Software User Documentation" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106688 …} #channels: Doctrine\ORM\PersistentCollection {#106682 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#106686 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106684 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106697 …} -apiLastModifiedAt: DateTime @1754517600 {#106666 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106705 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1008802800 {#106704 date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: DateTime @1190844000 {#106698 date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00) } -canceledAt: null -edition: null -coreDocument: "1063" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#106695 …} -favorites: Doctrine\ORM\PersistentCollection {#106693 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

132.0 MiB

0.70 ms

Input props

[
  "product" => App\Entity\Product\Product {#106699
    #id: 9071
    #code: "IEEE00001554"
    #attributes: Doctrine\ORM\PersistentCollection {#106680 …}
    #variants: Doctrine\ORM\PersistentCollection {#106677 …}
    #options: Doctrine\ORM\PersistentCollection {#106673 …}
    #associations: Doctrine\ORM\PersistentCollection {#106675 …}
    #createdAt: DateTime @1751037947 {#106706
      date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106679
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106729
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106699}
        #id: 31293
        #name: "IEEE 1063:2001 (R2007)"
        #slug: "ieee-1063-2001-r2007-ieee00001554-240723"
        #description: """
          Revision Standard - Superseded.<br />\n
          Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n
          A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software User Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106688 …}
    #channels: Doctrine\ORM\PersistentCollection {#106682 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106684 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106697 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106666
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106705
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1008802800 {#106704
      date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1190844000 {#106698
      date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1063"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#106695 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106693 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#106818
  +product: App\Entity\Product\Product {#106699
    #id: 9071
    #code: "IEEE00001554"
    #attributes: Doctrine\ORM\PersistentCollection {#106680 …}
    #variants: Doctrine\ORM\PersistentCollection {#106677 …}
    #options: Doctrine\ORM\PersistentCollection {#106673 …}
    #associations: Doctrine\ORM\PersistentCollection {#106675 …}
    #createdAt: DateTime @1751037947 {#106706
      date: 2025-06-27 17:25:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#106679
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106729
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106699}
        #id: 31293
        #name: "IEEE 1063:2001 (R2007)"
        #slug: "ieee-1063-2001-r2007-ieee00001554-240723"
        #description: """
          Revision Standard - Superseded.<br />\n
          Minimum requirements for the structure, information content, and format of user docu-mentation, including both printed and electronic documents used in the work environment by usersof systems containing software, are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides minimum requirements for the structure, information content, and format of user documentation, to include both paper and electronic documentation used in the work environment by users of systems containing software. The standard is limited to the software documentation product and will not include the processes of developing or managing software user documentation. The standard includes printed user manuals, online help, and user reference documentation. It does not apply to specialized course materials intended primarily for use in formal training programs.<br />\n
          A timely revision of Std 1063 will update the existing standard, which addresses paper documentation only, to provide requirements for the structure, information content and format of electronic documentation as well. The revised standard will address the interests of software acquirers, producers, and users in standards for consistent, complete, accurate, and usable documentation.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software User Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106688 …}
    #channels: Doctrine\ORM\PersistentCollection {#106682 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106684 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106697 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106666
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106705
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1008802800 {#106704
      date: 2001-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1190844000 {#106698
      date: 2007-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1063"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#106695 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106693 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductState	App\Twig\Components\ProductState	132.0 MiB	0.19 ms
Input props	["product" => App\Entity\Product\Product {#93699 #id: 12069 #code: "IEEE00007030" #attributes: Doctrine\ORM\PersistentCollection {#93681 …} #variants: Doctrine\ORM\PersistentCollection {#93678 …} #options: Doctrine\ORM\PersistentCollection {#93674 …} #associations: Doctrine\ORM\PersistentCollection {#93676 …} #createdAt: DateTime @1751040177 {#93707 date: 2025-06-27 18:02:57.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#93686 date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93692 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93727 #locale: "en_US" #translatable: App\Entity\Product\Product {#93699} #id: 43285 #name: "IEEE/ISO/IEC 26511:2018" #slug: "ieee-iso-iec-26511-2018-ieee00007030-243721" #description: """ Revision Standard - Active.<br />\n <br />\n \t\t\t\t<br />\n This document supports the needs of users for consistent, complete, accurate, and usable information. It provides requirements for strategy, planning, managing, staffing, translation, production, and quality and process-maturity assessment for managers of information for users. It specifies processes and procedures for managing information for users throughout the product- or systems-development life cycle. It also includes requirements for key documents produced for managing information for users, including strategic and project plans. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for managers of information for users of systems, software, and services" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …} #channels: Doctrine\ORM\PersistentCollection {#93683 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93688 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93685 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …} -apiLastModifiedAt: DateTime @1754517600 {#93670 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#93706 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1545260400 {#93705 date: 2018-12-20 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 90 -documents: Doctrine\ORM\PersistentCollection {#93696 …} -favorites: Doctrine\ORM\PersistentCollection {#93694 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#113432+product: App\Entity\Product\Product {#93699 #id: 12069 #code: "IEEE00007030" #attributes: Doctrine\ORM\PersistentCollection {#93681 …} #variants: Doctrine\ORM\PersistentCollection {#93678 …} #options: Doctrine\ORM\PersistentCollection {#93674 …} #associations: Doctrine\ORM\PersistentCollection {#93676 …} #createdAt: DateTime @1751040177 {#93707 date: 2025-06-27 18:02:57.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#93686 date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93692 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93727 #locale: "en_US" #translatable: App\Entity\Product\Product {#93699} #id: 43285 #name: "IEEE/ISO/IEC 26511:2018" #slug: "ieee-iso-iec-26511-2018-ieee00007030-243721" #description: """ Revision Standard - Active.<br />\n <br />\n \t\t\t\t<br />\n This document supports the needs of users for consistent, complete, accurate, and usable information. It provides requirements for strategy, planning, managing, staffing, translation, production, and quality and process-maturity assessment for managers of information for users. It specifies processes and procedures for managing information for users throughout the product- or systems-development life cycle. It also includes requirements for key documents produced for managing information for users, including strategic and project plans. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for managers of information for users of systems, software, and services" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …} #channels: Doctrine\ORM\PersistentCollection {#93683 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93688 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93685 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …} -apiLastModifiedAt: DateTime @1754517600 {#93670 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#93706 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1545260400 {#93705 date: 2018-12-20 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 90 -documents: Doctrine\ORM\PersistentCollection {#93696 …} -favorites: Doctrine\ORM\PersistentCollection {#93694 …} } +appearance: "state-active" +labels: [ "Active" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

132.0 MiB

0.19 ms

Input props

[
  "product" => App\Entity\Product\Product {#93699
    #id: 12069
    #code: "IEEE00007030"
    #attributes: Doctrine\ORM\PersistentCollection {#93681 …}
    #variants: Doctrine\ORM\PersistentCollection {#93678 …}
    #options: Doctrine\ORM\PersistentCollection {#93674 …}
    #associations: Doctrine\ORM\PersistentCollection {#93676 …}
    #createdAt: DateTime @1751040177 {#93707
      date: 2025-06-27 18:02:57.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93686
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93727
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 43285
        #name: "IEEE/ISO/IEC 26511:2018"
        #slug: "ieee-iso-iec-26511-2018-ieee00007030-243721"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the needs of users for consistent, complete, accurate, and usable information. It provides requirements for strategy, planning, managing, staffing, translation, production, and quality and process-maturity assessment for managers of information for users. It specifies processes and procedures for managing information for users throughout the product- or systems-development life cycle. It also includes requirements for key documents produced for managing information for users, including strategic and project plans.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for managers of information for users of systems, software, and services"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …}
    #channels: Doctrine\ORM\PersistentCollection {#93683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93688 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93670
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93706
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1545260400 {#93705
      date: 2018-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#93696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93694 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#113432
  +product: App\Entity\Product\Product {#93699
    #id: 12069
    #code: "IEEE00007030"
    #attributes: Doctrine\ORM\PersistentCollection {#93681 …}
    #variants: Doctrine\ORM\PersistentCollection {#93678 …}
    #options: Doctrine\ORM\PersistentCollection {#93674 …}
    #associations: Doctrine\ORM\PersistentCollection {#93676 …}
    #createdAt: DateTime @1751040177 {#93707
      date: 2025-06-27 18:02:57.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93686
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93727
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 43285
        #name: "IEEE/ISO/IEC 26511:2018"
        #slug: "ieee-iso-iec-26511-2018-ieee00007030-243721"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the needs of users for consistent, complete, accurate, and usable information. It provides requirements for strategy, planning, managing, staffing, translation, production, and quality and process-maturity assessment for managers of information for users. It specifies processes and procedures for managing information for users throughout the product- or systems-development life cycle. It also includes requirements for key documents produced for managing information for users, including strategic and project plans.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for managers of information for users of systems, software, and services"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …}
    #channels: Doctrine\ORM\PersistentCollection {#93683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93688 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93670
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93706
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1545260400 {#93705
      date: 2018-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#93696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93694 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	132.0 MiB	0.71 ms
Input props	["product" => App\Entity\Product\Product {#93699 #id: 12069 #code: "IEEE00007030" #attributes: Doctrine\ORM\PersistentCollection {#93681 …} #variants: Doctrine\ORM\PersistentCollection {#93678 …} #options: Doctrine\ORM\PersistentCollection {#93674 …} #associations: Doctrine\ORM\PersistentCollection {#93676 …} #createdAt: DateTime @1751040177 {#93707 date: 2025-06-27 18:02:57.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#93686 date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93692 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93727 #locale: "en_US" #translatable: App\Entity\Product\Product {#93699} #id: 43285 #name: "IEEE/ISO/IEC 26511:2018" #slug: "ieee-iso-iec-26511-2018-ieee00007030-243721" #description: """ Revision Standard - Active.<br />\n <br />\n \t\t\t\t<br />\n This document supports the needs of users for consistent, complete, accurate, and usable information. It provides requirements for strategy, planning, managing, staffing, translation, production, and quality and process-maturity assessment for managers of information for users. It specifies processes and procedures for managing information for users throughout the product- or systems-development life cycle. It also includes requirements for key documents produced for managing information for users, including strategic and project plans. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for managers of information for users of systems, software, and services" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …} #channels: Doctrine\ORM\PersistentCollection {#93683 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93688 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93685 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …} -apiLastModifiedAt: DateTime @1754517600 {#93670 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#93706 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1545260400 {#93705 date: 2018-12-20 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 90 -documents: Doctrine\ORM\PersistentCollection {#93696 …} -favorites: Doctrine\ORM\PersistentCollection {#93694 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#113499+product: App\Entity\Product\Product {#93699 #id: 12069 #code: "IEEE00007030" #attributes: Doctrine\ORM\PersistentCollection {#93681 …} #variants: Doctrine\ORM\PersistentCollection {#93678 …} #options: Doctrine\ORM\PersistentCollection {#93674 …} #associations: Doctrine\ORM\PersistentCollection {#93676 …} #createdAt: DateTime @1751040177 {#93707 date: 2025-06-27 18:02:57.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#93686 date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93692 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93727 #locale: "en_US" #translatable: App\Entity\Product\Product {#93699} #id: 43285 #name: "IEEE/ISO/IEC 26511:2018" #slug: "ieee-iso-iec-26511-2018-ieee00007030-243721" #description: """ Revision Standard - Active.<br />\n <br />\n \t\t\t\t<br />\n This document supports the needs of users for consistent, complete, accurate, and usable information. It provides requirements for strategy, planning, managing, staffing, translation, production, and quality and process-maturity assessment for managers of information for users. It specifies processes and procedures for managing information for users throughout the product- or systems-development life cycle. It also includes requirements for key documents produced for managing information for users, including strategic and project plans. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for managers of information for users of systems, software, and services" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …} #channels: Doctrine\ORM\PersistentCollection {#93683 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93688 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93685 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …} -apiLastModifiedAt: DateTime @1754517600 {#93670 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#93706 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1545260400 {#93705 date: 2018-12-20 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 90 -documents: Doctrine\ORM\PersistentCollection {#93696 …} -favorites: Doctrine\ORM\PersistentCollection {#93694 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

132.0 MiB

0.71 ms

Input props

[
  "product" => App\Entity\Product\Product {#93699
    #id: 12069
    #code: "IEEE00007030"
    #attributes: Doctrine\ORM\PersistentCollection {#93681 …}
    #variants: Doctrine\ORM\PersistentCollection {#93678 …}
    #options: Doctrine\ORM\PersistentCollection {#93674 …}
    #associations: Doctrine\ORM\PersistentCollection {#93676 …}
    #createdAt: DateTime @1751040177 {#93707
      date: 2025-06-27 18:02:57.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93686
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93727
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 43285
        #name: "IEEE/ISO/IEC 26511:2018"
        #slug: "ieee-iso-iec-26511-2018-ieee00007030-243721"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the needs of users for consistent, complete, accurate, and usable information. It provides requirements for strategy, planning, managing, staffing, translation, production, and quality and process-maturity assessment for managers of information for users. It specifies processes and procedures for managing information for users throughout the product- or systems-development life cycle. It also includes requirements for key documents produced for managing information for users, including strategic and project plans.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for managers of information for users of systems, software, and services"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …}
    #channels: Doctrine\ORM\PersistentCollection {#93683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93688 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93670
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93706
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1545260400 {#93705
      date: 2018-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#93696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93694 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#113499
  +product: App\Entity\Product\Product {#93699
    #id: 12069
    #code: "IEEE00007030"
    #attributes: Doctrine\ORM\PersistentCollection {#93681 …}
    #variants: Doctrine\ORM\PersistentCollection {#93678 …}
    #options: Doctrine\ORM\PersistentCollection {#93674 …}
    #associations: Doctrine\ORM\PersistentCollection {#93676 …}
    #createdAt: DateTime @1751040177 {#93707
      date: 2025-06-27 18:02:57.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93686
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93727
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 43285
        #name: "IEEE/ISO/IEC 26511:2018"
        #slug: "ieee-iso-iec-26511-2018-ieee00007030-243721"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document supports the needs of users for consistent, complete, accurate, and usable information. It provides requirements for strategy, planning, managing, staffing, translation, production, and quality and process-maturity assessment for managers of information for users. It specifies processes and procedures for managing information for users throughout the product- or systems-development life cycle. It also includes requirements for key documents produced for managing information for users, including strategic and project plans.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for managers of information for users of systems, software, and services"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93690 …}
    #channels: Doctrine\ORM\PersistentCollection {#93683 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93688 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93685 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93700 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93670
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93706
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1545260400 {#93705
      date: 2018-12-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 90
    -documents: Doctrine\ORM\PersistentCollection {#93696 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93694 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductState	App\Twig\Components\ProductState	132.0 MiB	0.21 ms
Input props	["product" => App\Entity\Product\Product {#7310 #id: 10995 #code: "IEEE00005408" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039414 {#7274 date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#7322 date: 2025-08-08 01:00:11.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: 38989 #name: "IEEE/ISO/IEC 26511:2012" #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647" #description: """ Revision Standard - Superseded.<br />\n ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n \t\t\t\t<br />\n This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n team;<br />\n * measurements and estimates needed for management control;<br />\n * the application of management control to user documentation work;<br />\n * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n * managers of the software development process;<br />\n * acquirers of documentation prepared by suppliers;<br />\n * experienced writers who develop the written content for user documentation;<br />\n * developers of tools for creating on-screen documentation;<br />\n * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n * graphic designers with expertise in electronic media;<br />\n * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n and development, based on reuse of user documentation topics;<br />\n * documentation of products other than software;<br />\n * multimedia marketing presentations using animation, video, and sound;<br />\n * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n * maintenance documentation describing the internal operation of systems software.<br />\n NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n does not contain a purpose statement """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation" -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 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1331766000 {#7318 date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 54 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#113564+product: App\Entity\Product\Product {#7310 #id: 10995 #code: "IEEE00005408" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039414 {#7274 date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#7322 date: 2025-08-08 01:00:11.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: 38989 #name: "IEEE/ISO/IEC 26511:2012" #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647" #description: """ Revision Standard - Superseded.<br />\n ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n \t\t\t\t<br />\n This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n team;<br />\n * measurements and estimates needed for management control;<br />\n * the application of management control to user documentation work;<br />\n * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n * managers of the software development process;<br />\n * acquirers of documentation prepared by suppliers;<br />\n * experienced writers who develop the written content for user documentation;<br />\n * developers of tools for creating on-screen documentation;<br />\n * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n * graphic designers with expertise in electronic media;<br />\n * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n and development, based on reuse of user documentation topics;<br />\n * documentation of products other than software;<br />\n * multimedia marketing presentations using animation, video, and sound;<br />\n * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n * maintenance documentation describing the internal operation of systems software.<br />\n NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n does not contain a purpose statement """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation" -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 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1331766000 {#7318 date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 54 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

132.0 MiB

0.21 ms

Input props

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039414 {#7274
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.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: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#7318
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#113564
  +product: App\Entity\Product\Product {#7310
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039414 {#7274
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.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: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#7318
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -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	132.0 MiB	0.73 ms
Input props	["product" => App\Entity\Product\Product {#7310 #id: 10995 #code: "IEEE00005408" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039414 {#7274 date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#7322 date: 2025-08-08 01:00:11.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: 38989 #name: "IEEE/ISO/IEC 26511:2012" #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647" #description: """ Revision Standard - Superseded.<br />\n ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n \t\t\t\t<br />\n This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n team;<br />\n * measurements and estimates needed for management control;<br />\n * the application of management control to user documentation work;<br />\n * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n * managers of the software development process;<br />\n * acquirers of documentation prepared by suppliers;<br />\n * experienced writers who develop the written content for user documentation;<br />\n * developers of tools for creating on-screen documentation;<br />\n * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n * graphic designers with expertise in electronic media;<br />\n * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n and development, based on reuse of user documentation topics;<br />\n * documentation of products other than software;<br />\n * multimedia marketing presentations using animation, video, and sound;<br />\n * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n * maintenance documentation describing the internal operation of systems software.<br />\n NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n does not contain a purpose statement """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation" -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 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1331766000 {#7318 date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 54 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#113591+product: App\Entity\Product\Product {#7310 #id: 10995 #code: "IEEE00005408" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039414 {#7274 date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#7322 date: 2025-08-08 01:00:11.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: 38989 #name: "IEEE/ISO/IEC 26511:2012" #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647" #description: """ Revision Standard - Superseded.<br />\n ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n \t\t\t\t<br />\n This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n team;<br />\n * measurements and estimates needed for management control;<br />\n * the application of management control to user documentation work;<br />\n * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n * managers of the software development process;<br />\n * acquirers of documentation prepared by suppliers;<br />\n * experienced writers who develop the written content for user documentation;<br />\n * developers of tools for creating on-screen documentation;<br />\n * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n * graphic designers with expertise in electronic media;<br />\n * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n and development, based on reuse of user documentation topics;<br />\n * documentation of products other than software;<br />\n * multimedia marketing presentations using animation, video, and sound;<br />\n * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n * maintenance documentation describing the internal operation of systems software.<br />\n NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n does not contain a purpose statement """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation" -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 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1331766000 {#7318 date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "26511" -bookCollection: "" -pageCount: 54 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

132.0 MiB

0.73 ms

Input props

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039414 {#7274
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.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: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#7318
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#113591
  +product: App\Entity\Product\Product {#7310
    #id: 10995
    #code: "IEEE00005408"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039414 {#7274
      date: 2025-06-27 17:50:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#7322
      date: 2025-08-08 01:00:11.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: 38989
        #name: "IEEE/ISO/IEC 26511:2012"
        #slug: "ieee-iso-iec-26511-2012-ieee00005408-242647"
        #description: """
          Revision Standard - Superseded.<br />\n
          ISO/IEC/IEEE 26511:2012 specifies procedures for managing user documentation throughout the software life cycle. It applies to people or organizations producing suites of documentation, to those undertaking a single documentation project, and to documentation produced internally, as well as to documentation contracted to outside service organizations. It provides an overview of the software documentation and information management processes, and also presents aspects of portfolio planning and content management that user documentation managers apply.<br />\n
          It covers management activities in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team. It includes examples of roles needed on a user documentation team. It addresses measurements and estimates needed for management control, and the use of supporting processes such as change management, schedule and cost control, resource management, and quality management and process improvement. It includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans. ISO/IEC/IEEE 26511:2012 is independent of the software tools that may be used to produce or manage documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software.<br />\n
          \t\t\t\t<br />\n
          This International Standard supports the needs of software users for consistent, complete, accurate, and usable documentation. It provides requirements for strategy, planning, performance, and control for documentation managers. It specifies procedures for managing user documentation throughout the software life cycle. It also includes requirements for key documents produced for user documentation management, including documentation plans and documentation management plans.<br />\n
          This International Standard provides an overview of the software documentation and information management processes which are specialized for user documentation in this International Standard. It also presents aspects of portfolio planning and content management for user documentation. Specifically, it addresses the following:<br />\n
          * management requirements in starting a project, including setting up procedures and specifications, establishing infrastructure, and building a team, with examples of roles needed on a user documentation<br />\n
          team;<br />\n
          * measurements and estimates needed for management control;<br />\n
          * the application of management control to user documentation work;<br />\n
          * the use of supporting processes such as change management, schedule and cost control, resource management, quality management and process improvement.<br />\n
          The works listed in the Bibliography provide guidance on the processes of managing, preparing, and testing user documentation.<br />\n
          NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering -- Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering -- Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering -- Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -- Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software<br />\n
          engineering -- Requirements for acquirers and suppliers of user documentation.<br />\n
          This International Standard is applicable for use by managers of user documentation projects or organizations with information designers and documentation developers. This International Standard may also be consulted by those with other roles and interests in the documentation process:<br />\n
          * managers of the software development process;<br />\n
          * acquirers of documentation prepared by suppliers;<br />\n
          * experienced writers who develop the written content for user documentation;<br />\n
          * developers of tools for creating on-screen documentation;<br />\n
          * human-factors experts who identify principles for making documentation more accessible and easily used;<br />\n
          * graphic designers with expertise in electronic media;<br />\n
          * user interface designers and ergonomics experts working together to design the presentation of the documentation on the screen.<br />\n
          This International Standard may be applied to manage the following types of documentation, although it does not cover all aspects of them:<br />\n
          * documentation for user assistance, training, marketing, and systems documentation for product design<br />\n
          and development, based on reuse of user documentation topics;<br />\n
          * documentation of products other than software;<br />\n
          * multimedia marketing presentations using animation, video, and sound;<br />\n
          * computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<br />\n
          * maintenance documentation describing the internal operation of systems software.<br />\n
          NOTE 2: ISO/IEC/IEEE 15289:2011 provides more detailed content for life-cycle process information items (documentation).<br />\n
          does not contain a purpose statement
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Requirements for managers of user documentation"
        -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
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1331766000 {#7318
      date: 2012-03-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26511"
    -bookCollection: ""
    -pageCount: 54
    -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	134.0 MiB	8.03 ms
Input props	["product" => App\Entity\Product\Product {#135059 #id: 10372 #code: "IEEE00004260" #attributes: Doctrine\ORM\PersistentCollection {#135083 …} #variants: Doctrine\ORM\PersistentCollection {#135081 …} #options: Doctrine\ORM\PersistentCollection {#135076 …} #associations: Doctrine\ORM\PersistentCollection {#135079 …} #createdAt: DateTime @1751039021 {#135072 date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#135065 date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135094 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135190 #locale: "en_US" #translatable: App\Entity\Product\Product {#135059} #id: 36497 #name: "IEEE/ISO/IEC 12207:2008" #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024" #description: """ Revision Standard - Superseded.<br />\n Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n software.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …} #channels: Doctrine\ORM\PersistentCollection {#135085 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#135089 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135087 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …} -apiLastModifiedAt: DateTime @1754517600 {#135058 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135107 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1201734000 {#135078 date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "12207" -bookCollection: "" -pageCount: 138 -documents: Doctrine\ORM\PersistentCollection {#135098 …} -favorites: Doctrine\ORM\PersistentCollection {#135096 …} } "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 {#135151+product: App\Entity\Product\Product {#135059 #id: 10372 #code: "IEEE00004260" #attributes: Doctrine\ORM\PersistentCollection {#135083 …} #variants: Doctrine\ORM\PersistentCollection {#135081 …} #options: Doctrine\ORM\PersistentCollection {#135076 …} #associations: Doctrine\ORM\PersistentCollection {#135079 …} #createdAt: DateTime @1751039021 {#135072 date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#135065 date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135094 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135190 #locale: "en_US" #translatable: App\Entity\Product\Product {#135059} #id: 36497 #name: "IEEE/ISO/IEC 12207:2008" #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024" #description: """ Revision Standard - Superseded.<br />\n Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n software.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …} #channels: Doctrine\ORM\PersistentCollection {#135085 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#135089 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135087 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …} -apiLastModifiedAt: DateTime @1754517600 {#135058 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135107 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1201734000 {#135078 date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "12207" -bookCollection: "" -pageCount: 138 -documents: Doctrine\ORM\PersistentCollection {#135098 …} -favorites: Doctrine\ORM\PersistentCollection {#135096 …} } +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"}

ProductCard

App\Twig\Components\ProductCard

134.0 MiB

8.03 ms

Input props

[
  "product" => App\Entity\Product\Product {#135059
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135083 …}
    #variants: Doctrine\ORM\PersistentCollection {#135081 …}
    #options: Doctrine\ORM\PersistentCollection {#135076 …}
    #associations: Doctrine\ORM\PersistentCollection {#135079 …}
    #createdAt: DateTime @1751039021 {#135072
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135065
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135094 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135190
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135059}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …}
    #channels: Doctrine\ORM\PersistentCollection {#135085 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135089 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135087 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135058
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135107
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135078
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135098 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135096 …}
  }
  "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 {#135151
  +product: App\Entity\Product\Product {#135059
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135083 …}
    #variants: Doctrine\ORM\PersistentCollection {#135081 …}
    #options: Doctrine\ORM\PersistentCollection {#135076 …}
    #associations: Doctrine\ORM\PersistentCollection {#135079 …}
    #createdAt: DateTime @1751039021 {#135072
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135065
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135094 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135190
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135059}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …}
    #channels: Doctrine\ORM\PersistentCollection {#135085 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135089 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135087 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135058
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135107
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135078
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135098 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135096 …}
  }
  +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	134.0 MiB	0.19 ms
Input props	["product" => App\Entity\Product\Product {#135059 #id: 10372 #code: "IEEE00004260" #attributes: Doctrine\ORM\PersistentCollection {#135083 …} #variants: Doctrine\ORM\PersistentCollection {#135081 …} #options: Doctrine\ORM\PersistentCollection {#135076 …} #associations: Doctrine\ORM\PersistentCollection {#135079 …} #createdAt: DateTime @1751039021 {#135072 date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#135065 date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135094 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135190 #locale: "en_US" #translatable: App\Entity\Product\Product {#135059} #id: 36497 #name: "IEEE/ISO/IEC 12207:2008" #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024" #description: """ Revision Standard - Superseded.<br />\n Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n software.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …} #channels: Doctrine\ORM\PersistentCollection {#135085 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#135089 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135087 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …} -apiLastModifiedAt: DateTime @1754517600 {#135058 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135107 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1201734000 {#135078 date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "12207" -bookCollection: "" -pageCount: 138 -documents: Doctrine\ORM\PersistentCollection {#135098 …} -favorites: Doctrine\ORM\PersistentCollection {#135096 …} }]
Attributes	[`"showFullLabel" => false`]
Component	App\Twig\Components\ProductState {#135192+product: App\Entity\Product\Product {#135059 #id: 10372 #code: "IEEE00004260" #attributes: Doctrine\ORM\PersistentCollection {#135083 …} #variants: Doctrine\ORM\PersistentCollection {#135081 …} #options: Doctrine\ORM\PersistentCollection {#135076 …} #associations: Doctrine\ORM\PersistentCollection {#135079 …} #createdAt: DateTime @1751039021 {#135072 date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#135065 date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135094 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135190 #locale: "en_US" #translatable: App\Entity\Product\Product {#135059} #id: 36497 #name: "IEEE/ISO/IEC 12207:2008" #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024" #description: """ Revision Standard - Superseded.<br />\n Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n software.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …} #channels: Doctrine\ORM\PersistentCollection {#135085 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#135089 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135087 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …} -apiLastModifiedAt: DateTime @1754517600 {#135058 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135107 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1201734000 {#135078 date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "12207" -bookCollection: "" -pageCount: 138 -documents: Doctrine\ORM\PersistentCollection {#135098 …} -favorites: Doctrine\ORM\PersistentCollection {#135096 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

134.0 MiB

0.19 ms

Input props

[
  "product" => App\Entity\Product\Product {#135059
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135083 …}
    #variants: Doctrine\ORM\PersistentCollection {#135081 …}
    #options: Doctrine\ORM\PersistentCollection {#135076 …}
    #associations: Doctrine\ORM\PersistentCollection {#135079 …}
    #createdAt: DateTime @1751039021 {#135072
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135065
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135094 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135190
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135059}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …}
    #channels: Doctrine\ORM\PersistentCollection {#135085 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135089 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135087 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135058
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135107
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135078
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135098 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135096 …}
  }
]

Attributes

[
  "showFullLabel" => false
]

Component

App\Twig\Components\ProductState {#135192
  +product: App\Entity\Product\Product {#135059
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135083 …}
    #variants: Doctrine\ORM\PersistentCollection {#135081 …}
    #options: Doctrine\ORM\PersistentCollection {#135076 …}
    #associations: Doctrine\ORM\PersistentCollection {#135079 …}
    #createdAt: DateTime @1751039021 {#135072
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135065
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135094 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135190
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135059}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …}
    #channels: Doctrine\ORM\PersistentCollection {#135085 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135089 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135087 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135058
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135107
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135078
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135098 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135096 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	134.0 MiB	0.67 ms
Input props	["product" => App\Entity\Product\Product {#135059 #id: 10372 #code: "IEEE00004260" #attributes: Doctrine\ORM\PersistentCollection {#135083 …} #variants: Doctrine\ORM\PersistentCollection {#135081 …} #options: Doctrine\ORM\PersistentCollection {#135076 …} #associations: Doctrine\ORM\PersistentCollection {#135079 …} #createdAt: DateTime @1751039021 {#135072 date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#135065 date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135094 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135190 #locale: "en_US" #translatable: App\Entity\Product\Product {#135059} #id: 36497 #name: "IEEE/ISO/IEC 12207:2008" #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024" #description: """ Revision Standard - Superseded.<br />\n Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n software.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …} #channels: Doctrine\ORM\PersistentCollection {#135085 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#135089 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135087 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …} -apiLastModifiedAt: DateTime @1754517600 {#135058 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135107 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1201734000 {#135078 date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "12207" -bookCollection: "" -pageCount: 138 -documents: Doctrine\ORM\PersistentCollection {#135098 …} -favorites: Doctrine\ORM\PersistentCollection {#135096 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#135269+product: App\Entity\Product\Product {#135059 #id: 10372 #code: "IEEE00004260" #attributes: Doctrine\ORM\PersistentCollection {#135083 …} #variants: Doctrine\ORM\PersistentCollection {#135081 …} #options: Doctrine\ORM\PersistentCollection {#135076 …} #associations: Doctrine\ORM\PersistentCollection {#135079 …} #createdAt: DateTime @1751039021 {#135072 date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#135065 date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135094 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135190 #locale: "en_US" #translatable: App\Entity\Product\Product {#135059} #id: 36497 #name: "IEEE/ISO/IEC 12207:2008" #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024" #description: """ Revision Standard - Superseded.<br />\n Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n software.<br />\n This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …} #channels: Doctrine\ORM\PersistentCollection {#135085 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#135089 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135087 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …} -apiLastModifiedAt: DateTime @1754517600 {#135058 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135107 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1201734000 {#135078 date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "12207" -bookCollection: "" -pageCount: 138 -documents: Doctrine\ORM\PersistentCollection {#135098 …} -favorites: Doctrine\ORM\PersistentCollection {#135096 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

134.0 MiB

0.67 ms

Input props

[
  "product" => App\Entity\Product\Product {#135059
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135083 …}
    #variants: Doctrine\ORM\PersistentCollection {#135081 …}
    #options: Doctrine\ORM\PersistentCollection {#135076 …}
    #associations: Doctrine\ORM\PersistentCollection {#135079 …}
    #createdAt: DateTime @1751039021 {#135072
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135065
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135094 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135190
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135059}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …}
    #channels: Doctrine\ORM\PersistentCollection {#135085 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135089 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135087 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135058
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135107
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135078
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135098 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135096 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#135269
  +product: App\Entity\Product\Product {#135059
    #id: 10372
    #code: "IEEE00004260"
    #attributes: Doctrine\ORM\PersistentCollection {#135083 …}
    #variants: Doctrine\ORM\PersistentCollection {#135081 …}
    #options: Doctrine\ORM\PersistentCollection {#135076 …}
    #associations: Doctrine\ORM\PersistentCollection {#135079 …}
    #createdAt: DateTime @1751039021 {#135072
      date: 2025-06-27 17:43:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135065
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135094 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135190
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135059}
        #id: 36497
        #name: "IEEE/ISO/IEC 12207:2008"
        #slug: "ieee-iso-iec-12207-2008-ieee00004260-242024"
        #description: """
          Revision Standard - Superseded.<br />\n
          Supersedes Std. 12207.0 and also makes 12207.2 obsolete. This International Standard was jointly developed by ISO/IEC and IEEE. 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 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards.<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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.<br />\n
          This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.<br />\n
          This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.<br />\n
          The processes, activities and tasks of this International Standard either alone or in conjunction with ISO/IEC 15288—may also be applied during the acquisition of a system that contains software.<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 product.<br />\n
          This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-the-shelf<br />\n
          software.<br />\n
          This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of 0ff-the-shelf software.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering -- Software life cycle processes"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135092 …}
    #channels: Doctrine\ORM\PersistentCollection {#135085 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135089 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135087 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135099 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135058
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135107
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1201734000 {#135078
      date: 2008-01-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "12207"
    -bookCollection: ""
    -pageCount: 138
    -documents: Doctrine\ORM\PersistentCollection {#135098 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135096 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

Symfony Profiler

GET https://dev.normadoc.fr/_partial/products/10995/associations/12830/sort?fieldSort=%7B%22publishedAt%22%3A%22DESC%22%7D&isSubscriberDashboard=0&template=%40Syliu…

Configuration Settings

Theme

Page Width

Components

Components

Render calls