 |
|
The Software Development
Methodology that ECS adopts is evolved to be a multi-disciplinary
process for developing and delivering effective solutions
and is based on the foundation of our people; their determination
to succeed; and, their ability to deliver |
|
INITIAL PHASE |
Requirements Gathering |
To deliver a truly effective
system/application, thorough understanding of client’s
business needs is called for. Our Business Analysts, Development
Manager, and Technical Lead take time to dig deep into client’s
business to gain an accurate and thorough discernment of the
application/system requirements in client’s business
context and to determine how best to do it |
THE PENULTIMATE PHASE |
URS |
Based on the detailed
specs foregathered during system study, the User Requirements
Specification, which precisely outlines what clients are expecting
from the system, would be turned out on behalf of their organization
or would be received from the client.
|
Proposal |
The latter step would
be to submit
|
- A Technical Proposal responsive to client’s needs
emphasizing the strengths of their company and
- A Cost Proposal depicting necessary financial information
|
SRS |
The technical specification
as to- ‘what business, or other requirements must be
satisfied by the proposed system and how’ -would be
detailed herein this sub-phase. |
Design |
Project Analysts and team
leads would study and prepare a strategy blueprint integrating
function, process, and industry specific strategies assessing
the optimal set of technologies and business models and then
design the system, database and control flow.
|
Development |
Developers, would, then
set out programming the system as per the studies carried
out and the design turned out and accomplishes the tasks on
hand.
|
Testing & Debugging |
To ensure the system performs
as precisely as expected and as accurately as required, tests
on hardware and software would be taken up in accordance with
a documented test plan, which not only documents what will
be tested, but also the expected results. Following the completion
of the tests, those that would be found to have failed to
meet an acceptable standard would be allocated a severity
level. Enabling an objective view, all the errors (bugs) are
noted and analyzed and subjected to corrective actions
|
Client Review & Acceptance
|
In order to obtain client’s
acceptance, the system developed and tested would, then, be
sent to the client, enabling their review. |
Implementation Of The Suggested
Changes |
The changes, if any, that
they might suggest following review of the system/application,
would then be implemented ameliorating the system/application
accordingly |
THE ULTIMATE PHASE |
Delivery |
Finally the system developed
to client’s specifications and expectations would be
delivered on time and within budget keeping up our promise
of reliable and effective application for clients. This approach
to software development enables all of our activities to be
focused on in digging deep all the key aspects to be reckoned
and issues to be dealt with while developing a perfect solution
for clients and then in creating ways to resolve them, which
in turn, pleases clients beyond what they expect .
|
| |