Water Fall Model, Waterfall Model in
Software Testing, Different Phases of Waterfall Model
Water Fall model is like a serialize
software development model where development is look as going slowly
downwards like any waterfall except this through several phase
Functioning in a systematic way will
called waterfall model that took the production live software from
the most upper basic step to going downward toward the explaing just
as Water Fall starts from the top to downward but never to the
backward.
 |
| Water Fall Model |
Water Fall Model - Different Phases:
Requirement Study and Analysis:
Research has been conducted in this phase on the requirement, it
actually very brainstorming about the software. Mean come to know
about that what is need t do and how, and what is the purpose of
this.
Basic Design: After successfully
completion of first phase, First require to design the software
requirement so that without any delay work can be processed.
Technically Designing and Detailed
Designing: After approving the basic design, then requirement
need to elaborated with technically design and planned. So the each
functions here have decided and the units of engineering are placed
for the examples of module, program etc.
First Construction and
Implementation: Source code will be written in this phase.
Testing will be done of whole design or its some constructed part to
confirm the developed functionality. If there is any type of error
then that will be reported and processed further to development team.
Integration: Integration Phase,
After completion of testing on low levels, company will put all
efforts together. Management and Maintenance:- yes these are required
to confirm that the system required to continue to process as the
desired result.
Advantages of Water Fall Model:
- Waterfall model is easy to implement and also the simple in amount of resource needed for minimal.
- This type is refer in the project where qualities are more necessary as compared to schedule or any cost.
- All software development stages will be documented properly. With this documentation easily project can be understood by anyone.
- Later on when major stages of software will be coded, Then testing will be completed and confirmation will be listed as for correct running code.
Waterfall Iterative Model
Disadvantages:
- Actual project rarely follow the iterations and sequential flow in this model are handled indirectly. These type of changes can create confusion as the projects proceed.
- In such model you freeze hardware and software. But as new or version technology change at a fast pace, such chilling is not advisable especially in long term project.
- Also some little changes in any previous stages can cause blunder problem for subsequent phase or phases because all phases are dependent or co-related to or on each-other.
- Repetition of any phase or going back will be very costly.
No comments:
Post a Comment