Inspection

• Teams of experts, developers, and testers will thoroughly scan the content (algorithms, programming code, documents, equations) in the original conceptual model, and compare with the appropriate counterpart to verify how closely the executable model matches.

Limit Value Analysis

• This criterion places its attention on the limit values of the program's input domain, because according to the literature, this is where the greatest number of errors is concentrated.

Partitioning into Equivalence Classes

• This criterion divides the program's input domain into equivalence classes or partitions, based on information from both the input and output of the program. This criterion can simplify and reduce the test cases, because it selects representative elements of each valid and invalid class, testing through an element, a set or class of input data, thus reducing the input domain and, consequently, the time associated with the activity.

Structural Testing (White Box)

• The Structural Test criteria are based on different types of components to determine which parts of the program should be run. They are classified into criteria based on flow of control and criteria based on data flow. The structured test considers the implementation aspects when choosing test cases, that is, the tester uses the internal structure (implementation) of the product to be tested.

Step by Step Abstraction

• The procedure consists of readings taken in the source code, from which the reviewers write their own specifications for the program. The abstractions constructed for each block are combined, generating a more general abstraction, repeating successively and, at the end, the Program Function is obtained, which must then be compared with the Specification to identify if there are inconsistencies.

Inspection

• Teams of experts, developers, and testers will thoroughly scan the content (algorithms, programming code, documents, equations) in the original conceptual model, and compare with the appropriate counterpart to verify how closely the executable model matches.

Face Validation

• One of the benefits of face validation is that it can effectively be used during a real-time virtual simulation where the interaction between the user and the simulation is of priority. The best way to validate that the model meets the criteria, is by having users who have experienced the model situation in real life confirm that the model accurately represents the situation they are familiar with.

Walkthrough

• A walkthrough is a scheduled meeting with the author/authors in charge of the model, or documents that are set to be reviewed. In addition to the authors, there is usually a group of senior technical, and possibly business staff that are there to analyze the model. Finally, there is a facilitator who is in charge of leading the meeting. Prior to the official meeting, the author/authors will review the document/model for any potential cosmetic errors.

Desk checking

• Desk checking consists of the author careful stepping through the model in an attempt to catch any inconsistencies. The author will thoroughly read all original documents, notes, and goals and try to verify that the completed product accurately and completely modeled everything that it set out to do.