Forms
sylius_add_to_cart
Errors
This form has no errors.
Default Data
| Property | Value |
|---|---|
| Model Format | same as normalized format |
| Normalized Format | Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#120538 -cart: App\Entity\Order\Order {#13364 …} -cartItem: App\Entity\Order\OrderItem {#120526 #id: null #order: null #quantity: 1 #unitPrice: 0 #originalUnitPrice: 0 #total: 0 #immutable: false #units: Doctrine\Common\Collections\ArrayCollection {#120550 …} #unitsTotal: 0 #adjustments: Doctrine\Common\Collections\ArrayCollection {#120551 …} #adjustmentsTotal: 0 #version: 1 #variant: App\Entity\Product\ProductVariant {#8103 #id: 6186 #code: "IEEE00005789PDF" #product: App\Entity\Product\Product {#7310 #id: 11240 #code: "IEEE00005789" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 #collection: Doctrine\Common\Collections\ArrayCollection {#7917 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7310} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#277600 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039567 {#7274 : 2025-06-27 17:52:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969918 {#7322 : 2025-07-31 15:51:58.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #id: 39969 #name: "IEEE/ISO/IEC 15289:2015" #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892" #description: """ Revision Standard - Superseded.<br />\n The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. However, the requirements for the life-cycle processes do not uniquely and unambiguously state the requirements for the information items contents or the information needed by a user of an information item. Moreover, the information from the life-cycle processes may overlap or may be created and revised at different times. In short, the analyzed references do not result in a logically complete list of information items.<br />\n \t\t\t\t<br />\n This International Standard specifies the purpose and content of all identified systems and software life-cycle and service management information items (documentation). The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of the documentation schema would be more rigorous than specified by ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” Thus, information items may be combined or subdivided as needed for project or organizational purposes, as further defined in Clause 2, applicability, and Clause 3, Conformance. This International Standard does not establish a service management system. The scope of this International Standard does not include the following: a) the format or content of recommended input data or input information items, except for the content of those input items that are also output information items; b) instructions on combining or subdividing information items and information item contents of a similar nature; c) guidance on selecting an appropriate presentation format, delivery media, and maintenance technology for system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1743289200 {#7317 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1645138800 {#7292 : 2022-02-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1431640800 {#7318 : 2015-05-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "15289" -bookCollection: "" -pageCount: 95 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } #optionValues: Doctrine\ORM\PersistentCollection {#8319 …} #position: 0 #createdAt: DateTime @1751041267 {#7283 : 2025-06-27 18:21:07.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1756908201 {#8120 : 2025-09-03 16:03:21.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#8263 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductVariantTranslation {#93368 #locale: "en_US" #translatable: App\Entity\Product\ProductVariant {#8103} #id: 6216 #name: null -shortDescription: null -description: null -notes: null -shippingInformation: "Instant download" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #version: 10 #onHold: 0 #onHand: 0 #tracked: false #weight: 0.0 #width: null #height: null #depth: null #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8135 …} #shippingCategory: null #channelPricings: Doctrine\ORM\PersistentCollection {#8297 …} #shippingRequired: true #images: Doctrine\ORM\PersistentCollection {#8294 …} -apiLastModifiedAt: DateTime @1756850400 {#8102 : 2025-09-03 00:00:00.0 Europe/Paris (+02:00) } -publishedAt: null -isbn: "978-0-7381-9529-2" -ean: "9780738195292" -numberOfUsers: 1 -physicalProduct: false -downloadableImmediately: true -downloadable: true -drmViewerUrl: "https://online-viewer.normadoc.com/DBqhCn" -sellable: true -documents: Doctrine\ORM\PersistentCollection {#8131 …} -drmTokens: Doctrine\ORM\PersistentCollection {#8123 …} -enabledForSubscribers: true -currentAreaContext: null } #productName: null #variantName: null } } |
| View Format | same as normalized format |
Submitted Data
This form was not submitted.
Passed Options
| Option | Passed Value | Resolved Value |
|---|---|---|
| data | Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#120538 -cart: App\Entity\Order\Order {#13364 …} -cartItem: App\Entity\Order\OrderItem {#120526 #id: null #order: null #quantity: 1 #unitPrice: 0 #originalUnitPrice: 0 #total: 0 #immutable: false #units: Doctrine\Common\Collections\ArrayCollection {#120550 …} #unitsTotal: 0 #adjustments: Doctrine\Common\Collections\ArrayCollection {#120551 …} #adjustmentsTotal: 0 #version: 1 #variant: App\Entity\Product\ProductVariant {#8103 #id: 6186 #code: "IEEE00005789PDF" #product: App\Entity\Product\Product {#7310 #id: 11240 #code: "IEEE00005789" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 #collection: Doctrine\Common\Collections\ArrayCollection {#7917 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7310} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#277600 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039567 {#7274 : 2025-06-27 17:52:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969918 {#7322 : 2025-07-31 15:51:58.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #id: 39969 #name: "IEEE/ISO/IEC 15289:2015" #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892" #description: """ Revision Standard - Superseded.<br />\n The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. However, the requirements for the life-cycle processes do not uniquely and unambiguously state the requirements for the information items contents or the information needed by a user of an information item. Moreover, the information from the life-cycle processes may overlap or may be created and revised at different times. In short, the analyzed references do not result in a logically complete list of information items.<br />\n \t\t\t\t<br />\n This International Standard specifies the purpose and content of all identified systems and software life-cycle and service management information items (documentation). The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of the documentation schema would be more rigorous than specified by ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” Thus, information items may be combined or subdivided as needed for project or organizational purposes, as further defined in Clause 2, applicability, and Clause 3, Conformance. This International Standard does not establish a service management system. The scope of this International Standard does not include the following: a) the format or content of recommended input data or input information items, except for the content of those input items that are also output information items; b) instructions on combining or subdividing information items and information item contents of a similar nature; c) guidance on selecting an appropriate presentation format, delivery media, and maintenance technology for system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1743289200 {#7317 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1645138800 {#7292 : 2022-02-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1431640800 {#7318 : 2015-05-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "15289" -bookCollection: "" -pageCount: 95 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } #optionValues: Doctrine\ORM\PersistentCollection {#8319 …} #position: 0 #createdAt: DateTime @1751041267 {#7283 : 2025-06-27 18:21:07.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1756908201 {#8120 : 2025-09-03 16:03:21.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#8263 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductVariantTranslation {#93368 #locale: "en_US" #translatable: App\Entity\Product\ProductVariant {#8103} #id: 6216 #name: null -shortDescription: null -description: null -notes: null -shippingInformation: "Instant download" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #version: 10 #onHold: 0 #onHand: 0 #tracked: false #weight: 0.0 #width: null #height: null #depth: null #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8135 …} #shippingCategory: null #channelPricings: Doctrine\ORM\PersistentCollection {#8297 …} #shippingRequired: true #images: Doctrine\ORM\PersistentCollection {#8294 …} -apiLastModifiedAt: DateTime @1756850400 {#8102 : 2025-09-03 00:00:00.0 Europe/Paris (+02:00) } -publishedAt: null -isbn: "978-0-7381-9529-2" -ean: "9780738195292" -numberOfUsers: 1 -physicalProduct: false -downloadableImmediately: true -downloadable: true -drmViewerUrl: "https://online-viewer.normadoc.com/DBqhCn" -sellable: true -documents: Doctrine\ORM\PersistentCollection {#8131 …} -drmTokens: Doctrine\ORM\PersistentCollection {#8123 …} -enabledForSubscribers: true -currentAreaContext: null } #productName: null #variantName: null } } |
same as passed value |
| product | App\Entity\Product\Product {#7310 #id: 11240 #code: "IEEE00005789" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 #collection: Doctrine\Common\Collections\ArrayCollection {#7917 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7310} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#277600 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039567 {#7274 : 2025-06-27 17:52:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969918 {#7322 : 2025-07-31 15:51:58.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #id: 39969 #name: "IEEE/ISO/IEC 15289:2015" #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892" #description: """ Revision Standard - Superseded.<br />\n The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. However, the requirements for the life-cycle processes do not uniquely and unambiguously state the requirements for the information items contents or the information needed by a user of an information item. Moreover, the information from the life-cycle processes may overlap or may be created and revised at different times. In short, the analyzed references do not result in a logically complete list of information items.<br />\n \t\t\t\t<br />\n This International Standard specifies the purpose and content of all identified systems and software life-cycle and service management information items (documentation). The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of the documentation schema would be more rigorous than specified by ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” Thus, information items may be combined or subdivided as needed for project or organizational purposes, as further defined in Clause 2, applicability, and Clause 3, Conformance. This International Standard does not establish a service management system. The scope of this International Standard does not include the following: a) the format or content of recommended input data or input information items, except for the content of those input items that are also output information items; b) instructions on combining or subdividing information items and information item contents of a similar nature; c) guidance on selecting an appropriate presentation format, delivery media, and maintenance technology for system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1743289200 {#7317 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1645138800 {#7292 : 2022-02-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1431640800 {#7318 : 2015-05-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "15289" -bookCollection: "" -pageCount: 95 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } |
same as passed value |
Resolved Options
| Option | Value |
|---|---|
| action | "" |
| allow_extra_fields | false |
| allow_file_upload | false |
| attr | [] |
| attr_translation_parameters | [] |
| auto_initialize | true |
| block_name | null |
| block_prefix | null |
| by_reference | true |
| compound | true |
| constraints | [] |
| csrf_field_name | "_token" |
| csrf_message | "The CSRF token is invalid. Please try to resubmit the form." |
| csrf_protection | true |
| csrf_token_id | null |
| csrf_token_manager | Symfony\Component\Security\Csrf\CsrfTokenManager {#120558 -generator: Symfony\Component\Security\Csrf\TokenGenerator\UriSafeTokenGenerator {#120559 …} -storage: Symfony\Component\Security\Csrf\TokenStorage\SessionTokenStorage {#120560 …} -namespace: Closure() {#120562 …} } |
| data | Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#120538 -cart: App\Entity\Order\Order {#13364 …} -cartItem: App\Entity\Order\OrderItem {#120526 #id: null #order: null #quantity: 1 #unitPrice: 0 #originalUnitPrice: 0 #total: 0 #immutable: false #units: Doctrine\Common\Collections\ArrayCollection {#120550 …} #unitsTotal: 0 #adjustments: Doctrine\Common\Collections\ArrayCollection {#120551 …} #adjustmentsTotal: 0 #version: 1 #variant: App\Entity\Product\ProductVariant {#8103 #id: 6186 #code: "IEEE00005789PDF" #product: App\Entity\Product\Product {#7310 #id: 11240 #code: "IEEE00005789" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 #collection: Doctrine\Common\Collections\ArrayCollection {#7917 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7310} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#277600 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039567 {#7274 : 2025-06-27 17:52:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969918 {#7322 : 2025-07-31 15:51:58.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #id: 39969 #name: "IEEE/ISO/IEC 15289:2015" #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892" #description: """ Revision Standard - Superseded.<br />\n The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. However, the requirements for the life-cycle processes do not uniquely and unambiguously state the requirements for the information items contents or the information needed by a user of an information item. Moreover, the information from the life-cycle processes may overlap or may be created and revised at different times. In short, the analyzed references do not result in a logically complete list of information items.<br />\n \t\t\t\t<br />\n This International Standard specifies the purpose and content of all identified systems and software life-cycle and service management information items (documentation). The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of the documentation schema would be more rigorous than specified by ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” Thus, information items may be combined or subdivided as needed for project or organizational purposes, as further defined in Clause 2, applicability, and Clause 3, Conformance. This International Standard does not establish a service management system. The scope of this International Standard does not include the following: a) the format or content of recommended input data or input information items, except for the content of those input items that are also output information items; b) instructions on combining or subdividing information items and information item contents of a similar nature; c) guidance on selecting an appropriate presentation format, delivery media, and maintenance technology for system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1743289200 {#7317 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1645138800 {#7292 : 2022-02-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1431640800 {#7318 : 2015-05-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "15289" -bookCollection: "" -pageCount: 95 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } #optionValues: Doctrine\ORM\PersistentCollection {#8319 …} #position: 0 #createdAt: DateTime @1751041267 {#7283 : 2025-06-27 18:21:07.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1756908201 {#8120 : 2025-09-03 16:03:21.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#8263 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductVariantTranslation {#93368 #locale: "en_US" #translatable: App\Entity\Product\ProductVariant {#8103} #id: 6216 #name: null -shortDescription: null -description: null -notes: null -shippingInformation: "Instant download" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #version: 10 #onHold: 0 #onHand: 0 #tracked: false #weight: 0.0 #width: null #height: null #depth: null #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8135 …} #shippingCategory: null #channelPricings: Doctrine\ORM\PersistentCollection {#8297 …} #shippingRequired: true #images: Doctrine\ORM\PersistentCollection {#8294 …} -apiLastModifiedAt: DateTime @1756850400 {#8102 : 2025-09-03 00:00:00.0 Europe/Paris (+02:00) } -publishedAt: null -isbn: "978-0-7381-9529-2" -ean: "9780738195292" -numberOfUsers: 1 -physicalProduct: false -downloadableImmediately: true -downloadable: true -drmViewerUrl: "https://online-viewer.normadoc.com/DBqhCn" -sellable: true -documents: Doctrine\ORM\PersistentCollection {#8131 …} -drmTokens: Doctrine\ORM\PersistentCollection {#8123 …} -enabledForSubscribers: true -currentAreaContext: null } #productName: null #variantName: null } } |
| data_class | "Sylius\Bundle\OrderBundle\Controller\AddToCartCommand" |
| disabled | false |
| empty_data | Closure(FormInterface $form) {#120585 : "Symfony\Component\Form\Extension\Core\Type\FormType" : { : "Sylius\Bundle\OrderBundle\Controller\AddToCartCommand" } } |
| error_bubbling | true |
| error_mapping | [] |
| extra_fields_message | "This form should not contain extra fields." |
| form_attr | false |
| getter | null |
| help | null |
| help_attr | [] |
| help_html | false |
| help_translation_parameters | [] |
| inherit_data | false |
| invalid_message | "This value is not valid." |
| invalid_message_parameters | [] |
| is_empty_callback | null |
| label | null |
| label_attr | [] |
| label_format | null |
| label_html | false |
| label_translation_parameters | [] |
| mapped | true |
| method | "POST" |
| post_max_size_message | "The uploaded file was too large. Please try to upload a smaller file." |
| priority | 0 |
| product | App\Entity\Product\Product {#7310 #id: 11240 #code: "IEEE00005789" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 #collection: Doctrine\Common\Collections\ArrayCollection {#7917 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7310} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#277600 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039567 {#7274 : 2025-06-27 17:52:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969918 {#7322 : 2025-07-31 15:51:58.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #id: 39969 #name: "IEEE/ISO/IEC 15289:2015" #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892" #description: """ Revision Standard - Superseded.<br />\n The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. However, the requirements for the life-cycle processes do not uniquely and unambiguously state the requirements for the information items contents or the information needed by a user of an information item. Moreover, the information from the life-cycle processes may overlap or may be created and revised at different times. In short, the analyzed references do not result in a logically complete list of information items.<br />\n \t\t\t\t<br />\n This International Standard specifies the purpose and content of all identified systems and software life-cycle and service management information items (documentation). The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of the documentation schema would be more rigorous than specified by ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” Thus, information items may be combined or subdivided as needed for project or organizational purposes, as further defined in Clause 2, applicability, and Clause 3, Conformance. This International Standard does not establish a service management system. The scope of this International Standard does not include the following: a) the format or content of recommended input data or input information items, except for the content of those input items that are also output information items; b) instructions on combining or subdividing information items and information item contents of a similar nature; c) guidance on selecting an appropriate presentation format, delivery media, and maintenance technology for system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1743289200 {#7317 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1645138800 {#7292 : 2022-02-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1431640800 {#7318 : 2015-05-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "15289" -bookCollection: "" -pageCount: 95 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } |
| property_path | null |
| required | true |
| row_attr | [] |
| setter | null |
| translation_domain | null |
| trim | true |
| upload_max_size_message | Closure() {#120587 : "Symfony\Component\Form\Extension\Validator\Type\UploadValidatorExtension" : { : Symfony\Component\Translation\DataCollectorTranslator {#2251 …} : Closure() {#120586 …} : "validators" } } |
| validation_groups | [
"sylius"
] |
View Vars
| Variable | Value |
|---|---|
| action | "" |
| attr | [] |
| attr_translation_parameters | [] |
| block_prefixes | [ "form" "sylius_add_to_cart" "_sylius_add_to_cart" ] |
| cache_key | "_sylius_add_to_cart_sylius_add_to_cart" |
| compound | true |
| data | Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#120538 -cart: App\Entity\Order\Order {#13364 …} -cartItem: App\Entity\Order\OrderItem {#120526 #id: null #order: null #quantity: 1 #unitPrice: 0 #originalUnitPrice: 0 #total: 0 #immutable: false #units: Doctrine\Common\Collections\ArrayCollection {#120550 …} #unitsTotal: 0 #adjustments: Doctrine\Common\Collections\ArrayCollection {#120551 …} #adjustmentsTotal: 0 #version: 1 #variant: App\Entity\Product\ProductVariant {#8103 #id: 6186 #code: "IEEE00005789PDF" #product: App\Entity\Product\Product {#7310 #id: 11240 #code: "IEEE00005789" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 #collection: Doctrine\Common\Collections\ArrayCollection {#7917 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7310} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#277600 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039567 {#7274 : 2025-06-27 17:52:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969918 {#7322 : 2025-07-31 15:51:58.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #id: 39969 #name: "IEEE/ISO/IEC 15289:2015" #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892" #description: """ Revision Standard - Superseded.<br />\n The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. However, the requirements for the life-cycle processes do not uniquely and unambiguously state the requirements for the information items contents or the information needed by a user of an information item. Moreover, the information from the life-cycle processes may overlap or may be created and revised at different times. In short, the analyzed references do not result in a logically complete list of information items.<br />\n \t\t\t\t<br />\n This International Standard specifies the purpose and content of all identified systems and software life-cycle and service management information items (documentation). The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of the documentation schema would be more rigorous than specified by ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” Thus, information items may be combined or subdivided as needed for project or organizational purposes, as further defined in Clause 2, applicability, and Clause 3, Conformance. This International Standard does not establish a service management system. The scope of this International Standard does not include the following: a) the format or content of recommended input data or input information items, except for the content of those input items that are also output information items; b) instructions on combining or subdividing information items and information item contents of a similar nature; c) guidance on selecting an appropriate presentation format, delivery media, and maintenance technology for system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1743289200 {#7317 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1645138800 {#7292 : 2022-02-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1431640800 {#7318 : 2015-05-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "15289" -bookCollection: "" -pageCount: 95 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } #optionValues: Doctrine\ORM\PersistentCollection {#8319 …} #position: 0 #createdAt: DateTime @1751041267 {#7283 : 2025-06-27 18:21:07.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1756908201 {#8120 : 2025-09-03 16:03:21.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#8263 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductVariantTranslation {#93368 #locale: "en_US" #translatable: App\Entity\Product\ProductVariant {#8103} #id: 6216 #name: null -shortDescription: null -description: null -notes: null -shippingInformation: "Instant download" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #version: 10 #onHold: 0 #onHand: 0 #tracked: false #weight: 0.0 #width: null #height: null #depth: null #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8135 …} #shippingCategory: null #channelPricings: Doctrine\ORM\PersistentCollection {#8297 …} #shippingRequired: true #images: Doctrine\ORM\PersistentCollection {#8294 …} -apiLastModifiedAt: DateTime @1756850400 {#8102 : 2025-09-03 00:00:00.0 Europe/Paris (+02:00) } -publishedAt: null -isbn: "978-0-7381-9529-2" -ean: "9780738195292" -numberOfUsers: 1 -physicalProduct: false -downloadableImmediately: true -downloadable: true -drmViewerUrl: "https://online-viewer.normadoc.com/DBqhCn" -sellable: true -documents: Doctrine\ORM\PersistentCollection {#8131 …} -drmTokens: Doctrine\ORM\PersistentCollection {#8123 …} -enabledForSubscribers: true -currentAreaContext: null } #productName: null #variantName: null } } |
| disabled | false |
| errors | Symfony\Component\Form\FormErrorIterator {#120612 -form: Symfony\Component\Form\Form {#120617 …} -errors: [] } |
| form | Symfony\Component\Form\FormView {#120588 …5} |
| full_name | "sylius_add_to_cart" |
| help | null |
| help_attr | [] |
| help_html | false |
| help_translation_parameters | [] |
| id | "sylius_add_to_cart" |
| label | null |
| label_attr | [] |
| label_format | null |
| label_html | false |
| label_translation_parameters | [] |
| method | "POST" |
| multipart | false |
| name | "sylius_add_to_cart" |
| priority | 0 |
| required | true |
| row_attr | [] |
| submitted | false |
| translation_domain | null |
| unique_block_prefix | "_sylius_add_to_cart" |
| valid | true |
| value | Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#120538 -cart: App\Entity\Order\Order {#13364 …} -cartItem: App\Entity\Order\OrderItem {#120526 #id: null #order: null #quantity: 1 #unitPrice: 0 #originalUnitPrice: 0 #total: 0 #immutable: false #units: Doctrine\Common\Collections\ArrayCollection {#120550 …} #unitsTotal: 0 #adjustments: Doctrine\Common\Collections\ArrayCollection {#120551 …} #adjustmentsTotal: 0 #version: 1 #variant: App\Entity\Product\ProductVariant {#8103 #id: 6186 #code: "IEEE00005789PDF" #product: App\Entity\Product\Product {#7310 #id: 11240 #code: "IEEE00005789" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 #collection: Doctrine\Common\Collections\ArrayCollection {#7917 …} #initialized: true -snapshot: [ …4] -owner: App\Entity\Product\Product {#7310} -association: [ …21] -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …} -backRefFieldName: null -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#277600 …} -isDirty: false } #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751039567 {#7274 : 2025-06-27 17:52:47.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969918 {#7322 : 2025-07-31 15:51:58.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #id: 39969 #name: "IEEE/ISO/IEC 15289:2015" #slug: "ieee-iso-iec-15289-2015-ieee00005789-242892" #description: """ Revision Standard - Superseded.<br />\n The purpose and content of all identified systems and software life cycle and service management information items (documentation) are specified in this standard. The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard provides a mapping of ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013), and ISO/IEC 20000-2 (IEEE Std 20000-2:2013) clauses with a set of information items. This International Standard identifies records and information items based on analysis of references in ISO/IEC/IEEE 15288, ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012 (IEEE 20000-2:2013), which in some cases provide partial or complete outlines for the content of specific documents. However, the requirements for the life-cycle processes do not uniquely and unambiguously state the requirements for the information items contents or the information needed by a user of an information item. Moreover, the information from the life-cycle processes may overlap or may be created and revised at different times. In short, the analyzed references do not result in a logically complete list of information items.<br />\n \t\t\t\t<br />\n This International Standard specifies the purpose and content of all identified systems and software life-cycle and service management information items (documentation). The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document (Clause 10). This International Standard assumes an organization is implementing life-cycle processes, or practicing service management, using one or more of the following: ISO/IEC 15288:2008 (IEEE Std 15288-2008), Systems and software engineering -- System life cycle processes, ISO/IEC 12207:2008 (IEEE Std 12207-2008), Systems and software engineering -- Software life cycle processes, ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013), Information technology -- Service management -- Part 1: Service management system requirements. This International Standard provides a mapping of ISO/IEC 15288:2008 (IEEE Std 15288-2008), ISO/IEC 12207:2008 (IEEE Std 12207-2008), and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2 (IEEE Std 20000-2-2013) clauses with a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and IT service management. ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008) define a set of processes for managing and performing the stages of a systems life cycle. They define an Information Management process, but they do “not detail documentation in terms of name, format, explicit content, and recording media”. ISO/IEC 15288:2008 (IEEE Std 15288-2008), and ISO/IEC 12207:2008 (IEEE Std 12207-2008) establish a common framework for software life-cycle processes and in passing identify or require a number of documentation items. Its process reference model does not represent a particular process implementation approach, nor does it prescribe a system/software life-cycle model, methodology, or technique. ISO/IEC 12207:2008 (IEEE Std 12207-2008) does not always specify when software information items are to be prepared, nor does it identify information item contents. ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) establishes comprehensive requirements for documents and records, with some specific requirements. ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013), Information technology -- Service management -- Part 2: Guidance on the application of service management systems provides guidance on the use of Part 1. The generic document types (which may be referred to as information item types) are to be used to identify the information necessary to support the ISO/IEC 15288:2008 (IEEE Std 15288-2008) agreement, enterprise, project, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207-2008) primary, supporting, and organizational life-cycle processes; or the ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) service management system (SMS), service delivery, relationship, resolution, and control processes. For each life-cycle process or service, it would be possible to prepare a policy, plan, procedures, and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of the documentation schema would be more rigorous than specified by ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008). As ISO/IEC 15288:2008 (IEEE Std 15288-2008) points out (1.4), “This International Standard does not detail the life-cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.” Thus, information items may be combined or subdivided as needed for project or organizational purposes, as further defined in Clause 2, applicability, and Clause 3, Conformance. This International Standard does not establish a service management system. The scope of this International Standard does not include the following: a) the format or content of recommended input data or input information items, except for the content of those input items that are also output information items; b) instructions on combining or subdividing information items and information item contents of a similar nature; c) guidance on selecting an appropriate presentation format, delivery media, and maintenance technology for system and software life-cycle data, records, information items, or documentation, such as electronic publishing systems, content management systems, or data repositories. NOTE 2 ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation, provides guidance on formats for software user documentation. NOTE 3 ISO/IEC 15504-5:2012, Information technology -- Process Assessment -- Part 5: An exemplar software life cycle process assessment model, Annex B (informative), and ISO/IEC 15504-6:2013 Information technology -- Process assessment -- Part 6: An exemplar system life cycle process assessment model, Annex B (informative) detail the content of work products as well as information items. Their guidance includes descriptions of a set of information items (documents) that an assessor may encounter. The information items in their guidance may be produced by combinations and subdivisions of the required information items in this International Standard.<br />\n The purpose of this International Standard is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) for identifying and planning the specific information items (information products) to be developed and revised during systems and software life cycles and service management processes. This International Standard is intended for use as follows. a) To address the technical information needed by those involved in ISO/IEC 15288:2008 (IEEE Std 15288-2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) processes.<br />\n b) To specify information in an agreement process as described in ISO/IEC 15288:2008 (IEEE Std 15288-2008) or a two-party situation as described in ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013) and ISO/IEC 20000-2:2012 (IEEE Std 20000-2-2013). The two-party situation may range from an informal agreement within an organization to a legally binding contract between organizations. c) To develop information items that provide evidence for process assessment performed with respect to ISO/IEC 15504, and to guide process improvement activities. d) To guide a single party in self-imposed tasks. 2.2 Intended users of this International Standard This International Standard is applicable for use by: a) project managers responsible for the Information Management process of ISO/IEC 15288:2008 (IEEE Std 15288-2008) (6.3.6) during a system life cycle; b) project managers responsible for identifying information item requirements and document contents when using ISO/IEC 12207:2008 (IEEE Std 12207-2008), or any other software engineering life-cycle process, to help determine what should be documented, when the documentation should be developed, and what the contents of the documents should be; c) acquirers responsible for determining what information items are needed to help ensure the quality of the project, or delivered system, product or service; d) individuals who write or support the design and development of service, systems and software information items; e) individuals responsible for identifying information items required to claim conformance with ISO/IEC 12207:2008 (IEEE Std 12207-2008), ISO/IEC 15288:2008 (IEEE Std 15288-2008), or ISO/IEC 20000-1:2011 (IEEE Std 20000-1-2013); f) individuals undertaking service, system or software process improvement in their organizations. """ #metaKeywords: null #metaDescription: null #shortDescription: "ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1743289200 {#7317 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1645138800 {#7292 : 2022-02-18 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1431640800 {#7318 : 2015-05-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "15289" -bookCollection: "" -pageCount: 95 -documents: Doctrine\ORM\PersistentCollection {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } #optionValues: Doctrine\ORM\PersistentCollection {#8319 …} #position: 0 #createdAt: DateTime @1751041267 {#7283 : 2025-06-27 18:21:07.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1756908201 {#8120 : 2025-09-03 16:03:21.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#8263 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductVariantTranslation {#93368 #locale: "en_US" #translatable: App\Entity\Product\ProductVariant {#8103} #id: 6216 #name: null -shortDescription: null -description: null -notes: null -shippingInformation: "Instant download" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #version: 10 #onHold: 0 #onHand: 0 #tracked: false #weight: 0.0 #width: null #height: null #depth: null #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8135 …} #shippingCategory: null #channelPricings: Doctrine\ORM\PersistentCollection {#8297 …} #shippingRequired: true #images: Doctrine\ORM\PersistentCollection {#8294 …} -apiLastModifiedAt: DateTime @1756850400 {#8102 : 2025-09-03 00:00:00.0 Europe/Paris (+02:00) } -publishedAt: null -isbn: "978-0-7381-9529-2" -ean: "9780738195292" -numberOfUsers: 1 -physicalProduct: false -downloadableImmediately: true -downloadable: true -drmViewerUrl: "https://online-viewer.normadoc.com/DBqhCn" -sellable: true -documents: Doctrine\ORM\PersistentCollection {#8131 …} -drmTokens: Doctrine\ORM\PersistentCollection {#8123 …} -enabledForSubscribers: true -currentAreaContext: null } #productName: null #variantName: null } } |