Scribd
Upload
0 views

Verification and validation

The document outlines the processes of verification and validation in the Software Development Life Cycle (SDLC). Verification ensures the correctness and completeness of documents before software development through techniques like peer review, walkthroughs, and inspections, while validation evaluates the actual software product post-development to ensure it meets business requirements and user needs. Various testing techniques such as unit, integration, functional, performance, and security testing are employed during validation to confirm the software's functionality and reliability.

Uploaded by

vikasadari25
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 views

Verification and validation

The document outlines the processes of verification and validation in the Software Development Life Cycle (SDLC). Verification ensures the correctness and completeness of documents before software development through techniques like peer review, walkthroughs, and inspections, while validation evaluates the actual software product post-development to ensure it meets business requirements and user needs. Various testing techniques such as unit, integration, functional, performance, and security testing are employed during validation to confirm the software's functionality and reliability.

Uploaded by

vikasadari25
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Verification and validation

Title: Verification in SDLC


Verification is the process of evaluating documents, plans, and specifications to ensure they are

correct and complete before the actual software is developed. It is also known as Static Testing

because it involves reviewing documentation without executing the code.

Purpose:

To check the correctness and completeness of the documents used for software development.

Documents Involved:
- BRS (Business Requirement Specification)

- FRS (Functional Requirement Specification)

- Design Documents (HLD - High-Level Design, LLD - Low-Level Design)

Verification techniques are methods used to evaluate the correctness, completeness, and
quality of software documents without executing the actual code. These techniques help in
identifying errors early in the Software Development Life Cycle (SDLC), saving time and cost. The
main verification techniques are:

1. Peer Review

• Definition: A process where a colleague (peer) reviews your work (document or code) to
identify mistakes.

• Purpose: To catch obvious errors, improve document quality, and share knowledge.

• Example: A team member reviews a test case or requirement document before it is finalized.

2. Walkthrough

• Definition: The author of the document explains it step-by-step to a group (developers,


testers, etc.) to gather feedback.

• Purpose: To ensure that everyone understands the content and to find errors through
discussion.

• Characteristics:

o Conducted in an informal or semi-formal way.

o Useful for knowledge sharing and validation of logic.

• Example: A developer walks the team through a high-level design document.

3. Inspection

• Definition: A formal and structured review process with specific roles (moderator, reader,
recorder, author).

• Purpose: To detect and document defects in the document through a systematic approach.

• Steps Involved:

1. Planning

2. Overview Meeting

3. Preparation
4. Inspection Meeting

5. Rework and Follow-up

• Example: Inspecting the test plan document with a checklist to identify missing or unclear
requirements.

Summary Table

Technique Formally Structured? Involves Author? Main Benefit

Peer Review No Sometimes Quick feedback from a colleague

Walkthrough Semi-formal Yes Understanding & brainstorming

Inspection Yes Yes Thorough defect detection

Title: Validation in SDLC


Definition:

Validation is the process of evaluating the actual software product after coding is complete, by
executing the application, to determine whether it meets the business requirements and produces
the expected output.

It ensures that "we built the right product."

Nature:

• Dynamic Testing technique

• Requires actual execution of code

• Helps detect bugs in the working software

Purpose:

• To check if the software system behaves as expected in real-world scenarios

• To ensure it fulfills user needs and business goals

Validation Testing Techniques:

1. Unit Testing

• Tests individual components or functions


• Performed by developers

• Ensures each part works in isolation

2. Integration Testing

• Tests how modules or units interact

• Detects interface and communication issues

• Ensures modules work together properly

3. Functional Testing

• Verifies the application works according to the functional requirements

• Focuses on inputs, expected outputs, and user flows

• Typically done by QA testers

4. Performance Testing

• Checks how the system performs under load or stress

• Validates speed, scalability, and stability

• Tools: JMeter, LoadRunner, etc.

5. Security Testing

• Ensures the application is protected against vulnerabilities

• Verifies access control, data encryption, and protection against threats like SQL injection or
XSS

Summary:

Technique Purpose Performed By

Unit Testing Test individual modules/components Developers

Integration Testing Test interaction between components Developers/Testers

Functional Testing Validate against business requirements QA Testers

Performance Testing Measure response time and load behavior Performance Engineers

Security Testing Identify security weaknesses Security Experts

Conclusion:

Validation is critical to confirm that the final product is usable, meets expectations, and is ready for
release. It is typically performed after verification is complete.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy