Software Verification and Validation

Software Verification

The process of evaluating work-products of a development phase to determine whether they meet the specified requirements for that phase. Its objective is to ensure that the product is being built according to the requirements and design specifications. It evaluates the plans, requirement speculations, design speculations, code, test cases

Software Validation

The process of evaluating software at the end of the development process to determine whether it satisfies business requirements. Its objective is to ensure that the product will actually meet the user’s needs.

 

Summarizing, software verification is made during the process of creating the software for making sure the requirements will be meet, and software validation is done after the software is finished and it makes sure that all the requirements were met.


SW Verification and Validation

10774285196_653eda105c_z.jpg

2

In one of our previous post we have talked about software testing. There are many options totest your software, but now we have another topic related to discuss. Is software validation the same as software verification?

In https://iiseblogs.org/  words:

Validation can be described as verifying that you are building what the customer wants. Software validation is the process of ensuring that your application meets functional and non-functional requirements before coding and during development.

Verification if verifying that the product is being assembled correctly, after you have determined what you are supposed to build.

Keep in mind both concepts, the difference between validation and verification is functional. Validations is to cover all of the “requirements” of the user, and verification means “functionality” in all of thse parts.

For example, we have shown that software testing is performed in different layers, from Unit testing to Exploratory testing. In verification you guarantee that all of this parts really works appropiately before the project is “built”.

In http://www.fda.gov/RegulatoryInformation/Guidances/ucm085281.htm you can find a really complete guide ofsoftware validation, actually the name of the document is:

General Principles of Software Validation; Final Guidance for Industry and FDA Staff

Some of the topics covered are:

I personally read the 4.7, which I saw asone of the most important ones. Let me give you a little explanation of my thouhgs:

Think on what an application tells you there is an update available (yes an update instead on an upgrade), there are a lot of steps before developers launch this

Continue reading "SW Verification and Validation"