You can use this video series to learn how to build and operate an application model in MDriven Designer, from your first UML diagram to ViewModels, actions, reports, search, and deployment-related topics.
MDriven Designer is a UML modeling tool for defining the details of a software system. The series follows the work of creating and evolving a model, then using declarative UI concepts such as ViewModels and actions to make the model behave as an application.
Start here
- Begin with Part 1: Introduction to MDriven Designer to install or launch the Designer and understand the overview screen, repository tree, diagrams, and classes.
- Continue in numerical order through Parts 2–10. Later sessions build on the model, ViewModels, and navigation introduced earlier.
- Use Part 11 and the sessions on actions, ViewModels, snapshots, and uploads when you need to revisit those focused subjects.
- Keep your own model open while watching. Recreate each small step before moving on; for example, create a class diagram, add two classes, and verify where each class appears in the repository tree.
For a broader entry point into the product and its learning material, see Documentation:GettingStarted and HowTos:HowTo.
What you will learn
The series covers the path from a model structure to an executable prototype:
- Model structure: diagrams are visual representations of model elements, while the repository tree represents the complete model structure.
- UML classes and relationships: create classes and associations, including link objects (association classes).
- OCL: use Object Constraint Language expressions in the OCL editor to express model logic and transformations.
- ViewModels: define transformed views of model data together with UI hints. A ViewModel can, for example, present a collection of houses and navigate to one selected house.
- Actions and navigation: connect an application entry point or user command to a ViewModel and its navigation flow.
- WECPOF prototyping: run a declarative prototype based on the model, ViewModels, UI hints, and action definitions.
- Application features: work with database search, OpenDocument reports, files, images, access groups, and deployment-related tooling.
Series map
| Session | Topic | What to focus on |
|---|---|---|
| Part 1 | Introduction to MDriven Designer | Launch the Designer, create and rename diagrams, use the repository tree and Object Inspector, create categories, and add classes to a diagram. |
| Part 2 | OCL editor, system prototyper, and ViewModel | Learn how model expressions, the prototyper, and ViewModels work together. |
| Part 3 | WECPOF prototyper application | See how actions and ViewModels are organized in a prototype application. The overview can show available ViewModels and action navigation, helping you identify how views are reached. |
| Part 4 | Modal ViewModels and more | Work with ViewModels that are presented modally and related UI behavior. |
| Part 5 | Searching in databases | Explore database-search behavior in the application. |
| Part 6 | OpenDocument reports | Create or work with reports in OpenDocument format. |
| Part 7 | Files and images in reports and UI | Include files and images in reports and in the user interface. |
| Part 8 | Link objects and association classes | Model associations that need their own information, rather than only a connection between two classes. |
| Part 9 | MDriven Turnkey, cloud tools, and access groups | Review Turnkey-related tooling and access-group topics. |
| Part 10 | Actions and navigation | Define how users initiate behavior and move between ViewModels. |
| Part 11 | ViewModel Designer updates | Review updates related to designing ViewModels. |
Follow Part 1 with your own model
Part 1 establishes a distinction that is important throughout the series: a class belongs to the model repository, while a diagram is one visual representation of that class. The same class can be placed on more than one diagram without creating a second class.
Use this exercise while following the introduction:
- Launch MDriven Designer from the Designer site using Run with ClickOnce. ClickOnce is Microsoft distribution technology; it updates the application when an update is available. Your browser may need an association or plug-in for the
.applicationextension. - Start a new model. The overview screen displays the available diagrams and the repository tree.
- In the repository tree, select Add Class diagram. Rename the new diagram in the Object Inspector; for example, use
Domain overview. - Double-click the diagram to open it. Right-click the diagram canvas and select Add a class. Create
House. - Add a second class, such as
Owner. - Return to the overview and open another diagram. Drag
Housefrom the repository onto that diagram. - Confirm the result:
Houseis visible in both diagrams, but it remains one class in the repository.
You can also create categories from the repository tree and assign them to diagrams. For example, create Important and Less Important to classify diagrams. Categories are optional, but they help organize larger models.
Watch Part 1: Introduction to MDriven Designer while completing this exercise.
Use the prototype sessions effectively
A ViewModel is a set of transformation expressions that presents a selected part of the model, optionally with UI hints. An action initiates behavior or navigation that can lead to a ViewModel. In the prototyper, these concepts form a navigable application structure.
When working through the WECPOF and action sessions, use this check:
- Identify the action that starts a flow.
- Identify the ViewModel that the action opens.
- Follow the navigation to the next ViewModel.
- Refresh the overview when needed to inspect the available ViewModels and action-navigation structure.
- Check for ViewModels that are not reachable from an action. The prototype overview can identify stale ViewModels that cannot be reached through the defined navigation.
For example, a flow named show.allhouses can lead to a ViewModel that shows houses, then continue to a ViewModel that shows one selected house. The flow is easier to maintain when each action and ViewModel has a clear purpose and reachable navigation path.
Watch Part 3: WECPOF prototyper application for an example of reviewing ViewModels and action navigation in the overview.
Related learning paths
This series is an overview, not a replacement for topic-specific documentation. Use the following pages when you need deeper guidance:
- Documentation:Designer for the MDriven Designer documentation area.
- Documentation:MDriven Product Line to understand where MDriven Designer fits in the product line.
- Training:MDriven Shorts for shorter training material.
- Documentation:MDriven Designer Overview Series for the documentation-series entry.