2.2. V Model

It is a development process with better mapping and sequential way of product development. You may read more about it in Wikipedia.

../../_images/v-model-theory.jpeg

Basically, it means:

  • Specify/Document test scenarios as early as possible. Map them back to the original requirements.

  • When we map test scenarios back to the Requirements, the Requirements get clearer.

  • If its specified, eventually, it will definitely get implemented. And since it is implemented, it will get tested.

  • But still, tests are implemented after development.

  • Any late change in development implementaiton will also have a cascading effect on the test implementation.

  • As we see in V Model — Practice, there is more than what meets the eye.