The
Waterfall model [2] [3] is the first applied software development strategy, resembling the designs that were used in other industries.
The paperwork-based, process-oriented, traditional
waterfall model of engineering development fits nicely into bureaucracies.
Traditionally in the early 2000s, in the
waterfall model, QA was always seen as a subsequent phase to development, often referred to playfully, as the dishwashing stage of the SDLC.
Some of these were the Iterative model,
Waterfall model, Sashimi model, Spiral model, Fish Bone or Ishikawa Diagram, and Prototyping.
Although many models have been presented at the beginning of the
waterfall model [7].Each phase of the SDLC (Software Development Life Cycle) is vulnerable to the different kinds of risk factors.
For the purpose of automation of assessment of classification type answers, a classification models namely
waterfall model is proposed.
The first formal description of the
Waterfall model is described by Royce in 1970 [2].
It has its roots in the world of software development, where the software project management community got weary with the inefficiencies and theocracy of the
Waterfall Model, which presupposes a fixed, unchanging scope, monolithic development and, finally, one-shot user acceptance testing, where it's inevitable that there be rejects, negotiations, leading to a badly compromised product being shipped out into the marketplace.