Release Process - Draft Template
Release Process - Draft Template
No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by
any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of the
copyright owner.
The Open Group® is a registered trademark of The Open Group in the United States and other countries.
Best Practice for Quality Assurance of Product Development in the Lottery Industry:
Development Process
Comments relating to the material contained in this document may be submitted to:
Quality Assurance of Project Development in the Lottery Industry: Development Process iii
1 Introduction
This template contains all the best practice requirements contained in the Best Practice for
Quality Assurance of Product Development in the Lottery Industry: Development Process:
Release Process.
This project will be implemented and maintained in compliance with the NSI Best Practice for
Quality Assurance of Product Development in the Lottery Industry: Development Process (Doc.
No. BP0402).
Project Name:
Project Description:
Project Start Date:
The Release Process covers both the preparatory steps performed on the vendor side, and the
documentation necessary to facilitate the installation and integration performed on the lottery
side. The Release Process addresses installation plans, start-up strategies and plans, and
conversion requirements. The Release Process could also include training of operations staff, the
lottery, and retailers.
Representatives from the vendor must create the plans for the release of the system or system
components. The plans must be documented.
Vendor Representatives
This section should include a formal build description for the software portion of the release,
which must include:
• The system version
• The version of all component modules
• The version of all deliverable documents
System Description Version
This section should include a list of any known problems in the release and the plans for
resolving them.
This section should include any limitations in the scope of the system, or any requirements that
were included in the specifications but were deferred or eliminated and will not be implemented
as a part of this release.
This section should include a definition of any additional functionality that is being delivered but
was not defined in the Requirements Specification (i.e., enhancements); this must include a
reference to where the functionality is documented.
This section should include a list of all deliverables, which must include:
• A description of and identifying serial and part numbers for all hardware components
• Software components and associated software modules
• Documents
• Tools
The vendor should create a test report that summarizes the test results of internal testing.
This section should include any known usability constraints (for example, performance
limitations).
The lottery and vendor must work together to produce an Integration Plan. The Integration Plan
should be created during the Requirements Definition.
The Integration Plan must be performed in accordance with the agreed plan. It may be refined
during Acceptance Testing.
The Integration Plan must be approved by both the vendor and the lottery.
This section includes a review of the business processes impacted by the changes.
This section includes ensuring that people responsible for the affected business functions know
of the changes.
This section includes ensuring that the people responsible for the affected business functions are
notified in advance of what business process changes need to be made (if any).
This section ensures that non-software issues are resolved in time to support the installation of
the new software or hardware.
The Integration Plan must include information that covers the complete environment into which
the product will be integrated and deployed.
This section must identify the impact of the product release on the overall lottery system,
including but not limited to the areas described below.
This section must include any security changes that are required. The security changes must be
identified in the Integration Plan together with assigned actions for the responsible parties from
either the vendor or the lottery.
This section must include any data conversion that is necessary. The vendor must provide details
and assigned actions for execution of the data conversion.
This section must include the identification of platform variations that may occur at different
lottery or retail sites and document assigned actions to address them.
This section must include the identification of deployment variations that may occur at different
lottery or retail sites and document assigned actions to address them.
The vendor must thoroughly test the installation procedures defined in the Installation Guide
prior to release.
Signatures indicate that the Integration Plan associated with the project below has been created
by both the lottery and the vendor.
Project Name:
Project Description:
Project Start Date:
Lottery Authorization
Vendor Authorization
Signatures indicate that the Integration Plan associated with the project below has been approved
by both the lottery and the vendor.
Project Name:
Project Description:
Project Start Date:
Lottery Authorization
Vendor Authorization
This appendix defines the terms and acronyms used in the Release Process document.