We are familiar with using various standard development methodologies based on the requirement context, complexity and clarity of the scope of work. Our core technical team has real exposure to diverse project environments and has successfully used different methodologies in their long stint in the industry.

Our product life cycle is defined in seven progressive stages illustrated below:

Waterfall Model
For smaller and medium projects with a clear scope of work we adopt the Waterfall Model where the development steps are sequential stages with distinct goals for each phase of development. This is most suitable when the client requirement comes to us with a detailed functional specification and less intervention is required during development.

• Document System Concept
  
• Identify System Requirements and Analyze them
• Break the System into Pieces (Architectural Design)
• Design Each Piece (Detailed Design)
• Code the System Components and Test them individually (Coding, Debugging, and Unit Testing)
• Integrate the Pieces and Test the System (System Testing)
• Deploy the System and Operate it

Iterative Model
We use this model for large, complex projects where the user is involved throughout the process, risks are mitigated at an early stage, and the development team emphasizes fast results for quick implementation.

The advantages include improving both user participation in system development and communication among project stakeholders. As a result, iteration works well in situations where project objectives are unclear, requirements are unstable, or users are not highly knowledgeable.




Spiral Model
We use this model to provide rational and time efficient development of software solutions for our clients. The Spiral Methodology reflects the relationship of tasks with rapid prototyping, increased parallelism, and concurrency in design and builds on activities.

This Development Methodology:

• Combines the iterative nature of prototyping with the controlled and systematic aspects of the Waterfall Model.
  
• Rapidly develops software in a series of incremental releases
  (During early iterations the incremental releases may be a paper model or prototype)
  
• Produces increasingly complete versions of the software in later iterations.

The Spiral Model for Software Engineering Process




The Spiral Model for Software Engineering ProcessOur software engineering team uses the Spiral Model of the software development process and moves clockwise in a spiral beginning from the core.

• Product Specifications are developed with the first (or more) circuits of the planning regions of the spiral.
  
• TThe Prototype and sophisticated versions of the software are developed progressively by repeatedly following all the steps outlined in the planning stages.
• Project Plans are adjusted with each spiral of the planning regions.
• Cost and Schedules are adjusted based on the feedback from the Client Evaluation.)

The Spiral model is adapted to apply throughout the life of the software. Whenever a change is initiated, the process starts at the appropriate entry point (e.g. Product enhancements).