Using a traditional method of software development in particular the Waterfall Model follows a series of steps that should be adhered to when building an Information System. They normally follow a strict format in a predefined order and a review at the end of each stage. Only when the review of each stage is complete can you begin the next stage.
The format typically follows as below:-
3. Logical Design
4. Physical Design
It is a model that is simple to understand and use. The technologies and tools used within the Waterfall Model are well known and the requirements are clearly defined and well known. An example of a Waterfall model is Hewlett-Packard’s Evolutionary Development (EVO) Model where development cycles are divided into smaller, incremental waterfall models in which users are able to get access to the product at the end of each cycle. The users then provide feedback on the product for the planning stage of the next cycle and the development team responds, often by changing the product, plans or process. These incremental cycles are typically two or four weeks in duration. EVO is very simple in its concept and it (previously) provided significant challenges to the company but notable benefits.
According to Elaine L. May and Barbara A. Zimmer The traditional waterfall life cycle has been the mainstay for software developers for many years. For software products that do not change very much once they are specified, the waterfall model is still viable. However, for software products that have their feature sets redefined during development because of user feedback and other factors, the traditional waterfall model is no longer appropriate
Doyle, C. (2012) ‘Week 5’: Systems Analysis and Design
May, E.L., Zimmer, B.A., (1996) The Evolutionary Development Model for Software, Hewlett Packard Journal, Article 4, Page 1 & 2,.http://www.hpl.hp.com/hpjournal/96aug/aug96a4.pdf (accessed: 4th February 2013)