Process Step By Step
» Establishing contact
» Understanding you requirements
» Analysis
» Taking your approval
» Signing contract
» Designing
» Development
» Testing
» Deployment
» Tape out
» Maintenance

Overview of Complete Process

Maintenance

Key features of our process

Complete Confidentiality
We make every effort to ensure that your project remains secure and confidential.

To ensure confidentiality, we sign a Non Disclosure Agreement (NDA). Additionally, project details are available only to the team members who are involved in the specific project.

All employees are required to sign confidentiality agreements with us.

Service Level Agreement
A service level agreement contract is signed that details the responsibilities of both the parties, deliverables, pricing, important mile stones and the delivery schedule of the project.

Payments are made only after taking your approval on the milestones and deliverables

Communication Methodology
We completely understand that clear communication is the key ingredient of a successful outsourced project. Any misunderstanding due to communication gap can play havoc in the completion of the project.
We use various tools to facilitate clear, unhindered one-on-one interaction with our customers. Some of the utilities we use to ensure effective communication and information flow through the project lifecycle include -
Skype - For all one-on-one communication, we use instant messenger or Skype, to make it easier for you to voice any concerns or clarifications in real time. We also use Skype for online conference calls with our customers.
Web Ex - For projects that require customer walkthroughs, we use Web Ex, an online conferencing software.
Documentation - We document the minutes of all meetings and share them with all stakeholders involved
One point of Contact
The project manager assigned to your software development project will serve as your single point of contact for all communication.

Understanding your requirements
Our Business Analysts take an extra effort to understand all your Business requirements, user requirements and functional requirements to make sure that we deliver what exactly you require and that is in tune with your business requirements.

We also involve the end-user or customers as much as possible during the requirements capture stage to gather their inputs and understand their specific requirements.

We make sure that the requirements are quantifiable and measurable. Areas that are unclear may require more detailed analysis or even the development of a prototype.

Prioritizing requirements by the relative importance helps weed out high cost-low value functionality. It also helps us in making informed and critical decisions when faced with time/ resource and functionality tradeoffs and also identify and remove any functionality which will not be used or which do not help meet any of the business objectives.

We also make s ure that the project scope is clearly defined in the Scope document.

Taking your Approval
We keep in touch with you regularly to gather your feed back before working on the design. The payment has to be made after both the parties reach at a common platform and your approval is taken to go ahead with the agreed milestones and deliverables.

Signing Contract
We sign a service level agreement, which details the responsibilities, deliverables, important milestones to make sure there is complete transparency while we move ahead with the design and development of the project.

We also enter into a contract with our clients which is a legal document so that the clients feel assured in case of any dispute between the parties.


Development Process:

Designing
The application design is developed on the basis of the software requirement specification; use case specification, business rules & diagrams and the scope agreed upon in the Requirement Definition stage. This stage has the following steps:

» Designing Architectural Diagrams
» Creation of High Level Design and Low Level Design class diagrams
» Establishment of Entity Relationship Diagram, Data Flow Diagram and Deployment Diagram
» User Interface - The prototype is developed and validated against the requirements and presented to the client for approval
» The use cases elaborated in the analysis model are represented using collaboration diagrams
» Design model elaborations are made from the analysis model. Validation of the scope, estimates against the contract and revisions are made if necessary
» The Implementation Model is generated from design
» The Test Model is generated from use cases.

Development
We follow a process oriented development methodology designed to minimize project risks and development time. We focus on business solutions that fulfill business goals, instead of merely providing technical solutions.

We have defined processes for requirements capture, analysis, design, development, testing and deployment. We generate UML diagrams representing the Use Case Model, Analysis Model, Design Model, Implementation Model and Test Model.

In this stage, the actual code based on the design is created and tested against design requirements and test cases. This stage has the following steps:

» The development of code base proceeds as per implementation and design models
» The application source code is tested according to the test cases and test plan
» Documentation of processes
» Creation of Use Case Test results

Testing
The developed application is tested through test cases, test plans and user acceptance criteria in the deployed environment.

» Integration and quality testing is carried out resulting in test reports.
» Client acceptance tests carried out.
» Client feedback and debugging.
» Client acceptance

Deployment and Acceptance
In this stage, the developed application is deployed on the live server.
» Integrated Application and Deployment plan
» Implementation on client Premises or Hosting Server.
» Implementation Signoff by Client.
» Creation of Archived Software Articrafts
» Transition of application to the maintenance team.

Tape Out

Maintenance

The steps above are iterated through until the final deliverable is completed.

We will submit a detailed project schedule in accordance with the above deliverables. The project schedule will clearly indicate the responsibility of the client and the developer and indicate the dates by which each person will submit their deliverables.