Verification and Validation in Software Engineering.docx

Verification and Validation in Software Engineering

1. Verification and Validation (V&V) in
Software Engineering
1. Introduction to Verification & Validation
Verification and Validation (V&V) are two critical processes in software engineering that ensure
software meets requirements and works correctly before deployment.
Verification → "Are we building the product right?"
Validation → "Are we building the right product?"
2. Differences Between Verification & Validation
Aspect Verification Validation
Definition
Ensures software is built correctly
according to specifications.
Ensures the software meets user needs.
Focus
Internal consistency (requirements,
design, coding).
External correctness (actual user
requirements).
Methods
Used
Reviews, inspections, walkthroughs,
static testing.
Functional testing, user acceptance testing
(UAT), dynamic testing.
When
Done?
During development (before execution).After development (with real execution).
Outcome Ensures correctness of implementation.
Ensures customer satisfaction and
usability.
3. Verification Process

2. Verification is a static process that involves reviewing artifacts without executing the software.
Key Verification Activities
1.Requirement Verification
oEnsures all functional and non-functional requirements are clearly defined and
consistent.
2.Design Verification
oChecks architectural and detailed design documents for correctness and
completeness.
3.Code Verification
oStatic code analysis, peer reviews, and walkthroughs.
4.Test Plan Verification
oEnsures test cases are correctly written to cover all software requirements.
Techniques for Verification
Technique Description
Reviews Manual examination of software documents by experts.
Walkthroughs Step-by-step peer discussion to identify issues.
Inspections Formal review process to detect defects.
Static Code AnalysisAutomated tools (e.g., SonarQube, PMD) analyze the source code.
4. Validation Process
Validation is a dynamic process that involves actual execution of the software to verify that it
meets user requirements.
Key Validation Activities
1.Unit Testing
oTests individual functions and modules for correctness.

3. 2.Integration Testing
oEnsures different software modules work together.
3.System Testing
oChecks if the entire system meets specified requirements.
4.User Acceptance Testing (UAT)
oEnd-users test the software in a real-world scenario.
5.Performance & Security Testing
oEnsures software can handle required loads and security threats.
Techniques for Validation
Technique Description
Black-box TestingTesting based on expected inputs and outputs, without looking at the code.
White-box TestingTesting internal logic and structure of the code.
Regression TestingEnsures that changes don’t break existing functionality.
Beta Testing Releasing the software to a limited user base for feedback.