Our Development Methodology

We believe the software development process is a collaborative effort requiring interaction and dialogue between the entire development team and the customer.

We realize that requirements change and new business needs may arise during the course of development and that is why we practice a flexible development methodology that allows us to adapt to changing requirements.

Our methodology is not always linear; instead the following four processes are iterative and often overlap each other:

Listening

Communication is critical to the success of any project not only at the beginning but throughout the entire process. Our developers don't know your particular business needs so we will make sure that before the first line of code is written we know exactly what you want.

We believe effective communication is so vital to the success of each project that we dedicate a systems analyst to each and every project we undertake. This helps us to better understand your needs and ensures that miscommunication will not derail the project.

Designing

We are committed to creating flexible applications that can adapt to changing requirements. This is easier said than done and requires that we spend time putting together an appropriate design.

By taking the time up front to understand what you need, we will be able to design a system that will meet your current requirements and will have the flexibility to adapt to and incorporate your future requirements.

Also, throughout the course of the project we will be working with you (listening) to ensure that our design will deliver as promised.

Coding

Developing software is what we love to do and our methodology makes it fun to work on our customers' projects. Having a well-thought-out plan tailored to your specific needs enables us to focus solely on the task at hand rather than trying to design as we go. This ensures that the quality of our work is second-to-none.

Testing

Testing is obviously a critical aspect of the software development process and we don't cut any corners in this area.

We conduct unit tests on our code to ensure that every line executes in the proper way. Next we run integration tests to make sure each piece of the project interacts with the other pieces in the appropriate manner. Finally, when we're sure the code is ready; the customer conducts user acceptance tests to make sure that the system behaves according to the requirements.