GET https://dev.normadoc.fr/products/ieee-1058-1-1987-r1993-ieee00001543-240716

Response
200 OK
IP
216.73.216.2
Profiled on
Token
71dc0f

Components

4 Twig Components
8 Render Count
14 ms Render Time
96.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		3 1.02ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		3 3.02ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.29ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		1 11.18ms

Render calls

ProductState App\Twig\Components\ProductState 74.0 MiB 0.45 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 9064
    #code: "IEEE00001543"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037941 {#7536
      date: 2025-06-27 17:25:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31265
        #name: "IEEE 1058.1:1987 (R1993)"
        #slug: "ieee-1058-1-1987-r1993-ieee00001543-240716"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised as IEEE Std 1058-1998. The format and content of software project management plans are prescribed. By software project plan is meant the controlling document that defines the technical and managerial processes necessary to satisfy the project requirements. The requirements are applicable to all types of software projects and to software products of any size, complexity, or criticality at any point in the life cycle. All forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon are included.<br />\n
          \t\t\t\t<br />\n
          This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.<br />\n
          This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in silicon. This standard can be applied to any and all segments of a software product lifecycle.<br />\n
          This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format speciÞed in this standard.<br />\n
          Various sections and subsections of a software project management plan may be included in the plan<br />\n
          by direct incorporation or by reference to other plans and documents.<br />\n
          This standard for software project management plans incorporates and subsumes the software development plans described in ANSI/IEEE Std 729-1983 [1] and ANSI/IEEE Std 730-1984 [2].
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Project Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @588981600 {#7531
      date: 1988-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#7521
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1058.1"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#95003
  +product: App\Entity\Product\Product {#7519
    #id: 9064
    #code: "IEEE00001543"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037941 {#7536
      date: 2025-06-27 17:25:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31265
        #name: "IEEE 1058.1:1987 (R1993)"
        #slug: "ieee-1058-1-1987-r1993-ieee00001543-240716"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised as IEEE Std 1058-1998. The format and content of software project management plans are prescribed. By software project plan is meant the controlling document that defines the technical and managerial processes necessary to satisfy the project requirements. The requirements are applicable to all types of software projects and to software products of any size, complexity, or criticality at any point in the life cycle. All forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon are included.<br />\n
          \t\t\t\t<br />\n
          This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.<br />\n
          This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in silicon. This standard can be applied to any and all segments of a software product lifecycle.<br />\n
          This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format speciÞed in this standard.<br />\n
          Various sections and subsections of a software project management plan may be included in the plan<br />\n
          by direct incorporation or by reference to other plans and documents.<br />\n
          This standard for software project management plans incorporates and subsumes the software development plans described in ANSI/IEEE Std 729-1983 [1] and ANSI/IEEE Std 730-1984 [2].
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Project Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @588981600 {#7531
      date: 1988-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#7521
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1058.1"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 74.0 MiB 0.29 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 9064
    #code: "IEEE00001543"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037941 {#7536
      date: 2025-06-27 17:25:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31265
        #name: "IEEE 1058.1:1987 (R1993)"
        #slug: "ieee-1058-1-1987-r1993-ieee00001543-240716"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised as IEEE Std 1058-1998. The format and content of software project management plans are prescribed. By software project plan is meant the controlling document that defines the technical and managerial processes necessary to satisfy the project requirements. The requirements are applicable to all types of software projects and to software products of any size, complexity, or criticality at any point in the life cycle. All forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon are included.<br />\n
          \t\t\t\t<br />\n
          This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.<br />\n
          This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in silicon. This standard can be applied to any and all segments of a software product lifecycle.<br />\n
          This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format speciÞed in this standard.<br />\n
          Various sections and subsections of a software project management plan may be included in the plan<br />\n
          by direct incorporation or by reference to other plans and documents.<br />\n
          This standard for software project management plans incorporates and subsumes the software development plans described in ANSI/IEEE Std 729-1983 [1] and ANSI/IEEE Std 730-1984 [2].
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Project Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @588981600 {#7531
      date: 1988-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#7521
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1058.1"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#95196
  +product: App\Entity\Product\Product {#7519
    #id: 9064
    #code: "IEEE00001543"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037941 {#7536
      date: 2025-06-27 17:25:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31265
        #name: "IEEE 1058.1:1987 (R1993)"
        #slug: "ieee-1058-1-1987-r1993-ieee00001543-240716"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised as IEEE Std 1058-1998. The format and content of software project management plans are prescribed. By software project plan is meant the controlling document that defines the technical and managerial processes necessary to satisfy the project requirements. The requirements are applicable to all types of software projects and to software products of any size, complexity, or criticality at any point in the life cycle. All forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon are included.<br />\n
          \t\t\t\t<br />\n
          This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.<br />\n
          This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in silicon. This standard can be applied to any and all segments of a software product lifecycle.<br />\n
          This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format speciÞed in this standard.<br />\n
          Various sections and subsections of a software project management plan may be included in the plan<br />\n
          by direct incorporation or by reference to other plans and documents.<br />\n
          This standard for software project management plans incorporates and subsumes the software development plans described in ANSI/IEEE Std 729-1983 [1] and ANSI/IEEE Std 730-1984 [2].
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Project Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @588981600 {#7531
      date: 1988-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#7521
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1058.1"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 74.0 MiB 0.99 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 9064
    #code: "IEEE00001543"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037941 {#7536
      date: 2025-06-27 17:25:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31265
        #name: "IEEE 1058.1:1987 (R1993)"
        #slug: "ieee-1058-1-1987-r1993-ieee00001543-240716"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised as IEEE Std 1058-1998. The format and content of software project management plans are prescribed. By software project plan is meant the controlling document that defines the technical and managerial processes necessary to satisfy the project requirements. The requirements are applicable to all types of software projects and to software products of any size, complexity, or criticality at any point in the life cycle. All forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon are included.<br />\n
          \t\t\t\t<br />\n
          This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.<br />\n
          This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in silicon. This standard can be applied to any and all segments of a software product lifecycle.<br />\n
          This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format speciÞed in this standard.<br />\n
          Various sections and subsections of a software project management plan may be included in the plan<br />\n
          by direct incorporation or by reference to other plans and documents.<br />\n
          This standard for software project management plans incorporates and subsumes the software development plans described in ANSI/IEEE Std 729-1983 [1] and ANSI/IEEE Std 730-1984 [2].
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Project Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @588981600 {#7531
      date: 1988-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#7521
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1058.1"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#95271
  +product: App\Entity\Product\Product {#7519
    #id: 9064
    #code: "IEEE00001543"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037941 {#7536
      date: 2025-06-27 17:25:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31265
        #name: "IEEE 1058.1:1987 (R1993)"
        #slug: "ieee-1058-1-1987-r1993-ieee00001543-240716"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised as IEEE Std 1058-1998. The format and content of software project management plans are prescribed. By software project plan is meant the controlling document that defines the technical and managerial processes necessary to satisfy the project requirements. The requirements are applicable to all types of software projects and to software products of any size, complexity, or criticality at any point in the life cycle. All forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon are included.<br />\n
          \t\t\t\t<br />\n
          This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.<br />\n
          This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in silicon. This standard can be applied to any and all segments of a software product lifecycle.<br />\n
          This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format speciÞed in this standard.<br />\n
          Various sections and subsections of a software project management plan may be included in the plan<br />\n
          by direct incorporation or by reference to other plans and documents.<br />\n
          This standard for software project management plans incorporates and subsumes the software development plans described in ANSI/IEEE Std 729-1983 [1] and ANSI/IEEE Std 730-1984 [2].
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Project Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @588981600 {#7531
      date: 1988-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#7521
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1058.1"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 74.0 MiB 0.28 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 9064
    #code: "IEEE00001543"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037941 {#7536
      date: 2025-06-27 17:25:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31265
        #name: "IEEE 1058.1:1987 (R1993)"
        #slug: "ieee-1058-1-1987-r1993-ieee00001543-240716"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised as IEEE Std 1058-1998. The format and content of software project management plans are prescribed. By software project plan is meant the controlling document that defines the technical and managerial processes necessary to satisfy the project requirements. The requirements are applicable to all types of software projects and to software products of any size, complexity, or criticality at any point in the life cycle. All forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon are included.<br />\n
          \t\t\t\t<br />\n
          This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.<br />\n
          This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in silicon. This standard can be applied to any and all segments of a software product lifecycle.<br />\n
          This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format speciÞed in this standard.<br />\n
          Various sections and subsections of a software project management plan may be included in the plan<br />\n
          by direct incorporation or by reference to other plans and documents.<br />\n
          This standard for software project management plans incorporates and subsumes the software development plans described in ANSI/IEEE Std 729-1983 [1] and ANSI/IEEE Std 730-1984 [2].
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Project Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @588981600 {#7531
      date: 1988-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#7521
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1058.1"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#102214
  +product: App\Entity\Product\Product {#7519
    #id: 9064
    #code: "IEEE00001543"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037941 {#7536
      date: 2025-06-27 17:25:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31265
        #name: "IEEE 1058.1:1987 (R1993)"
        #slug: "ieee-1058-1-1987-r1993-ieee00001543-240716"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised as IEEE Std 1058-1998. The format and content of software project management plans are prescribed. By software project plan is meant the controlling document that defines the technical and managerial processes necessary to satisfy the project requirements. The requirements are applicable to all types of software projects and to software products of any size, complexity, or criticality at any point in the life cycle. All forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon are included.<br />\n
          \t\t\t\t<br />\n
          This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.<br />\n
          This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in silicon. This standard can be applied to any and all segments of a software product lifecycle.<br />\n
          This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format speciÞed in this standard.<br />\n
          Various sections and subsections of a software project management plan may be included in the plan<br />\n
          by direct incorporation or by reference to other plans and documents.<br />\n
          This standard for software project management plans incorporates and subsumes the software development plans described in ANSI/IEEE Std 729-1983 [1] and ANSI/IEEE Std 730-1984 [2].
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Project Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @588981600 {#7531
      date: 1988-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#7521
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1058.1"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 74.0 MiB 1.05 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 9064
    #code: "IEEE00001543"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037941 {#7536
      date: 2025-06-27 17:25:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31265
        #name: "IEEE 1058.1:1987 (R1993)"
        #slug: "ieee-1058-1-1987-r1993-ieee00001543-240716"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised as IEEE Std 1058-1998. The format and content of software project management plans are prescribed. By software project plan is meant the controlling document that defines the technical and managerial processes necessary to satisfy the project requirements. The requirements are applicable to all types of software projects and to software products of any size, complexity, or criticality at any point in the life cycle. All forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon are included.<br />\n
          \t\t\t\t<br />\n
          This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.<br />\n
          This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in silicon. This standard can be applied to any and all segments of a software product lifecycle.<br />\n
          This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format speciÞed in this standard.<br />\n
          Various sections and subsections of a software project management plan may be included in the plan<br />\n
          by direct incorporation or by reference to other plans and documents.<br />\n
          This standard for software project management plans incorporates and subsumes the software development plans described in ANSI/IEEE Std 729-1983 [1] and ANSI/IEEE Std 730-1984 [2].
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Project Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @588981600 {#7531
      date: 1988-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#7521
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1058.1"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#102298
  +product: App\Entity\Product\Product {#7519
    #id: 9064
    #code: "IEEE00001543"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751037941 {#7536
      date: 2025-06-27 17:25:41.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7535
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 31265
        #name: "IEEE 1058.1:1987 (R1993)"
        #slug: "ieee-1058-1-1987-r1993-ieee00001543-240716"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised as IEEE Std 1058-1998. The format and content of software project management plans are prescribed. By software project plan is meant the controlling document that defines the technical and managerial processes necessary to satisfy the project requirements. The requirements are applicable to all types of software projects and to software products of any size, complexity, or criticality at any point in the life cycle. All forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in-silicon are included.<br />\n
          \t\t\t\t<br />\n
          This standard prescribes the format and content of software project management plans. A software project management plan is the controlling document for managing a software project; it defines the technical and managerial processes necessary to satisfy the project requirements.<br />\n
          This standard may be applied to all types of software projects. Use of this standard is not restricted by the size, complexity, or criticality of the software product. This standard is applicable to all forms of product delivery media, including firmware, embedded systems code, programmable logic arrays, and software-in silicon. This standard can be applied to any and all segments of a software product lifecycle.<br />\n
          This standard identifies the minimal set of elements that shall appear in all software project management plans. In order to conform to this standard, software project management plans must adhere to the format and content for project plans specified in the standard. However, users of this standard may incorporate other elements by appending additional sections or subsections to their project management plans. In any case, the numbering scheme of the required sections and subsections must adhere to the format speciÞed in this standard.<br />\n
          Various sections and subsections of a software project management plan may be included in the plan<br />\n
          by direct incorporation or by reference to other plans and documents.<br />\n
          This standard for software project management plans incorporates and subsumes the software development plans described in ANSI/IEEE Std 729-1983 [1] and ANSI/IEEE Std 730-1984 [2].
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Project Management Plans"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @588981600 {#7531
      date: 1988-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @754786800 {#7521
      date: 1993-12-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1058.1"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 96.0 MiB 11.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#123536
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#123541 …}
    #variants: Doctrine\ORM\PersistentCollection {#123539 …}
    #options: Doctrine\ORM\PersistentCollection {#123534 …}
    #associations: Doctrine\ORM\PersistentCollection {#123537 …}
    #createdAt: DateTime @1751037679 {#123530
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123565
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123552 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123650
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123536}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123550 …}
    #channels: Doctrine\ORM\PersistentCollection {#123543 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123545 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123557 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#123564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#123523
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#123556 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123554 …}
  }
  "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 {#123609
  +product: App\Entity\Product\Product {#123536
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#123541 …}
    #variants: Doctrine\ORM\PersistentCollection {#123539 …}
    #options: Doctrine\ORM\PersistentCollection {#123534 …}
    #associations: Doctrine\ORM\PersistentCollection {#123537 …}
    #createdAt: DateTime @1751037679 {#123530
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123565
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123552 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123650
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123536}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123550 …}
    #channels: Doctrine\ORM\PersistentCollection {#123543 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123545 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123557 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#123564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#123523
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#123556 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123554 …}
  }
  +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 96.0 MiB 0.28 ms
Input props 
[
  "product" => App\Entity\Product\Product {#123536
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#123541 …}
    #variants: Doctrine\ORM\PersistentCollection {#123539 …}
    #options: Doctrine\ORM\PersistentCollection {#123534 …}
    #associations: Doctrine\ORM\PersistentCollection {#123537 …}
    #createdAt: DateTime @1751037679 {#123530
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123565
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123552 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123650
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123536}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123550 …}
    #channels: Doctrine\ORM\PersistentCollection {#123543 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123545 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123557 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#123564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#123523
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#123556 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123554 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#123652
  +product: App\Entity\Product\Product {#123536
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#123541 …}
    #variants: Doctrine\ORM\PersistentCollection {#123539 …}
    #options: Doctrine\ORM\PersistentCollection {#123534 …}
    #associations: Doctrine\ORM\PersistentCollection {#123537 …}
    #createdAt: DateTime @1751037679 {#123530
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123565
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123552 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123650
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123536}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123550 …}
    #channels: Doctrine\ORM\PersistentCollection {#123543 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123545 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123557 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#123564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#123523
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#123556 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123554 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 96.0 MiB 0.98 ms
Input props 
[
  "product" => App\Entity\Product\Product {#123536
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#123541 …}
    #variants: Doctrine\ORM\PersistentCollection {#123539 …}
    #options: Doctrine\ORM\PersistentCollection {#123534 …}
    #associations: Doctrine\ORM\PersistentCollection {#123537 …}
    #createdAt: DateTime @1751037679 {#123530
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123565
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123552 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123650
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123536}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123550 …}
    #channels: Doctrine\ORM\PersistentCollection {#123543 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123545 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123557 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#123564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#123523
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#123556 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123554 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#123729
  +product: App\Entity\Product\Product {#123536
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#123541 …}
    #variants: Doctrine\ORM\PersistentCollection {#123539 …}
    #options: Doctrine\ORM\PersistentCollection {#123534 …}
    #associations: Doctrine\ORM\PersistentCollection {#123537 …}
    #createdAt: DateTime @1751037679 {#123530
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123565
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123552 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123650
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123536}
        #id: 30013
        #name: "IEEE 729:1983"
        #slug: "ieee-729-1983-ieee00000967-240403"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Software engineering is an emerging field. New terms are continually being generated, and new<br />\n
          meanings are being adopted for existing terms. The Glossary of Software Engineering Terminology<br />\n
          was undertaken to document this vocabulary. Its purpose is to identify terms currently used in software engineering and to present the current meanings of these terms. It is intended to serve as a useful reference for software engineers and for those in related fields and to promote clarity and consistency in the vocabulary of software engineering. It is recognized that software engineering is a dynamic area; thus the standard will be subject to appropriate change as becomes necessary.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in general use in the software engineering field.<br />\n
          A term was excluded from the glossary if it was considered to be:<br />\n
          (1) Parochial to one particular group or organization.<br />\n
          (2) A company proprietary term.<br />\n
          (3) A standard term in some other well defined discipline, although terms used in software engineering were repeated in this glossary to avoid conflicts.<br />\n
          (4) A multi-word term whose meaning could be inferred from definitions of the component terms.<br />\n
          (5) A term whose meaning for software engineering could be directly inferred from its standard English meaning.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123550 …}
    #channels: Doctrine\ORM\PersistentCollection {#123543 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123547 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123545 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123557 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#123564
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#123523
      date: 1983-02-18 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "729"
    -bookCollection: ""
    -pageCount: 40
    -documents: Doctrine\ORM\PersistentCollection {#123556 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123554 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}