<title>SoftwareEngineeringMethodologies</title> <style> h1{color:#711797;font-size:300%;font-family:consolas} h2{color:#711797;font-family:consolas;font-size:20px} h3{font-family:consolas;font-size:30px} p{font-family:consolas} img{float:left} span{font-family:consolas} table{width:100%;align:center} </style> The Waterfall Lifecycle is a linear model. This means that the next stage can only be started once the current stage is complete. The stages are as follows; requirements - where the developer sits down with the client to see what the program will need to do, analysis- this is where its determined if the program is technically(is the technology available), economically, legally, operationally and whether it will be done in time. Then there is design where flowcharts, pseudo codes, etc. are used to design the software. It is then coded by software engineers. After which it is tested and then finally maintained to ensure it stays functional over time. after any stage you can go back a step e.g. if some more requirements are needed for a proper analysis. It is used in mainly straightforward, short projects.

Advantages	Disadvantage
There is a lot of documentation to refer to.	There are no prototypes produced so a functional program is only produced near the end of the model
Its a fairly easy model to understand an apply	if in a testing a requirment needs to be changed it can take up to twice the original cost and time to recreate the program