Use this page to organize how a team reviews and refines a shared business model with the people who know the business domain.

Reviewing model changes

The goal is continuous refinement: reduce the difference between business reality and the model as the business changes.

Communicating through the model

Use the model as a reviewable description of the business domain. Keep discussions connected to a concrete process, relationship, attribute, or rule.

For example, a team reviewing project progress can inspect the expressions used for the derived values:

• Total tasks: self.tasks->size
• Completed tasks: self.tasks->select(IsCompleted)->size

Onboarding team members

Give new team members a small, complete modeling exercise that they can run and inspect.

1. Create Project, Task, and Member classes and define their relationships.
2. Add attributes such as Title, IsCompleted, and Priority.
3. Add a derived value or validation rule using OCL.
4. Use AutoForms to create or refresh generated ViewModels and UI views.
5. Run the model using the prototyping option or MDriven Turnkey and test the behavior with sample data.
6. Review the result with a mentor and relate the observed application behavior to the model.

Release readiness

For example, if a change adds a priority rule, test that values outside the accepted range are rejected.

Do not infer a product-specific workflow for model storage, version history, branches, merges, conflict resolution, or promotion between environments from this page. Use the project-approved process until official MDriven guidance is available.

See also

• Discovering Business Requirements
• Reality and the Theoretical Best Model
• How to Build a Team Task Planner in 15 Minutes with MDriven