Talk:Verification and validation
|WikiProject Systems||(Rated Start-class, Mid-importance)|
- 1 Separate page
- 2 Why have some of the content been moped up from this version ???
- 3 See Also Section
- 4 Merge of V&V Section from Formal verification#Validation and Verification
- 5 Please verify the link of...
- 6 Verification is failed for....
- 7 Can someone verify if....
- 8 Verification and validation V & V (from Software Quality perspective)
- 9 IEEE definitions of Verification and Validation
- 10 Different approaches for the same goals in different contexts
- 11 The version comparisons of this topic......
- 12 Welll, I let my cloned writers to add the following info....
- 13 The following info is about the writer who maybe a vandalist.....
- 14 Also...the following trails is not normal either......and....
- 15 can someone correct a typo I tried am to busy and give up
- 16 QC vs QA
- 17 Request to completely revise this page
Why have some of the content been moped up from this version ???
If one does not agree with the writing, edit it please with your reasons provided
See Also Section
Please remove Atsec information security, this is a description of a company. It does not contribute any informative value to the subject that is being discussed. —Preceding unsigned comment added by 220.127.116.11 (talk) 15:18, 30 June 2008 (UTC)
Merge of V&V Section from Formal verification#Validation and Verification
and the article of
http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6TG9-3VVMNBN-11&_user=10&_rdoc=1&_fmt=&_orig=search&_sort=d&_docanchor=&view=c&_acct=C000050221&_version=1&_urlVersion=0&_userid=10&md5=4f97b06a577bb7fc16f8b6602d5db3ff --18.104.22.168 (talk) 00:21, 12 July 2009 (UTC)
Verification is failed for....
the logo in the letter http://www.fda.gov/downloads/Drugs/GuidanceComplianceRegulatoryInformation/EnforcementActivitiesbyFDA/WarningLettersandNoticeofViolationLetterstoPharmaceuticalCompanies/ucm085293.pdf
However, I'm confused that why government logos do not coexist with their department logos at the offical department home page.
Can someone verify if....
Can it be found at EU government site?
an academic review of this is not available though http://scholar.google.com/scholar?hl=en&q=allintitle%3A+2.2.44+European+Pharmacopoeia&btnG=Search --22.214.171.124 (talk) 05:03, 12 July 2009 (UTC)
additional info http://www.globalspec.com/reference/7531/Pharmaceutical-System-Suitability-Testing-Simplifying-a-Critical-Element-in-the-TOC-Monitoring-Process --126.96.36.199 (talk) 05:05, 12 July 2009 (UTC)
Verification and validation V & V (from Software Quality perspective)
== Verification versus Validation ==
Verification Vs Validation
Verification ensures that the system (software, hardware, documentation, and personnel) complies with an organization’s standards and processes, relying on review or non-executable methods.
Validation physically ensures that the system operates according to plan by executing the system functions through a series of tests that can be observed and evaluated.
Verification answers the question, “Did we build the right system?” while validations addresses, “Did we build the system right?”
Keep in mind that verification and validation techniques can be applied to every element of the computerized system. You’ll find these techniques in publications dealing with the design and implementation of user manuals and training courses, as well as in industry publications.
I find it strange that I see verification being done before validation. Who cares if the function is verified (done right), until you have validated the function to be required (done the right thing)? —Preceding unsigned comment added by 188.8.131.52 (talk) 18:47, 29 December 2010 (UTC)
- Because validation is an actual test of real-world function, not an analysis of the spec before starting. Implementation is usually done hand in hand with verification, which is why the verification usually comes first (despite seeming kinda backwards). In many (most?) informal developments, validation probably does come before verification (give it to the customer - it breaks - do some tests to figure out why). Adx (talk) 14:38, 6 December 2011 (UTC)
IEEE definitions of Verification and Validation
Contrary to the above definitions of "Validation vs. Verification", IEEE defines them as such:
Validation : "Confirmation by examination and provisions of objective evidence that the particular requirements for a specific intended use are fulfilled." i.e. is it the right design? does the product meet the needs of the customer?
Verification : "Confirmation by examination and provisions of objective evidence that specified requirements have been fulfilled." i.e. is the design right? does it work as specifed?
Thus, It is clear that you can perfectly verify what turns out to be an invalid design... it is hinged in the requirements definition.
FULLY AGREE, THIS PAGE IS INCORRECT. I suspect Walter X (see how often he erases all material) to perform -for whathever reason - Wiki vandalism. He is refusing to accept how international standards define V&V. This also counts for the V-model. — Preceding unsigned comment added by 184.108.40.206 (talk) 15:36, 30 March 2012 (UTC)
- Suspect all you want. Add reverences and you'll have my support. There are two competing definitions of the term. Sorry you don't understand that. --Walter Görlitz (talk) 15:51, 30 March 2012 (UTC)
Where's those definitions at, yo?
So let's have a few.
From: "IEEE Standard Glossary of Software Engineering Terminology", IEEE Std 610.12-1990:
VALIDATION: "The process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements. Contrast with: verification."
VERIFICATION: "(1) The process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. Contrast with: validation. (2) Formal proof of program correctness. See: proof of correctness.
VERIFICATION & VALIDATION (V&V): "The process of determining whether the requirements for a system or component are complete and correct, the products of each development phase fulfill the requirements or conditions imposed by the previous phase, and the final system or component complies with specified requirements. See also: independent verification & validation"
From: "Standard glossary of terms used in Software Testing; Version 2.2 (dd. October 19th, 2012), Produced by the ‘Glossary Working Party’ International Software Testing Qualifications Board"
VALIDATION: "Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. [ISO 9000]"
VERIFICATION: "Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled. [ISO 9000]"
The [ISO 9000] reference above is meant for "ISO 9000:2005. Quality Management Systems – Fundamentals and Vocabulary.", which I don't have at hand.
From: "European Cooperation for Space Standardization - Glossary of Terms" ECSS P-001B of July 14, 2004, ECSS Secretariat, ESA ESTEC, Requirements and Standards Division, Nordwijk, The Netherlands:
VALIDATION: "Confirmation, through the provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. NOTE 1: The term “validated” is used to designate the corresponding status. NOTE 2: The use conditions for validation can be real or simulated. [ISO 9000:2000]"
VERIFICATION: "Confirmation through the provision of objective evidence that specified requirements have been fulfilled. NOTE 1: The term “verified” is used to designate the corresponding status. NOTE 2: Confirmation can comprise activities such as (1) performing alternative calculations (2) comparing a new design specification with a similar proven design specification (3) undertaking tests and demonstrations, and (4) reviewing documents prior to issue. [ISO 9000:2000]"
The [ISO 9000:2000] reference above is meant for "ISO 9000:2000. Quality Management Systems – Fundamentals and Vocabulary.", which I don't have at hand.
From: "Galileo Software Standard" (Galileo Industries document "GAL-SPE-GLI-SYST-A/0092", 24/05/2004):
VALIDATION: "Confirmation, by examination and provision of objective evidence, that the particular requirements for a specific intended use are fulfilled, i.e. to ensure that specification requirements of the product are met."
VERIFICATION: "Confirmation, by examination and provision of objective evidence, that specified requirements have been fulfilled, i.e. check to ensure that the requirements process for a dedicated phase is properly applied."
High-Level Flow of Validation and Verification
step 1. create a high-level behavioral model to validate a customer's reqmts. step 2. from that model one extracts reqmts for the design. step 3. verify the reqmts for the design against the previously validated model.
as long as each step is performed correctly, prior to the subsequent step you should satisfy both validation and verification of the design.
In the international counsil on systems engineering provides it like this
1 Needs --> 2 Requirements --> 3 Design --> 4 Product
FIRST VALIDATE (2) Requirements against the Need (1) THAN VERIFY (3) Designs against the Requirements [e.g. Analysis] (2) AND/OR VERIFY (4) Products against the Requirements (2) [e.g. Testing] THAN finally VALIDATE (4) PRODUCT AGAINS THE NEEDS (1) (customer review...)
So, verification is ALWAYS against the Requirements AND Validation ALWAYS against the real world , which is the whol purpose of all of it: The NEEDS from (internal) Customer — Preceding unsigned comment added by 220.127.116.11 (talk) 15:21, 2 November 2012 (UTC)
Different approaches for the same goals in different contexts
Since I was insterested in program verification, a long time ago, I start to read about Software Engineering. Broadly speaking I observed two approaches Quality Assurance and Formal Methods. The first QA, place more emphasis in organizational aspects in software development, the second FM, logical and algebraic methods to make proofs to ensure the quality of programs.
Giving a sight to the v&v link talking about QA standards like iso9000, that are used in many engineering projects, like building NASA's navies.
QA, may use the approach of formal methods to achieve some goals, but FM are independent of the way a team building software is organized.
I think that the pages should not be merged, just be disambiguated for the context, this does not exclude that the entry V&V (QA) pointing to V&V (FM) when necessary. —Preceding unsigned comment added by Elias (talk • contribs) 15:50, 8 October 2009 (UTC)
Validation is not a quality assurance activity
I disagree that validation is a quality assurance activity. It is in fact a quality control activity, just like verification. Quality assurance is about providing visibility to various stakeholders into the process used to develop the product (including quality control activities) through objective evidences, in order to provide confidence and assurance about the product quality. Mobius80 (talk) 16:01, 15 October 2009 (UTC)mobius80
- In my opinion validation cover both quality control and quality assurance aspect, because in the process of validation it has to verify that the product meet specification which is quality control, parameter,measurement ect. but at the same time it has to follow and compliance with the general regulation (standards) and products - user requirement. —Preceding unsigned comment added by 18.104.22.168 (talk) 21:04, 11 April 2011 (UTC)
The version comparisons of this topic......
Just let you know that all the writers for these versions maybe proxy writers or the writers who are cloned, except for the originals. This can be evidenced by the fact that the original references were retrievable
- Anyway, The above 6 links are like modern hexograms. The bottom three can been further traced whereas the top 3 remain questioned. I don't know whether wiki admin should be responsible for the traceability--22.214.171.124 (talk) 04:55, 12 April 2010 (UTC)
Welll, I let my cloned writers to add the following info....
The following info is about the writer who maybe a vandalist.....
- Then report the vandal, but I don't see a problem. --Walter Görlitz (talk) 04:32, 12 April 2010 (UTC)
Also...the following trails is not normal either......and....
the critical infos of the article have been wrecked off....
See what those have been done
- The majority of these edits look perfectly correct to me. If there's a problem, and remember these edits were all done a eighteen months ago, feel free to revert them with an explanation. --Walter Görlitz (talk) 04:34, 12 April 2010 (UTC)
can someone correct a typo I tried am to busy and give up
I only corrected the spelling of word from Waning Letter to Warning Letter after ascertaining that “Warning Letter” was the correct title and spelling. When I pressed the link to download and save the PDF document the complete name appeared automatically on the save as document name window, above the saving format window, the complete title of the reference and the link all together, both spellings incorrect and correct concurrently in one. Thus the word WARNING was spelled incorrectly on the title of the link but correctly in the URL link which I copied and pasted entirely. However, I modified in bolde here the text pasted for this explanation only to emphasize the problem visually subsequently: 36. ^ United States Department of Health & Human Services (2009). "Waning Letter (WL No. 320-08-04)". http://www.fda.gov/downloads/Drugs/GuidanceComplianceRegulatoryInformation/EnforcementActivitiesbyFDA/WarningLettersandNoticeofViolationLetterstoPharmaceuticalCompanies/ucm085293.pdf. Retrieved 12 July 2009.
So I could not changed I hope that this explanation brings the matter to your attention so someone can make the necessary corrections I tried to make.
It should read when corrected: 36. ^ United States Department of Health & Human Services (2009). "Warning Letter (WL No. 320-08-04)". http://www.fda.gov/downloads/Drugs/GuidanceComplianceRegulatoryInformation/EnforcementActivitiesbyFDA/WarningLettersandNoticeofViolationLetterstoPharmaceuticalCompanies/ucm085293.pdf. Retrieved 12 July 2009.
I have edited and corrected a couple of times before small errors or false links and had no problems yet on this occasion despite my efforts and since I do not have much time and for some reason the text in question when I pressed edit button did not appear in the editing box & page as it should maybe there are special methods to deal with text within the reference section which seems not very logic as if there is something more necessary than so many other things is to facilitate the referencing system from adding citations, changing, improving, to deleting them, The reliability of any encyclopaedia, academic publication, published dictionaries or non fiction book that calls for references is key to its credibility and finally its acceptance and usefulness. So if dealing with citations and referencing becomes specially painful, well we might as well close the kiosk and go fly a kite because the primary objective, that Wikipedia becomes respected world wide and can be used as a reliable source specially in Academia, and while it is visible that citations and Wikipedia has improved very much in the last years it has still a long way to go before it becomes an accepted and serious source in academic circles. It would be a pity that after so much efforts such a project would finally become worthless due to a lack of a serious yet easy and dependable referencing methodology. If I need to make such a fuss only to correct a typo... well what can I say? Best regards, Santiago 126.96.36.199 (talk) 10:25, 11 November 2010 (UTC)
- I fixed the typo, thanks for the notice. Often references are defined at the place they are used (and not in the references section). To find where a reference is used, click the "^" (or "a" or "b" etc, if multiple usages occur) link at the beginning of the line with the reference in the references section. Johnuniq (talk) 10:38, 11 November 2010 (UTC)
QC vs QA
Quality Control and Quality Assurance have a variety of usages: see . Often QC is internal and is product oriented while QA is much broader and is process oriented. The terms have definitions by ASQ and several other groups but I have not seen a definitive link between verification and QA and validation and QC. Unless we can find a universal connection (and reliable source) between these concepts, I say we remove the claimed connections. Rlsheehan (talk) 23:51, 25 January 2012 (UTC)
- It seems to me you're referencing two statements in the overview section. I'm not sure we need to go into that when their articles do. --Walter Görlitz (talk) 23:55, 25 January 2012 (UTC)
Request to completely revise this page
- It seems adequate and since the group you mention is only one interested party, we can't cater only to their terms and definitions. Are there specific changes that you'd like to see? --Walter Görlitz (talk) 14:21, 3 April 2012 (UTC)
The entire entry seems to have been written by a non-English speaker. Noun verb agreement is often incorrect. The grammar is horrible. Read the section on the FAA. Every sentence contains at least one grammar mistake. Content aside, this one of the worst Wikipedia entries I have read. PLEASE edit for grammar. It was probably written by a foreign engineer. Engineers, even native English speakers are notoriusly bas writers. I am a native English speaking engineer, albiet with a BA in a liberal arts discipline. — Preceding unsigned comment added by 188.8.131.52 (talk) 15:21, 3 August 2012 (UTC)