You use Verify to check that your MDriven Designer model is coherent and ready to execute before you run it in the Prototyper or deploy it.
Contents
Verify the model
A model must make sense as a whole before MDriven can execute it. Verification, also called validation, checks the model for errors that prevent this.
- In MDriven Designer, click the Validation button.
- Review the reported errors.
- Correct each error in the relevant part of the model.
- Run validation again until no errors remain.
Validation also runs automatically when you save the model. Run it manually whenever you have made a related set of changes and want to check the result before continuing.
Resolve validation errors
Validation errors point to model definitions that conflict or are incomplete. For example, two classes must not use the same class name. Rename one class so that each class has a distinct name.
When an error is reported, use the error as a starting point and inspect the affected model element. Common areas to review include:
- Classes and their names.
- Attributes and their declared simple-value types.
- Associations between classes.
- ViewModels, including the class to which each ViewModel is typed and whether it is rooted or not rooted.
- Methods, including whether a query method uses OCL and whether an action method is allowed to change data.
- User actions and the ViewModels or classes they use.
For example, if you add a new document ViewModel for Order, verify that the ViewModel is typed to the Order class and is rooted when it is intended to show one specific order.
Keep the model clean before you run it
Do not start the Prototyper or deploy a model while validation reports errors. A clean model has no validation errors and is the baseline for testing how the application behaves.
After validation succeeds:
- Start the Prototyper to execute the model locally and inspect the application in your browser.
- Use the running application to find missing information, views, or user actions.
- Return to MDriven Designer, make changes, save, and verify the model again.
The Prototyper updates the running system when you change the model, but validation remains the first check: correct model errors before evaluating the user experience.
Suggested working cycle
Use verification throughout development rather than only at the end:
- Define or change information: classes, attributes, and associations.
- Save and validate the model.
- Add or change ViewModels and user actions.
- Save and validate again.
- Run the Prototyper and test the result.