{"id":12033,"date":"2022-12-26T17:47:52","date_gmt":"2022-12-26T10:47:52","guid":{"rendered":"https:\/\/bestarion.com\/us\/?p=12033"},"modified":"2024-10-06T03:21:35","modified_gmt":"2024-10-05T20:21:35","slug":"what-is-v-model-in-software-testing","status":"publish","type":"post","link":"https:\/\/bestarion.com\/us\/what-is-v-model-in-software-testing\/","title":{"rendered":"What is V-Model in Software Testing?"},"content":{"rendered":"

The V-Model is a highly disciplined SDLC model that includes a testing phase alongside each development phase. The V-model is an extension of the waterfall model that involves sequential software development and testing. It’s referred to as the Validation or Verification Model.<\/span><\/p>\n

<\/span>Important Software Engineering Terms<\/span><\/span><\/h2>\n

SDLC:<\/b> SDLC is <\/span>Software Development Life Cycle<\/span><\/a>. It is the series of activities performed by Developers to design and develop high-quality software.<\/span><\/p>\n

STLC:<\/b> STLC is <\/span>Software Testing Life Cycle<\/span><\/a>. It consists of a series of activities carried out methodically by Testers to test your software product.<\/span><\/p>\n

Waterfall Model: <\/b>A waterfall model is a sequential model that divides software development activity into different phases. Each stage is intended to be used for a specific activity. The testing phase in the waterfall model begins only after the system has been implemented.<\/span><\/p>\n

<\/span>Example To Understand the V-Model\u00a0<\/span><\/span><\/h2>\n

Suppose, you are assigned a task, to develop a custom software for a client. Now, irrespective of your technical background, try and make an educated guess about the sequence of steps you will follow, to achieve the task.<\/span><\/p>\n

The correct sequence would be.<\/span><\/p>\n\n\n\n\n\n\n\n\n\n
Phases of Software Development<\/b><\/td>\nActivities performed in each stage<\/b><\/td>\n<\/tr>\n
Requirement Gathering stage<\/b><\/td>\n\n
    \n
  • Gather as much information as possible about the details & specifications of the desired software from the client. This is nothing but the Requirements gathering stage.<\/span><\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Design Stage<\/b><\/td>\n\n
    \n
  • Plan the programming language like Java, PHP, .net; database like Oracle, MySQL, etc. Which would be suited for the project, also some high-level functions & architecture.<\/span><\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Build Stage<\/b><\/td>\n\n
    \n
  • After the design stage, it is build stage, that is nothing but actually code the software<\/span><\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Test Stage<\/b><\/td>\n\n
    \n
  • Next, you test the software to verify that it is built as per the specifications are given by the client.<\/span><\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Deployment stage<\/b><\/td>\n\n
    \n
  • Deploy the application in the respective environment<\/span><\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Maintenance stage<\/b><\/td>\n\n
    \n
  • Once your system is ready to use, you may require to change the code later on as per customer request<\/span><\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    All these levels constitute the <\/span>waterfall method<\/b> of the software development lifecycle.<\/span><\/p>\n

    <\/span>Problem with the Waterfall Model<\/b><\/span><\/h2>\n

    As you may observe, that <\/span>testing in the model starts only after implementation is done.<\/b><\/p>\n

    But if you are working in the large project, where the systems are complex, it\u2019s easy to miss out the key details in the requirements phase itself. In such cases, an entirely wrong product will be delivered to the client and you might have to start afresh with the project OR if you manage to note the requirements correctly but make serious mistakes in design and architecture of your software you will have to redesign the entire software to correct the error.<\/span><\/p>\n

    Assessments of thousands of projects have shown that <\/span>defects introduced during requirements & design make up close to half of the total number of defects.<\/b><\/p>\n

    \"\"<\/p>\n

    Also, the <\/span>costs of fixing a defect increase across the development lifecycle. The earlier in life cycle a defect is detected, the cheaper it is to fix it.<\/b> As they say, \u201cA stitch in time saves nine.\u201d<\/span><\/p>\n

    <\/span>Solution: The V-Model<\/b><\/span><\/h2>\n

    \"v-model<\/p>\n

    To address this concern, <\/span>the V-model of testing<\/b> was developed where <\/span>for every phase, in the Development life cycle there is a corresponding Testing phase<\/b><\/p>\n

      \n
    • The left side of the model is Software Development Life Cycle \u2013 <\/span>SDLC<\/b><\/li>\n
    • The right side of the model is Software Test Life Cycle \u2013 <\/span>STLC<\/b><\/li>\n
    • The entire figure looks like a V, hence the name <\/span>V-model<\/b><\/li>\n<\/ul>\n

      Apart from the V-model, there are iterative development models, where development is carried in phases, with each phase adding a functionality to the software. Each phase comprises its independent set of development and testing activities.<\/span><\/p>\n

      Good examples of Development lifecycles following iterative method are Rapid Application Development, Agile Development<\/span><\/p>\n

      <\/span>Conclusion<\/b><\/span><\/h2>\n

      There are numerous development life cycle models. <\/span>Development model selected for a project depends on the aims and goals of that project.<\/b><\/p>\n

        \n
      • Testing is not a stand-alone activity, and it has to adapt the development model chosen for the project.<\/span><\/li>\n
      • In any model, testing should be performed at all levels i.e. right from requirements until maintenance.<\/span><\/li>\n<\/ul>\n