Challenges in Combining SysML and MARTE for Model-Based Design of Embedded Systems Huascar Espinoza 1 , Daniela Cancila 1 , Bran Selic 2 , and Sébastien Gérard 1 1 CEA LIST, Model-Driven Engineering Labs Point Courrier 94, 91191, Gif sur Yvette, France {huascar.espinoza, daniela.cancila, sebastien.gerard}@cea.fr 2 Malina Software Corporation 10 Blueridge Court, Nepean, Ontario, Canada selic@acm.org Abstract. Using model-based approaches for designing embedded systems helps abstract away unnecessary details in a manner that increases the potential for easy validation and verification, and facilitates reuse and evolution. A common practice is to use UML as the base language, possibly specialized by the so-called profiles. Despite the ever increasing number of profiles being built in many domains, there is still insufficient focus on discussing the issue of combining multiple profiles. Indeed, a single profile may not be adequate to cover all aspects required in the multidisciplinary domain of embedded sys- tems. In this paper, we assess possible strategies for combining the SysML and MARTE profiles in a common modelling framework, while avoiding specifica- tion conflicts. We show that, despite some semantic and syntactical overlap- ping, the two are highly complementary for specifying embedded systems at different abstraction levels. We conclude, however, that a convergence agenda is highly desirable to align some key language features. Keywords: model-based engineering, embedded systems, SysML, MARTE. 1 Introduction The design of embedded systems is a complex process that depends more and more on the effective interplay of multiple disciplines, such as mechanical, electronics, and software engineering. In particular, the lack of a common design language between different disciplines hampers reasoning about system properties. The architecture of a system is particularly vulnerable to bad design choices made in the early design phases, which, unfortunately, often tend to show up later during the integration or construction phases. Designers of one part of the system may make wrong assump- tions concerning some other parts resulting in increasing development costs due to long feedback cycles. The use of models throughout the design process is gaining momentum in address- ing these issues [20]. Models allow designers from different disciplines to share knowledge, facilitate design comprehension, and assess system-level trade-offs seek- ing higher quality and reliability. We subscribe to the view that both system design