Anyone can use the MDriven Designer to model requirements and prototype detailed information systems. You will not grow out of this product. Even if you use nothing else this product helps you to think about large complex interlocked requirements for any domain. MDriven Designer is free for use for models up to 50 information classes.
With MDriven Turnkey you can be in the cloud with your information system later today. Your system will follow your model without deviation. Found issues are corrected in the model – model is uploaded to the supporting MDriven Server – and system is re-rendered and refreshed by a simple F5 in the browser.
MDriven Framework offers more degrees of freedom – and as such is a harder product to master. It is recommended that you start with MDriven Designer, then MDriven Turnkey. MDriven Framework is the best choice if you have scenarios where Turnkey is not right like building a standalone app in a device like a Hololens, Android phone, IOs or some other reason.
MDriven Framework is is the best choice if you want to write c# code towards your domain model – the c# can replace OCL implementations of methods and derivations. Such c# domain layer code may integrate with anything you can reach from c#. A complete system produced with MDriven Framework can run standalone – but the domain layer (including c# code you have written) can be submitted to MDriven Turnkey to reach the product advantages available there (security model, AngularJS etc).
Use MDriven Server for your MDriven Framework projects if you want a cloud based server application that talk WCF (over https amongst other) and manage your model and database with zero hassle. The MDriven Server is included as a required component in MDriven Turnkey. It is optional in MDriven Framework. MDriven Server is included in active license for Turnkey or Framework.
During the life cycle of our software toolset, strategy and scope have evolved. To better reflect our current vision, the product line now has consistent naming and branding: MDriven Framework, MDriven Designer, MDriven Server, MDriven Turnkey. This was not always the case and you may find old names in articles. To mitigate confusion we supply this list of old names:
Other names you may read:
WECPOF: This is what we call the prototyping motor. The motor is part of MDriven Designer and can be used to quickly execute the model including view model UI’s and actions. The WECPOF engine got its name from mixing ECO with WPF. Since then ECO has changed name to MDriven Framework – and the WECPOF motor is used for WPF, MVC and AngularJS. The name is still used to denote the prototyping ability and the runtime assembly MDriven Framework users can use to get the Prototyping engine inside their own applications (WECPOFLogic.dll).