At the end of the application development phase, the application must be prepared for the next phase which is client testing. An Installation Checklist has been created to assist the developer in preparing an application for client testing.

To prepare an application for cleint testing all of the source code (programs, forms, database procedures, etc.) must be checked into Harvest, Miami University's source code management system. If any changes need to be made to the source code, the developer must check the source code out of Harvest before making the modifications.

Once the Harvest package is ready, the developer will promote it to the 'Test' state of Harvest. The automated promotion process will check the source code out of Harvest and migrate and compile it in the appropriate directory(s) in the testing environment (TESTx). In some cases, a 'work request' is required in addition to promoting a package to the 'Test' state of Harvest.

Some applications will require extra steps in order to prepare the application for the client testing phase. For example, some applications will need to be set up in the EM job scheduler, while others must be published to the Miami Information Environment (MInE).

Refer to the list below for the appropriate installation standard:

• Harvest (Approved)
• Data Admin Work Requests (Approved)
• EM (Approved)
• MInE Publishing (Approved)

When purchased software is being installed, developers must coordinate the installation with CCS. For new servers, after CCS has prepped the server in the staging area, they will move it to the machine room and deploy the firewall rules. Once this is completed, the application will be ready for client testing

Please send comments and suggestions to the ISS Standards Committee at MCSUASTD@Listserv.muohio.edu.