0% found this document useful (0 votes)
165 views3 pages

Guidelines For V & V V1 0

The document provides guidelines for verification and validation of software projects at different lifecycle phases. It lists test factors to consider at each phase and the appropriate verification and validation techniques.

Uploaded by

Ram_p
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
165 views3 pages

Guidelines For V & V V1 0

The document provides guidelines for verification and validation of software projects at different lifecycle phases. It lists test factors to consider at each phase and the appropriate verification and validation techniques.

Uploaded by

Ram_p
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

GUIDLEINE FOR VERIFICATION AND VALIDATION

Test Factor Lifecycle Verification Validation


Phase
• Trace-ability of requirements All Requirement
Tracing
across phases Matrix
• Compliance with regulatory
requirements (if applicable)
• Stake holder’s needs have Requirements Document Prototyping
been captured correctly (e.g. Review.
no omissions, ambiguity). • SRS
• Consistency and clarity in • PRS
elicited requirements.
• HLD: Definition of components Design Design
as per PRS (e.g. consistency Review
in interfaces defined in PRS
and HLD).
• HLD: Suitability of architecture.
e.g. whether to deploy a
layered architecture/pipe and
filter etc.)
• HLD: Design entities correctly
identified.
• LLD: Inputs, Processing,
Outputs of design entities for
each design entity defined (e.g.
consistency in usage of
entities.
• Code as per the LLD (e.g. Coding Code
function calls in conformance Review
to sequence diagrams)
• Effectiveness of measures Unit Testing • Test Black Box
from Risk Analysis Protocol Testing
White Box

QMS-TST-V1.0 Page 1 of 3 Controlled Document

Procedure for Testing Copyright - Do Not Duplicate


Test Factor Lifecycle Verification Validation
Phase
Testing
• Effectiveness of measures Integration Test
from Risk Analysis. Testing Protocol
• Functioning of integrated
components/units
• Suitability of operating System Test Black Box
Protocol
instruction. Testing Testing
• Correctness of installation
guide.
• HLD: Architectural robustness.
• LLD: Inputs, Outputs and
Processing for each design
entity.
• Code Cleanup. Coding Code
• Runtime Exceptions Review
• Mean Time between failures System Black Box
Testing Testing
• Code Comment Density. Coding Code
• Conformance to standards. Review
• Performance Criteria (HLD) Design Design
• Pseudocode, Detailed Review
Flowcharts (LLD).
• Appropriate distribution of
responsibilities to components
and their coupling.
• Appropriate data structures. Coding Code
• Code optimisation. Review
• Memory leaks Unit Testing Black Box
Testing
System Black Box
Testing Testing

QMS-TST-V1.0 Page 2 of 3 Controlled Document

Procedure for Testing Copyright - Do Not Duplicate


Test Factor Lifecycle Verification Validation
Phase
• User Documentation contains System Black Box
description of published Testing Testing
interfaces with clarity.
• Interfaces between
components.

QMS-TST-V1.0 Page 3 of 3 Controlled Document

Procedure for Testing Copyright - Do Not Duplicate

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