1.2.3 software development

Question 1

name all the non agile methodologies

Answer 1

Waterfall
spiral

Question 2

name all the agile methodologies

Answer 2

extreme programming
rapid application

Question 3

explain the waterfall model (dont go through all phases)

Answer 3

follows distinct phases
rigid methodlogy cannot go back
documentation heavy

Question 4

what are the phases of the waterfall model

Answer 4

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

Question 5

pros of water and when to use it

Answer 5

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

Question 6

cons of waterfall

Answer 6

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

Question 7

explain the spiral methodology

Answer 7

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

Question 8

pros of the spiral methodology and when its used

Answer 8

utalised on large projects where requirements are unsure

pros
risk analysis at each loop

Question 9

cons of the spiral

Answer 9

risk analysis can be more expensive because

Question 10

define agile methodologies

Answer 10

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

Question 11

explain RAD

Answer 11

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

client driven

Question 12

explain extreme programming

Answer 12

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

Question 13

pros of RAD and when it would be used

Answer 13

requirements dont need to be clear
constant feedback from clients

used for when requirements unclear

Question 14

cons of RAD

Answer 14

Not suitable for projects where high quality code is required because of its usability focus

regular contact with client is needed

Question 15

pros of extreme programming and when would it be used

Answer 15

likely to have high quality code
constant feedback from client

when priority is on the quality of the coded result

Question 16

cons of extreme programming

Answer 16

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