GET https://dev.normadoc.fr/_partial/cart/summary?template=%40SyliusShop%2FCart%2F_widget.html.twig

Response
200 OK
IP
216.73.216.2
Profiled on
Token
140b3b

Components

4 Twig Components
12 Render Count
621 ms Render Time
124.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		5 3.42ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		5 7.74ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.65ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		1 612.93ms

Render calls

ProductState App\Twig\Components\ProductState 124.0 MiB 2.31 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7273
    #id: 12590
    #code: "IEEE00010236"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040532 {#7306
      date: 2025-06-27 18:08:52.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7273}
        #id: 45369
        #name: "IEEE/ISO/IEC 15026-2:2022"
        #slug: "ieee-iso-iec-15026-2-2022-ieee00010236-244245"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.<br />\n
          The purpose of this document is to define assurance case structure and related restrictions on assurance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#7287
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#7318
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#92950
  +product: App\Entity\Product\Product {#7273
    #id: 12590
    #code: "IEEE00010236"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040532 {#7306
      date: 2025-06-27 18:08:52.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7273}
        #id: 45369
        #name: "IEEE/ISO/IEC 15026-2:2022"
        #slug: "ieee-iso-iec-15026-2-2022-ieee00010236-244245"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.<br />\n
          The purpose of this document is to define assurance case structure and related restrictions on assurance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#7287
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#7318
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 124.0 MiB 0.65 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7273
    #id: 12590
    #code: "IEEE00010236"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040532 {#7306
      date: 2025-06-27 18:08:52.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7273}
        #id: 45369
        #name: "IEEE/ISO/IEC 15026-2:2022"
        #slug: "ieee-iso-iec-15026-2-2022-ieee00010236-244245"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.<br />\n
          The purpose of this document is to define assurance case structure and related restrictions on assurance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#7287
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#7318
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93121
  +product: App\Entity\Product\Product {#7273
    #id: 12590
    #code: "IEEE00010236"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040532 {#7306
      date: 2025-06-27 18:08:52.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7273}
        #id: 45369
        #name: "IEEE/ISO/IEC 15026-2:2022"
        #slug: "ieee-iso-iec-15026-2-2022-ieee00010236-244245"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.<br />\n
          The purpose of this document is to define assurance case structure and related restrictions on assurance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#7287
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#7318
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 124.0 MiB 1.36 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7273
    #id: 12590
    #code: "IEEE00010236"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040532 {#7306
      date: 2025-06-27 18:08:52.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7273}
        #id: 45369
        #name: "IEEE/ISO/IEC 15026-2:2022"
        #slug: "ieee-iso-iec-15026-2-2022-ieee00010236-244245"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.<br />\n
          The purpose of this document is to define assurance case structure and related restrictions on assurance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#7287
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#7318
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93196
  +product: App\Entity\Product\Product {#7273
    #id: 12590
    #code: "IEEE00010236"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040532 {#7306
      date: 2025-06-27 18:08:52.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7273}
        #id: 45369
        #name: "IEEE/ISO/IEC 15026-2:2022"
        #slug: "ieee-iso-iec-15026-2-2022-ieee00010236-244245"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.<br />\n
          The purpose of this document is to define assurance case structure and related restrictions on assurance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#7287
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#7318
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 124.0 MiB 0.29 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100191
    #id: 10883
    #code: "IEEE00005234"
    #attributes: Doctrine\ORM\PersistentCollection {#100172 …}
    #variants: Doctrine\ORM\PersistentCollection {#100169 …}
    #options: Doctrine\ORM\PersistentCollection {#100165 …}
    #associations: Doctrine\ORM\PersistentCollection {#100167 …}
    #createdAt: DateTime @1751039343 {#100198
      date: 2025-06-27 17:49:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100171
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100182 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100210
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 38541
        #name: "IEEE 15026-2:2011"
        #slug: "ieee-15026-2-2011-ieee00005234-242535"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          ISO/IEC 15026-2:2011 is adopted by this standard. ISO/IEC 15026-2:2011 specifies minimum requirements for the structure and contents of an assurance case to improve the consistency and comparability of assurance cases and to facilitate stakeholder communications, engineering decisions, and other uses of assurance cases. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R&amp;M) case. ISO/IEC 15026-2:2011 does not place requirements on the quality of the contents of an assurance case and does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC 15026 specifies minimum requirements for the structure and contents of an assurance case. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. This part of ISO/IEC 15026 does not place requirements on the quality of the contents of an assurance case. Rathere, it places requirements on the existence of the contents and structure of an assurance case. While several notations and slightly varying terminologies are currently used in practice, this part of ISO/IEC 15026 does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard--Adoption of ISO/IEC 15026-2:2011 Systems and Software Engineering--Systems and Software Assurance--Part 2: Assurance Case"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100180 …}
    #channels: Doctrine\ORM\PersistentCollection {#100174 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100178 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100176 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100189 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100158
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#100197
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1318284000 {#100196
      date: 2011-10-11 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#100190
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#100187 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100185 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100249
  +product: App\Entity\Product\Product {#100191
    #id: 10883
    #code: "IEEE00005234"
    #attributes: Doctrine\ORM\PersistentCollection {#100172 …}
    #variants: Doctrine\ORM\PersistentCollection {#100169 …}
    #options: Doctrine\ORM\PersistentCollection {#100165 …}
    #associations: Doctrine\ORM\PersistentCollection {#100167 …}
    #createdAt: DateTime @1751039343 {#100198
      date: 2025-06-27 17:49:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100171
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100182 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100210
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 38541
        #name: "IEEE 15026-2:2011"
        #slug: "ieee-15026-2-2011-ieee00005234-242535"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          ISO/IEC 15026-2:2011 is adopted by this standard. ISO/IEC 15026-2:2011 specifies minimum requirements for the structure and contents of an assurance case to improve the consistency and comparability of assurance cases and to facilitate stakeholder communications, engineering decisions, and other uses of assurance cases. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R&amp;M) case. ISO/IEC 15026-2:2011 does not place requirements on the quality of the contents of an assurance case and does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC 15026 specifies minimum requirements for the structure and contents of an assurance case. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. This part of ISO/IEC 15026 does not place requirements on the quality of the contents of an assurance case. Rathere, it places requirements on the existence of the contents and structure of an assurance case. While several notations and slightly varying terminologies are currently used in practice, this part of ISO/IEC 15026 does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard--Adoption of ISO/IEC 15026-2:2011 Systems and Software Engineering--Systems and Software Assurance--Part 2: Assurance Case"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100180 …}
    #channels: Doctrine\ORM\PersistentCollection {#100174 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100178 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100176 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100189 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100158
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#100197
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1318284000 {#100196
      date: 2011-10-11 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#100190
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#100187 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100185 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 124.0 MiB 1.09 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100191
    #id: 10883
    #code: "IEEE00005234"
    #attributes: Doctrine\ORM\PersistentCollection {#100172 …}
    #variants: Doctrine\ORM\PersistentCollection {#100169 …}
    #options: Doctrine\ORM\PersistentCollection {#100165 …}
    #associations: Doctrine\ORM\PersistentCollection {#100167 …}
    #createdAt: DateTime @1751039343 {#100198
      date: 2025-06-27 17:49:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100171
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100182 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100210
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 38541
        #name: "IEEE 15026-2:2011"
        #slug: "ieee-15026-2-2011-ieee00005234-242535"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          ISO/IEC 15026-2:2011 is adopted by this standard. ISO/IEC 15026-2:2011 specifies minimum requirements for the structure and contents of an assurance case to improve the consistency and comparability of assurance cases and to facilitate stakeholder communications, engineering decisions, and other uses of assurance cases. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R&amp;M) case. ISO/IEC 15026-2:2011 does not place requirements on the quality of the contents of an assurance case and does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC 15026 specifies minimum requirements for the structure and contents of an assurance case. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. This part of ISO/IEC 15026 does not place requirements on the quality of the contents of an assurance case. Rathere, it places requirements on the existence of the contents and structure of an assurance case. While several notations and slightly varying terminologies are currently used in practice, this part of ISO/IEC 15026 does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard--Adoption of ISO/IEC 15026-2:2011 Systems and Software Engineering--Systems and Software Assurance--Part 2: Assurance Case"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100180 …}
    #channels: Doctrine\ORM\PersistentCollection {#100174 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100178 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100176 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100189 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100158
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#100197
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1318284000 {#100196
      date: 2011-10-11 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#100190
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#100187 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100185 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100316
  +product: App\Entity\Product\Product {#100191
    #id: 10883
    #code: "IEEE00005234"
    #attributes: Doctrine\ORM\PersistentCollection {#100172 …}
    #variants: Doctrine\ORM\PersistentCollection {#100169 …}
    #options: Doctrine\ORM\PersistentCollection {#100165 …}
    #associations: Doctrine\ORM\PersistentCollection {#100167 …}
    #createdAt: DateTime @1751039343 {#100198
      date: 2025-06-27 17:49:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100171
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100182 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100210
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 38541
        #name: "IEEE 15026-2:2011"
        #slug: "ieee-15026-2-2011-ieee00005234-242535"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          ISO/IEC 15026-2:2011 is adopted by this standard. ISO/IEC 15026-2:2011 specifies minimum requirements for the structure and contents of an assurance case to improve the consistency and comparability of assurance cases and to facilitate stakeholder communications, engineering decisions, and other uses of assurance cases. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R&amp;M) case. ISO/IEC 15026-2:2011 does not place requirements on the quality of the contents of an assurance case and does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC 15026 specifies minimum requirements for the structure and contents of an assurance case. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. This part of ISO/IEC 15026 does not place requirements on the quality of the contents of an assurance case. Rathere, it places requirements on the existence of the contents and structure of an assurance case. While several notations and slightly varying terminologies are currently used in practice, this part of ISO/IEC 15026 does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard--Adoption of ISO/IEC 15026-2:2011 Systems and Software Engineering--Systems and Software Assurance--Part 2: Assurance Case"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100180 …}
    #channels: Doctrine\ORM\PersistentCollection {#100174 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100178 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100176 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100189 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100158
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#100197
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1318284000 {#100196
      date: 2011-10-11 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#100190
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#100187 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100185 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 124.0 MiB 0.26 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7273
    #id: 12590
    #code: "IEEE00010236"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040532 {#7306
      date: 2025-06-27 18:08:52.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7273}
        #id: 45369
        #name: "IEEE/ISO/IEC 15026-2:2022"
        #slug: "ieee-iso-iec-15026-2-2022-ieee00010236-244245"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.<br />\n
          The purpose of this document is to define assurance case structure and related restrictions on assurance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#7287
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#7318
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#106905
  +product: App\Entity\Product\Product {#7273
    #id: 12590
    #code: "IEEE00010236"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040532 {#7306
      date: 2025-06-27 18:08:52.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7273}
        #id: 45369
        #name: "IEEE/ISO/IEC 15026-2:2022"
        #slug: "ieee-iso-iec-15026-2-2022-ieee00010236-244245"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.<br />\n
          The purpose of this document is to define assurance case structure and related restrictions on assurance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#7287
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#7318
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 124.0 MiB 1.05 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7273
    #id: 12590
    #code: "IEEE00010236"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040532 {#7306
      date: 2025-06-27 18:08:52.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7273}
        #id: 45369
        #name: "IEEE/ISO/IEC 15026-2:2022"
        #slug: "ieee-iso-iec-15026-2-2022-ieee00010236-244245"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.<br />\n
          The purpose of this document is to define assurance case structure and related restrictions on assurance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#7287
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#7318
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#106947
  +product: App\Entity\Product\Product {#7273
    #id: 12590
    #code: "IEEE00010236"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040532 {#7306
      date: 2025-06-27 18:08:52.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7273}
        #id: 45369
        #name: "IEEE/ISO/IEC 15026-2:2022"
        #slug: "ieee-iso-iec-15026-2-2022-ieee00010236-244245"
        #description: """
          Revision Standard - Active.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.<br />\n
          The purpose of this document is to define assurance case structure and related restrictions on assurance case structure, thereby improving consistency and comparability among instances of assurance cases and facilitating stakeholder communications, engineering decisions, and other uses of assurance cases.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance--Part 2: Assurance case"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1668985200 {#7287
      date: 2022-11-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1667775600 {#7318
      date: 2022-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 30
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 124.0 MiB 0.24 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100191
    #id: 10883
    #code: "IEEE00005234"
    #attributes: Doctrine\ORM\PersistentCollection {#100172 …}
    #variants: Doctrine\ORM\PersistentCollection {#100169 …}
    #options: Doctrine\ORM\PersistentCollection {#100165 …}
    #associations: Doctrine\ORM\PersistentCollection {#100167 …}
    #createdAt: DateTime @1751039343 {#100198
      date: 2025-06-27 17:49:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100171
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100182 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100210
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 38541
        #name: "IEEE 15026-2:2011"
        #slug: "ieee-15026-2-2011-ieee00005234-242535"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          ISO/IEC 15026-2:2011 is adopted by this standard. ISO/IEC 15026-2:2011 specifies minimum requirements for the structure and contents of an assurance case to improve the consistency and comparability of assurance cases and to facilitate stakeholder communications, engineering decisions, and other uses of assurance cases. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R&amp;M) case. ISO/IEC 15026-2:2011 does not place requirements on the quality of the contents of an assurance case and does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC 15026 specifies minimum requirements for the structure and contents of an assurance case. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. This part of ISO/IEC 15026 does not place requirements on the quality of the contents of an assurance case. Rathere, it places requirements on the existence of the contents and structure of an assurance case. While several notations and slightly varying terminologies are currently used in practice, this part of ISO/IEC 15026 does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard--Adoption of ISO/IEC 15026-2:2011 Systems and Software Engineering--Systems and Software Assurance--Part 2: Assurance Case"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100180 …}
    #channels: Doctrine\ORM\PersistentCollection {#100174 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100178 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100176 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100189 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100158
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#100197
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1318284000 {#100196
      date: 2011-10-11 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#100190
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#100187 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100185 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#107012
  +product: App\Entity\Product\Product {#100191
    #id: 10883
    #code: "IEEE00005234"
    #attributes: Doctrine\ORM\PersistentCollection {#100172 …}
    #variants: Doctrine\ORM\PersistentCollection {#100169 …}
    #options: Doctrine\ORM\PersistentCollection {#100165 …}
    #associations: Doctrine\ORM\PersistentCollection {#100167 …}
    #createdAt: DateTime @1751039343 {#100198
      date: 2025-06-27 17:49:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100171
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100182 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100210
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 38541
        #name: "IEEE 15026-2:2011"
        #slug: "ieee-15026-2-2011-ieee00005234-242535"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          ISO/IEC 15026-2:2011 is adopted by this standard. ISO/IEC 15026-2:2011 specifies minimum requirements for the structure and contents of an assurance case to improve the consistency and comparability of assurance cases and to facilitate stakeholder communications, engineering decisions, and other uses of assurance cases. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R&amp;M) case. ISO/IEC 15026-2:2011 does not place requirements on the quality of the contents of an assurance case and does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC 15026 specifies minimum requirements for the structure and contents of an assurance case. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. This part of ISO/IEC 15026 does not place requirements on the quality of the contents of an assurance case. Rathere, it places requirements on the existence of the contents and structure of an assurance case. While several notations and slightly varying terminologies are currently used in practice, this part of ISO/IEC 15026 does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard--Adoption of ISO/IEC 15026-2:2011 Systems and Software Engineering--Systems and Software Assurance--Part 2: Assurance Case"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100180 …}
    #channels: Doctrine\ORM\PersistentCollection {#100174 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100178 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100176 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100189 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100158
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#100197
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1318284000 {#100196
      date: 2011-10-11 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#100190
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#100187 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100185 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 124.0 MiB 0.98 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100191
    #id: 10883
    #code: "IEEE00005234"
    #attributes: Doctrine\ORM\PersistentCollection {#100172 …}
    #variants: Doctrine\ORM\PersistentCollection {#100169 …}
    #options: Doctrine\ORM\PersistentCollection {#100165 …}
    #associations: Doctrine\ORM\PersistentCollection {#100167 …}
    #createdAt: DateTime @1751039343 {#100198
      date: 2025-06-27 17:49:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100171
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100182 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100210
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 38541
        #name: "IEEE 15026-2:2011"
        #slug: "ieee-15026-2-2011-ieee00005234-242535"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          ISO/IEC 15026-2:2011 is adopted by this standard. ISO/IEC 15026-2:2011 specifies minimum requirements for the structure and contents of an assurance case to improve the consistency and comparability of assurance cases and to facilitate stakeholder communications, engineering decisions, and other uses of assurance cases. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R&amp;M) case. ISO/IEC 15026-2:2011 does not place requirements on the quality of the contents of an assurance case and does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC 15026 specifies minimum requirements for the structure and contents of an assurance case. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. This part of ISO/IEC 15026 does not place requirements on the quality of the contents of an assurance case. Rathere, it places requirements on the existence of the contents and structure of an assurance case. While several notations and slightly varying terminologies are currently used in practice, this part of ISO/IEC 15026 does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard--Adoption of ISO/IEC 15026-2:2011 Systems and Software Engineering--Systems and Software Assurance--Part 2: Assurance Case"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100180 …}
    #channels: Doctrine\ORM\PersistentCollection {#100174 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100178 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100176 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100189 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100158
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#100197
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1318284000 {#100196
      date: 2011-10-11 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#100190
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#100187 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100185 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#107039
  +product: App\Entity\Product\Product {#100191
    #id: 10883
    #code: "IEEE00005234"
    #attributes: Doctrine\ORM\PersistentCollection {#100172 …}
    #variants: Doctrine\ORM\PersistentCollection {#100169 …}
    #options: Doctrine\ORM\PersistentCollection {#100165 …}
    #associations: Doctrine\ORM\PersistentCollection {#100167 …}
    #createdAt: DateTime @1751039343 {#100198
      date: 2025-06-27 17:49:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100171
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100182 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100210
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 38541
        #name: "IEEE 15026-2:2011"
        #slug: "ieee-15026-2-2011-ieee00005234-242535"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          ISO/IEC 15026-2:2011 is adopted by this standard. ISO/IEC 15026-2:2011 specifies minimum requirements for the structure and contents of an assurance case to improve the consistency and comparability of assurance cases and to facilitate stakeholder communications, engineering decisions, and other uses of assurance cases. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. Assurance cases are generally developed to support claims in areas such as safety, reliability, maintainability, human factors, operability, and security, although these assurance cases are often called by more specific names, e.g. safety case or reliability and maintainability (R&amp;M) case. ISO/IEC 15026-2:2011 does not place requirements on the quality of the contents of an assurance case and does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.<br />\n
          \t\t\t\t<br />\n
          This part of ISO/IEC 15026 specifies minimum requirements for the structure and contents of an assurance case. An assurance case includes a top-level claim for a property of a system or product (or set of claims), systematic argumentation regarding this claim, and the evidence and explicit assumptions that underlie this argumentation. Arguing through multiple levels of subordinate claims, this structured argumentation connects the top-level claim to the evidence and assumptions. This part of ISO/IEC 15026 does not place requirements on the quality of the contents of an assurance case. Rathere, it places requirements on the existence of the contents and structure of an assurance case. While several notations and slightly varying terminologies are currently used in practice, this part of ISO/IEC 15026 does not require the use of a particular terminology or graphical representation. Likewise, it places no requirements on the means of physical implementation of the data, including no requirements for redundancy or co-location.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard--Adoption of ISO/IEC 15026-2:2011 Systems and Software Engineering--Systems and Software Assurance--Part 2: Assurance Case"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100180 …}
    #channels: Doctrine\ORM\PersistentCollection {#100174 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100178 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100176 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100189 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100158
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1648764000 {#100197
      date: 2022-04-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1318284000 {#100196
      date: 2011-10-11 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#100190
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "15026-2"
    -bookCollection: ""
    -pageCount: 28
    -documents: Doctrine\ORM\PersistentCollection {#100187 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100185 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 124.0 MiB 612.93 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128461
    #id: 12143
    #code: "IEEE00007155"
    #attributes: Doctrine\ORM\PersistentCollection {#128485 …}
    #variants: Doctrine\ORM\PersistentCollection {#128483 …}
    #options: Doctrine\ORM\PersistentCollection {#128478 …}
    #associations: Doctrine\ORM\PersistentCollection {#128481 …}
    #createdAt: DateTime @1751040228 {#128474
      date: 2025-06-27 18:03:48.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128467
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128496 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128592
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128461}
        #id: 43581
        #name: "IEEE/ISO/IEC 15026-1_Revision:2019"
        #slug: "ieee-iso-iec-15026-1-revision-2019-ieee00007155-243796"
        #description: """
          Revision Standard - Active.<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and their relationships, thereby establishing a basis for shared understanding of the concepts and principles central to all parts of ISO/IEC/IEEE 15026 across its user communities. It provides information to users of the subsequent parts of ISO/IEC/IEEE 15026, including the use of each part and the combined use of multiple parts. Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in the ISO/IEC/IEEE 15026 series.<br />\n
          \t\t\t\t<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and relationships to form a basis for shared understanding across user communities for assurance. It provides information to users of the other parts of ISO/IEC/IEEE 15026 including the combined use of multiple parts. The essential concept introduced by ISO/IEC/IEEE 15026 (all parts) is the statement of claims in an assurance case and the support of those claims through argumentation and evidence. These claims are in the context of assurance for properties of systems and software within life cycle processes for the system or software product. Assurance for a service being operated and managed on an ongoing basis is not covered in ISO/IEC/IEEE 15026 (all parts). A variety of potential users of ISO/IEC/IEEE 15026 (all parts) exists including developers and maintainers of assurance cases and those who wish to develop, sustain, evaluate or acquire a system that possesses requirements for specific properties in such a way as to be more certain of those properties and their requirements. ISO/IEC/IEEE 15026 (all parts) uses concepts and terms consistent with ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and generally consistent with the ISO/IEC 25000 series, but the potential users of ISO/IEC/IEEE 15026 (all parts) need to understand the differences from concepts and terms to which they may be accustomed. This document attempts to clarify these differences. The primary purpose of this document is to aid users of the other parts of ISO/IEC/IEEE 15026 by providing context, concepts and explanations for assurance, assurance cases and integrity levels. While essential to assurance practice, details regarding exactly how to measure, demonstrate or analyse particular properties are not covered. These are the subjects of more specialized standards of which a number are referenced and included in the Bibliography.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance --Part 1:Concepts and vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128494 …}
    #channels: Doctrine\ORM\PersistentCollection {#128487 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128491 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128489 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128501 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128460
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128509
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1551394800 {#128480
      date: 2019-03-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-1"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#128500 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128498 …}
  }
  "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 {#128553
  +product: App\Entity\Product\Product {#128461
    #id: 12143
    #code: "IEEE00007155"
    #attributes: Doctrine\ORM\PersistentCollection {#128485 …}
    #variants: Doctrine\ORM\PersistentCollection {#128483 …}
    #options: Doctrine\ORM\PersistentCollection {#128478 …}
    #associations: Doctrine\ORM\PersistentCollection {#128481 …}
    #createdAt: DateTime @1751040228 {#128474
      date: 2025-06-27 18:03:48.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128467
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128496 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128592
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128461}
        #id: 43581
        #name: "IEEE/ISO/IEC 15026-1_Revision:2019"
        #slug: "ieee-iso-iec-15026-1-revision-2019-ieee00007155-243796"
        #description: """
          Revision Standard - Active.<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and their relationships, thereby establishing a basis for shared understanding of the concepts and principles central to all parts of ISO/IEC/IEEE 15026 across its user communities. It provides information to users of the subsequent parts of ISO/IEC/IEEE 15026, including the use of each part and the combined use of multiple parts. Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in the ISO/IEC/IEEE 15026 series.<br />\n
          \t\t\t\t<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and relationships to form a basis for shared understanding across user communities for assurance. It provides information to users of the other parts of ISO/IEC/IEEE 15026 including the combined use of multiple parts. The essential concept introduced by ISO/IEC/IEEE 15026 (all parts) is the statement of claims in an assurance case and the support of those claims through argumentation and evidence. These claims are in the context of assurance for properties of systems and software within life cycle processes for the system or software product. Assurance for a service being operated and managed on an ongoing basis is not covered in ISO/IEC/IEEE 15026 (all parts). A variety of potential users of ISO/IEC/IEEE 15026 (all parts) exists including developers and maintainers of assurance cases and those who wish to develop, sustain, evaluate or acquire a system that possesses requirements for specific properties in such a way as to be more certain of those properties and their requirements. ISO/IEC/IEEE 15026 (all parts) uses concepts and terms consistent with ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and generally consistent with the ISO/IEC 25000 series, but the potential users of ISO/IEC/IEEE 15026 (all parts) need to understand the differences from concepts and terms to which they may be accustomed. This document attempts to clarify these differences. The primary purpose of this document is to aid users of the other parts of ISO/IEC/IEEE 15026 by providing context, concepts and explanations for assurance, assurance cases and integrity levels. While essential to assurance practice, details regarding exactly how to measure, demonstrate or analyse particular properties are not covered. These are the subjects of more specialized standards of which a number are referenced and included in the Bibliography.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance --Part 1:Concepts and vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128494 …}
    #channels: Doctrine\ORM\PersistentCollection {#128487 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128491 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128489 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128501 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128460
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128509
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1551394800 {#128480
      date: 2019-03-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-1"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#128500 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128498 …}
  }
  +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 124.0 MiB 0.32 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128461
    #id: 12143
    #code: "IEEE00007155"
    #attributes: Doctrine\ORM\PersistentCollection {#128485 …}
    #variants: Doctrine\ORM\PersistentCollection {#128483 …}
    #options: Doctrine\ORM\PersistentCollection {#128478 …}
    #associations: Doctrine\ORM\PersistentCollection {#128481 …}
    #createdAt: DateTime @1751040228 {#128474
      date: 2025-06-27 18:03:48.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128467
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128496 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128592
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128461}
        #id: 43581
        #name: "IEEE/ISO/IEC 15026-1_Revision:2019"
        #slug: "ieee-iso-iec-15026-1-revision-2019-ieee00007155-243796"
        #description: """
          Revision Standard - Active.<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and their relationships, thereby establishing a basis for shared understanding of the concepts and principles central to all parts of ISO/IEC/IEEE 15026 across its user communities. It provides information to users of the subsequent parts of ISO/IEC/IEEE 15026, including the use of each part and the combined use of multiple parts. Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in the ISO/IEC/IEEE 15026 series.<br />\n
          \t\t\t\t<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and relationships to form a basis for shared understanding across user communities for assurance. It provides information to users of the other parts of ISO/IEC/IEEE 15026 including the combined use of multiple parts. The essential concept introduced by ISO/IEC/IEEE 15026 (all parts) is the statement of claims in an assurance case and the support of those claims through argumentation and evidence. These claims are in the context of assurance for properties of systems and software within life cycle processes for the system or software product. Assurance for a service being operated and managed on an ongoing basis is not covered in ISO/IEC/IEEE 15026 (all parts). A variety of potential users of ISO/IEC/IEEE 15026 (all parts) exists including developers and maintainers of assurance cases and those who wish to develop, sustain, evaluate or acquire a system that possesses requirements for specific properties in such a way as to be more certain of those properties and their requirements. ISO/IEC/IEEE 15026 (all parts) uses concepts and terms consistent with ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and generally consistent with the ISO/IEC 25000 series, but the potential users of ISO/IEC/IEEE 15026 (all parts) need to understand the differences from concepts and terms to which they may be accustomed. This document attempts to clarify these differences. The primary purpose of this document is to aid users of the other parts of ISO/IEC/IEEE 15026 by providing context, concepts and explanations for assurance, assurance cases and integrity levels. While essential to assurance practice, details regarding exactly how to measure, demonstrate or analyse particular properties are not covered. These are the subjects of more specialized standards of which a number are referenced and included in the Bibliography.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance --Part 1:Concepts and vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128494 …}
    #channels: Doctrine\ORM\PersistentCollection {#128487 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128491 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128489 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128501 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128460
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128509
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1551394800 {#128480
      date: 2019-03-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-1"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#128500 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128498 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#128594
  +product: App\Entity\Product\Product {#128461
    #id: 12143
    #code: "IEEE00007155"
    #attributes: Doctrine\ORM\PersistentCollection {#128485 …}
    #variants: Doctrine\ORM\PersistentCollection {#128483 …}
    #options: Doctrine\ORM\PersistentCollection {#128478 …}
    #associations: Doctrine\ORM\PersistentCollection {#128481 …}
    #createdAt: DateTime @1751040228 {#128474
      date: 2025-06-27 18:03:48.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128467
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128496 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128592
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128461}
        #id: 43581
        #name: "IEEE/ISO/IEC 15026-1_Revision:2019"
        #slug: "ieee-iso-iec-15026-1-revision-2019-ieee00007155-243796"
        #description: """
          Revision Standard - Active.<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and their relationships, thereby establishing a basis for shared understanding of the concepts and principles central to all parts of ISO/IEC/IEEE 15026 across its user communities. It provides information to users of the subsequent parts of ISO/IEC/IEEE 15026, including the use of each part and the combined use of multiple parts. Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in the ISO/IEC/IEEE 15026 series.<br />\n
          \t\t\t\t<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and relationships to form a basis for shared understanding across user communities for assurance. It provides information to users of the other parts of ISO/IEC/IEEE 15026 including the combined use of multiple parts. The essential concept introduced by ISO/IEC/IEEE 15026 (all parts) is the statement of claims in an assurance case and the support of those claims through argumentation and evidence. These claims are in the context of assurance for properties of systems and software within life cycle processes for the system or software product. Assurance for a service being operated and managed on an ongoing basis is not covered in ISO/IEC/IEEE 15026 (all parts). A variety of potential users of ISO/IEC/IEEE 15026 (all parts) exists including developers and maintainers of assurance cases and those who wish to develop, sustain, evaluate or acquire a system that possesses requirements for specific properties in such a way as to be more certain of those properties and their requirements. ISO/IEC/IEEE 15026 (all parts) uses concepts and terms consistent with ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and generally consistent with the ISO/IEC 25000 series, but the potential users of ISO/IEC/IEEE 15026 (all parts) need to understand the differences from concepts and terms to which they may be accustomed. This document attempts to clarify these differences. The primary purpose of this document is to aid users of the other parts of ISO/IEC/IEEE 15026 by providing context, concepts and explanations for assurance, assurance cases and integrity levels. While essential to assurance practice, details regarding exactly how to measure, demonstrate or analyse particular properties are not covered. These are the subjects of more specialized standards of which a number are referenced and included in the Bibliography.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance --Part 1:Concepts and vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128494 …}
    #channels: Doctrine\ORM\PersistentCollection {#128487 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128491 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128489 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128501 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128460
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128509
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1551394800 {#128480
      date: 2019-03-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-1"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#128500 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128498 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 124.0 MiB 3.26 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128461
    #id: 12143
    #code: "IEEE00007155"
    #attributes: Doctrine\ORM\PersistentCollection {#128485 …}
    #variants: Doctrine\ORM\PersistentCollection {#128483 …}
    #options: Doctrine\ORM\PersistentCollection {#128478 …}
    #associations: Doctrine\ORM\PersistentCollection {#128481 …}
    #createdAt: DateTime @1751040228 {#128474
      date: 2025-06-27 18:03:48.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128467
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128496 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128592
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128461}
        #id: 43581
        #name: "IEEE/ISO/IEC 15026-1_Revision:2019"
        #slug: "ieee-iso-iec-15026-1-revision-2019-ieee00007155-243796"
        #description: """
          Revision Standard - Active.<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and their relationships, thereby establishing a basis for shared understanding of the concepts and principles central to all parts of ISO/IEC/IEEE 15026 across its user communities. It provides information to users of the subsequent parts of ISO/IEC/IEEE 15026, including the use of each part and the combined use of multiple parts. Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in the ISO/IEC/IEEE 15026 series.<br />\n
          \t\t\t\t<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and relationships to form a basis for shared understanding across user communities for assurance. It provides information to users of the other parts of ISO/IEC/IEEE 15026 including the combined use of multiple parts. The essential concept introduced by ISO/IEC/IEEE 15026 (all parts) is the statement of claims in an assurance case and the support of those claims through argumentation and evidence. These claims are in the context of assurance for properties of systems and software within life cycle processes for the system or software product. Assurance for a service being operated and managed on an ongoing basis is not covered in ISO/IEC/IEEE 15026 (all parts). A variety of potential users of ISO/IEC/IEEE 15026 (all parts) exists including developers and maintainers of assurance cases and those who wish to develop, sustain, evaluate or acquire a system that possesses requirements for specific properties in such a way as to be more certain of those properties and their requirements. ISO/IEC/IEEE 15026 (all parts) uses concepts and terms consistent with ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and generally consistent with the ISO/IEC 25000 series, but the potential users of ISO/IEC/IEEE 15026 (all parts) need to understand the differences from concepts and terms to which they may be accustomed. This document attempts to clarify these differences. The primary purpose of this document is to aid users of the other parts of ISO/IEC/IEEE 15026 by providing context, concepts and explanations for assurance, assurance cases and integrity levels. While essential to assurance practice, details regarding exactly how to measure, demonstrate or analyse particular properties are not covered. These are the subjects of more specialized standards of which a number are referenced and included in the Bibliography.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance --Part 1:Concepts and vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128494 …}
    #channels: Doctrine\ORM\PersistentCollection {#128487 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128491 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128489 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128501 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128460
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128509
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1551394800 {#128480
      date: 2019-03-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-1"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#128500 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128498 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#128671
  +product: App\Entity\Product\Product {#128461
    #id: 12143
    #code: "IEEE00007155"
    #attributes: Doctrine\ORM\PersistentCollection {#128485 …}
    #variants: Doctrine\ORM\PersistentCollection {#128483 …}
    #options: Doctrine\ORM\PersistentCollection {#128478 …}
    #associations: Doctrine\ORM\PersistentCollection {#128481 …}
    #createdAt: DateTime @1751040228 {#128474
      date: 2025-06-27 18:03:48.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970307 {#128467
      date: 2025-07-31 15:58:27.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128496 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128592
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128461}
        #id: 43581
        #name: "IEEE/ISO/IEC 15026-1_Revision:2019"
        #slug: "ieee-iso-iec-15026-1-revision-2019-ieee00007155-243796"
        #description: """
          Revision Standard - Active.<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and their relationships, thereby establishing a basis for shared understanding of the concepts and principles central to all parts of ISO/IEC/IEEE 15026 across its user communities. It provides information to users of the subsequent parts of ISO/IEC/IEEE 15026, including the use of each part and the combined use of multiple parts. Coverage of assurance for a service being operated and managed on an ongoing basis is not covered in the ISO/IEC/IEEE 15026 series.<br />\n
          \t\t\t\t<br />\n
          This document defines assurance-related terms and establishes an organized set of concepts and relationships to form a basis for shared understanding across user communities for assurance. It provides information to users of the other parts of ISO/IEC/IEEE 15026 including the combined use of multiple parts. The essential concept introduced by ISO/IEC/IEEE 15026 (all parts) is the statement of claims in an assurance case and the support of those claims through argumentation and evidence. These claims are in the context of assurance for properties of systems and software within life cycle processes for the system or software product. Assurance for a service being operated and managed on an ongoing basis is not covered in ISO/IEC/IEEE 15026 (all parts). A variety of potential users of ISO/IEC/IEEE 15026 (all parts) exists including developers and maintainers of assurance cases and those who wish to develop, sustain, evaluate or acquire a system that possesses requirements for specific properties in such a way as to be more certain of those properties and their requirements. ISO/IEC/IEEE 15026 (all parts) uses concepts and terms consistent with ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and generally consistent with the ISO/IEC 25000 series, but the potential users of ISO/IEC/IEEE 15026 (all parts) need to understand the differences from concepts and terms to which they may be accustomed. This document attempts to clarify these differences. The primary purpose of this document is to aid users of the other parts of ISO/IEC/IEEE 15026 by providing context, concepts and explanations for assurance, assurance cases and integrity levels. While essential to assurance practice, details regarding exactly how to measure, demonstrate or analyse particular properties are not covered. These are the subjects of more specialized standards of which a number are referenced and included in the Bibliography.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Systems and software assurance --Part 1:Concepts and vocabulary"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128494 …}
    #channels: Doctrine\ORM\PersistentCollection {#128487 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7272 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128491 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128489 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128501 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128460
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128509
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1551394800 {#128480
      date: 2019-03-01 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "15026-1"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#128500 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128498 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}