software dev methodologies (waterfall method) (week 1) Flashcards

1
Q

what is software development methodologies

A

–> predefinition of specific deliverables and artifacts created and completed by the team to develop or maintain a software application

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

what is the waterfall model

A

–> highly structures process which depends heavily on upfront planning and a set of sequential and prescribed steps

–> it is a linear process where the outcome of one phase acts as the input for the next phase

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

what are the steps of the waterfall model

A
REQUIREMENTS 
DESIGN 
IMPLEMENTATION
VERIFICATION
MAINTENANCE
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

When to use the waterfall model

A
  • -> requirements are clear and fixed
  • -> project is short
  • -> technology is understood and not dynamic
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

When to use the waterfall model

A
  • -> requirements are clear and fixed
  • -> project is short
  • -> technology is understood and not dynamic
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

benefits of the waterfall model

A
  • -> easy to understand and use
  • -> easy to manage as each phase has specific deliverables and a review process
  • -> works well for smaller projects
  • -> process and results are well documented
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

drawbacks of the waterfall model

A
  • -> no working software is produced until late in the dev process
  • -> high amounts of risk and uncertainty
  • -> cannot accommodate changing requirements
  • -> integration is done at the end of the process which does not allow for identifying business or technological bottleneck challenges early.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly