Hybrid Model in Software Engineering

What is Hybrid Model?

A hybrid model in software engineering is a combination of two or more models and modifies them according to business needs. This model depends on other SDLC models, such as spiral, V and V, and prototype models. The hybrid model is mainly used for small, medium, and large projects.

Whenever we want to get features of two models in one model we go for the hybrid model.

The most commonly used combination of the two models is as follows:

  1. Spiral and Prototype Hybrid Model
  2. V&V and Prototype Hybrid Model

1. Spiral and Prototype Hybrid Model

Spiral and prototype hybrid models are used for the following conditions:

  • Whenever there is dependency we go for spiral and prototype models.
  • When the customer provides requirements in stages and we develop products in stages using this model.
  • When the user is very new to the software industry and is unclear about the requirements.
  • When developers are new to certain software.

Spiral and prototype hybrid model process

The spiral and prototype hybrid model process will be completed in different stages, which are as follows:

  • The process of this model starts with gathering the requirements from the customer for different modules like A, B, and C.
  • After gathering the business requirements of the software, we will build prototype A.
  • Once we have developed the prototype, we will test prototype A.
  • After successfully testing the prototype, we will send it to the customer for review and approval.
  • Once they have reviewed and approved the prototype, we will design the prototype for the actual module.
  • After the designing phase is complete, the developer starts writing the code for the modules.
  • After the development is completed, it will send it to the testing team, they will test the module.
  • And when the testing phase is complete, it will be deployed to the customer.
  • And this process continues till all the modules (B, C).

2. V & V and prototype Hybrid Model

We go for this model for the following reasons:

  • When both the customer and the developer are new to the industry.
  • When the client is expecting a very high-quality product within the required time because every step is tested, and the developer and testing team are working in parallel.

V & V and prototype hybrid model process

In this model, a testing team is involved to test the prototype and testing will start at an early stage of product development, which avoids bugs from going downstream, helping us reduce rework.

The V&V and prototype hybrid model process will be completed in the following phases.

Step 1: The process begins with gathering business requirements in the form of CRS documents, and the tester will do the following:

  • Review the CRS.
  • And write User Acceptance Test Cases and Test Plans.

Step 2: The BA will then convert this CRS document into an SRS document, and the web developer will design and develop the prototype, send it to the tester, and the tester will test the following:

  • First, they will review the SRS document.
  • and writing system testing test cases and test plans.

Step 3: After that, the testing team will check the prototype and identify the bugs and send it back to the respective developer. Once the prototype is tested, it is sent to the customer for review and approval.

Step 4: Once the customer approves it, we will create a high-level design of the specific prototype and send it to the testing team where they will do the following:

  • Review the HLD.
  • Writes integration testing test documentation.

Step 5: Once this is done, we will start working on the low-level design and send it to the tester and the tester will perform the following tasks.

  • Review the LL.D.
  • and writes functional test cases and test plans.

Step 6: After that, the developer starts writing the code for the specific prototype and does a round of white box testing from his end, and sends it to the testing team for further testing where they do different types of testing.

This process will continue until the modules and prototypes are stable and then they will deliver to the customer.

Advantages of Hybrid Model

  • The hybrid model is extremely flexible.
  • In this model, there is less customer rejection due to the prototype.
  • It is easy to implement as it has the flexibility of synchronization.
  • It is easy to use and implement, especially with small and medium projects.
  • In this, the development process will be smooth and fast as here we only follow the relevant process cycles.

Disadvantages of Hybrid Model

  • Every hybrid model is different from the others.
  • It does not adhere to normal standards.

Other Popular Articles

Test Maturity Model in Software Testing

Leave a Comment