2.1. Waterfall Model

../../_images/waterfall-model.jpg

It is a simple sequential way of product development. You may read more about it in Wikipedia. But here are some of the basic flaws with this way of development.

  • Problem:

    (We think) product is already developed as expected in the DEV stage. Every one has seen developed product. No one seem to have any issue with it.

    So… how long do we keep testing it? The longer we test… the longer is the release delayed. The shorter we test… we may ship out an untested product.

  • Bigger Problem:

    Our understanding of product requirement/FRS evolves/improves when start testing or specifying new tests.

  • Much Bigger Problem:

    You only test what is implemented.

(Probable) Solution V Model:

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

When we map test scenarios back to the requirements, the requirements get more clearer.

If it’s specified, it will definitely get implemented.

Once it gets implemented, it will get tested.