Ambrosia
provides a structured product development process to its clients to
ensure that the released product is robust and ready for deployment.
The diagram below provides an overview of Ambrosia’s Product Development
and Engineering Process.
Requirements and Specifications:
Software product requirements/specifications are analyzed and documented,
which is reviewed by the client. Various software usage scenarios are
studied and documented.
Prototype:
Prototype acts as a proof of concept for various applications. Clients
get a chance to provide feedback early in software development cycle,
which can be incorporated in actual design and development.
Architecture & Product Design:
Ambrosia development team architects and designs the software product
taking into consideration various attributes such as reliability,
scalability, etc. The team uses industry best-practices during the
designing phase.
Code Complete:
Coding is done in a phased manner. During this stage component unit
testing is completed and it is ensured that each component is fully
working.
Alpha:
Alpha product has most of the User Interface and functionality. A
detailed integration testing is done before releasing "Alpha"
version of the product. The Alpha release provides the first look
of the application, and is useful for the client's integration team.
In this phase the client reviews Alpha code, and provides appropriate
feedback.
Beta:
At this stage the application is complete as per requirements and
specifications, and any approved change requests, along with unit
testing. The integration testing is done as well for a few modules,
and system testing is over as well. To uncover some bugs, which might
be there, the application is exposed to a limited number of business
users in a controlled environment. The client gives the feedback on
the system along with a list of bugs that might be remaining.
User Acceptance:
The QA team approves the application and releases it to the client
with the Alpha and Beta bugs fixed. Limited set of client users then
perform User Acceptance Testing (UAT). Any feedback/corrections are
then incorporated in the system before the final go-live.
Go-Live:
After the QA team approves the application, including fixes for any
bugs reported during UAT, the team makes it available to the client
for general use.
Customer Support:
Once the application is live, Ambrosia works with clients to support
end users, and manages the feedback loop to improve the functionality
and develop enhancements.
|
