Workflow-Driven Tool Integration Using Model Transformations ⋆ Andr´ as Balogh 3 , G´ abor Bergmann 1 , Gy ¨ orgy Csert´ an 3 , L´ aszl´ oG¨ onczy 1 , ´ Akos Horv´ ath 1 , Istv´ an Majzik 1 , Andr´ as Pataricza 1 , Bal´ azs Polg´ ar 1 , Istv´ an R´ ath 1 , D´ aniel Varr´ o 1 , and Gergely Varr´ o 2 1 Budapest University of Technology and Economics, Department of Measurement and Information Systems, H-1117 Magyar tud´ osok krt. 2, Budapest, Hungary {bergmann,gonczy,ahorvath,majzik,pataric,polgar,rath,varro}@mit.bme.hu 2 Department of Computer Science and Information Theory, H-1117 Magyar tud´ osok krt. 2, Budapest, Hungary gervarro@cs.bme.hu 3 OptxWare Research and Development LLC, H-1137 Katona J. u. 39. {andras.balogh,gyorgy.csertan}@optxware.com Abstract. The design of safety-critical systems and business-critical services ne- cessitates to coordinate between a large variety of tools used in different phases of the development process. As certification frequently prescribes to achieve jus- tified compliance with regulations of authorities, integrated tool chain should strictly adhere to the development process itself. In order to manage complex- ity, we follow a model-driven approach where the development process is cap- tured using a precise domain-specific modeling language. Each individual step within this process is represented transparently as a service. Moreover, to carry out individual tasks, systems engineers are guided by semi-automated transfor- mation steps and well-formedness constraint checking. Both of them are formal- ized by graph patterns and graph transformation rules as provided by the VI - ATRA2 framework. In our prototype implementation, we use the popular JBPM workflow engine as orchestration means between different design and verification tools. We also give some insights how this tool integration approach was applied in recent projects. 1 Introduction Complex development projects, especially, in the field of safety-critical systems, ne- cessitate the use of a multitude of software tools throughout the entire life-cycle of the system under design for requirements eliciation, design, implementation, verification and validation as well as change management activities. However, in order to ensure safety, the verification of tool output is mandated by in- dustrial certification standards (like DO-178B [1] for avionics systems), which requires ⋆ This work was partially supported by the European Union as part of the MOGENTES (STREP- 216679), the DIANA (AERO1-030985) and the SENSORIA (IST-3-016004) projects. G. Engels et al. (Eds.): Nagl Festschrift, LNCS 5765, pp. 224–248, 2010. c  Springer-Verlag Berlin Heidelberg 2010