E2D provides accelerated, cost efficient development that ensures client satisfaction.
The principles of E2D are:
- Client representatives are an integral part of the development team.
- Members of the development team must have a common understanding of the desired end result before beginning work on a project.
- All projects can be divided into component parts, that when integrated, will produce the desired results.
- All requirements may not be expressed at the outset of a project, therefore processes must allow for this.
- The review of component parts of a system at strategic points throughout the development process is a means of reviewing/confirming both user requirements and developed products.
- Models, visuals and prototypes are a better method of communicating development concepts than words.
- While various team members have different roles to play, they have a common goal that is the focal point of all work.
As a non-linear process, E2D facilitates the interaction of stated requirements with a business re-engineering mindset, and allows for innovative improvements to be brought forward during the development process. E2D ensures that initial stated requirements are met, and in many cases leads to the development of a system that is more efficient and effective than the original vision.
The following is a summary of the ten phases of E2D:
- A high level functional analysis is completed to document the desired outputs and available inputs of the system being developed.
- Work begins on known elements/components. Standard features or known elements of a system can begin to be developed as soon as the functional analysis is completed.
- Where necessary, each component is further analyzed to create a common understanding of the required functionality, inputs and outputs.
- Mock-ups are created of the desired outputs beginning with the general design, through to outputs such as newsletters and standard reports. The look and content of these mock-ups assists to confirm user requirements and lays the foundation for the development of a database or other infrastructure.
- Design database, if required.
- Complete programming for functionality of the web applications, including the storage and access of data, auto content generation, auto generated emails, etc.
- Rather than presenting the entire system for review at the end of the development process, where possible, component parts of the system are sent to you for review as soon as they are functional. They may or may not be presented with the final user interface, however the purpose is again two-fold, to confirm user requirements and to test the functionality of the component so that any changes can be made prior to the integration of components.
- When each component has been completed and approved, they are integrated to become a complete system. The system is available at this point for review, testing, and final approval.
- Applications are made available to you via a web interface linked to your host server where the website and all components are hosted.
- On-going support, modifications and enhancements, and general maintenance are performed to maintain the website or application therein.
Peer review, management review, and testing occur on a regular basis during the development period. Formal testing is completed just prior to final submission of the website or application for the client’s approval to publish.