Siksha Sarovar

Siksha Sarovar (sikshasarovar.com) is a free educational web application that helps students in India learn programming and prepare for academic and competitive exams. The platform offers structured coding courses (C, C++, Python, Java, HTML, CSS, PHP, Power BI, AI, Machine Learning, Data Science), complete university curriculum notes for BCA/MCA students with previous year question papers, Class 10 and Class 12 CBSE/HBSE school notes, and dedicated preparation material for SSC, UPSC, Banking, Railway and other government exams. Browsing the site is completely free and requires no account. Users may optionally sign in with Google solely to save their learning progress, quiz scores and personal preferences across devices.

Privacy Policy | Terms of Service | Contact Siksha Sarovar | About Siksha Sarovar

v4.0.9 · PWA
Siksha Sarovar logo
Siksha Sarovar
Your Learning Universe

Siksha Sarovar is a free e-learning platform for coding courses, BCA university notes and competitive exam preparation. Optional Google sign-in saves your learning progress across devices.

Initializing knowledge base…
Compiling modules 0%

Unit 1.3: V-Model & V&V

Lesson 4 of 16 in the free Software Testing notes on Siksha Sarovar, written by Rohit Jangra.

Unit 1.3: Verification vs. Validation

These two terms are often confused but have distinct meanings.

1. Comparison Table

FeatureVerificationValidation
Question"Are we building the product right?""Are we building the right product?"
ObjectiveTo check if the software matches the specification.To check if the software meets the user's needs.
ProcessStatic Testing (Review, Walkthrough, Inspection).Dynamic Testing (Executing code).
When?Done during development.Done after development (or modules).
Performed ByQA Team, Developers.Testing Team, Users (UAT).
GoalFind bugs in specs, logic, and code structure.Find bugs in functionality and behavior.

---

2. The V-Model (V-Testing Life Cycle)

The V-Model is an extension of the Waterfall model. It emphasizes that for every development phase, there is a corresponding testing phase. Execution happens in a V-shape.

Left Side (Verification / Development):

  1. Requirement Analysis: Gathering needs. → Planned Test: Acceptance Testing.
  2. System Design: High-level architecture. → Planned Test: System Testing.
  3. Architecture Design: High-level design. → Planned Test: Integration Testing.
  4. Module Design: Low-level Code design. → Planned Test: Unit Testing.

Right Side (Validation / Testing):

  1. Unit Testing: Testing individual components (Code level).
  2. Integration Testing: Testing interaction between verified units.
  3. System Testing: Testing the complete system against functional requirements.
  4. Acceptance Testing: Validation by the client (UAT).

---

3. Software Testing Life Cycle (STLC)

STLC defines the phases of testing:

  1. Requirement Analysis: Understand what to test.
  2. Test Planning: Resource planning, estimating time/cost, tool selection.
  3. Test Case Development: Writing test cases and scripts.
  4. Test Environment Setup: Preparing hardware/software/network.
  5. Test Execution: Running the tests and logging defects.
  6. Test Cycle Closure: Reporting results and learning lessons.