Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

V-Model (Verification and validation)


Published on

V- model means Verification and Validation model. Just like the waterfall model, the V-Shaped life cycle is a sequential path of execution of processes. Each phase must be completed before the next phase begins. V-Model is one of the many software development models. Testing of the product is planned in parallel with a corresponding phase of development in V-model.

Published in: Software
  • Be the first to comment

  • Be the first to like this

V-Model (Verification and validation)

  2. 2. VERIFICATION ANDVALIDATION MODEL Just like waterfall Sequential path Execution Testing parallel with Development
  3. 3. Source: approaches/v_shaped_sdlc_model/
  4. 4. Requirements analysis Functional Specification (System design) Architecture design (High-Level Design) Detail design(Low-Level Design) VERIFICATION PHASE
  5. 5.  Unit testing  Integration testing  System testing  User acceptance testing VALIDATION PHASE
  6. 6. Advantages ofV-model Simple and easy to use Testing activities happens well before coding  Saves Time Proactive defect Avoids the downward flow of the defects Works well for small projects
  7. 7. Disadvantages of V-model Very rigid and least flexible No early prototypes of the software  Changes in test documents Lacks Adaptability Timeline Restrictions
  8. 8. Project Based on V-Model Suited for Restricted Projects: Due to the stringent nature of theV-Model and its linear design, implementation, and testing phases, it’s perhaps no wonder that theV-Model has been heavily adopted by the medical device industry in recent years. In situations where the project length and scope are well-defined, the technology is stable, and the documentation & design specifications are clear, theV-Model can be a great method.
  9. 9. V- Model ─ Application Requirements are well defined, clearly documented and fixed Technology is not dynamic and is well understood by the project team No ambiguous or undefined requirements used for small to medium sized projects where requirements are clearly defined and fixed chosen when ample technical resources are available with needed technical expertise