Who is MDriven for?
MDriven is intended for organizations and software teams that build, maintain, modernize, or integrate business-support systems. Its model-driven approach is presented as a way to make business logic more structured, transparent, reusable, and less dependent on individual developers.
Organizations building or evolving business systems
MDriven may fit businesses that want scalable, maintainable software and that need their systems to adapt as requirements, scope, or demand change. MDriven describes its architecture as modular and cloud-ready, with built-in practices for concerns such as security, concurrency, and fault tolerance.
Teams working with complex business logic
MDriven may be useful when a team needs to make complex business logic easier to understand, document, and maintain. Its visual models are intended to let domain experts contribute directly and to provide reusable documentation rather than relying on knowledge held by particular individuals.
This can be relevant to teams experiencing miscommunication between developers and business experts, or organizations that want their business core to be less dependent on particular programming languages and development tools.
Organizations modernizing or integrating legacy systems
MDriven is positioned for companies working with legacy-system limitations. It can work alongside existing systems rather than requiring a "rip-and-replace" approach. The supplied material also states that MDriven has features for integration with C and APIs, and that reverse-engineering capabilities can help accelerate migration when an organization is ready to modernize.
Roles that may benefit
| Role | Relevant use of MDriven |
|---|---|
| Domain expert or business stakeholder | Contribute to and review visual models that document the business domain. |
| Developer | Build applications with MDriven's development environment. |
| Architect or technical lead | Use a model-driven approach for systems that need to scale in scope and complexity. |
| Engineering or business leader | Support clearer documentation, collaboration between stakeholders, and reduced reliance on individual developers' undocumented knowledge. |
Application and integration scenarios
MDriven ViewModels can define a user interface or an interface to another system. A ViewModel can read and write data in the system and run actions; it can be exposed as a REST or web-service interface. This can support integrations with other systems or act as a backend for a native mobile application.
Related information
- Evaluation Guide: https://mdriven.net/Turnkey/WAct?actionref=EvaluationGuide
- What is MDriven? (video): https://www.youtube.com/watch?v=XrJ9uMYtnn0