BridgePoint now open source!

I’ve been talking about open source modelling tools for the last little while, mainly about Papyrus and promoting Papyrus-RT (with which I am, obviously from my posts, involved). Well another company has seen the open source light: Mentor Graphics has now formally released its BridgePoint tools to open source. A new company, OneFact, staffed with ex-Mentor Graphics employees, is taking over the mantle for the maintenance, support, and consulting for the tool.

You can read the announcement here and the accompanying presentation (Prezi) here.

This good news. First, it is further indication that there is a business case around open source modelling tools, so our own efforts are validated. Second, the approach taken by Mentor Graphics does not leave existing customers wondering what is happening or will happen (there have been questions about Mentor Graphics’ intentions for BridgePoint for quite a while) and ensures continuity.

Congratulations and good luck to the folks at OneFact!

EclipseCon Europe 2014

I am now at EclipseCon Europe 2014 for the week, planning on discussing Papyrus, building alliances and friendships, and promoting our vision of modelling and open source.

I will be presenting the work we are doing with regards to Papyrus-RT during the modelling symposium tomorrow. A short, 10-minutes talk, so I will be concise and  to the point. I will also have a demo for people to see after the talk : code generation from capsule-based state machines and running – all based on Papyrus models.

Are you at the conference? Then look me up!

And follow my twitter feed (and @PapyrusUML ‘s ) to know what happening!

 

MDA, MDD, MDE

Jordi Cabot has an interesting Blog on Modeling Languages. In it (an on LinkedIn) there was a discussion recently on the difference or similitudes between MDA, MDD, and MDE. It’s interesting that Wikipedia treats the last two as the same thing – I like Jordi’s description better.

However, as I read Jordi’s blog posting, I found that his explanation certainly makes sense and is probably correct nowadays, in a more modern sense of the terms.

However, “MDD” has been used for quite a long time to describe model-based (as opposed to model-driven) development. That use of the term would not fit within the definitions presented by OMG as part of MDA (e.g., the CIM/PIM/PSM levels of abstractions and transformations). I suspect that this approach may also still be in use today – although probably not the best way of working with models. This may especially be true of some of the model uses seen in “agile” approaches.

So perhaps there is a need, in the diagram shown on that blog, to also have a model-based development (MBD?) circle that would intersect with MDD, but not the others?

All this also can not be discussed without mentioning the standards, processes, and methods (and the effect of tools on these) surrounding these approaches. Models need to have a standard representation to be useful – and the UML (and SysML) is certainly one that is common these days. However, other notations such as BPMN, ERD, etc., should not be discounted as they represent interesting domain specific modeling languages – and not all can be easily expressed using UML . Tools are too often viewed as a panacea to what ails software development – when they can be a hindrance when one does not understand the standards, processes, and methods they support.