 |
|
|
 |
|
|
| |
| Global Solutions |
| |
| 24X7 Support Service |
|
|
|
|
| |
|
|
|
| |
|
|
| |
|
|
|
| |
|
|
|
|
|
| |
| |
Offshore Methodology
|
Our project managers recommend following our exclusive offshore methodology throughout the software development process within our organization for assured quality. Our offshore methodology is unique, compatible and standardized. Newcomers into an ongoing project can easily catch up with this software development methodology. In short, it is beneficial to both the experienced and inexperienced staff. Projects like document management application demand alternatives to the standards. The flexibility of our offshore methodology accommodates the changes our team has to adapt, in certain projects. |
|
|
Methodology |
|
|
| |
Project Activation |
| |
Clarity about the objectives and scope is obtained |
| |
The sources of business knowledge are explored |
| |
A preliminary timeline and the approximate cost is determined |
| |
A project plan document is made |
| |
The number of customer interactions required to finalize the projectplan is determined. The approval of the project plan is followed by the next life cycle stage. |
| |
|
|
Scrutiny |
| |
Initial understanding is established with the client, by acquiring any existing document related to the project and by means of conference call |
| |
| |
An entity relationship diagram is brought forth, for consideration |
| |
An outline business model formally valid with the customer is made |
| |
The process logic and business rules are evaluated |
| |
It is ensured that the detailed business model is up to date |
|
|
Project Planning |
| |
A sketch of the system structure is prepared |
| |
The scope of data and procedure interactions is described |
| |
Software design accuracy and completeness is verified |
| |
A scheme for technical design is developed |
| |
The technical context and requirements are explained to the client |
| |
The data structures are formulated |
| |
| |
The client is reminded separately about it with due versioning of the design document |
| |
The final technical design document is completed and frozen |
| |
The project plan document is rechecked if necessary |
| |
Requirements of change are collected after the design is proposed |
|
|
|
Project Improvement |
| |
The environment is prepared for the methodology |
| |
The procedures and conventions including configuration Management and source code control are prepared |
| |
| |
The database environment is set up |
| |
Test data and system documents are produced |
| |
Coding is done by programmers if needed, method level and inline documentation |
| |
Unit testing facilitated |
| |
Our weekly deliveries provide clients with opportunities to check out the progress |
| |
The technical design document is revisited if necessary |
| |
Stream testing (both internal and external) is done |
| |
Change in design documents is gathered and implemented |
|
| |
Project Testing |
| |
Integration tests are carried out |
| |
System tests are executed |
| |
Benchmark and load tests are performed |
| |
Metrics on requirements and frequency of change are gathered |
| |
Acceptance tests are put into effect |
| |
Training deliverables, user deliverables and implementation deliverables are made |
|
|
Project Deployment |
| |
The production system is fixed |
| |
The users are instructed |
| |
Action is taken in critical situations. (Another requisite of this phase is the insertion of some of the members of the development team at the client site.) |
| |
|
| |
Post Deployment Evaluation |
| |
Aids you to draw new dimensions regarding project management from the acquired experience, which may enable one to be aware of the possible pitfalls in future. |
| |
| |
The benefits of following a systematic offshore methodology are undeniable. Join hands with us and let your firm profit from the experience. |
| |
|
|
|
|
|
|
|
| Copyright 2007 GCS Infoserv Private Limited.
All rights reserved |
|||| |
|
| Designed by GCS |
|
Back to Top