Model Debugger Domain

To inspect, test, validate, and debug a modeled system we need a model debugger.

Here we can load a population for each modeled domain, define and run a scenario, set breakpoints on model elements and conditions, and intermittently view various aspects of the populated models and execution status.

And, of course, we model the model debugger. Since the subject matter of debugging and testing is largely distinct from that of executable models and certainly Shlaer-Mellor, we abstract the subject matter in its own domain.

When we debug our models we will bridge together the executing Metamodel Domain (Shlaer-Mellor Metamodel) and this Model Debugger Domain.

As shown in the domain chart, the Metamodel Domain is the application since it represents the business purpose of our system: specifying and executing a modeled system. The Model Debugger Domain helps us control and manage what's going on during execution as a service domain.