Skip to main content

Verification and Validation (V&V)- a software testing approach

Verification:

It focuses on PROCESS related activities to ensure that the Products and deliverables meet a specific requirement before the final testing.

Can be done through:

A. Technical review

B. Business review

C. Management review

Simply: Are we building the product in the right way? that is, does the software conform to its specification

verification is the process of checking that the software meets the specification.

 Verification is an example of QA

Validation:

It focuses on PRODUCT related activities, that attempt to determine if the system or project deliverables meet the customer or client's expectations.

Will be done by: Testing.

Simply: Did we build the right product? that is, is the software doing what the user really requires.

Validation is the process of checking whether the specification captures the customer's needs.

 According to the Capability Maturity Model(CMMI-SW v1.1) we can also define validation as The process of evaluating software during or at the end of the development process to determine whether it satisfies specified requirements. [IEEE-STD-610].

Comments

Post a Comment

Popular posts from this blog

Smoke Testing vs Sanity Testing

Differences between Smoke Testing and Sanity Testing are as follows: Topic Smoke Testing Sanity Testing Purpose To verify the BASIC or CRITICAL existing functionality of an Application- before starting rigorous testing. To verify NEWLY ADDED/UPDATED functionality or BUG FIXES. Who does these testing? Performed by both TESTERS and DEVELOPERS Performed only by TESTERS Can these tests be automated? Can be automated Can’t be automated In technical terms Exercises the ENTIRE system from END-TO-END Exercises only a particular COMPONENT of the entire system In general terms SHALLOW and WIDE range of testing. More like a GENERAL HEALTH CHECKUP Narrow and DEEP approach of testing. More like a SPECIALIZED HEALTH CHECKUP
Post a Comment
Read more

Quality Assurance vs. Quality Control

            Quality Assurance             Quality Control Definition:    QA is a set of activities for ensuring quality in the processes by which products are developed. QC is a set of activities for ensuring quality in products. The activities focus on identifying defects in the actual products produced. Focus on:    QA aims to prevent defects with a focus on the process used to make the product. It is a proactive quality process. QC aims to identify (and correct) defects in the finished product. Quality control, therefore, is a reactive process. Goal:   The goal of QA is to improve development and test processes so that defects do not arise when the product is being developed. The goal of QC is to identify defects after a product is developed and before it's released. How:   Establish a good quality management system and the assessment of its adequacy. Periodic conforman...
Post a Comment
Read more

Branches of Testing- to be continued.

Unit testing: Focuses on the module, program or object level to determine whether specific functions work properly. Black box testing: Tests the program against specific requirements or functionalities. White box testing: Examines paths of logic or the structure inside a program Gray box testing:  Gray-box testing  (International English spelling:  grey-box testing ) is a combination of  white-box testing  and  black-box testing . The aim of this testing is to search for the defects if any due to improper structure or improper usage of applications http://www.careerride.com/Testing-white-box-black-box-gray-box.aspx https://en.wikipedia.org/wiki/Gray_box_testing Integration testing: Tests whether a set of logically related units (functions, modules, programs etc.) WORK TOGETHER PROPERLY after unit testing is done. System testing: Tests the system as a whole in an OPERATING ENVIRONMENT verifying FUNCTIONALITY and FITNESS for use. Ma...
Post a Comment
Read more