Skip to main content

What is V-Model?

 V Model

V Model is a very disciplined SDLC model with a testing phase simultaneous to every development phase. V model is an extension of the waterfall model where software development and testing is carried out in a sequential manner. It is referred to as the Validation or Verification Model.

Key Software Engineering Terms



SDLC: SDLC stands for Software Development Life Cycle. It is the activity cycle executed by Developers to develop high-quality software.

STLC: STLC stands for Software Testing Life Cycle. It is a set of activities executed by Testers systematically to test your software product.


Waterfall Model: Waterfall model is a sequential model segmented into various phases of the activity of software development. Every step is meant for carrying out the corresponding activity. Testing phase of waterfall model begins only after completion of implementation of the system.


Example To Understand the V Model



Let's say, you have been given an assignment, to create a customized software for a customer. Now, regardless of your technical history, attempt to make an informed guess of the order of steps you would take, to accomplish the task.

Phases of Software Development Activities done in each phase



Requirement Gathering stage 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.

Design Stage 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.

Build Stage\tFollowing the design stage, it is build stage, i.e., nothing but actually code the software

Test Stage\tThen you test the software to check if it is developed according to the specifications are provided by the client.

Deployment stage\tDeploy the application in the respective environment

Maintenance stage\tAfter your system is deployed to use, you may need to alter the code later on as per customer request


photo

Khushboo Mishra
Manual Tester | QA Enthusiast

www.linkedin.com/in/khushboo-mishra-663584216/

khushboom099@gmail.com


 

Comments

Post a Comment

Popular posts from this blog

No, AI Won't Steal Your Job: Why Manual Testing is More Critical Than Ever

"Manual Testing Isn't Dead. It's Your Secret Weapon for Quality." If you spend any time on tech forums or LinkedIn, you’ve heard the prophecy: “Automation and AI are coming to replace manual testers.” The story goes that in the near future, smart algorithms will handle everything, making human testers obsolete. I’m a Software QA Engineer who has been in the trenches with everything from complex fintech platforms to social media and gaming apps. And I’m here to tell you that this prediction is fundamentally wrong. Manual testing isn't dead. It's evolving. And in an age dominated by automation, its role has become more specialized and more critical than ever. Automation can check for expected outcomes, but it can't replicate the one thing that truly defines quality: the human experience. The Automation Fallacy: What a Script Can't See Test automation is a game-changer, and I rely on it every day. It's brilliant for running repetitive regression suite...
Post a Comment
Read more

🌟 The Future of QA in 2025: Why Testers Are the Superheroes of Tech

  🚀 Introduction Developers get the spotlight. AI steals the headlines. But here’s the truth no one tells you: without testers, everything breaks . Think about it. Banking apps that lose your money. Healthcare systems that give wrong reports. Flight booking portals that crash mid-payment. One missed bug can cost millions — and sometimes even lives. That’s why 2025 is not the end of QA . It’s the beginning of a new era where testers become the superheroes of software development . 🦸 Testers: The Last Line of Defense In every software team, roles are clear: Developers build features. Testers protect users. And in today’s world, protection = trust . Companies spend billions building features, but a single bug can: Destroy customer trust. Damage brand reputation. Trigger lawsuits and losses. Testers are not bug hunters. Testers are business protectors . That’s why testers are more critical than ever. 🤖 AI Won’t Replace Testers — It Will ...
Post a Comment
Read more

Top 10 Manual Test Cases for Login Page (With Examples)

 The login page is the gateway to any application. As a QA tester, validating this feature is critical. In this post, we’ll cover 10 essential manual test cases you must write for login functionality, along with examples. Test Cases: Test Case ID Test Scenario Expected Result TC01 Enter valid username and password User logs in successfully TC02 Leave both fields blank and click login Show “Fields cannot be empty” TC03 Enter wrong username and correct password Show “Invalid credentials” TC04 Enter correct username and wrong password Show “Invalid credentials” TC05 Check password masking Password should be hidden with dots TC06 Check "Remember Me" functionality User stays logged in after refresh TC07 Click on "Forgot Password" Redirects to password recovery page TC08 Enter SQL injection script Input should be sanitized TC09 Enter special characters in username Show input validation TC10 Test login with expired credentials Show “Account expired” Bonus Tips: Al...
Post a Comment
Read more