Software verification: Difference between revisions

Content deleted Content added
No edit summary
Tags: Reverted Visual edit Mobile edit Mobile web edit
No edit summary
Tags: Reverted Visual edit Mobile edit Mobile web edit
Line 24:
 
The aim of software dynamic verification is to find the errors introduced by an activity (for example, having a medical software to analyze bio-chemical data); or by the repetitive performance of one or more activities (such as a stress test for a web server, i.e. check if the current product of the activity is as correct as it was at the beginning of the activity).
 
== Static verification (Analysis) ==
 
Static verification is the process of checking that software meets requirements by inspecting the code before it runs. For example:
* ''[[Code conventions]] verification''
* ''Bad practices ([[anti-pattern]]) detection''
* [[Software metric]]s calculation
* [[Formal verification#Formal verification for software|Formal verification]]
 
Verification by Analysis - The analysis verification method applies to verification by investigation, mathematical calculations, logical evaluation, and calculations using classical textbook methods or accepted general use computer methods. Analysis includes sampling and correlating measured data and observed test results with calculated expected values to establish conformance with requirements.
 
*