DEVASC Flashcards

1
Q

Waterfall Methodology Advantages

A
  • Design errors are highlighted before any code is written, saving time during the implementation phase.
  • Good documentation is mandatory for this kind of methodology. This effort is useful for engineers in the later stages of the process.
  • Because the process is rigid and structured, it is easy to measure progress and set milestones.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Waterfall Methodology Disadvantages

A
  • In the very early stages of a project, it can be difficult to gather all the possible requirements. Clients can only fully appreciate what is needed when the application is delivered.
  • It becomes very difficult (and expensive) to re-engineer the application, making this approach very inflexible.
  • The product will only be shipped at the very end of the chain, without any middle phases to test. Therefore, it can be a very lengthy process.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

The TDD iteration is finished when…

A

code refactoring is done and all tests pass.

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

What is the correct order of steps in a TDD iteration?

A

Step 1: Write tests; Step 2: Run tests (should fail); Step 3: Write code; Step 4: Run tests (should pass); Step 5: Refactor code.

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