Define and agree the functionality to be included with the intended customer, and define the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) criteria for each release (Release = A product delivered to a customer, including a defined set of functionalities and properties.).
Note 1: This may include the hardware elements (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.), software elements (Software element = A software element is subject to integration within the software. Can represent a →SOFTWARE COMPONENT or →SOFTWARE UNIT), and extra application parameter (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 (System = A collection of interacting components organized to accomplish a specific function or set of functions within a specific environment.) functionality) that are needed for the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.).
Note 2: The intended customer may be an internal organizational unit or an external organization.

Define the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) as well as supporting tools and information.
Note 3: The release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) package may include also programming tools.

Ensure a unique identification of the releases (Release = A product delivered to a customer, including a defined set of functionalities and properties.) based upon the intended purpose and expectations of the releases (Release = A product delivered to a customer, including a defined set of functionalities and properties.).
Note 4: Unique identification may be realized by a classification and numbering scheme for product releases (Release = A product delivered to a customer, including a defined set of functionalities and properties.).

Build the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) from items under configuration control to ensure integrity.
Note 5: This practice may be supported by the SUP.8 Configuration Management Process.

The criteria for the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) are satisfied before the delivery takes place.

Each release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) is accompanied by information detailing the key characteristics of the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.).
Note 6: The release (Release = A 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.

Identify and communicate the type, service level and duration of support for a release (Release = A product delivered to a customer, including a defined set of functionalities and properties.).

Deliver the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) package to the intended customer as per the agreement.

Evidence of items shipped or electronically delivered to customer.

Identifies:

• Receiver
• Delivery address
• Delivery date
• Acknowledgment of receipt

Includes:

• Identification information

Evidence of approval (Approval = Written statement that a deliverable is fit for its intended use, compliant with defined criteria.) for a product release (Release = A product delivered to a customer, including a defined set of functionalities and properties.).

Identifies:

• Release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) date
• Name and role of approver
• Intended customer
• Restrictions and limitations for usage

Includes:

• Delivery / shipping address
• Release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) information of what is to be shipped or delivered
• If applicable, supplier approval (Approval = Written statement that a deliverable is fit for its intended use, compliant with defined criteria.) evidence(s)

Conditions to be satisfied prior to authorization of a product for delivery.

Identifies:

• Release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) type and status
• Elements of the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.)
• Completeness conditions
• Documentation needs

Includes:

• Adequacy considerations
• Coverage
• Limits, for example the maximum of residing risk (Risk = The combination of the probability of occurrence and the consequences of a given future undesirable event.) in a product.

Examples and References:

• Acceptance conditions for an engineering service product to a specific milestone.

Set of Elements delivered in the product release (Release = A product delivered to a customer, including a defined set of functionalities and properties.).

Identifies:

• Physical components
• Elements necessary for intended use
• Warnings and alerts
• Application Parameters (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.)

Includes:

• Documentation to maintain or service the product
• Information for the user, for example installation and setup instruction within a manual.

Documentation of content provided in the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.).

Identifies:

• Set of functionalities provided in the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.)
• Limitations in relation to the committed scope
• Known non-conformities
• Application parameters (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.)
• Configurations and variants
• Unique name and version of the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.).
• Additional or removed functionalities
• Changed or improved functionalities
• Documentation of resolved non-conformities

Includes:

• Intended area and environment of usage
• Impact to other components linked to the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.)
• Upstream or downstream compatibility of delivered release (Release = A product delivered to a customer, including a defined set of functionalities and properties.)
• Copyright and license information
• Result of verification and validation measures (Validation measure = Validation measure can be:
  • Operational use case testing under real-life conditions
  • Highly accelerated life testing (HALT)
  • Simulations under real-life conditions
  • End user trials
  • Panel or blind tests
  • Expert panels
  )
• Approval (Approval = Written statement that a deliverable is fit for its intended use, compliant with defined criteria.) for delivery of the release (Release = A product delivered to a customer, including a defined set of functionalities and properties.) by responsible roles
• Dependencies to other linked products, for example hardware (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) revision.