Home / Model Expert Homepage / Model Expert Help / Getting Started / Model Expert Walk-through – Guided Modeling
Import an MDG to create a Reference Model
Importing and exporting Reference Models
Editing RM Connector type properties
Stereotypes inheriting from other Element Types
Customizing Reference Model Properties
Customizing Reference Model Element Properties
Model Expert Walk-through – Guided Modeling
Guided Modeling
All of the functions in the first part of the Model Expert walkthrough – which are part of the free-for-life version of Model Expert – allow your modelers to get guidance on how they model. The functions above will let you find out what they have already done, and fix it, but that’s going to get boring if they keep doing it wrong, and you keep having to fix it.
Guided Modeling lets you specify how you want your models to look, and enforce those rules. And, at the same time, educate your modelers in how to do it right first time, next time.
Validating a Package
- First find the Reference Model that you’re going to use to validate this part of the model. That’s in ‘Example Reference Models / 1- Requirements and Stakeholders’.
- Now find the packages we want to validate.
Find the package ‘Example requirements diagrams – un-managed’ in the example model.
This has some really simple content: just requirements, and the stakeholder who are connected to them. - There are a set of sub-packages under this just called Example #1…n.
Example #1
- Pick the first one ‘Example #1’ and right-click and choose ‘Specialize / Model Expert / Check package’
- In the Reference Model drop-down, choose ‘Requirements and Stakeholders’.
- Everything should be ok: there isn’t very much content in this package, and MX will only check elements which are children of the package.This what we want all our packages to look like!
Example #2
- Now try the same thing on the ‘Example #2’ package.
- This has a whole set of violations.
Notice that the Violation List has a Severity for each violation, to give an idea of how serious each one is. See Built-in validation rules for how to configure these. - This is an example package, and we’ve added lots of errors into it to show what Model Expert can do.
It’s more friendly to show user what they are doing wrong in a diagram (see below) or in a sheet.
Validating a Diagram
Instead of validating a whole package, try validating a diagram.
- In the Example #2 package, find the diagram, and right-click and Check Diagram.
- Here’s you will need to choose the Stakeholders and Requirements Reference Model, and there is also an option to choose which kind of diagram this is. See Validate a Diagram against a Reference Model