Verification ? or Validation ?


Verification and Validation are both done in order to ensure that a software product as a whole satisfies its specifications.
Verification is ensuring that a step in the process of creating a software product has been correctly carried out [1]. This is usually done at the end of each step or stage. Verification usually is performed by mostly carrying out static testing type of activities like code review, walk through and code inspection. Verification activities may also include dynamic testing type of activities such as functional testing, unit testing and integration testing to execute the actual program code [2]. All of this activities are performed during the development process of the software product.
Validation on the other hand is evaluating the end product of the development process in order to ensure that the software product meet’s customers expectations or its specifications. This is usually done by executing the software program in its production environment to perform a variety of test on it to make sure that the customer is satisfied with the software product.
Both verification and validation ensures that the software product is assured of its quality. Both verification and validation are performed using a process in order to ensure that any feedback is readily addressed in order to increase the quality of the software product

[1] S. Schach, Object Oriented & Classical Software Engineering. New York, NY : McGraw-Hill,2007,pp. 150.
[2] K.Naik, Software Testing and Quality Assurance: Theory and Practice. Hoboken, NJ : Wiley & Sons,2008,pp. 8.

Comments

Popular posts from this blog

OAuth 1.0a Request Signing and Verification - HMAC-SHA1 - HMAC-SHA256

Spark DataFrame - Array[ByteBuffer] - IllegalAurmentException

Gensim Doc2Vec on Spark - a quest to get the right Vector