V-model in Software Engineering - Step-by-Step Execution

Concept Flow - V-model

Requirements Analysis

↓

System Design

↓

Architecture Design

↓

Module Design

↓

Coding

↓

Unit Testing

↓

Integration Testing

↓

System Testing

↓

Acceptance Testing

↓

Release

The V-model shows software development steps on the left going down, and corresponding testing steps on the right going up, forming a V shape.

Execution Sample

Software Engineering

Step 1: Gather requirements
Step 2: Design system
Step 3: Write code
Step 4: Test units
Step 5: Test integration
Step 6: Test system
Step 7: Acceptance testing

This sequence follows the V-model phases from requirements to coding and then testing in reverse order.

Analysis Table

Step	Phase	Action	Output/Result
1	Requirements Analysis	Gather and document what users need	Clear requirements document
2	System Design	Plan overall system structure	System design specification
3	Architecture Design	Define system components and their interactions	Architecture diagrams
4	Module Design	Design individual modules	Module design documents
5	Coding	Write code for modules	Working code modules
6	Unit Testing	Test individual modules	Verified modules
7	Integration Testing	Test combined modules	Integrated system tested
8	System Testing	Test complete system against requirements	System validated
9	Acceptance Testing	User tests system in real environment	User acceptance
10	Release	Deploy system to users	Software delivered
11	End	All phases complete	Project finished

💡 All development and testing phases completed successfully, project delivered.

State Tracker

Phase	Start	After Step 1	After Step 5	After Step 9	Final
Requirements	None	Defined	Defined	Validated	Validated
Design	None	Started	Completed	Reviewed	Reviewed
Code	None	None	Written	Tested	Tested
Test	None	None	Started	Completed	Completed
Release	None	None	None	Planned	Done

Key Insights - 3 Insights

Why does testing start only after coding in the V-model?

Testing phases correspond to earlier design phases and happen after coding to verify that each development phase was done correctly, as shown in execution_table rows 6-9.

Is the V-model flexible to changes during development?

No, the V-model is rigid and assumes each phase is completed before moving on, which can make late changes difficult, as seen in the strict step order in execution_table.

Why is acceptance testing at the end of the V?

Acceptance testing validates the whole system with real users to ensure requirements are met, matching the initial requirements analysis phase, completing the V shape (rows 1 and 9).

Visual Quiz - 3 Questions

Look at the execution_table, at which step does coding happen?

A Step 5

B Step 3

C Step 6

D Step 7

💡 Hint

Check the 'Phase' column for 'Coding' in the execution_table.

According to variable_tracker, when is the 'Code' variable first marked as 'Written'?

A After Step 1

B After Step 5

C After Step 9

D At Start

💡 Hint

Look at the 'Code' row and see the value under 'After Step 5' in variable_tracker.

If testing started before coding, how would the execution_table change?

A Coding and testing steps would merge

B No change, testing always after coding

C Testing steps would appear before coding step

D Testing steps would be removed

💡 Hint

Refer to the order of steps in execution_table where coding is step 5 and testing starts at step 6.

Concept Snapshot

V-model is a software development process shaped like a V.
Left side: development phases from requirements to coding.
Right side: testing phases corresponding to each development phase.
Testing verifies each earlier phase.
Strict, sequential process.
Ensures quality by linking tests to requirements.

Full Transcript

The V-model is a software development method that organizes phases in a V shape. On the left side, it starts with requirements analysis, then system and module design, followed by coding. On the right side, testing phases mirror the development steps: unit testing tests modules, integration testing tests combined modules, system testing validates the whole system, and acceptance testing confirms the system meets user needs. This model emphasizes verification and validation at each stage. Execution proceeds down the left side for development, then up the right side for testing, ensuring each phase is checked before moving on. The process ends with software release. The V-model is rigid and best for projects with clear, stable requirements.