software release code and build development procedure

This document describes the process cycle in moving code from development to production.

The process to move code from development to production should take place in three steps, as follows

Staging Machine (Stage 1) (developers workstation)

1. Build and test code on workstation
2. Resolve all known bugs and issues on workstation
3. Test code locally
4. Test code on local network from another computer if possible
5. Document code with a brief write up and store it in the p_materials folder on the ftp server.
6. Name the documentation something descriptive, i.e., Remote Manager Summary.
7. The type of documentation should include an overview of the application.  It is not intended to cover everything, rather, give an explanation of the code, what it does, and the resources it needs to work.  Some examples follow:
1. If a Virtual web directory is needed
2. If a SQL Backend is needed, if so how many databases.
3. Connection string overview
4. Dependent services
5. Associated programs needed in-conjunction with the code, i.e., Data Generator, etc..
8.  Note any hard coded items
1. Connection Strings
2. Path or UNC Statements, or Mapped drives
3. Usernames and Passwords associated with code
9. Document any caveats
10. Identify and special software or controls (3^rd party) needed in addition to the code, for example
1. ChartFX
2. .Net Framework
3. Special controls, i.e, Microsoft Tree controls
11. Document and special services that are required
1. SMTP mail server
2. Web server
3. FTP server
4. SQL Server
5. DNS
6. ODBC
12. DO NOT Name everything test.  Instead give the application, code, database, etc. descriptive names.  This will help make things more organized in the future when we don’t remember for example what the database name TEST was for
13. Once the application/code is working without any problems prepare to move it to the development server

Development Server (Stage 2)

1. Document all changes made to the dev server in a Change Control Form (CCF)
   The CCF Template forms are located on the ftp server in the following folder:
   \...\p_materials\change-control-forms-Template
2. Any user accounts that were created in Windows or SQL
1. Where the application, service or code was installed, i.e., c:\program files\application1
2. Any DSN’s that were created
3. Any Databases that were created
4. Any special components, software or code that was installed to make the application, service or code run, i.e.,

                                                              i.      ChartFX

                                                            ii.      Dundas Chart software

                                                          iii.      Microsoft Tree controls

                                                          iv.      Etc.

5. Document any NTFS modifications that are needed
2. Make sure you can rollback the server (remove application, service or code) if the application, service or code causes problems on the dev server.
1. Several steps can be taken here to assure a clean rollback
2. Contact the Systems Administrator for help if needed
3. Prepare the dev sever for the application, service or code
1. Create any needed databases

                                                              i.      Create Local SQL server users on the dev server for application, service or code testing and try to give the SQL user as few rights as possible, i.e, do not make them part of the DBA group if possible.

                                                            ii.      Do not call the database “TEST” instead give it a descriptive name.

2. Create any needed DSN’s
4. Install and configure the application, service or code on the dev server
5. Test the application, service or code
1. Test from computers inside the firewall
2. Test from computers outside the firewall
3. Test every feature and resolve all problems
4. Have a colegue test the code
5. Test the code from a computer that does not have development tools on it.
6. Monitor the server performance before installing the application, service or code
7. Monitor the server after the application, service or code is installed

                                                              i.      Inform the Systems Administrator if the code is consuming server resources and it can not be resolved.

                                                            ii.      Resolve the problem of consuming resources on the dev server before moving it to production

7. Use specific domain users designed for connection strings before moving the code from the dev server to the production server
1. Ask the System Administrator to create this user, if it has not been created and tested already
2. Note that the domain users used for testing on the dev server will be the same users used on the production server.  This will make the application, service or code portable in the domain.
3. If you can not make the application, service or code run with domain accounts, run it as needed on the dev server with local accounts, but please resolve the problem before moving it to the production server as it will use domain accounts on the production server.