Packaging Requirements

4.6.1. The System shall be delivered as a set of installers that performs the basis of the installation process and a comprehensive instruction that contains necessary steps and tips on how to install and tune the system in context of an enterprise. The System installation steps might also include running some initialization scripts, in this case such scripts shall be bundled together with the system and complimented with appropriate documentation for a member of a Maintenance Team to be able to go through this procedure.

4.6.2. The System Installer should be implemented using standard.NET installer tools.

4.6.3. A member of a Maintenance Team must ensure that he/she has all the necessary permissions to install and configure the System, that the Acceptance Testing and the Production Environment comply the necessary requirements defined either in this document or in any subsequent documents that comply the project lifecycle (such as AAD, Installation and Deployment Guide and Acceptance Test Document). The maintenance Team shall notify the DEVLOPER about any security limitations that the System might face beforehand and may not write it off to the DEVELOPER if some of the System parts cannot operate properly because of any security, network or underlying system software limitations (such as OS, DBMS and Application Servers including inappropriate versions and modifications (like Standard Edition vs. Enterprise Edition) thereof). Should this situation be the case (e.g. after successful functionality Acceptance Testing the System cannot be run in a production environment because of some environmental limitations), the DEVELOPER reserves a right to treat such situations as a technical support request which is a subject of separate estimations, shall be considered out of the scope of the project and shall not affect the fact of successful System acceptance.

Дата добавления: 2015-08-27