Home Services Products Portfolio Contact Us About Us
IT Consultancy > Project Process Document

IWe have developed a process for handling all our projects which allows us to manage and deliver solutions to our clients. Please review our specification below for more information on how we do our work.

Systems Development Process

A major part of our time is spent with the client ironing out details and requirements for the project. Our process is broken into the following steps:

Initial Interview
The initial interview lays the foundation for the future of the project. This meeting focuses on the overall project description, general requirements are gathered including project scope, timeline considerations, budget, business goals and technology. With the information gathered here our team can begin planning a draft of the project.

Project Outline creation
Immediately following the Initial Interview phase we begin drafting the outline of the project. This outline will define general data pathways, business relationships, entities, timelines, resources allocations, tasks, milestones and goals.

Brainstorming
The brainstorming phase occurs both at the client and at our offices. We sit with the client and hammer out key features and generate possible solutions for the business problems. Interviews with all client staff that will interact with the data are conducted. Process flow diagrams are drafted and entity relationships are setup.

Requirements Analysis
To us, this is probably the most important phase of development. After this phase is completed a functional requirements document is produced. This document is essentially the blueprint for the proposed system. This document is handed off to the development team to create the actual implementation, therefore this phase must gather all the information that is need to ensure success. Along with the client, we design and map out the entire system, a paper prototype of sorts, of the proposed system. At the end of it all our developers should have exactly what is needed in the functional requirements document to jump in and start coding.

Database Design
The core of any business is the data. The proper design of data sinks (databases) for storing and managing the data is essential and most important. With the functional requirements document in hand the database designers map the entity relationships to data tables for capturing data. When this phase is completed the programming staff can now begin coding the front end of the application.

Implementation
This phase is as the name suggests. This is where the developers create the application that will mimic the real life situations for solving the business problems. Business rules are implementated and features/functions highlighted in the functional requirement documentation created.

Testing and Debugging
During the actual coding of the application, our developers perform rigorous testing, but when the entire application is completed an even more intense testing and debugging schedule is initiated. Load testing, security testing and requirements matching are done to ensure that the application, first of all, does what is was supposed to do and then to ensure that it performs well under load. When we are sure that the system can be moved into Beta software level, this means that a sufficient number of the bugs in the software have been removed we can now deploy the system.

Documentation
Prior to deployment, the entire system is documented, including technical and end user documentation so that future enhancements and user interation will be easily handled because of the reference materials available.

Deployment
During this phase we take the software into the front lines and deploy it into the actual operating environment.

Acceptance Testing
Live data is introduced into the system and we allow the system to operate in a real world environment. All persons who will interact with the system have a chance to work and test the system. This is a key phase because it is the people who actually have to use the system who provide the most insight into flaws and benefits. Discovered bugs are fixed and changes are made during this phase. When the software has been approved after this phase we move it into final release status, indicating that the software has passed all tests successfully and should now perform operations adequately.

End User Training
Users are trained in the proper use of the system.

Support and Maintenance
During the lifetime of the system, we may be contracted to support and maintain the system, including upgrades that may become necessary due to a change in business operations.


We believe that the phases outlined above guarantee a wholesome product for our clients and allow us to deliver solutions that reflect client requirements.

          Navigation