Softwhite Inc

Quantify, Design, Execute

Deployment Protocol


Softwhite's deployment protocol introduces newly developed functionality in a phased, structured aproach designed to minimize production disruptions. Code is developed and unit tested by the engineer responsible for modeling the functionality as described in the Business Requirements Document (BRD). The code is then deployed in a test environment, a replica of the production environment where system integration testing (SIT) is performed to assure that the code works within the current production code base. If the code passes SIT, the next step in the process is user acceptance testing to assure that the functionality works as expected. Upon completion of user acceptance testing, a defined deployment date is established with the project team and the code is deployed into production.

The entire Deployment Protocol resides on a foundation of source control that allows for the close monitoring of version control and conflict resolution within the code base.

The following table provides a high level overview of critical components of Softwhite's Deployment Protocol.

Source Control   Milestone marking, version control, conflict resolution, compliance auditing
Unit Tests   Regression testing: as code is introduced full unit testing validates the whole build
Use Cases   Define use cases for predeployment table top testing
Deployment Testing   Test Environment>QualityControl Environment>Production Environment


The Team

Quick Links:

Softwhite Blog
Softwhite SoftSend
Case Management System
Web Mail