Ecrux' Omega Model

There are several software lifecycle models in use. A few of the popular ones include:

• Waterfall Model
• Spiral Model
• Rapid Application Development (RAD)
• Joint Application Model
• Agile Development

These all have their own advantages and disadvantages. Some companies use one of these models, some use more than one model depending on the project they work, some use a derivative of one of these models and some use none.

We use a derivative of the rapid development model and where required, incorporate the Agile approach. We call it the Omega model because it is shaped like Omega.  We took the benefits of RAD such as fast development time and good quality, removed the drawbacks like less scalability and limitations on the features and created a methodology that not only works for us, but which other companies have also adopted.

We modified and adapted this approach to have an innovative new model, which carries forward its advantages and also addresses its limitations.
By doing this, it allows us to spend quality time in the initial design phase to design the product so that it is scalable, modular and has support for long term features.  It also means we get the alpha release out very soon with basic features and functionalities so we can get client’s feedback and confirm that we are on right track.