This page collects MDriven documentation areas that can be relevant when reviewing how business information is described, changed, accessed, persisted, and evolved.
Model the business information
Start with the model as the description of the information in the system.
- Define classes that describe the data.
- Add associations between classes to describe aggregated things.
- Try the classes with data by creating objects that adhere to those descriptions.
- Refine views of data for specific needs or use cases.
See MDriven Designer for modeling basics, associations, unique constraints, enumerations, class diagrams, and nested diagrams.
Define rules for change
Use the documented modeling features to review rules that affect business information:
- State machines and workflows
- Actions and business logic
- ViewModels and ViewModel actions
The enterprise-information-systems guidance recommends adding state machines to reflect business rules for data changes. See MDriven Designer for ViewModels and actions.
Review access and persistence
Review the documentation for access control and data storage together with the model and views that expose business information.
- MDriven Designer includes Access Control System and Restricting Data Access topics.
- Integration includes authentication and security integration, external APIs and services, and data import and export topics.
Evolve the model deliberately
As user feedback introduces new needs, refine the classes and views and iterate. When changing a model, review the affected classes, associations, rules, views, access-control considerations, and persistence considerations together.
See MDriven Designer for renaming classes and efficient refactoring.