Fleckner und Simon Informationstechnik GmbH              http://www.FlecSim.de

4.2.2 SPL.2 Product release

Process ID SPL.2
Process Name

Product release

Process Purpose

The purpose of Product release process is to control the release of a product to the intended customer.

Process Outcomes

As a result of successful implementation of this process:

  1. the contents of the product release are determined;

  2. the release is assembled from configured items;

  3. the release documentation is defined and produced;

  4. the release delivery mechanism and media is determined;

  5. release approval is effected against defined criteria;

  6. the product release is made available to the intended customer; and

  7. confirmation of release is obtained.

Base Practices

SPL.2.BP1: Define the functional content of releases. Establish a plan for releases that identify the functionality to be included in each release. [Outcomes 1, 3]

NOTE 1: The plan should point out which application parameters influencing the identified functionality are effective for which release.

SPL.2.BP2: Define release products. The products associated with the release are defined. [Outcome 1]

NOTE 2: The release products may include programming tools where these are stated. In automotive terms a release may be associated with a sample e.g. A, B, C.

SPL.2.BP3: Establish a product release classification and numbering scheme. A product release classification and numbering scheme is established based upon the intended purpose and expectations of the release(s). [Outcome 2]

NOTE 3: A release numbering implementation may includethe major release number

the feature release number

the defect repair number

the alpha or beta release

the iteration within the alpha or beta release.

SPL.2.BP4: Define the build activities and build environment. A consistent build process is established and maintained. [Outcome 2]

NOTE 4: A specified and consistent build environment should be used by all parties.

SPL.2.BP5: Build the release from configured items. The release is built from configured items to ensure integrity. [Outcome 2]

NOTE 5: Where relevant the software release should be programmed onto the correct hardware revision before release.

SPL2.BP6: The type, service level and duration of support for a release are communicated. The type, service level and duration of support for a release is identified and communicated. [Outcome 3]

SPL.2.BP7: Determine the delivery media type for the release. The media type for product delivery is determined in accordance with the needs of the customer. [Outcome 4]

NOTE 6: The media type for delivery may be intermediate (placed on an adequate media such as floppy disk and delivered to customer), or direct (such as delivered in firmware as part of the package) or a mix of both. The release may be delivered electronically by placement on a server. The release may also need to be duplicated before delivery.

SPL.2.BP8: Identify the packaging for the release media. The packaging for different types of media is identified. [Outcome 4]

NOTE 7: The packaging for certain types of media may need physical or electronic protection for instance specific encryption techniques.

SPL.2.BP9: Define and produce the product release documentation / release notes. Ensure that all documentation to support the release is produced, reviewed, approved and available. [Outcome 3]

SPL.2.BP10: Ensure product release approval before delivery. Criteria for the product release are satisfied before release takes place. [Outcome 5]

SPL.2.BP11: Ensure consistency. Ensure consistency between software release number, paper label and EPROM-Label (where relevant). [Outcome 5]

SPL.2.BP12: Provide a release note. A release is supported by information detailing key characteristics of the release. [Outcome 6]

NOTE 8: The release 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.BP13: Deliver the release to the intended customer. The product is delivered to the intended customer with positive confirmation of receipt. [Outcomes 6, 7]

NOTE 9: Confirmation of receipt may be achieved by hand, electronically, by post, by telephone or through a distribution service provider.

NOTE 10: These practices are typically supported by the SUP.8 Configuration Management process.

NOTE 11: Refer to ISO/IEC 9127: 1988 'User Documentation and Cover Information for Consumer Software Packages' for guidance on packaging aspects of software product supply.

Output Work Products

06-01 Customer manual [Outcome 3]

08-16 Release plan [Outcome 1, 3]

11-03 Product release information [Outcome 1, 3, 4, 6]

11-04 Product release package [Outcome 2, 3, 6]

11-07 Temporary solution [Outcome 6]

13-06 Delivery record [Outcome 6,7]

13-13 Product release approval record [Outcome 5]

15-03 Configuration status report [Outcome 2]

18-06 Product release criteria [Outcome 5, 7]

 

5.Process Capability Indicators

Level 2: Managed process

Level 3: Established process

Level 4: Predictable process

Level 5: Optimizing process