How we work

How we work?

1

Requirements Gathering and Analysis

During the requirements gathering and analysis phase, it is very important that most of the major requirements are captured accurately. It’s best to have as many meetings as necessary to make sure the client’s needs are understood. When analyzing the requirements, we try to identify any risks and offer strategies for risk mitigation. All requirements should be documented clearly and should be provided at meetings to keep track of what has been discussed to help ensure that everyone is on the same page. In some cases, we also provide demos of the future application via screenshots and/or prototypes to make sure requirements are met successfully.

Design & Development

In the design phase, the requirements will be broken down further to be able to forecast the project’s timeline and estimate the level of effort and amount of resources needed. During this phase, we also identify any specific designs and workflows for the application. Once most of the design is identified, the development phase can begin. We 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.

2

3

Quality Control

The testing phase commences after a development release has been 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 iteratively 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 implementation.

Delivery & Implementation

Once all the other phases are completed, we prepare for the implementation. For a first time deployment, we can deploy the entire database and code repository, but going forward, we can deploy the specific changes for all future release efforts. We will package or export our database for deployment on the production server. For the application code, we can create a build or zip file of the entire application to deploy, or we can copy the top directory or files manually.