Home

Welcome to the model-execution (MX) wiki!

Here we will execute the models we have built using Python.

The goal here is not to implement a system, but to execute it for the purposes of testing, validation, inspection, and experimentation.

Why not implement? Well, there are a variety of model compilers that can deliver an implementation of the models on a target platform such as an embedded ARM processor. (See the great work being done at Model Realization, for example).

Concepts

Let's see how all this works with the Elevator Case Study.

The Elevator domain models are defined in a system package. The structure of this package is defined in the readme file of the xuml-populate repository.

Now let's say that we have only one domain built so far and put the focus on that. MX will be designed to execute multiple domains, but we're just keeping it simple for the discussion of concepts.

We need a name for the execution environment we are creating to run our elevator domain(s).

In fact, we'll just call it that: Execution Environment (XE).

So the XE represents a workspace where you load your model components (classes, states, activities) so that you can run them against various scenarios that you've defined.

That gets us to the next term: Scenario.

A Scenario