Our development process

Gathering Info

Gathering Information is the process of identifying the requirements for your project. Of course, it goes without saying that a written list of your expectations for the project is something that helps considerably at the outset. Discussion between the project stakeholders, for example conference calls or intensive e-mail correspondence, will also bring to light important details including required functionality, budget, time frame, and required or existing infrastructure.

System Architecture

System architecture involves identifying the organizational relationships between the various content and functionalities of your application, categorizing content, defining internal system work flow and basic interface.

Rapid Application Prototyping

With all the information gathered, work on a prototype begins. A prototype is a live version of your system, and it will be used as a starting point for testing overall information architecture and intended work flow. It is not unusual that new ideas and concepts will emerge from this point from all project stakeholders, so keep in mind that visual design will be performed in a later phase, when the functionality is cleared and communicated.

Development

With the protype approved for development we now begin any necessary custom coding and testing. For example, if your web-site requires functionality not inherent to the Drupal Content-Management-Systemor community contributed modules, we need to write the code that will perform that specific functionality.

Visual Design

Visual design provides you with a fresh and elegant look, which will for instance help your web page consumers to identify you and your services from myriads of similar pages in the Web. Visual design involves determining the look and feel, which includes an overall graphic design for your system, as well as designing any eventually needed smaller elements. To produce a design that satisfies both functionality and aesthetic criteria, we work together with our customers through a number of iterations until the design has been finally approved.

Beta Testing

Information systems tend to be rather complex than simple. Beta testing is the process of allowing others to use the software while identifying and fixing any bugs that may arise. For this we use a case tracking software built into our intranet, allowing all of the stakeholders to be involved in the process of improving the system functionality. Again, it is not unusual that new ideas and concepts will emerge from this point. We take careful note of your wishes and demands , which is a valuable source for further system developing, and once the first iteration of your application or site is up and l running, revisit your wish list and make some decisions about what to do next.

Training & Documentation

Because we involve the project stakeholders throughout the process of the creation of the system, there is not necessarily a special ‘training’ phase in our development process. However, if that would satisfy your needs, we can provide training in person, via telephone, instant messenger, desktop sharing, through interactive filmed sessions - or via email and written documentation.

Maintenance & Support

Once your information system has been set up, it doesn’t mean that all of the work is complete, but rather the real life of your system begins. Web-Sites often need ongoing maintenance and security updates. In addition, the application often needs upgrades and on-going support. To allow our clients the full benefit of delivered systems, we have set up a system for maintenance and support for our clients. Although often forgotten in the budget planning phase, maintenance is very import, and we always advise our clients to consider purchasing a maintenance plan for their systems.