Community use cases and examples
You can use these examples to compare your application need with ways MDriven users and example models apply model-driven development.
User stories
| Situation | How MDriven is used | Concrete outcome |
|---|---|---|
| Business operations across several functions | Steve Arena of The Continuity Group reports using MDriven for CRM, invoicing, and stock market portfolio management. The application model drives persistence, while state diagrams and state machines describe object workflows and ViewModels base the user interface on the model. | One model can describe data storage, workflows, and the user interface for distinct business functions. |
Use-case patterns to explore
| If you need to... | Start with | Example |
|---|---|---|
| Modernize a legacy ERP system without replacing what already works | Create a model around existing data, then add features and REST APIs. | Add a new ViewModel for an existing business process while retaining the existing data source. |
| Replace spreadsheet-based intranet processes with a shared application | Use MDriven Turnkey to turn a business model into a hub where users see the information intended for them. | Model an approval workflow, then present its work items in a ViewModel. |
| Build and evolve a SaaS application | Model core business logic and evolve the database and backend as business rules change. | Start with the entities and rules for a customer workflow, then revise the model when the workflow changes. |
Try an example model
Example Gist provides complete model-and-data samples that you can apply to a Turnkey site. Available examples include complaint handling, project planning, an instant poll, a board, map, balls, and Gantt sample, and Google Maps with Turnkey.
For merge-in functionality, use model examples. These include user authentication, password reset, an outgoing email queue, a calendar model, a Trello-like board, interactive Gantt chart, SVG move-boxes example, and Google Maps position updates. For example, you can merge the user-authentication pattern into an empty model before building registration and login features.