1.2.3 software development

Waterfall spiral

extreme programming rapid application

follows distinct phases rigid methodlogy cannot go back documentation heavy

feasability report requirements analysis and design implementaion (coding) testing deployment evaluation (with client) maintaining

on a large task where requirements are clear and dont change pros simple clear on responsibility easy to use if porject is on schedual

carries a high risk requirements must be well understood client only sees product at the end

spiral is a risk drivin methodology less of a methodolgy and more of a guide for developers not a fixed process can include RAD within spirals prototypes at the end of each spiral

utalised on large projects where requirements are unsure pros risk analysis at each loop

risk analysis can be more expensive because

a group of repetative methodologies that creates prototypes for the client throughout the development process

Rapid application development involves giving the client a prototype quickly i.e a gui prototypes increasing quality until client is happy client driven

extreme programming involves providing a coded solution to the client as soon as possible and

requirements dont need to be clear constant feedback from clients used for when requirements unclear

Not suitable for projects where high quality code is required because of its usability focus regular contact with client is needed

likely to have high quality code constant feedback from client when priority is on the quality of the coded result

collaborative programming means more money clients need a representative which would cost them more money