Waterfall Model

      Waterfall Model

        The waterfall model provided 2 primary enhancements to the stage wise

        Recognition of the feedback loops between stages, and a guideline to confine the feedback loops to successive stages to minimize the expensive rework involved in feedback across many stages.
        An initial incorporation of prototyping in the software life cycle, via a “build it twice” step running in parallel with requirements analysis and design.

        Waterfall model approach help get rid of many difficulties previously encountered on software projects.

        The waterfall model has become the basis for most software acquisition standards in government and industry.

        Some of its initial difficulties have been addressed by adding extensions to cover incremental development, parallel developments, program families, accommodation of evolutionary changes, formal software development and verification, and stagewise validation and risk analysis.

        However, even with extensive revisions and refinements, the waterfall model’s basic scheme has encountered some more fundamental difficulties, and these have led to the formulation of alternative process models.

        A primary source of difficulty with the waterfall model has been its emphasis on fully elaborated documents as completion criteria for early requirements and design phases.

        For some classes of software, such as compilers or secure operating systems, this is the most effective way to proceed.

        However, it does not work well for many classes of software, particularly interactive end-user applications.


      Computer (IT) Technician Services © 2018