During Develop phase applications are built as per specification created or agreed during design phase. Depending on project methodology, infrastructure and platform, there may be clear or even contractual demarcation between this phase and design phase. Where traditional waterfall method is used with mature technologies and applications, specifications are signed off during design phase and build phase develops the interfaces, codes, analytics to be tested by business analysts. Once the business analysts sign off the built, it is deployed as per deployment plan. If Agile is used or platform is cloud, the process is generally more fluid and interactive and design and development and deployment can run in parallel.
In Waterfall method, designs are detailed, signed off and more or less contractually fixed, and development effort can begin. The development itself can and often done by third parties. You will be able to assign specific tasks to each individual and provide them with the necessary documentation of the requirements and designs. Usually during this phase, development tasks will be broken down into release efforts so the application can be completed in parts and the client can preview what has been done during the process. Breaking up the development effort is crucial in order to provide interim results to customers. Otherwise, you may find out later that what has been developed does not meet your client’s needs. It’s best to keep the client involved during the entire process to ensure the application is on the right track.
The testing phase commences after a development release is completed. Usually the application will be released to the Quality Control (QC) group, which will test all the functionality in the application. After a release has been completed, the development and testing phases are performed iterative way as issues are found, corrected, and retested. After completion of QC, the next critical testing activity is User Acceptance Testing (UAT), which is performed by the client. Typically, the client will identify a group of users to test the new application. UAT testers often find issues that are not obvious to QC testers, who may not fully understand the application or its data. It’s always best to allow time for UAT testing before approving an application for production implementation. Once UAT is finished, sign offs are obtained from the users and stakeholders.
Deployment / Productive Use
The Systems that are developed and pass all tests are then planned for deployment and/ or release to productive. A detailed plan is created and depending on risk assessments, a dry run is performed that mimics exactly how the development will be used when the actual users of systems will start using the systems. Sometime it becomes necessary for business to get involved in during the dry run.