The Process

Receipt of software/web development requirement specification
Receipt of your specification is the initial phase of software development/web development. If you do not have a specification document our consulting team will be happy to meet with you to define the parameters of the said document.

General analysis
Gurg will carry out a general analysis of technical, operational and economic feasibilities based on  project specification outlining "our understanding" of the said project.

Requirement estimation
Based on "our understanding", estimations of risks and budget for the future stages of the development are compiled and presented once discussed in detail with the client, this will be presented in proposal form. This document will include;  cost, project management method and risk management analysis.

Contract signature
Once the proposal has been tabled and all parameters regarding obligations, responsibilities and payment are agreed in principal, we would then expect a sign off on the official contract.

Project startupt
Gurg Consulting will allocate a dedicated team, Project manager and specialist developers. A project development plan with detailed timeline of tasks, personnel arrangement and milestones is provided to ensure the project is completed on time and within the specified budget.

Detailed requirement analysis & system design
Once the project plan is accepted Gurg will define the most appropriate means of communication between our Project management team and the individuals responsible for the project within your organisation. Depending on the requirement analysis, we divide the whole task into several modules and ensure our systems analysts outline the system architecture with any expansibility and configurability issues fully taken into account. Later, our database architects design the back-end databases using constraints and ensure that the integrity of your data is maintained.

Implementation
The actual software programs/codes based on the design are created. Our highly experienced developers follow strict coding standards and modularise all coding to ensure debugging and any future feature expandability is achieved with the greatest of ease. Unit testing is carried out after a component's completion to reduce the development time and guarantee quality. All components are then integrated into the Alpha version of the software.

Test
The Alpha version presents a special testing environment in which integration errors, bugs etc are tackled, eliminated and the user interface is refined according to the test plan and test cases. The Beta version is then handed over to the client for UAT (Use Acceptance Test).

Deployment
Once the Beta version is accepted and “signed off” the software is released to its end users with all deployment documentation. All information regarding software prerequisites, configuration environment and deployment steps will obviously be included.


back to home pagemail to ussite map