GET https://dev.normadoc.fr/_partial/product/IEEE00001462/features

Response
200 OK
IP
216.73.216.245
Profiled on
Token
14a54f

Components

4 Twig Components
8 Render Count
15 ms Render Time
290.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		3 2.45ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		3 2.75ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.56ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		1 9.79ms

Render calls

ProductState App\Twig\Components\ProductState 290.0 MiB 2.11 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 9004
    #code: "IEEE00001462"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037891 {#7274
      date: 2025-06-27 17:24:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31025
        #name: "IEEE 1008:1987 (R2009)"
        #slug: "ieee-1008-1987-r2009-ieee00001462-240656"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.<br />\n
          \t\t\t\t<br />\n
          Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements. Measuring entails the use of sample data to exercise the unit and the comparison of the unit's actual behavior with its required behavior as specified in the unit's requirements documentation.<br />\n
          This standard defines an integrated approach to systematic and documented unit testing. The approach uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing.<br />\n
          This standard describes a testing process composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. Additional tasks may be added to any activity.<br />\n
          This standard requires the performance of each activity. For each task within an activity, this standard requires either that the task be performed, or that previous results be available and be re-verified. This standard also requires the preparation of two documents specified in ANSI/IEEE Std 829-1983 [2] 1 . These documents are the Test Design Specification and the Test Summary Report.<br />\n
          General unit test planning should occur during overall test planning. This general unit test planning activity is covered by this standard, although the balance of the overall test planning process is outside the scope of this standard.<br />\n
          This standard may be applied to the unit testing of any digital computer software or firmware. However, this standard does not specify any class of software or firmware to which it must be applied, nor does it specify any class of software or firmware that must be unit tested. This standard applies to the testing of newly developed and modified units.<br />\n
          This standard is applicable whether or not the unit tester is also the developer.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Unit Testing"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -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 @533689200 {#7318
      date: 1986-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#7316
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1008"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#92886
  +product: App\Entity\Product\Product {#7311
    #id: 9004
    #code: "IEEE00001462"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037891 {#7274
      date: 2025-06-27 17:24:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31025
        #name: "IEEE 1008:1987 (R2009)"
        #slug: "ieee-1008-1987-r2009-ieee00001462-240656"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.<br />\n
          \t\t\t\t<br />\n
          Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements. Measuring entails the use of sample data to exercise the unit and the comparison of the unit's actual behavior with its required behavior as specified in the unit's requirements documentation.<br />\n
          This standard defines an integrated approach to systematic and documented unit testing. The approach uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing.<br />\n
          This standard describes a testing process composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. Additional tasks may be added to any activity.<br />\n
          This standard requires the performance of each activity. For each task within an activity, this standard requires either that the task be performed, or that previous results be available and be re-verified. This standard also requires the preparation of two documents specified in ANSI/IEEE Std 829-1983 [2] 1 . These documents are the Test Design Specification and the Test Summary Report.<br />\n
          General unit test planning should occur during overall test planning. This general unit test planning activity is covered by this standard, although the balance of the overall test planning process is outside the scope of this standard.<br />\n
          This standard may be applied to the unit testing of any digital computer software or firmware. However, this standard does not specify any class of software or firmware to which it must be applied, nor does it specify any class of software or firmware that must be unit tested. This standard applies to the testing of newly developed and modified units.<br />\n
          This standard is applicable whether or not the unit tester is also the developer.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Unit Testing"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -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 @533689200 {#7318
      date: 1986-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#7316
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1008"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 290.0 MiB 0.56 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 9004
    #code: "IEEE00001462"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037891 {#7274
      date: 2025-06-27 17:24:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31025
        #name: "IEEE 1008:1987 (R2009)"
        #slug: "ieee-1008-1987-r2009-ieee00001462-240656"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.<br />\n
          \t\t\t\t<br />\n
          Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements. Measuring entails the use of sample data to exercise the unit and the comparison of the unit's actual behavior with its required behavior as specified in the unit's requirements documentation.<br />\n
          This standard defines an integrated approach to systematic and documented unit testing. The approach uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing.<br />\n
          This standard describes a testing process composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. Additional tasks may be added to any activity.<br />\n
          This standard requires the performance of each activity. For each task within an activity, this standard requires either that the task be performed, or that previous results be available and be re-verified. This standard also requires the preparation of two documents specified in ANSI/IEEE Std 829-1983 [2] 1 . These documents are the Test Design Specification and the Test Summary Report.<br />\n
          General unit test planning should occur during overall test planning. This general unit test planning activity is covered by this standard, although the balance of the overall test planning process is outside the scope of this standard.<br />\n
          This standard may be applied to the unit testing of any digital computer software or firmware. However, this standard does not specify any class of software or firmware to which it must be applied, nor does it specify any class of software or firmware that must be unit tested. This standard applies to the testing of newly developed and modified units.<br />\n
          This standard is applicable whether or not the unit tester is also the developer.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Unit Testing"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -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 @533689200 {#7318
      date: 1986-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#7316
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1008"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93070
  +product: App\Entity\Product\Product {#7311
    #id: 9004
    #code: "IEEE00001462"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037891 {#7274
      date: 2025-06-27 17:24:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31025
        #name: "IEEE 1008:1987 (R2009)"
        #slug: "ieee-1008-1987-r2009-ieee00001462-240656"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.<br />\n
          \t\t\t\t<br />\n
          Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements. Measuring entails the use of sample data to exercise the unit and the comparison of the unit's actual behavior with its required behavior as specified in the unit's requirements documentation.<br />\n
          This standard defines an integrated approach to systematic and documented unit testing. The approach uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing.<br />\n
          This standard describes a testing process composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. Additional tasks may be added to any activity.<br />\n
          This standard requires the performance of each activity. For each task within an activity, this standard requires either that the task be performed, or that previous results be available and be re-verified. This standard also requires the preparation of two documents specified in ANSI/IEEE Std 829-1983 [2] 1 . These documents are the Test Design Specification and the Test Summary Report.<br />\n
          General unit test planning should occur during overall test planning. This general unit test planning activity is covered by this standard, although the balance of the overall test planning process is outside the scope of this standard.<br />\n
          This standard may be applied to the unit testing of any digital computer software or firmware. However, this standard does not specify any class of software or firmware to which it must be applied, nor does it specify any class of software or firmware that must be unit tested. This standard applies to the testing of newly developed and modified units.<br />\n
          This standard is applicable whether or not the unit tester is also the developer.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Unit Testing"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -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 @533689200 {#7318
      date: 1986-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#7316
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1008"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 290.0 MiB 1.46 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 9004
    #code: "IEEE00001462"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037891 {#7274
      date: 2025-06-27 17:24:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31025
        #name: "IEEE 1008:1987 (R2009)"
        #slug: "ieee-1008-1987-r2009-ieee00001462-240656"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.<br />\n
          \t\t\t\t<br />\n
          Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements. Measuring entails the use of sample data to exercise the unit and the comparison of the unit's actual behavior with its required behavior as specified in the unit's requirements documentation.<br />\n
          This standard defines an integrated approach to systematic and documented unit testing. The approach uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing.<br />\n
          This standard describes a testing process composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. Additional tasks may be added to any activity.<br />\n
          This standard requires the performance of each activity. For each task within an activity, this standard requires either that the task be performed, or that previous results be available and be re-verified. This standard also requires the preparation of two documents specified in ANSI/IEEE Std 829-1983 [2] 1 . These documents are the Test Design Specification and the Test Summary Report.<br />\n
          General unit test planning should occur during overall test planning. This general unit test planning activity is covered by this standard, although the balance of the overall test planning process is outside the scope of this standard.<br />\n
          This standard may be applied to the unit testing of any digital computer software or firmware. However, this standard does not specify any class of software or firmware to which it must be applied, nor does it specify any class of software or firmware that must be unit tested. This standard applies to the testing of newly developed and modified units.<br />\n
          This standard is applicable whether or not the unit tester is also the developer.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Unit Testing"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -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 @533689200 {#7318
      date: 1986-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#7316
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1008"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93145
  +product: App\Entity\Product\Product {#7311
    #id: 9004
    #code: "IEEE00001462"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037891 {#7274
      date: 2025-06-27 17:24:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31025
        #name: "IEEE 1008:1987 (R2009)"
        #slug: "ieee-1008-1987-r2009-ieee00001462-240656"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.<br />\n
          \t\t\t\t<br />\n
          Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements. Measuring entails the use of sample data to exercise the unit and the comparison of the unit's actual behavior with its required behavior as specified in the unit's requirements documentation.<br />\n
          This standard defines an integrated approach to systematic and documented unit testing. The approach uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing.<br />\n
          This standard describes a testing process composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. Additional tasks may be added to any activity.<br />\n
          This standard requires the performance of each activity. For each task within an activity, this standard requires either that the task be performed, or that previous results be available and be re-verified. This standard also requires the preparation of two documents specified in ANSI/IEEE Std 829-1983 [2] 1 . These documents are the Test Design Specification and the Test Summary Report.<br />\n
          General unit test planning should occur during overall test planning. This general unit test planning activity is covered by this standard, although the balance of the overall test planning process is outside the scope of this standard.<br />\n
          This standard may be applied to the unit testing of any digital computer software or firmware. However, this standard does not specify any class of software or firmware to which it must be applied, nor does it specify any class of software or firmware that must be unit tested. This standard applies to the testing of newly developed and modified units.<br />\n
          This standard is applicable whether or not the unit tester is also the developer.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Unit Testing"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -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 @533689200 {#7318
      date: 1986-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#7316
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1008"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 290.0 MiB 0.17 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 9004
    #code: "IEEE00001462"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037891 {#7274
      date: 2025-06-27 17:24:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31025
        #name: "IEEE 1008:1987 (R2009)"
        #slug: "ieee-1008-1987-r2009-ieee00001462-240656"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.<br />\n
          \t\t\t\t<br />\n
          Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements. Measuring entails the use of sample data to exercise the unit and the comparison of the unit's actual behavior with its required behavior as specified in the unit's requirements documentation.<br />\n
          This standard defines an integrated approach to systematic and documented unit testing. The approach uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing.<br />\n
          This standard describes a testing process composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. Additional tasks may be added to any activity.<br />\n
          This standard requires the performance of each activity. For each task within an activity, this standard requires either that the task be performed, or that previous results be available and be re-verified. This standard also requires the preparation of two documents specified in ANSI/IEEE Std 829-1983 [2] 1 . These documents are the Test Design Specification and the Test Summary Report.<br />\n
          General unit test planning should occur during overall test planning. This general unit test planning activity is covered by this standard, although the balance of the overall test planning process is outside the scope of this standard.<br />\n
          This standard may be applied to the unit testing of any digital computer software or firmware. However, this standard does not specify any class of software or firmware to which it must be applied, nor does it specify any class of software or firmware that must be unit tested. This standard applies to the testing of newly developed and modified units.<br />\n
          This standard is applicable whether or not the unit tester is also the developer.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Unit Testing"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -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 @533689200 {#7318
      date: 1986-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#7316
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1008"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100088
  +product: App\Entity\Product\Product {#7311
    #id: 9004
    #code: "IEEE00001462"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037891 {#7274
      date: 2025-06-27 17:24:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31025
        #name: "IEEE 1008:1987 (R2009)"
        #slug: "ieee-1008-1987-r2009-ieee00001462-240656"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.<br />\n
          \t\t\t\t<br />\n
          Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements. Measuring entails the use of sample data to exercise the unit and the comparison of the unit's actual behavior with its required behavior as specified in the unit's requirements documentation.<br />\n
          This standard defines an integrated approach to systematic and documented unit testing. The approach uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing.<br />\n
          This standard describes a testing process composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. Additional tasks may be added to any activity.<br />\n
          This standard requires the performance of each activity. For each task within an activity, this standard requires either that the task be performed, or that previous results be available and be re-verified. This standard also requires the preparation of two documents specified in ANSI/IEEE Std 829-1983 [2] 1 . These documents are the Test Design Specification and the Test Summary Report.<br />\n
          General unit test planning should occur during overall test planning. This general unit test planning activity is covered by this standard, although the balance of the overall test planning process is outside the scope of this standard.<br />\n
          This standard may be applied to the unit testing of any digital computer software or firmware. However, this standard does not specify any class of software or firmware to which it must be applied, nor does it specify any class of software or firmware that must be unit tested. This standard applies to the testing of newly developed and modified units.<br />\n
          This standard is applicable whether or not the unit tester is also the developer.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Unit Testing"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -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 @533689200 {#7318
      date: 1986-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#7316
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1008"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 290.0 MiB 0.65 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 9004
    #code: "IEEE00001462"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037891 {#7274
      date: 2025-06-27 17:24:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31025
        #name: "IEEE 1008:1987 (R2009)"
        #slug: "ieee-1008-1987-r2009-ieee00001462-240656"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.<br />\n
          \t\t\t\t<br />\n
          Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements. Measuring entails the use of sample data to exercise the unit and the comparison of the unit's actual behavior with its required behavior as specified in the unit's requirements documentation.<br />\n
          This standard defines an integrated approach to systematic and documented unit testing. The approach uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing.<br />\n
          This standard describes a testing process composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. Additional tasks may be added to any activity.<br />\n
          This standard requires the performance of each activity. For each task within an activity, this standard requires either that the task be performed, or that previous results be available and be re-verified. This standard also requires the preparation of two documents specified in ANSI/IEEE Std 829-1983 [2] 1 . These documents are the Test Design Specification and the Test Summary Report.<br />\n
          General unit test planning should occur during overall test planning. This general unit test planning activity is covered by this standard, although the balance of the overall test planning process is outside the scope of this standard.<br />\n
          This standard may be applied to the unit testing of any digital computer software or firmware. However, this standard does not specify any class of software or firmware to which it must be applied, nor does it specify any class of software or firmware that must be unit tested. This standard applies to the testing of newly developed and modified units.<br />\n
          This standard is applicable whether or not the unit tester is also the developer.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Unit Testing"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -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 @533689200 {#7318
      date: 1986-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#7316
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1008"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100172
  +product: App\Entity\Product\Product {#7311
    #id: 9004
    #code: "IEEE00001462"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037891 {#7274
      date: 2025-06-27 17:24:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#7322
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31025
        #name: "IEEE 1008:1987 (R2009)"
        #slug: "ieee-1008-1987-r2009-ieee00001462-240656"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          An integrated approach to systematic and documented unit testing is defined. It uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing. The testing process described composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. The standard can be applied to the unit testing of any digital computer software or firmware and to the testing of both newly developed and modified units. The software engineering concepts and testing assumption on which this standard approach is based and guidance and resource information to assist with the implementation and usage of the standard unit testing approach are provided in appendixes.<br />\n
          \t\t\t\t<br />\n
          Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements. Measuring entails the use of sample data to exercise the unit and the comparison of the unit's actual behavior with its required behavior as specified in the unit's requirements documentation.<br />\n
          This standard defines an integrated approach to systematic and documented unit testing. The approach uses unit design and unit implementation information, in addition to unit requirements, to determine the completeness of the testing.<br />\n
          This standard describes a testing process composed of a hierarchy of phases, activities, and tasks and defines a minimum set of tasks for each activity. Additional tasks may be added to any activity.<br />\n
          This standard requires the performance of each activity. For each task within an activity, this standard requires either that the task be performed, or that previous results be available and be re-verified. This standard also requires the preparation of two documents specified in ANSI/IEEE Std 829-1983 [2] 1 . These documents are the Test Design Specification and the Test Summary Report.<br />\n
          General unit test planning should occur during overall test planning. This general unit test planning activity is covered by this standard, although the balance of the overall test planning process is outside the scope of this standard.<br />\n
          This standard may be applied to the unit testing of any digital computer software or firmware. However, this standard does not specify any class of software or firmware to which it must be applied, nor does it specify any class of software or firmware that must be unit tested. This standard applies to the testing of newly developed and modified units.<br />\n
          This standard is applicable whether or not the unit tester is also the developer.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Unit Testing"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -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 @533689200 {#7318
      date: 1986-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1260313200 {#7316
      date: 2009-12-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1008"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 290.0 MiB 9.79 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121560
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#121565 …}
    #variants: Doctrine\ORM\PersistentCollection {#121563 …}
    #options: Doctrine\ORM\PersistentCollection {#121558 …}
    #associations: Doctrine\ORM\PersistentCollection {#121561 …}
    #createdAt: DateTime @1751037679 {#121554
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#121589
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121576 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121674
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121560}
        #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 {#121574 …}
    #channels: Doctrine\ORM\PersistentCollection {#121567 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121571 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121569 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121581 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121540
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121588
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#121547
      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 {#121580 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121578 …}
  }
  "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 {#121633
  +product: App\Entity\Product\Product {#121560
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#121565 …}
    #variants: Doctrine\ORM\PersistentCollection {#121563 …}
    #options: Doctrine\ORM\PersistentCollection {#121558 …}
    #associations: Doctrine\ORM\PersistentCollection {#121561 …}
    #createdAt: DateTime @1751037679 {#121554
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#121589
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121576 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121674
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121560}
        #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 {#121574 …}
    #channels: Doctrine\ORM\PersistentCollection {#121567 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121571 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121569 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121581 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121540
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121588
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#121547
      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 {#121580 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121578 …}
  }
  +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 290.0 MiB 0.16 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121560
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#121565 …}
    #variants: Doctrine\ORM\PersistentCollection {#121563 …}
    #options: Doctrine\ORM\PersistentCollection {#121558 …}
    #associations: Doctrine\ORM\PersistentCollection {#121561 …}
    #createdAt: DateTime @1751037679 {#121554
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#121589
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121576 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121674
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121560}
        #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 {#121574 …}
    #channels: Doctrine\ORM\PersistentCollection {#121567 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121571 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121569 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121581 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121540
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121588
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#121547
      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 {#121580 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121578 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#121676
  +product: App\Entity\Product\Product {#121560
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#121565 …}
    #variants: Doctrine\ORM\PersistentCollection {#121563 …}
    #options: Doctrine\ORM\PersistentCollection {#121558 …}
    #associations: Doctrine\ORM\PersistentCollection {#121561 …}
    #createdAt: DateTime @1751037679 {#121554
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#121589
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121576 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121674
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121560}
        #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 {#121574 …}
    #channels: Doctrine\ORM\PersistentCollection {#121567 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121571 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121569 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121581 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121540
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121588
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#121547
      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 {#121580 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121578 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 290.0 MiB 0.65 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121560
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#121565 …}
    #variants: Doctrine\ORM\PersistentCollection {#121563 …}
    #options: Doctrine\ORM\PersistentCollection {#121558 …}
    #associations: Doctrine\ORM\PersistentCollection {#121561 …}
    #createdAt: DateTime @1751037679 {#121554
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#121589
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121576 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121674
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121560}
        #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 {#121574 …}
    #channels: Doctrine\ORM\PersistentCollection {#121567 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121571 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121569 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121581 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121540
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121588
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#121547
      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 {#121580 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121578 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#121753
  +product: App\Entity\Product\Product {#121560
    #id: 8751
    #code: "IEEE00000967"
    #attributes: Doctrine\ORM\PersistentCollection {#121565 …}
    #variants: Doctrine\ORM\PersistentCollection {#121563 …}
    #options: Doctrine\ORM\PersistentCollection {#121558 …}
    #associations: Doctrine\ORM\PersistentCollection {#121561 …}
    #createdAt: DateTime @1751037679 {#121554
      date: 2025-06-27 17:21:19.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#121589
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121576 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121674
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121560}
        #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 {#121574 …}
    #channels: Doctrine\ORM\PersistentCollection {#121567 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121571 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121569 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121581 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121540
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121588
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @414370800 {#121547
      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 {#121580 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121578 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}