Are you an EPFL student looking for a semester project?
Work with us on data science and visualisation projects, and deploy your project as an app on top of Graph Search.
Concept
Software verification
Summary
Software verification is a discipline of software engineering, programming languages, and theory of computation whose goal is to assure that software satisfies the expected requirements.
A broad definition of verification makes it related to software testing. In that case, there are two fundamental approaches to verification:
Dynamic verification, also known as experimentation, dynamic testing or, simply testing. - This is good for finding faults (software bugs).
Static verification, also known as analysis or, static testing - This is useful for proving the correctness of a program. Although it may result in false positives when there are one or more conflicts between the process a software really does and what the static verification assumes it does.
Under the ACM Computing Classification System, software verification topics appear under "Software and its engineering", within "Software creation", whereas Program verification also appears under Theory of computation under Semantics and reasoning, Program reasoning.
Dynamic verification is performed during the execution of software, and dynamically checks its behavior; it is commonly known as the Test phase.
Verification is a Review Process.
Depending on the scope of tests, we can categorize them in three families:
Test in the small: a test that checks a single function or class (Unit test)
Test in the large: a test that checks a group of classes, such as
Module test (a single module)
Integration test (more than one module)
System test (the entire system)
Acceptance test: a formal test defined to check acceptance criteria for a software
Functional test
Non functional test (performance, stress test)
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).
Official source
About this result
This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.