SPI | Delivery Model

At SPI, we are familiar with various software development lifecycle models and their applicability. The software development models that we have successfully used include :

When the project can be divided into a sequence of well-defined phases, SPI chooses the Waterfall Model or the Linear Sequential Model. The actual phases - their length and content - depend on the project and are usually driven by customer needs. Typically, the phases in a development project are :

THE WATERFALL MODEL
The Waterfall Model is the simplest model and is recommended on projects for customers new to offshore relationships.

PROTOTYPING MODEL
When the construction of requirements is a major hurdle and the knowledge exists with a small group of customer stakeholders, the Prototyping Model may be followed. A prototype is built to quickly demonstrate to customer stakeholders what the product would look like. Only minimal functionality is provided in the prototype built in this manner. The prototype is also usually discarded after requirements have been signed off by the customer.

RAPID APPLICATION DEVELOPMENT MODEL
We sometimes combine the features of the Prototyping Model and the Waterfall Model to execute projects based on the Rapid Application Development (RAD) Model . In consultation with the customer we agree on the decomposition of the final product into manageable units that can be developed in short periods of time, for example, in. 100-day cycles.

THE SPIRAL MODEL
The Spiral Model is a popular method with customers (and therefore with us) to build a software product. The concept revolves around adding in different degrees of functionality with each additional spiral (level). Each level indicates the stage of evolution of the final product. The Spiral Model is a realistic way to develop software and mirrors natural thinking. However, to ensure success, levels and phases as well as goals and objectives have to be carefully defined while starting the project.