He presented some findings on experiences from using model-based development in industry from the EA-MDE project. I talked to him afterwards and there apparently had only been one automotive company in the study, and I personally think that the conclusions might have been different if they were more data from them. If you are working model-based in your company and want to participate in the study you can do so by answering the questionare on the project web site.
One benefit of model-based development which I expected to see in the study was that it allows domain experts to actually do implementation, for example can chassis control experts actually do code for use in ECUs.
Note: You can substitue model-based development with several other acronyms and Jon's study is still relevant; MDD, MBSE, MDA, ...
I find this study to be similar to what Sascha Kirstan is working on in the automotive industry. I participated in Sascha's study this spring and just got a report with preliminary results, which I haven't had the time to read yet. I sure hope these two researcher will look at each others result and see if they can corroborate their findings or if they are contradictions.
Jon concluded his talk with the top ten tips for companies wanting to adopt model-based development and here they are (but to truly utilise them you must know a lot more about the context where they were found):
- Keep the domains (modelled, I assume) tight and narrow.
- Target well known domains.
- Put MDD on the critical path (he means that pilot projects never get sufficient attention and resources).
- MDD works best form the ground up.
- Be careful of gains that are offset elsewhere.
- Don't obsess about code generation.
- Not everyone can think abstractly.
- Most projects fail at scale-up
- Match tools and processes to the way people think, not the other way around
- Ok, there was only 9...