One of the key differences between the two methodologies is that Waterfall requires everything to be described in written documentation before any code is created.
Waterfall software software#
Waterfall is often placed on the opposite end of the software development spectrum to Agile software development. One of them is PRINCE2, which was created by the UK Government and is still held in high regard in the public sector. There are several well-recognised waterfall methodologies. The original Waterfall model consisted of five stages: In other words, we’re not so much looking at one big Niagara Falls, but a series of cascading waterfalls – each with their own little pool of activities. This means that it follows a simple structure of phases where the results of each phase cascade down to the next level of development. We often describe Waterfall as a ‘linear-sequential lifecycle model’. It was first described in a 1970 paper (Dr Winston W Royce), as one of the very first formal software development process models. The Waterfall model has been around for more than 50 years. Here we will look at the Waterfall model in a bit more detail, exploring its advantages and disadvantages. One of the models we discussed was Waterfall Software Development. In a previous blog post we looked at various development models and what makes them different.
0 kommentar(er)
