week 3 Software process model

What is the water fall process model

a linear sequential (non-iterative) design approach for software development, in which progress flows in one direction downwards through the phases of conception, initiation, analysis, design, construction, testing, deployment and maintenance.

What is the Incremental development process model

The incremental build model is a method of software development where the product is designed, implemented and tested incrementally (a little more is added each time) until the product is finished. It involves both development and maintenance

What is the Reuse-oriented software engineering process model

Although the initial requirements specification stage and the validation stage are comparable with other software processes, the intermediate stages in a reuse-oriented process are different

What is the Agile process model

A como of iterative and incremental process models with focus on adaptability and customer satisfaction by rapid delivery of working software product. This Method breaks the product into small incremental builds. These builds are provided in iterations.

What are the benefits of the waterfall method

Consistent with other engineering process models -Documentation is produced at each phase Process visible so -progress can be monitored

What are the disadvantages of the waterfall method s

Inflexibility -Should only be used when requirements are well understood and unlikely to change

What are the advantages of the incremental development method

The cost of changing requirements is reduced -Easier to get customer feedback -More rapid delivery of useful software is possible

What are the disadvantages of the incremental development method

The process is not visible -System structure tends to degrade as new increments are added

What are the core requirements setout in the agile manifesto?

Individuals and interactions over processes and tools -Working software over comprehensive documentation -Customer collaboration over contract negotiation -Responding to change over following a plan

Name 4 agile metods

Extreme programming (XP) -Scrum -Feature-driven -development -Pair programming

When is agile a good method to use?

Small or medium-sized software products/teams -Customer committed to be involved in the development process -Limited number of external rules and regulations affecting the software -Requirements change often -Culture that thrives in chaos

When is it a bad idea to use the Agile method?

Inexperienced engineers! -Difficult to keep the interest of customers who are involved in the process -The intense involvements characterizing agile methods may not work for the development team -Strict contracts required upfront