Digital Mesh :: India in-house software business application ecommerce development team

convert your vision

into reality

Our Customer Fulfillment Process

Our customer fulfillment process begins with initiating the project once the estimates are given to the Client engagement team.

Output : Enhanced
Future List,Test
Plans & Test Cases,
ProjectSchedule and
Estimate, SRS

Output : Design,
Document, Prototype,
Enhanced Test Plans &
Test Cases.

Output :Clients
AcceptancesTest
Signoff.

Output :TestReports
Applications.Code Review
Reports.

CUSTOMER FULFILLMENT FLOWCHART

Plan and Elaborate

Once the project is confirmed, an enhanced feature list is prepared. The project and it's associated tasks are then assigned to the respective leads in the Design and Development team. The Use cases and the Software Requirements documents are created here. The design architecture is then articulated to the organization and the prototyping begins.

Design and Development

We follow the iterative model of development - an intermediate model between the traditional Waterfall method and the Extreme Programming methods.

In this methodology, once the preliminary requirements are clarified, the next step is to quickly build the prototype of the website/web application. From then on, it is the continuing evolutions of this prototype until it becomes the final product, exact to specifications.

Our design and development processes are well defined and also strictly adhered to.

Some of the notable features are:

Visibility

	This is a revolutionary, new approach to software development and extremely suited to offshore development and outsourced services. When you outsource your requirement of web solutions to us, we are sensitive to the fact that you require high visibility of the WIP (work in progress). This is the reason why we have adapted this methodology to our web development process. At each stage along the development, the website/web application evolves before your own eyes. Here are the broad milestones in this process:

Prototype

	The most crucial phase that gives you an idea of the shape of things to come. Keeping in mind the customer requirements, a more than visual representation of the same is displayed in the prototype. The client for further refinement evaluates this and we deliver the final product from the final "evolutionary prototype".

	A prototype ensures smooth communication between user and developer with different backgrounds. Vague requirements can be given a clear definition while risks and costs are reduced in development.

The Proof of Concept

	The prototype evolves to its more complex level of existence. Many parts of the prototype spring to life. This is an intermediate delivery stage before the final delivery that aims to establish the proof of concept. The client can now almost feel the solution that he/she had entrusted us to develop. What remains now is just a formality. Our production engine hauls the project to completion.

Functional specifications document

	This is a blueprint for how a particular web project or application looks and works. It details what the finished product will do, how a user will interact with it and what it will look like. This enables easy management of client expectations and saves time on productivity. The development process is streamlined here.

	This document marries user experience with the various departments, business and technology required for the project. The application being developed is defined and its purpose is stated clearly here. Information models that help convey the concepts of the application like the user model, the designer model and the programming models are developed here.

	The flow chart showing the Customer fulfillment process lists out the various deliverables and documents that are created and delivered during the development and deployment phase.

	Processes are measured at every stage and detail reports elucidating the same are submitted at every stage of our work. Our processes also take into account change and risk management functions.

Final delivery

	A QC (Quality control) resource is assigned to every project at the very beginning and proposes a Software Test Plan (SFT) for the project. This prescribes the scope of the testing involved and ensures that all the functional and design specifications are implemented. The QC representative ensures that Unit testing of all the phases in a project beginning from the requirements capture through the design, development and the final product are completed. Future recommendations are also made here.

Want to go open source ? PHP ? Linux ?
We can do it ! Call us.

I see no reason why anyone would want a computer in their home.

Kenneth Olsen,
Founder of Digital Equipment .