MDriven’s Team Task Planner tutorial introduces a lightweight planner modeled in MDriven Designer. The planned application includes projects, tasks, members, progress tracking, and automated business logic.
What the tutorial says the application will do[edit source]
The tutorial describes an application that can:
- Create projects and manage team members.
- Add, assign, and track tasks.
- Calculate project progress automatically.
- Enforce real-time validation rules.
It presents the model as the place where structure, relationships, business logic, and UI validation are defined.
Step 1: Create the domain model[edit source]
Create these four classes:
TeamProjectTaskMember
Add the following relationships:
- A
Teamhas manyProjectobjects. - A
Projecthas manyTaskobjects. - A
Taskcan be assigned to aMember.
According to the tutorial, defining these classes and associations establishes the structural foundation and database schema for the system.
Step 2: Add attributes[edit source]
Add these attributes:
| Class | Attribute | Type |
|---|---|---|
| Project | Name
|
String |
| Project | Deadline
|
Date |
| Task | Title
|
String |
| Task | IsCompleted
|
Boolean |
| Task | Priority
|
Integer |
| Member | Name
|
String |
| Member | Email
|
String |
Step 3: Add OCL-derived task counts[edit source]
The tutorial uses Object Constraint Language (OCL) expressions in the model to calculate project information.
Total task count[edit source]
Add a derived attribute named TotalTasks to Project:
self.tasks->sizeThis expression returns the number of tasks associated with the project.
Completed task count[edit source]
Add a derived attribute named CompletedTasks to Project:
self.tasks->select(IsCompleted)->sizeThis expression selects completed tasks and returns their count.
Needs human verification[edit source]
The supplied passage says that the two counts will be combined to calculate overall project progress, but it does not include the resulting OCL expression. It also does not document:
- The exact validation rule or permitted priority range.
- Any AutoForms commands or generated ViewModel behavior.
- Steps for running the planner in a browser.
- A test data set or expected calculated progress value.
Add those details only after checking the complete tutorial or another authoritative MDriven source.
