Subject: FAQ: Difference between Verification and Validation? - msg#00079

List: programming.software-qa

Date: Prev Next Index Thread: Prev Next Index

Q: Difference between Verification and Validation?

A: The ISO would say that Verification is a process of determining
whether or not the products of a given phase of the software
development cycle meets the implementation steps and can be traced to
the incoming objectives established during the previous phase. The
techniques for verification are testing, inspection and reviewing.

Validation is a process of evaluating software at the end of the
software development process to ensure compliance with software
requirements. The techniques for validation are testing, inspection
and reviewing.

According to the CSTE CBOK, Verification is done to ensure that the
system complies with the organization's policies, standards and
processes relying on the non- executable methods. Validation
physically ensures that the system operates according to the plan by
executing the system through a series of tests that can be observed
and evaluated.

NASA's SOFTWARE QUALITY ASSURANCE AUDITS GUIDEBOOK
http://satc.gsfc.nasa.gov/assure/agb.txt also explains this well.

Verification answers did we build the right system.
Validation answers did we build the system right.

This is backed up in Effective Methods for Software Testing
Verification answers the question "Do we build the right system?";
Validation answers the question "Do we build the system right?"

In other words, Verification is static testing or document review;
Validation is active testing or black box or functional testing,
testing of the system under test.

------------------------ Yahoo! Groups Sponsor --------------------~-->
$4.98 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/Q7_YsB/neXJAA/yQLSAA/03wwlB/TM
--------------------------------------------------------------------~->

Was this page helpful?

Thread at a glance:

Previous Message by Date: click to view message preview

INfo training QA

Dear all, I need an information training QA in south-east asia. Perhaps it would be gratefull if celebrate in indonesia or singapore. I'm hardly enough to find it in Jakarta Indonesia. Rgds, Tia ------------------------ Yahoo! Groups Sponsor --------------------~--> $4.98 domain names from Yahoo!. Register anything. http://us.click.yahoo.com/Q7_YsB/neXJAA/yQLSAA/03wwlB/TM --------------------------------------------------------------------~->

Next Message by Date: click to view message preview

A Query regarding the Defect Prevention procedure

Dear All, I have a query regarding defect prevention process. It would be great if you could spare some time and share your view point. There is a confusion on whether to prioritize (using Pareto chart) based on Defect Type or Defect Cause. One view is that we do the initial prioritization based on Defect Type. And we do the root cause analysis for the 20% of defect types causing 80% of the defects. Incase the volume of defects is high we might even skip assignining 'defect cause' to each and every defect and instead do the broad level causal analysis for the top priority defect types. The other view is that assigning 'Defect Cause' is essential for each and every defect identified, even though the volume of defects could be high. The prioritization (using Pareto) and action plan (using cause-effect diagram) for Defect Prevention is made on the basis of Defect Cause (and not on Defect Type). Activity 3 of Defect Prevention KPA, also seem to support the second view. Please refer to the extract (Activity 3) from the TR25 attached below with the mail Please let me know if there is any different opinion because there is a lot of confusion on this topic, with various procedures followed in different projects. Thanks and Regards, Aravind Activity 3 Causal analysis meetings are conducted according to a documented procedure. This procedure typically specifies that: 1. Each team that performs a software task conducts causal analysis meetings. q A causal analysis meeting is conducted shortly after the task is completed. q Meetings are conducted during the software task if and when the number of defects uncovered warrants the additional meetings. q Periodic causal analysis meetings are conducted after software products are released to the customer, as appropriate. q For software tasks of long duration, periodic in-process defect prevention meetings are conducted, as appropriate. An example of a long duration task is a level-of-effort, customer support task. 2. The meetings are led by a person trained in conducting causal analysis meetings. 3. Defects are identified and analyzed to determine their root causes. An example of a method to determine root causes is cause/effect diagrams. 4. The defects are assigned to categories of root causes.__________________________________________________Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com Yahoo! Groups Sponsor ADVERTISEMENT Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/Software_QA/ To unsubscribe from this group, send an email to:Software_QA-unsubscribe-hHKSG33TihhbjbujkaE4pw@xxxxxxxxxxxxxxxx Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Previous Message by Thread: click to view message preview

Next Message by Thread: click to view message preview

Re: FAQ: Difference between Verification and Validation?

So Can we safely say that Validation ensures that the software complies with Verified documents ??walter_gorlitz <wgorlitz-EynCeXvFgoheoWH0uzbU5w@xxxxxxxxxxxxxxxx> wrote: Q: Difference between Verification and Validation?__________________________________________________Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com Yahoo! Groups Sponsor ADVERTISEMENT Yahoo! Groups Links To visit your group on the web, go to:http://groups.yahoo.com/group/Software_QA/ To unsubscribe from this group, send an email to:Software_QA-unsubscribe-hHKSG33TihhbjbujkaE4pw@xxxxxxxxxxxxxxxx Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Loading Comments...