Home > Our Process
The beginning of a project lays the groundwork for the rest of the project. The purpose of this phase is to set the framework for the project, which involves:
Traditional Waterfall Methodology primarily takes care of the analysis phase, then the designing phase, and then the implementation phase to follow, with testing carrying out the whole process. All the phases have definite entry and exit criteria. The transition of this stage is triggered through management decision point by approving the phase end deliverables. This framework is called the Waterfall Model because each phase runs naturally into the next one like water over a series of falls.
This model works out as a best suite when the requirements freeze upfront and are well-documented with no uncertainty in the scope. It is usually used to execute small scale projects.
Iterative and Incremental Development is a product development and management methodology that permits iterative project development and cyclic progress assessment. This development methodology is derived from the well documented 'helix / iterative' software engineering models.
The whole project cycle is sub divided into vertical segments, called 'slices' and each slice calls for a deliverable. Each slice is developed individually using the 'waterfall model'. Developers will analyze, design, code and test in a rigid loop.
Slice partitioning is done up front, with the selection criteria like:
This lets a concrete part of the project to be complete at the end of a slice. The complete testing is carried out in each of the iterations. This methodology facilitates better risk management, better control on the project schedule through better monitoring and corrective actions in the early hours and better requirements management in an incremental mode.
This methodology facilitates requirement evolution in the development process as well as helps in managing larger projects.
The Unified Process is not simply a process, but rather an extensible framework which can and should be customized for specific organizations and/or projects. The Rational Unified Process is, similarly, a customizable framework.
In addition to the Software Development Process followed, we have well-developed processes for:
The beginning of a project lays the groundwork for the rest of the project. The purpose of this phase is to set the framework for the project, which involves:
Traditional SDLC based Waterfall Model
Traditional Waterfall Methodology primarily takes care of the analysis phase, then the designing phase, and then the implementation phase to follow, with testing carrying out the whole process. All the phases have definite entry and exit criteria. The transition of this stage is triggered through management decision point by approving the phase end deliverables. This framework is called the Waterfall Model because each phase runs naturally into the next one like water over a series of falls.
This model works out as a best suite when the requirements freeze upfront and are well-documented with no uncertainty in the scope. It is usually used to execute small scale projects.
Iterative Spiral Model
Iterative and Incremental Development is a product development and management methodology that permits iterative project development and cyclic progress assessment. This development methodology is derived from the well documented 'helix / iterative' software engineering models.
The whole project cycle is sub divided into vertical segments, called 'slices' and each slice calls for a deliverable. Each slice is developed individually using the 'waterfall model'. Developers will analyze, design, code and test in a rigid loop.
Slice partitioning is done up front, with the selection criteria like:
- The slices should be vertical, meaning they should not be sub-systems. Slices should cut across as much of the functionality of the system as possible, being tangible sets of functionality that allow the user to get a look and feel. Slices should represent features. In case of schedule slippages, certain functionality releases may be differed
- Slices should be executable and demonstrable
- A slice should typically take a few weeks to complete
This lets a concrete part of the project to be complete at the end of a slice. The complete testing is carried out in each of the iterations. This methodology facilitates better risk management, better control on the project schedule through better monitoring and corrective actions in the early hours and better requirements management in an incremental mode.
This methodology facilitates requirement evolution in the development process as well as helps in managing larger projects.
Rational Unified Process
The Unified Process is not simply a process, but rather an extensible framework which can and should be customized for specific organizations and/or projects. The Rational Unified Process is, similarly, a customizable framework.
In addition to the Software Development Process followed, we have well-developed processes for:
- Project Estimation and Initiation
- Knowledge & Responsibility Processes
- Critical Process Identification
- Defect Knowledge Database
- Defect History Management
- Risk Management.
Select Industry Select Services Select Technology
- Custom Application Development
- eBusiness Web Development
- Application Maintenance & Support
- .NET Migration
- Software Quality Assurance
- Intranet & Extranet Portals
- Enterprise Application Integration
- Enterprise Resource Planning
- Customer Relationship Management
- Content Management System
- Supply Chain Management
- Business Performance Management
- Business Process Outsourcing
- Search Engine Optimization
