The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing. The V-model illustrates how testing activities can be integrated into each phase of the software development life cycle.
V-Model recommends that unit and integration testing can also be used to verify the program design. That is all through unit and integration testing, the coders and test team members should ensure that all aspects of the program design have been implemented correctly in the code. Similarly System testing should verify the system design, making sure that all system design aspects are appropriately implemented. Acceptance testing which is conducted by the customer rather than the tester validates the requirements, by associating a testing step with each element of specification; this type of testing checks to see that all requirements have been fully implemented before the system is accepted or paid for. The focus of V-model is activity and correctness.
Image Source: Wikipedia
More on V-Model:
V-Model, V-Model concept, V-Model advantages and disadvantages, Structure of V-Model etc.
V-Model
Another good example of V-Model Testing
V-Model
The V-model of project execution Specification phases & QA
V-Model
The below presented Lifetime Testability V-model (LTV-model) is a procedure for managing the testability requirements and test processes of a product.
V-Model
V-Model as in Foundations of Software Testing: ISTQB Certification
By Dorothy Graham, Erik Van Veenendaal, Isabel Evans, Rex Black
V-Model