Waterfall Model
The waterfall model is the process that is used to create an
application or piece of software. The waterfall model below shows each stage
that needs to be completed in order to create software. It is called a
waterfall model as it is similar to a waterfall, in the sense that once one
step is complete the user cannot go back. One of the main benefits of the
waterfall model is that it is very simple to use and understand, this is due to
the fact that it is just a step by step process, and only one stage is being
worked on at a time. However one of the disadvantages is that no actual working
software is produced until late in the cycle. Once this product is finished it
cannot be changed or altered unless it is re done by starting ta the
requirements stage again, this is because the waterfall model does not allow
the team to go back to a previous stage.
Requirements
The requirements of the client for the new system needs to
be gathered at this stage. This can be
done by surveys and interviewing the people who will actually be using the
system. At the end of this stage a
requirements specification document is sent to the next stage.
Design
The design team will use the requirements
specification to help make sure they design a system that will meets the
requirements. At the end of this stage
the design team will give the developers a design specification for them to use
in the next stage.
Implementation
The implementation is where the software is actually
created, this is where any coding is done, and the implementation is the part
that allows the software to work the way it is supposed to. At the end of this stage the code will be
given to the testers for the next stage.
Verification
Verification is where the software is tested for bugs and
then corrected before it is installed in the client’s business for them to use.
