More Related Content
What's hot
What's hot (20)
Similar to V-Model (Verification and validation)
Similar to V-Model (Verification and validation) (20)
Recently uploaded
Recently uploaded (20)
V-Model (Verification and validation)
- 1. VERIFICATION ANDVALIDATION MODEL MUHAMMAD AWAIS SALEEM (SP15-BSE-026) COMSATS INSTITUTE OF INFORMATIONTECHNOLOGY (ABBOTTABAD)
- 2. VERIFICATION ANDVALIDATION MODEL Just like waterfall Sequential path Execution Testing parallel with Development
- 4. Requirements analysis Functional Specification (System design) Architecture design (High-Level Design) Detail design(Low-Level Design) VERIFICATION PHASE
- 5. Unit testing Integration testing System testing User acceptance testing VALIDATION PHASE
- 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. Disadvantages of V-model Very rigid and least flexible No early prototypes of the software Changes in test documents Lacks Adaptability Timeline Restrictions
- 9. 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.
- 10. 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
Editor's Notes
- 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. 2 Each phase must be completed before the next phase begins. 3 V-Model is one of the many software development models. 4 Testing of the product is planned in parallel with a corresponding phase of development in V-model.
- Requirements like BRS and SRS begin the life cycle model just like the waterfall model. But, in this model before development is started, a system test plan is created. The test plan focuses on meeting the functionality specified in the requirements gathering. The high-level design (HLD) phase focuses on system architecture and design. It provide overview of solution, platform, system, product and service/process. An integration test plan is created in this phase as well in order to test the pieces of the software systems ability to work together. The low-level design (LLD) phase is where the actual software components are designed. It defines the actual logic for each and every component of the system. Class diagram with all the methods and relation between classes comes under LLD. Component tests are created in this phase as well. CODE: The implementation phase is, again, where all coding takes place. Once coding is complete, the path of execution continues up the right side of the V where the test plans developed earlier are now put to use. This period should allot for as much time as is necessary to convert all previously generated design and specification docs into a coded, functional system. This stage should be fully complete once the testing phases begin.
- Validation phases In the V-model, each stage of verification phase has a corresponding stage in the validation phase. The following are the typical phases of validation in the V-Model, though they may be known by other names. Unit Testing Now the process moves back up the far side of the V-Model with inverse testing, starting with the unit tests developed during the module design phase. Ideally, this phase should eliminate the vast majority of potential bugs and issues, and thus will be the lengthiest testing phase of the project. Integration Testing Testing devised during the architecture design phase are executed here. These tests verify that units created and tested independently can coexist and communicate among themselves. System Testing The tests created during system design are next executed, largely focusing on performance and regression testing. System Test Plans are composed by client's business team. System Test ensures that expectations from application developed are met. The whole application is tested for its functionality, interdependency and communication. System Testing verifies that functional and non-functional requirements have been met. Load and performance testing, stress testing, regression testing, etc., are subsets of system testing. Acceptance Testing . UAT is performed in a user environment that resembles the production environment, using realistic data. UAT verifies that delivered system meets user's requirement and system is ready for deployment.
- saves a lot of time. Hence higher chance of success over the waterfall model. Works well for small projects where requirements are easily understood. Proactive defect tracking – that is defects are found at early stage.
- Software is developed during the implementation phase, so no early prototypes of the software are produced. 3. If any changes happen in midway, then the test documents along with requirement documents has to be updated.
- Military Systems also