1. MDD and Formal Methods Shusaku Iida School of Network and Information Senshu Univ.

2. Conclusion • MDD and formal methods are the same story that have different faces • MDD doesn’t care much about the formality • formal methods doesn’t care much about usability • these two issues are strongly related to language design IWFST2005 Shusaku Iida

3. What is MDD? • MDD(Model Driven Developments) • “model” means specification • in MDD you have to think about how to build and how to use models in system developments model A additional infomation transformation rules model A’ IWFST2005 Shusaku Iida

4. Our experience • we have built a blimp type robot by MDD • out team includes five undergraduate students and two engineers from a company, and several advisors • we have built more than 30 models (UML diagrams) mainly written in UML • work period is about two months • and, our blimp sailed! • however, building models are quite tough • especially for undergraduate students IWFST2005 Shusaku Iida

5. What is good and what is not about MDD • good • from the start, we don’t have to be so strict • there are several tools available for modeling • many people know something about UML • not good • we cannot be sure that our model is correct • there is few way to check it • we have to invent the transformation rules by our selves • so the productivity is low IWFST2005 Shusaku Iida

6. What shall we do? • We need to study interface of specification languages • Z has succeeded because it has special fonts and type-checker • We need to study more about language design • one possible idea is “Language Workbenches” by Martin Fowler • Domain Specific Languages can be the bridge between domain experts and MDD • and formal specification languages can help a lot IWFST2005 Shusaku Iida