[Day 211] Verification(확인), Validation(검증)

Verification(확인)

• Are we building the product right? (우리가 제품을 제대로 만들고 있는가?)
• SW가 버그없이 설계대로 구현되었는지 확인하는 프로세스
• SW가 규격을 준수하는지 확인
• 정적 테스트(reviews, walkthroughs, inspections and desk-checking)

Validation(검증)

•  Are we building the right product? (우리가 올바른 제품을 만들고 있는가?
• 실사용자의 요구사항을 검토하여 제품의 유효성을 확인하는 프로세스
• SW가 고객의 요구사항과 기대를 충족하는지 여부를 확인
• 동적 테스트(Black Box Testing, White Box Testing and non-functional testing)

 

Verification	Validation
It includes checking documents, design, codes and programs.	It includes testing and validating the actual product.
Verification is the static testing.	Validation is the dynamic testing.
It does not include the execution of the code.	It includes the execution of the code.
Methods used in verification are reviews, walkthroughs, inspections and desk-checking.	Methods used in validation are Black Box Testing, White Box Testing and non-functional testing.
It checks whether the software conforms to specifications or not.	It checks whether the software meets the requirements and expectations of a customer or not.
The goal of verification is application and software architecture and specification.	The goal of validation is an actual product.
Quality assurance team does verification.	Validation is executed on software code with the help of testing team.
It comes before validation.	It comes after verification.
It consists of checking of documents/files and is performed by human.	It consists of execution of program and is performed by computer.

 

*  출처 : Differences between Verification and Validation - GeeksforGeeks

Differences between Verification and Validation - GeeksforGeeks