Methodology
 


Methodology

Our offshore delivery capabilities are customer centric, process oriented and predictable. Well-established and proven methodologies are deployed to deliver timely outputs. A brief note on the approach we take is given below.

1. Proposal Phase

During this Phase following tasks are completed:

  • Identify Project goals, Milestones and Critical Success factors

  • Define broad Requirements, Boundaries and Exclusions

  • Propose Solution Architecture

  • Agree on Effort Estimates and Timelines

  • Proposal Document and Project plan are completed during this phase.
2. Requirements Management

Based on the Accepted proposal, Requirements phase is started. The Tasks during Requirements Management phase are:
  • Detailed Requirements gathering / Study

  • Use Case Models to help capturing Requirements

  • Pilots / Proof of Concept

  • Identification of external interfaces

  • Prototype Preparation

  • Acceptance Test Plan and System Test Plan preparation
Detailed Requirements Definition Report and Prototype are Signed-off after this stage. At this stage, the Acceptance Test Plan and System Test Plan are also prepared in consultation with the User Groups.

3. Analysis and Design

In this phase, using Requirement Definition Report and Prototype as the basis, High-level design is finalized. Tasks involved are:
  • Analysis of Requirements using


    • Detailed Use Cases-Sequence diagrams to identify core use cases


    • Identification of high-level subsystems/components and preparation of detailed Use Cases, Object model and State transition Model.


    • Sequence diagrams for major processes


    • Activity diagrams


    • Identification of the Screen Design and navigation, if applicable


  • High level Design


    • Preparation of detailed technical design


    • Specifications of the N-tier architecture for modularity and expandability


    • Identification of processes and standards to be followed


    • Identification of third party tools


    • Identification of Technical risks involved


  • Schema finalization



  • Preparation of Integration Test Plans

During this phase, Integration issues, usability issues are considered before finalization of the high level design.

4. Construction

Coding is done as per the IndonetGlobal Quality guidelines and this phase consists of development and the Unit Testing of the application. This stage is taken up on Customer approval of the Design document. The tasks involved are:

  • Low-level Design

  • Unit Test Plans

  • Coding

  • Code Walkthroughs by team leaders

  • Unit Testing by developer

  • Documentation - Technical Manual and User Manual
5. Testing and Audit

During this phase, Application goes through the following:
  • Installation Testing

  • Modular Testing

  • Integration Testing

  • System Testing

  • Fixing and Verification of the defects noted in each type of testing

  • Audit

  • Packaging / Shipping

6. Deployment

This phase is done Onsite and calls for significant involvement from customer. Tasks performed are:
  • Onsite Installation

  • Prepare end-user Procedures and Training

  • Acceptance testing by customer - Evaluate system readiness

  • Data conversion for production server, if applicable

  • Test the helpdesk infrastructure - if required
7. Support

Customers opting for Post-Warranty Support will have access to IndonetGlobal Comprehensive Support Systems.

The specific strength of IndonetGlobal is its Tool based approach to software development and support. The entire processes of the Software Development Life Cycle is Automated by the usage of a web based software tool built in house. Using the tool, Clients can view the progress of the project as well as participate by issuing approvals, logging bugs etc. The entire process of development and support is made transparent to every participant in the process. Usage of this tool has enabled capture of metrics data relating to all phases of development and helps the organization in continual improvement.