A clear understanding of your drivers and demands are critical to identify an appropriate delivery strategy. Through our experience we have acquired an in-depth understanding of your considerations in outsourcing software development.
Our world-class development centers allow us to perform project development work offsite.

Benefits of Offshore Application Software Development:

1. Cuts cost by up to 40%.

2. No capital expenditures.

3. Access to a wider and deeper range of skills than those that may be available within the organization or in the time required for the project completion.

4. Rapid deployment of contract resources to meet the peaks and valleys of the project workload - less need for client resource smoothing.

5. Less day-to-day client management required than for in-house projects.

6. Contractually enforceable commitment to results.

7. Time differentials enable offshore providers to make a 24-hour workday a reality. Where the project involves maintenance of an operational application, maintenance can be split between the offshore team and the client's own staff, taking advantage of the time difference between the two sites, and coordinating efforts via FTP uploads and downloads, and version control software (dual-site project).

Our Approach
    
 

Proposal requirements

This procedure starts from the point where the customer submits or communicates a request for a proposal. This stage comprises of preparing the proposals which would happen at our off-shore facility. The requirement would then be sent to the client for approval.

Project Initiation

After review and approval from client the sales team informs the group head (projects) to begin with the project initiation process. The proposed solution is discussed at length so that the hardware, software and human resouces requirement for the project can be ascertained.

Requirement Specification

Once the project is initiated, a detailed technical requirements specification is made. This serves as an input for the preparation of the design documents, test and documentation plan and the test cases. The scope, technical rationale, proposed solution overview, security and safety, performance, portability, documentation, support, compatibility and backup requirements along with a detailed description of each functionality of the system is stated.

Project Plan

The project manager and the project leader prepare the project plan after studying the requirements specification.

The project plan

1. Communicates scope and resources to software management, technical staff and customer.

2. Defines risk and suggest risk management techniques.

3. Defines schedule for management review.

4. Provides an overall approach to software development for all people associated with the project.

5. Outlines how quality will be ensured and change will be managed.

6. Software Estimation.

Devlopment Process

The development process cycle starts with the preparation of the technical specifications for the project. This is followed by a sound project plan, specifying the software, hardware and networking requirements, developing the high level and low level design documents and developing the test plan and test cases. Through out the development life cycle there is constant client interaction to keep all the parties on the same level of understanding.

Risk Management

Any project has its own risk and therefore a Risk Mitigation plan has to be in place to counter these risks. Risk could be categorized into

1. Project Risk threatens the project plan.

2. Technical Risk threatens quality and timeliness of the software.

3. Business Risk threaten the viability of the software.

Configuration Management and Change Control.

Configuration Mamagement and Change Control plan that takes care of configuration, versioning and change control mechanism. The following depicts the activities involved in Configuration Management.

1. Identifying CI

   1. Configuration items identified and their naming conventions.

   2. Storage of Configuration Item.

   3. Access levels.

2. Configuration status accounting

   1. Baseline.

   2. Check-in/Check-out.

3. Change control management

4. Backups

Back-up and Recovery

A weekly back-up of all Configurable items is taken at both the development facilities.

Project Scheduling and Tracking

Our constant endeavor is to deliver on time. We have in place a procedure for Project scheduling and tracking.

Closure and Post-develoyment

Once the development and testing are completed and the application is ready for rollout our experienced team will deploy the application at the client location. We would analyze the metrics collected during the project and share our learning with our clients.