The following key explains the flow:

[sujonkumar6300]

Figure 1. Model Based Testing


0. Ideation: ideas about what the software product should do.

1. Systematization of the previous information, with which the requirements document is generated.

2. Formalization of Requirements using the modeling language.

3. Design of the MBT Strategy considering context, scope, objectives switzerland consumer email list and risks associated with the product, as well as completion criteria for testing.

4a. Generation of abstract test cases (i.e. described in the modeling language). This step eventually also involves minimization and sequencing of the test cases.

5a. Refinement of abstract test cases to obtain concrete test cases, which can be described in natural language or in a scripting language to automate the tests.

6. Execution of the software product to be tested, applying the specific test cases obtained.

7a. Abstraction of the concrete outputs generated during execution, transforming them into abstract outputs (i.e., described in the modeling language).