Hybrid Model

Hybrid Model/Sandwich Model

Description

             The process of combining or merging more than one model into a single model is called Hybrid Model.

Eg1: Spiral & Prototype Model

Explanation

1. Customer gives requirement for module 'A'(60-70% requirement).
2. Business Analyst will do requirement collection for module 'A'.
3. Team will do Feasibility study for module 'A'.
4. Web Designer or Developer will design prototype for module 'A'.
5. Test Engineer will do prototype testing for module 'A'.
6. If test Engineer find any defect in prototype then he will communicate with developer.
7. Developer will fix the defect and give a new prototype.
8. Test Engineer will again do prototype testing for new prototype.
9. Once prototype testing is completed prototype will be send for customer review.
10. If customer find any defect or he want to change something then he will communicate change/defect to developer.
11. Developer will again fix the defect/change and give new prototype to test engineer.
12. Test Engineer will do prototype testing for new prototype.
13. Once prototype testing is completed prototype will be send for customer review again.
14. If customer approved the prototype then architecture will do actual design for module 'A'.
15. Developer will do actual coding for module 'A'.
16. Test Engineer will do actual testing for module 'A'.
17. Once testing is completed software quality is good module 'A' will be released to the customer.

For what kind of project we can go for prototype and spiral hybrid model

1. When customer is new to business.
2. When customer is not aware of complete requirement.
3. When there is dependency between modules.
4. When customer give requirement in stages.

Eg2: V&V  & Prototype Model

Explanation

1. Customer give requirement (60-70%) in form of CRS.
2. Business Analyst will collect requirement.
3. Explain it to project manager. Project Manager will take CRS and send it to developer and test engineer.
4. Test Engineer will review CRS, write acceptance test plan and test case.
5. Parallely developer will be converting CRS in to SRS and also design and develop the prototype.
6. Once both test engineer and developer complete the work, SRS and prototype will be ready.
7. Project Manager will take up SRS and Prototype and send it to both test engineer and developer.
8. Test Engineer will do prototype testing.
9. if there are no defect in prototype developer will start converting SRS to HLD parallely test engineer will review SRS against CRS and write system test plan and test case.
10. Once both developer and test engineer completes the work HLD will be ready.
11. Project Manager will take HLD and give it to test engineer.
12. Test Engineer will review HLD against SRS parallely developer will start converting HLD to LLD.
13. Once both developer and test engineer completes the work LLD will be ready.
14. Project Manager will take LLD and give it to test engineer.
15. Test Engineer will review LLD against HLD parallely developer will do actual coding.
16. Once both developer and test engineer completes the work software will be ready.
17. Project Manager will take software and give it to test engineer.
18. Test Engineer will start with actual testing.
19. Once testing is complete software quality is good software will be released to customer.

For what kind of project we go for v&v and prototype hybrid model ?

1. For complex project.
2. For long term project.
3. When customer is new to business.
4. When customer is not aware of complete requirement.

• Tweet
• Share
• Share
• Share

Related Post