Verification is the process of verifying a software product
The terms "verification" and "validation" are very oftenUsed in the technical literature and related to the analysis of the quality of any software. In the scientific literature one can find 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 monitoring the quality of a software product in order to detect errors in the early stages of the software product. It would seem that they have a common goal. But still these species have differences in the sources of the properties being tested, restrictions and rules, non-observance of which can be considered a mistake.
Verification is a test of compliancesoftware technical documentation, presented technical specification, architecture or model of the subject domain. In the "responsibilities" of this term, the comparison of the calculation procedure with the process of their development, rules and standards is included.
Verification of data can be performed forsetting the compliance of the functioning of the program with the established norms, requirements, design decisions and user documentation. At the same time, mandatory documents must be subject to preliminary verification, with which they are compared for compliance with their standards and standards established in the country where the software is used. It is necessary to take into account and compliance with all sequences of operations performed.
In the event of an error or defect in operationprogram or the detection of a contradiction between the documents mentioned above and the functioning of the program, the decision to choose the corrective document should be a solution to a particular task.
Unlike verification, validation is responsible forchecking the compliance of developed or accompanied software products with the needs or needs 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 the representative of the customer, the user participates, and also there can be an analyst or expert in the subject area. In other words, those that can express the specific needs and real needs of the stakeholders.
Verification is the answer to the question "Is the software done correctly?" And validation - "Is the correct software done?".
When searching for answers to the questions, you canfind that validation (or certification) by content has a value slightly wider than verification (verification). Verification, however, is closely related to ensuring the quality control of the software product.
For example, verification of a computer programprovides a process in which the goal is to ensure that the requirements of the data obtained in a certain product life cycle are met, to those that were obtained in the previous stage.
If we are talking about verification of the model, then it will be a question of verifying the correctness of the mapping of a given computational model to the necessary conceptual or mathematical models.
When the system code is verified, the source code is analyzed and its compliance documented.
In the verification process, operations,containing alternative calculations. The technical and scientific documentation of the new project is compared with the corresponding documentation of the already existing project, mandatory testing, testing of the new software product and demonstration of the results.