<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:922837924;
mso-list-template-ids:-1041972996;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1106000707;
mso-list-template-ids:1466182804;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">=================================================================================</span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Call for Papers:</span></b><o:p></o:p></p>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:"Arial",sans-serif">International Workshop on Multi-Paradigm Modelling for Cyber-Physical Systems (MPM4CPS)</span></i></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">(co-located with the MoDELS 2024 Conference)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">22-24 Septembre 2024 (Exact date to be announced)</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="DE" style="font-size:10.0pt;font-family:"Arial",sans-serif">Linz, Austria</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal"><a href="http://msdl.uantwerpen.be/conferences/MPM4CPS/2022" target="_blank"><span lang="DE">http://msdl.uantwerpen.be/conferences/MPM4CPS/2024</span></a><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">=================================================================================</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:13.5pt">Scope of the Workshop</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Tackling the complexity involved in developing truly complex, designed systems is a topic of intense research and development. System complexity has drastically increased once software components were introduced in the form of embedded systems, controlling
physical parts of the system, and has only grown in CPS, where the networking aspect of the systems and their environment are also considered. The complexity faced when engineering CPS is mostly due to the plethora of cross-disciplinary design alternatives
and inter-domain interactions. To date, no unifying theory or system design methods, techniques, or tools to design, analyze, and ultimately deploy CPS exist. Individual (physical systems, software, and network) engineering disciplines offer only partial solutions
and are no match for the complexity observed in CPS. Multi-Paradigm Modeling (MPM) offers one foundational framework (among others) for gluing the several disciplines together in a consistent way. The inherent complexity of CPS is broken down into different
levels of abstraction and views, each expressed in appropriate modeling formalisms, and organized in specific processes. MPM offers processes and tools that can combine, couple, and integrate each of the views that compose a system.<br>
<br>
MPM encompasses many research topics - from language engineering (for DSLs, including their (visual) syntax and semantics), to processes to support multi-view and multi-abstraction modeling, simulation for system analysis, and deployment. At the core of the
MPM approach lies the notion of choosing the most appropriate formalism(s), process(es), abstraction level(s), etc. to tackle a (engineering) task at hand (designing, deploying, etc.), with the objective of reducing accidental complexity. As a governing principle,
MPM promotes specificity and accuracy to better perform these tasks, while ensuring that all those components integrate as smoothly as possible.<br>
<br>
This year, the Workshop will be organized around group discussions around the topic of appropriateness, leaving limited time (typically in the morning) for paper presentations. We welcome Vision/Expert’s Opinion
<br>
<br>
<b><span style="font-size:13.5pt">Topics of Interest (including, but not limited to)</span></b><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
Appropriateness of approaches, in terms of formalisms, processes, abstraction levels, viewpoints, etc. wrt. captured domain, context, stakeholder experts, etc. regarding definitions, metrics, relevance, methodologies, etc. related to the notion of “the most
appropriate” in MPM4CPS.<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
Foundations of domain-specific modelling, with a particular focus on classifications of the various dimensions around MPM (formalisms; processes; related activities such as V&V, deployment, calibration, etc.; tools, and methodologies);<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
Modelling language engineering, modular design of modelling languages, with a particular focus on de-/composition;<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
Applications of MPM techniques in automotive, aviation, manufacturing, etc.<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
MPM for (self-)adaptive systems<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
MPM approaches, techniques, and tools for related domains: IoT, Digital Twins, SmartCPS<o:p></o:p></li></ul>
<p class="MsoNormal">Technical Contributions should clearly address the foundations of Multi-Paradigm Modeling by demonstrating the use of several models to achieve the stated objectives and discuss the benefits of explicit modeling.<br>
<br>
<b><span style="font-size:13.5pt">Important Dates</span></b><b><br>
</b><br>
<b>Paper submission deadline:</b> 5 July 2024<br>
<br>
<b>Notification of acceptance: </b> 9 August 2024<br>
<br>
<b>Workshop dates:</b> 22--24 September 2024 (exact date TBA)<br>
<br>
<b><span style="font-size:13.5pt">Submission Procedure</span></b><br>
<br>
Papers should be submitted electronically in PDF using the ACM formatting instructions available via EasyChair for one of the following topics.<br>
<br>
<a href="https://easychair.org/conferences/?conf=mpm4cps0" target="_blank">https://easychair.org/conferences/?conf=mpm4cps0</a><br>
<br>
Each submission will be peer-reviewed by at least three PC members.<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<b>Vision papers/Expert’s Opinion (5 pages max, all included)</b> present new ideas, visions, experience feedback, on how, why, and whether it is even relevant, to talk, discuss, and actually practice this moto of “the most appropriate” for each task.<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<b>(Technical) Research papers: short (5 pages max, all included) and long (10 pages max, all included)
</b>present a novel, innovative approach (not completely validated for short papers);<o:p></o:p></li></ul>
<p class="MsoNormal" style="margin-bottom:12.0pt">Technical Research papers will be published with the main conference’s workshop proceedings; authors submitting Vision/Opinions will eventually be invited to contribute to a Special Issue to further develop
their case. <o:p></o:p></p>
<p class="MsoNormal"><span lang="DE">--------------------------------------------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE">PD Dr. rer. nat. Robert Heinrich<o:p></o:p></span></p>
<p class="MsoNormal">Head of Quality-driven System Evolution Research Group<o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">Karlsruhe Institute of Technology (KIT)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">KASTEL – Institute of Information Security and Dependability<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">DSiS – Dependability of Software-intensive Systems group<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="DE"><a href="https://dsis.kastel.kit.edu/staff_robert_heinrich.php"><span lang="EN-US" style="color:blue">https://dsis.kastel.kit.edu/staff_robert_heinrich.php</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>