QM  7.0.0
Model-Based Design Tool
Loading...
Searching...
No Matches
Model-View-Controller

User InterfaceWorking with Dock Windows

Like most modeling tools, QM™ is based on the Model-View-Controller↑ architecture.

Model-View-Controller Architecture of QM™

Model

At the center of the system is an abstract hierarchical model of your software system. This model is kept entirely in memory and can be accessed very quickly. The abstract model is persisted in a Model File (file with extension .qm), which uses the XML↑ data format. By using external packages you can also store the model into multiple files (package files with extension .qmp).

Views

The visible components of the QM™ user interface provide different views of the model. For example, the Model Explorer provides the most comprehensive view of the whole model. Other GUI components provide the view of a specific item (see Current Item) or groups of related items (such as states and transitions in a diagram). The views are not just for viewing the model. You can also use them to change the model. For example, you can use the Model Explorer to add, remove, or re-order the items. You can also change diagrams by adding, removing, or re-arranging states and transitions. (NOTE: You always work with the same abstract model, regardless which view you are using.)

Controller

This is the internal logic built into the QM™ tool that coordinates which parts of the model are displayed by the views and which parts of the model are updated from the views. The effective controller function requires a lot of internal knowledge about all the model items. For example, QM™ "knows" all the rules of state nesting, rules for attaching transitions, choice-segments, etc. in the state diagrams.

User InterfaceWorking with Dock Windows