Software development lifecycles & testing types

Question 1

Waterfall model

Answer 1

Requirements analysis
System design
Implementation
System testing
System deployment
System maintenence

Question 2

Waterfall model advantages and disadvantages

Answer 2

adva
- Easy to understand, simple to use. Good for management control as each phase is completed before
- Provides structure for inexperienced staff
- Project milestones are well understood
- good when quality more important than cost
disad
- All requirements known upfront (deliverables for each phase are frozen)
- Can give a false impression of progress (different stages take different amounts of time)
- does not reflect problem-solving nature of software development (cannot change core features or functions)
- integration is done all at once at the end
- no customer input during process

Question 3

Iterative ‘Prototyping’ methodologies

Answer 3

Sits between predictive and adaptive approaches
- characterised by building multiple prototypes
- can be RAD (Rapid application development), RP (Rapid prototyping) or IIM (iterative incremental model)

Question 4

Rapid Application development

Answer 4

• focus on developing applications rapidly through frequent iterations and continuous feedback
• prioritise rapid prototyping over long-term planning, developing and testing phases
• not suitable for high risk projects (cannot do this for AI teslas for example)
• not suitable for large-scale projects (cannot just create a huge system multiple times)

Question 5

Iterative incremental model

Answer 5

Similar to RAD but instead you create one piece of the project at a time
Prioritise requirements at start, begin by only completing the high priority requirements

Question 6

incremental vs iterative

Answer 6

incremental - complete one piece at a time
iterative - start with a rough product and refine over time

Question 7

Agile methodology

Answer 7

A modern version of incremental and iterative approaches
- based on concept of MVP (minimum viable product)
- focus on production of product in a short period with rapid release timescales
- different to iterative models as you are creating a series of products instead of prototypes
- less focused on documentation
- promotes collaboration between team and client
- reacts better to changing requirements

Question 8

Agile manifesto

Answer 8

individuals and interactions over processes and tools
working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

Question 9

Readmore about

Answer 9

agile