11
MODIFIED WATERFALL MODEL

Modified Waterfall Method

Embed Size (px)

DESCRIPTION

Modified Waterfall

Citation preview

Page 1: Modified Waterfall Method

MODIFIED WATERFALL

MODEL

Page 2: Modified Waterfall Method

MODIFIED WATERFALL MODEL

The modified waterfall uses the same phases as the pure waterfall, but is not based on a

discontinuous basis. This enables the phases to overlap when needed.

It is modified by B. Boehm in the late 1976.

Page 3: Modified Waterfall Method

REQUIREMENT ANALYSIS

   The analysis phase is used to gather the system requirements and, which includes the user’s expectations of the system. At the end of the analysis phase the developers gain the

system specification.

Page 4: Modified Waterfall Method

DESIGN

 This phase involves design of interaction mode which is the input and output, the interfaces of the software and the data requirements of the system. The design

stage the software structure is defined and thus is one of the most crucial phases of the software life cycle. The output of this phase

is a system documentation.

Page 5: Modified Waterfall Method

IMPLEMENTATION

  In this phase the actual codes of the software are written and single units tested

for bugs, with the help of different programming languages. The end product of

this stage is a working program or set of programs.

Page 6: Modified Waterfall Method

TESTING

This phase allows the users to test the system as a whole, by bringing all the

different modules together. Tests are done on the interfaces, on the platform it will work on, the amount of data it will hold, and whether it meets the user’s requirements. The end

product is a test report and a ready deliverable system.

Page 7: Modified Waterfall Method

MAINTENANCE

This phase will last the entire life of the software. This because changes may be

made to it, or additional modules may be added to make the software more efficient

and meet the user’s needs.

Page 8: Modified Waterfall Method

METHODOLOGY

Page 9: Modified Waterfall Method

ADVANTAGES

More flexibility than the pure waterfall model.

If there is personnel continuity between the phases, documentation can be substantially reduced.

Implementation of easy areas do not need to wait for the hard ones.

Page 10: Modified Waterfall Method

DISADVANTAGES

Milestones are more ambiguous than for the pure waterfall.

Activities performed in parallel are subject to miscommunication and mistaken assumptions.

Unforeseen interdependencies can create problems.

Page 11: Modified Waterfall Method

WHAT IS THE DIFFERENCE BETWEEN

WATERFALL AND MODIFIED WATERFALL

MODEL? In Water fall method , there is no VALIDATION

OR VERIFICATION between the phases , so the listener will finally get unsatisfied on the

report.

This Modified Waterfall Model involves VALIDATION or VERIFICATION between the

phases , so any deviations can be corrected immediately , providing the listeners

satisfaction, so this is preferred.