User requirements – this is when the client tells the designer of the program how he/she wants it and explains the different functions and features which have to be on the program. This is done by an interview which the designer will ask specific questions to determine how the program will be designed.
Analysis - Analysis is when the business looks at the work and is able to understand what is written and find some patterns. The business would do this in every piece of work not only to see if it was acceptable to the reader but also to monitor the employees. Some businesses write reports on sales and costs of the business they would analysis the information to see the business was increasing their profits or just losing money.
Designing - An overview is an overall diagram with explanation showing all the page and user forms together explaining briefly the purpose of each and how they are linked together. For example calculations, size and formatting, data types and fields.
Implementation - this stage is to design the product with more efficiency adding all functions and features asked by the client.
Program testing – testing to see if all the functions and features of the program works. For example calculations inserted for functions and features.
System testing – this is just to test if all the programs with on the system as sometimes the program may work fine but when run on the system may perhaps have errors and faults.
Evaluation – this is where you can see if all the clients’ requirements have been met. And if there could have been any improvements made.
One of the advantages to waterfall methods are that only when the stage is complete can you go to the next stage, if there is an error you can always just go back at the end of the project, as demonstrated on the diagram. It is a straightforward method. A waterfall method is easy to understand, simple to be implemented and with experienced employees makes life very easy and gives customers confidence that the project will finish on time.
The biggest disadvantage to waterfall methods is that you cannot go back. For example if your implementation goes wrong the whole project can become very complicated in the next stage. Another limitation is throughout the project the client may not really have a perceptive of what the project would include which causes a lot of confusion to the workers. Small changes or errors to the project will cause a large number of problems, these problems can effect time spent on one stage. The waterfall model is only finished when the final stage of the development cycle is complete
