V-Model In Manual testing 

V-Model 

• This is the model where the test engineers come into the picture.
• Here the Developers & test engineers work parallelly.
• In the 1st  stage, the CRS is given to both the developers & test Engineers.
• The developers start converting CRS to SRS In the meanwhile, the test engineers review CRS (find wrong requirements, missing & duplicate requirements)  they write the Acceptance test plan & acceptance test case Any mistake in SRS will be sent back to the developers the developer s update CRS & convert into SRS.
• In the 2nd stage once the SRS is ready developers stage converts into HLD. The test engineers review SRS and write the system test case, any mistake in the SRS is sent to the developers They update the SRS & convert it again to HLD.
• In the 3rd stage once the HLD is ready developer converts it to LLD the test engineers review HLD, and write an integration test case any mistake in HLD is sent back to the developers they update HLD & again convert it to LLD.
• In the 4th stage once the LLD is ready developers start coding the testing team. reviews LLD write functional test  plan & functional test  case any  mistakes in LLD is sent back t the developers, they update LLD & remodify  the source code
• In the 5th stage once the source code is ready  the developers  store it in a repository & unit testing or write a box testing
• The developers will be sent the application to the  testing team the test engineers do functional testing integration testing system testing & acceptance testing & they  release the software to the customers

white box testing:  Every line of source code will be tested by developers.

Advantages:

• Developers & test engineers work parallelly time consumed is less.
• Testing is done in the early stages itself & it is carried out in each & every stage download flow of defects is reduced.
• Total investment is a lass. 

Drawbacks 

• The initial investment is more.
• Too much documentation is done in each & every stage.

Applications

• we use this model for complex applications. 
• for long-term projects.
• when the customer wants quality software. 

• Tweet
• Share
• Share
• Share
• Share