 |
Phase I - Project Initialization |
| |
A project is initialized through a
visit to the client by
E-Square. The purpose of the meeting is to:
|
|
|
 |
Introduce the
E-Square team |
 |
Explain our
development methodology |
 |
Demonstrate a
sample specification and
products |
 |
Access the
overall scope of the client's
project |
 |
Discuss our
terms and conditions |
|
 |
Phase II - User Requirement
Documentation |
| |
The next step in the
development process is to identify the
client's needs and opportunities more
closely. The purpose of this stage is to
gain a solid understanding of the
client's business requirements. |
| |
Meeting with the
client's project manager and users Web
E-Square produce a
User Requirements Document
that outlines the client's business
needs and the best software solutions. |
| |
Note:
If this project involves converting an
existing system, for example, from
Access to Oracle, and no functionality
changes are necessary, this phase may
not be required. |
 |
Phase III - Design Specifications |
| |
Design Specifications
of the system are identified from the
User Requirements Document. Design
Specifications include all the necessary
steps for design, delivery and
implementation of the project.
E-Square ensures that solid
foundations are prepared for the project
and discuss this document with the
client for acceptance and sign off. |
 |
Phase V - Implementation
|
| |
Once the software is
installed and ready for used,
E-Square's development and
implementation team will experiment in
live environment. Any modification
required will be done on the site
itself. |
 |
Phase VI - Handover and Acceptance |
| |
Software is installed
at the client's site for beta
testing and acceptance by the
client. Once accepted, the software is
ready to be installed for 'live' use. |
 |
Phase VII - Training
|
| |
Training can be
carried out during this phase if
required. |
 |
Phase VIII - Support and Enhancements |
| |
One of the most
important aspects of a software
development is the post-implementation
support. |