personAuthor: Process Fellows
SPL.2 – Product Release ensures that a complete and approved product is delivered to the intended customer. The process covers planning release content, performing builds, creating documentation, and validating that all components are consistent, traceable, and properly packaged for delivery.
school
PF_SPL.2_Product Release_Extract.pdf Short Overview of the SPL.2 Product Release Process covering base practices, some examples and a comparion between Automotive SPICE® version 3.1 and 4.0
# PROCESS PURPOSE
The purpose of the Product (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) Process is to control the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) of a product to the intended customer.
# PROCESS OUTCOMES
O1
The contents of the product (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) are determined;
O2
The (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) package is assembled from configured items.
O3
The (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) documentation is defined and produced.
O4 (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) (Approval = Written statement that a deliverable is fit for its intended use, and compliant with defined criteria.) is performed against defined criteria.
O5
The (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) package is made available to the intended customer.
# BASE PRACTICES
BP1
Define the functional content of releases. (
O1 )
Define the functionality to be included and the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) criteria for each (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.). Note 1: This may include the (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.), (Software element = Refers to software component or software unit), and extra (Application parameter = An application parameter is a software variable containing data that can be changed at the system or software levels; they influence the system’s or software behavior and properties. The notion of application parameter is expressed in two ways:
The specification (including variable names, the domain value range, technical data types, default values, physical unit (if applicable), the corresponding memory maps, respectively).
The actual quantitative data value it receives by means of data application.
Application parameters are not requirements. They are a technical implementation solution for configurability-oriented requirements.) files (influencing the identified system functionality) that are needed for the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.).
BP2
Define release package. (
O1 )
Define the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) as well as supporting tools and information. Note 2: The (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) package may include also programming tools.
BP3
Ensure unique identification of releases. (
O3 )
Ensure a unique identification of the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) based upon the intended purpose and expectations of the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.). Note 3: Unique identification may be realized by a classification and numbering scheme for product (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.).
intacs® Certified Process Expert (Automotive SPICE®)
Sponsored
The official intacs® certified training to become an Automotive SPICE® Process Expert.
BP4
Build the release from items under configuration control. (
O2 )
Build the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) from items under configuration control to ensure integrity. Note 4: This practice may be supported by the SUP.8 Configuration Management Process.
BP5
Ensure release approval before delivery. (
O4 )
Criteria for the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) are satisfied before delivery takes place.
BP6
Provide a release note. (
O3, O5 )
A (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) is accompanied by information detailing key characteristics of the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.). Note 5: The (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) note may include information about legal aspects like relevant target markets, legislation that is considered etc. See also VAL.1 Validation.
BP7
Communicate the type, service level and duration of support for a release. (
O3, O5 )
Identify and communicate the type, service level and duration of support for a (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.).
BP8
Deliver the release package to the intended customer. (
O5 )
Deliver the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) package to the intended customer. Note 6: The intended customer may be an internal organizational unit or an external organization.
# OUTPUT INFORMATION ITEMS
13-06
Delivery evidence (
O3, O5 )
Evidence of items shipped/delivered electronically to customer
Identification of:
to whom it was sent
address, where delivered
delivery date
receipt of delivered product
Used by these processes:
SPL.2 Product Release
13-13
Product release approval (
O4, O5 )
Content information of what is to be shipped or delivered
Identification of:
for whom it is intended
the address where to deliver
the date released
Evidence of supplier (Approval = Written statement that a deliverable is fit for its intended use, and compliant with defined criteria.)
Used by these processes:
SPL.2 Product Release
18-06
Product release criteria (
O1, O2, O4 )
Defines expectations for product (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.):
(Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) type and status
required elements of the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.)
product completeness including documentation
adequacy and coverage of testing
limit for open defects
change control status
Used by these processes:
SPL.2 Product Release
11-04
Product release package (
O2, O3 )
Includes the (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.)/software/product
Includes and associated (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) elements such as:
system (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.)/software/product elements
associated customer documentation
(Application parameter = An application parameter is a software variable containing data that can be changed at the system or software levels; they influence the system’s or software behavior and properties. The notion of application parameter is expressed in two ways:
The specification (including variable names, the domain value range, technical data types, default values, physical unit (if applicable), the corresponding memory maps, respectively).
The actual quantitative data value it receives by means of data application.
Application parameters are not requirements. They are a technical implementation solution for configurability-oriented requirements.) definitions defined
command language defined
installation instructions
(Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) letter
Used by these processes:
SPL.2 Product Release
11-03
Release note (
O1, O3, O4, O5 )
Coverage for key elements (as appropriate to the application):
Description of what is new or changed (including features removed)
System information and requirements
Identification of conversion programs and instructions
(Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) numbering implementation may include:
the major (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) number
the feature (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) number
the defect repair number
the alpha or beta (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.); and the iteration within the alpha or beta (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.)
Identification of the component list (version identification included):
(Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) / software / product elements, libraries, etc.
associated documentation list
New/changed parameter information (e.g., for (Application parameter = An application parameter is a software variable containing data that can be changed at the system or software levels; they influence the system’s or software behavior and properties. The notion of application parameter is expressed in two ways:
The specification (including variable names, the domain value range, technical data types, default values, physical unit (if applicable), the corresponding memory maps, respectively).
The actual quantitative data value it receives by means of data application.
Application parameters are not requirements. They are a technical implementation solution for configurability-oriented requirements.) or global variables) and/or commands. Note that (Application parameter = An application parameter is a software variable containing data that can be changed at the system or software levels; they influence the system’s or software behavior and properties. The notion of application parameter is expressed in two ways:
The specification (including variable names, the domain value range, technical data types, default values, physical unit (if applicable), the corresponding memory maps, respectively).
The actual quantitative data value it receives by means of data application.
Application parameters are not requirements. They are a technical implementation solution for configurability-oriented requirements.) are a technical implementation solution for configurability-oriented requirements)
Backup and recovery information
List of open known problems, faults, warning information, etc.
Identification of (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) and diagnostic procedures
Technical support information
Copyright and license information
The (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) note may include an introduction, the environmental requirements, installation procedures, product invocation, new feature identification and a list of defect resolutions, known defects and workarounds
SPL.2
Product Release
