You can use these examples to discuss how a team can work from a shared MDriven model; they are for teams evaluating a model-driven way of developing business applications.

Published team examples

The published statements below describe how named users apply MDriven concepts in their work. They do not provide enough project detail to establish timelines, team size, or quantified delivery outcomes.

Team or user	Reported use	What the example shows

Reproducible team exercise: task planning

You can give a small cross-functional team a concrete first exercise by building the Team Task Planner. The example models a team, projects, tasks, and members, then uses OCL to calculate task totals, completed-task totals, and project progress.

1. In MDriven Designer, create the Team, Project, Task, and Member classes and connect their associations.
2. Ask a domain expert to confirm the terms and relationships. For example, confirm whether a task is assigned to one member and whether a project contains many tasks.
3. Add the IsCompleted attribute to Task and define progress on Project with OCL. When a team member marks a task complete, the project's calculated progress changes with the model.
4. Generate ViewModels and UI views from the classes, relationships, and attributes.
5. Run the model, enter a team, projects, tasks, and members, and review whether the generated workflow matches the team's task-management rules.
6. Record the feedback as changes to the classes, associations, ViewModels, or OCL expressions, then repeat the exercise.

This exercise gives developers and domain experts a shared artifact to review: the model defines the data structure, relationships, business logic, and generated application behavior.

See also

• Documentation:MDriven features and benefits
• How to Build a Team Task Planner in 15 Minutes with MDriven
• Training:The declarative ViewModel