V-Model (Verification and validation)

ch_AwaisSaleem 1,690 views 10 slides Nov 25, 2017
Slide 1
Slide 1 of 10
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10

About This Presentation

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 planne...


Slide Content

VERIFICATION AND VALIDATION MODEL MUHAMMAD AWAIS SALEEM (SP15-BSE-026) COMSATS INSTITUTE OF INFORMATION TECHNOLOGY (ABBOTTABAD)

VERIFICATION AND VALIDATION MODEL Just like waterfall Sequential path Execution Testing parallel with Development

Source: https://tech-talk.org/2015/01/21/system-development-life-cycle-sdlc-approaches/v_shaped_sdlc_model/

Requirements analysis Functional Specification (System design) Architecture design (High-Level Design) Detail design(Low-Level Design) VERIFICATION PHASE

Unit testing Integration testing System testing User acceptance testing VALIDATION PHASE

Advantages of V-model Simple and easy to use Testing activities  happens well before coding S aves Time Proactive defect Avoids the downward flow of the defects Works well for small projects

Disadvantages of V-model Very rigid and least flexible N o early prototypes of the software C hanges in test documents Lacks Adaptability Timeline Restrictions

Project Based on V-Model Suited for Restricted Projects: Due to the stringent nature of the V-Model and its linear design, implementation, and testing phases, it’s perhaps no wonder that the V-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, the V-Model can be a great method.

V- Model ─ Application Requirements are well defined, clearly documented and fixed Technology is not dynamic and is well understood by the project team N o 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