Modeling Language

This is the modeling language we are debugging. Each modeling language defines its own granularity of execution for stepping through behavior, its own kinds of actions, and so forth.

Since the model debugger domain is intended, initially at least, to support the development of Shlaer-Mellor Executable UML models, it may seem odd to abstract the modeling language itself. We do so for a few reasons.

First is to establish clean domain separation from the metamodel and model execution domains. This yields all the usual benefits. We simplify the model debugging domain by focusing on a single coherent subject matter. We also put ourselves in a position to support other langauges as well as any future variations or branches of Executable UML. And we avoid having to mirror structures and semantics in the modeling domain that have already been adequatly modeled.

For now, we only intend there to be a single instance of Modeling Language and for that instance to be Shlaer-Mellor Executable UML. But we set the stage for debugging a system in the future with one or more components expressed in other modeling languages.

Identifiers

1. ID

Attributes

Name

A name such as Shlaer-Mellor Executable UML or maybe SM xUML v2.2, etc.

Type: Modeling Language Name, based on Name