On completion of each phase, we walk-through the outcomes with the customer to ensure that a clear, shared understanding of the project exists between all parties. The customer has the opportunity to confirm work to date and accept the work before we proceed to the next phase of the project.

Generally, a separate quotation is provided for each phase at the commencement of the phase, though an estimate for the full project is provided at the beginning of the project.

The phases are:

A project is initialized through a visit at the client. This meeting is free of charge. The purpose of the meeting is to:

• Introduce the DBS team
• Explain our development methodology
• Demonstrate a sample specification and products
• Discuss our Terms and Conditions
• Assess the overall scope of the client project

Date:_____________    By:_____________    _____________    

Phase II - Determine the Requirements

The next step in the development process is to identify the clients needs and opportunities more closely. The purpose of this stage is to gain a solid understanding of the business requirements. We do this by meeting with the client project manager and users alike. From this meeting we will produce a User Requirements Document which outlines the business needs and the best software solutions.

Prior to this meeting it is beneficial for the client to prepare an outline of requirements, the members involved in this project and main users.

Note: If this project involves converting an existing system, for example, from Access to ASP, and no functionality changes are necessary, this phase may not be required.

Date:_____________    By:_____________    _____________    

Phase III - Design Specifications

The Design Specifications of the systems are identified from the User Requirements Document. Design Specifications' include all the necessary steps for design, delivery and implementation of the project. DBS ensures that solid foundations are prepared for the project. We walk through this document with the client for acceptance and sign off.

At this stage we also like to get users to have a look at some of our past databases to get ideas and see our standard look and feel.

Date:_____________    By:_____________    _____________    

Phase IV - Software Development and Testing

Construction of the software is carried out during this phase, along with alpha testing and verification by our team.

Any changes required in the design are made using the DBS Change Request System. There are two methods for reporting changes:

1. Electronic submission (preferred)
2. Manual submission

In each case DBS requires Client approval for nominated changes.

DBS follows 13 different rules to developing better code. Please see DBS's 13 Rules to Better Code for more information.

Date:_____________    By:_____________    _____________  

Phase V - Handover and Acceptance

The software is installed at the customer's site for beta testing and acceptance by the customer. Once accepted, the software is ready to be installed into the production environment for 'live' use.

Date:_____________    By:_____________    _____________    

Phase VI - Training

Training can be carried out during this phase. A User Guide and On-line Help can also be provided if required.

Date:_____________    By:_____________    _____________    

Phase VII - Support and Enhancements

One of the most important aspects of a software development is the post-implementation support.

Support is defined as ensuring the database maintains its current functionality. The support cost is 15% of the total project cost. Otherwise it will be charged on an hourly basis. It does not include data corruption. Onsite visits will be charged on an hourly basis, unless otherwise agreed upon.

Enhancements are defined as changes to the delivered software package. There are two methods for reporting changes.:

1. Electronic submission (preferred)
2. Manual submission

In each case DBS requires Client approval for nominated changes.