Test model architecture:

Test model: Markov chains

The test model is basically a collection of States and Transitions and it represents the possible usage of the system.

It can be understood as a formal definition of all possible actions, defined by stimulations, called the "Inputs" and owned by the transition. Because this is a test model, transitions also own reactions defined by the "Expected Results".

Enhanced test model: Enhanced Markov chains

The model architecture can be implemented with numerous levels, thanks to "Macro Chains".

Additionally, enhanced objects such as "Conditions" and "Asynchronous events" allow the model designer to easily implement  more complex and powerful models.

Classes of Equivalence:

As current complex systems cannot be validated exhaustively, MaTeLo makes it possible to define "Classes of Equivalence". It increases the test generation variability and then extends the test coverage. 

Types, Sequences and Global Variables:

MaTeLo Usage Model Editor offers definition of customized data "Types" as well as "Global Variables". It helps to handle specific test data or simply allows for saving and retrieving calculated parameters value.

Test oracle:

“Transfer Functions” can be associated to the model and link variables together (the needed link between Expected Results and Inputs).

These functions can be defined with Mathworks Simulink©, Scilab Scicos© or with MaTeLo “context” functions.

Profiles and test strategy:

A test profile defines the probability data set of the model for the transitions and the inputs.

It can defined as a “usage profile” to calculate the reliability or as a “custom profile" to handle a customized test strategy.

Association with system requirements:

MaTeLo owns a "Requirements library" allowing associations of requirements to the model objects. The aim is to link the test model with the requirements and to ensure the requirements validation during the test campaign.

The requirements library can be automatically imported from other requirements databases such as IBM Telelogic Doors © (Native Plug-In) or via files such as CSV (Geensys Reqtify©,Microsoft Excel©...) or XML (RIF...).