English
Menu

What is V-model?

A development model that arranges the phases going down from requirements definition through design to implementation and the testing phases going back up from unit testing to acceptance testing in a V shape, and pairs the two sides, such as requirements definition with acceptance testing, design with integration and system testing, and module design with unit testing. Which design phase is paired with which test differs slightly between organizations and textbooks.

Japanese name: V字モデル

V-model appears in 1 practice question across 1 topic, including Software Development and Project Management.

Field: Software Development and Project Management

Try it: questions about V-model

In the V-model of software development, which test corresponds to the requirements definition phase and checks that what was decided in that phase is satisfied?

  1. AUnit testing
  2. BIntegration testing
  3. CAcceptance testing
Show answer and explanation

Answer: C. Acceptance testing

The V-model is a development model that places the phases going down from requirements definition through design to implementation on the left, places the testing phases going back up on the right, and links each pair of corresponding phases. Acceptance testing (operational testing) corresponds to requirements definition, and as the design phases become more detailed, system testing, integration testing and unit testing correspond to them in turn. The mapping of the intermediate phases differs slightly between organizations and textbooks, and system testing is sometimes also mapped to requirements definition, but all agree that acceptance testing, which checks the requirements from the customer's or user's point of view, corresponds to requirements definition. The key point of the model is to prepare the test plans and pass criteria at the time of the corresponding design phase.

V-model in the explanations

Questions that mention V-model (1)

  1. In the V-model of software development, which test corresponds to the requirements definition phase and checks that what was decided in that phase is satisfied?

Books on Software Development and Project Management Ad

As an Amazon Associate I earn from qualifying purchases.

Related terms

Agile development Black-box testing Boundary value analysis Branch coverage CI/CD (continuous integration and continuous delivery) Critical path method (CPM) Earned value management (EVM) Equivalence partitioning Scrum SLA (service level agreement)

Back to the glossary