A detailed look at v model in software testing

A Detailed Look At V-Model in Software Testing Software Testing, Software Testing Jobs, Types Of TestingAutomation Testing, Manual Testing, Software Technology, Software Testing, software testing training institute

A Detailed Look At V-Model in Software Testing V-model in software testing means Verification and Validation model. Much the same as the waterfall model, the V-Shaped life cycle is a consecutive path of execution of procedures. Every stage must be completed before the following stage starts. Testing of the product is arranged in parallel with a parallel stage of development in V-model.

Now, let us look at the basic structure of the V-model based on the various phases involved in it.

1. Requirements Phase: Prerequisites like BRS and SRS are the starting points of the life cycle; be it software development life cycle or the testing life cycle. Simply like the waterfall model. In any case, in this model, before the development phase begins, an application test plan is designed. The test plan aims at meeting the functionality indicated in the prerequisites or requirements document.

2. High Level Design Phase (HLD): The high level design (HLD) stage concentrates on system design and architecture. It gives review of system, product, solution, platform and process/service. A plan for integration test is prepared in this stage too, with a specific end goal to test the bits of the software systems’ capacity to work in tandem.

3. Low Level Design (LLD):

The low-level design (LLD) stage is the place where the software components are designed. It characterizes the actual logic for every single segment of the system.

Class diagram with every one of the methods and connection between classes goes under LLD. Component tests are made in this stage too.

4. Implementation Phase: The implementation stage is, once more, where all coding happens. When coding is finished, the way of execution proceeds up the right half of the V where the test plans created before are currently put to utilize.

5. Coding Phase: The bottom most point in the V-shaped model. The modular level design is transformed into code by the development guys.

Ideal Situation to Use the V-model: High trust of client is required for picking the V-Shaped model methodology. Since, no prototype models are created, there is a high hazard required in meeting client desires. • The V-shaped model ought to be utilized for small scale to medium scale projects where necessities are plainly stated and fixed. • The V-Shaped model ought to be picked when abundant technical resources are accessible with required specialized skill.

Advantages of Using the V-model: 1. Ideal for small scaled projects where understanding the requirements is an easy task.

2. Defects can be detected at an very early stage. Also known as the proactive defect tracking.

3. Refrains the downside flow of the defects in the product or the appliaction.

4. Testing exercises like planning, test outlining happens well before coding. This spares a great deal of time. Thus higher possibility of accomplishment over the waterfall model.

5. Very easy to use and easily understandable.

Disadvantages of Using the V-model: 1. In the event that any progressions or changes happen in halfway, then the test documents alongside requirement specifications, must be edited and changed.

2. Software is created amid the implementation stage, so no early prototype models of the product are delivered.

3. Happens to be very rigid and lacking flexibility.

This is a widely used model in the software testing industry. In this model, the testing and the development phases progress in a parallel manner. Testing starts from a very early stage. Bugs can therefore be found at a very early stage and can be fixed there and then. Here, it is not the case that first the development phase is completed and then testing is started. A lot of time is thus saved in the Vmodel. The waterfall model progresses in a sequential manner.

This article would be helpful for student Software Testing reviews.

More Related Video:

1. Software Testing- Quality Control And Quality Assurance 2. Purpose And Objectives Of Software Testing