The terms "verification" and "validation" are very oftenused in technical literature and are associated with the analysis of the quality of any software. In the scientific literature can be found various interpretations of these concepts. So, let's try to understand this issue.
The most correct, from our point of view,is the following definition. Validation and verification are activities that are aimed at carrying out quality control of a software product in order to detect errors in the early stages. It would seem that they have a common goal. Still, these species have differences in the sources of verifiable properties, restrictions, and rules, the non-observance of which can be considered an error.
Verification is a compliance check.software technical documentation provided by the technical project, architecture or domain model. The “duties” of this term include the comparison of the settlement procedure with the process of their development, rules and standards.
Data verification may be performed forinstallation of compliance of the program with the established standards, requirements, design solutions and user documentation. At the same time, those documents with which a comparison is made for compliance with their standards and standards established in the country where the software is used are subject to mandatory preliminary verification. It is necessary to take into account and respect for all sequences of operations performed.
In the event of an error or defect in the workthe program or the discovery of a contradiction between the above documents and the current functioning of the program, the decision to choose a document for correction should be a separate task.
In contrast to verification, validation is responsible forverification of the development or maintenance of software products with the needs or requirements of customers or users. These needs are often not recorded in any documentation. That is why validation is less formalized than verification. This is a process in which a representative of a customer, a user participates, and an analyst or subject matter expert may be present. In other words, those that can express the specific needs and real needs of the stakeholders.
Verification is the answer to the question “Has the software been executed correctly?”, And validation - “Has the correct software been done?”.
When searching for the answer to the questions posed, you canto find out that validation (or certification) in terms of content is somewhat broader than verification (verification). However, verification is closely related to ensuring control over the quality of a software product.
For example, verification of a computer programprovides for a process in which the goal is set to ensure that the requirements of the data obtained in a certain product life cycle are satisfied with those obtained at the previous stage.
If we talk about the verification of the model, then we will discuss the verification of the correctness of the mapping of this computational model of the necessary conceptual or mathematical models.
When verifying the system code, the source code is analyzed and its compliance with the documentary description is checked.
The verification process may include operationscontaining alternative calculations. Technical and scientific documentation of a new project is compared with the corresponding documentation of an existing project, mandatory testing, testing of a new software product and demonstration of results.
