This page describes how MDriven can be used alongside an existing ERP system when an organization wants to modernize or extend business capabilities without a rip-and-replace project.
ERP modernization with MDriven
MDriven is described as working with existing systems, including ERP, CRM, and databases. Its legacy-modernization guidance states that MDriven can work alongside legacy systems rather than requiring replacement of those systems.
A team can use MDriven Designer to model classes, relationships, business rules, and user interactions for a new or changed capability. MDriven Designer supports visual modeling, executable models, OCL-based business logic, automatic UI generation, and iterative model evolution.
MDriven applications can be deployed in cloud or on-premises environments.
Illustrative implementation pattern
The following is an illustrative pattern, not a documented customer implementation.
Consider an organization that retains its existing ERP for established operations but needs a new purchasing-approval capability around ERP-related business data.
- Model the concepts needed for the capability in MDriven Designer, such as a purchase request, requester, approval status, and relevant relationships.
- Define workflow-related business rules in OCL (Object Constraint Language), such as the conditions under which an approval status may change.
- Create a user interaction for the approval use case. MDriven Designer can generate customizable user interfaces and interactive ViewModels from modeled classes.
- Integrate the capability with the existing ERP and other required systems using the integration approach appropriate to the organization.
- Deploy the application in the required cloud or on-premises environment.
- Update the model as business needs change. MDriven Designer is intended to regenerate the system as models evolve.
| Need | MDriven implementation focus | Illustrative example |
|---|---|---|
| New workflow around an existing ERP | Model business concepts, relationships, and rules. | A purchase request moves through defined approval statuses. |
| User interaction | Generate a customizable UI and interactive ViewModel from modeled classes. | An approver reviews requests awaiting a decision. |
| Change to a business rule | Update the model and its OCL-based rule. | Add a condition to the approval workflow. |
Scope and limits
It is not a customer case study and does not establish that MDriven replaces an ERP system, supports a specific ERP product, or has produced a particular implementation result or timeline.