Main differences between software design processes [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 9 years ago.

I want to compare the following software design processes.

• Waterfall model
• V-Model
• Unified Process

The V-Model has test phases for each specification phase, the waterfall model doesn't.
The Unified Process is iterative and incremental, the others aren't.

Are those the main differences? Is there something to add?
I only need the main differences, not too detailed.

Answer 1

1. The water fall model is not iterative.

2. V-Model is iterative in the sense that

   a. It uses unit testing to verify procedural design

   b. It uses integration testing to verify architectural (system) design

   c. It uses acceptance testing to validate the requirements

   d. If problems are found during verification and validation, the left side of the V can be re-executed before testing on the right side is re-enacted

3. Unified Process Model is iterative

   a. System delivered in pieces.

   b. Allows production system and development system to run in parallel.

   c. Reduces risk and uncertainty in the development