ModComp'18

5th International Workshop on Interplay of Model-Driven and Component-Based Software Engineering (ModCamp '18)

Scope

Model-Driven Engineering (MDE) and Component-Based Software Engineering (CBSE) have been proven to effectively reduce software development complexity by (i) shifting the focus from source code to models and (ii) breaking down the set of desired features and their intricacy into smaller sub-modules, respectively. Moreover, the interplay of MDE and CBSE approaches is gaining recognition as a very promising means to boost the development of software systems by reducing costs and risks and shorten time-to-market. While several attempts to effectively combine MDE and CBSE have been documented, there are still unsolved clashes raising when exploiting interplay of MDE and CBSE, mostly due to mismatches in the related terminology as well as to differences in their basic essence.

As satellite event of MoDELS, the goal of ModComp'18 is to gather researchers and practitioners to share opinions, propose solutions to open challenges and generally explore the frontiers of interweaving between MDE and CBSE.

Topics

ModComp'18 aims at attracting contributions related to the subject at different levels, from modelling to analysis, from componentization to composition, from consistency to versioning; foundational contributions as well as concrete application experiments are sought.
In this direction topics of interest for ModComp’16 include, but are not limited to, the following:

• Partial model reuse: once individual components are modelled (interfaces and behavior), these models should be reusable in the different usage contexts of these components;
• Model composition: building a system model by composition of pre-existing models of individual components;
• Component versioning: in order to handle evolution when for instance one component is upgraded to a newer version;
• Modelling component interaction and component behaviours: clear separation of internal behaviour and externally visible interaction capabilities, e.g. by interface protocols;
• Model extraction for componentization of legacy systems: when legacy systems are componentized, generation of architectural and behavioural models from, e.g., implementation artefacts is needed in order to get full support from model-based activities such as analysis, e.g. if those components are reused in a new context. Along with implementation artefacts, other kinds of information regarding any observation of the system at runtime, such as, e.g., log files, system execution traces, traces, might need to be considered for reverse componentization;
• Component interoperability: in order to enable the automated construction of semantic matching and mapping between different modelling notations (e.g., component models) with emphasis on precise syntactic, protocol and operational descriptions of components
• Management and elicitation of model interdependencies: in order to infer and support automated reasoning on the possible interdependencies between the different software models exploited throughout the software life cycle;
• Component models evolution: tackling challenges in component models evolution and model co-evolution which are amplified by the high degree of interchangeability typical of CBSE;
• Model transformations in presence of third-party components: exploring how model-driven techniques may deal with third-party components, especially concerning the preservation of system properties (both functional and extra-functional) along the involved model manipulations for e.g. analysis, code generation, etc;
• - Metamodel modularity: reasoning on issues related to composability of (i) metamodels and (ii) views in terms of metamodel portions;
• Composition of MDE artefacts: analysis results, model transformations, and/or model viewpoints could take advantage of CBSE advancements in order to ease their reuse, and composition;
• Enforcement of incrementality: models and model manipulations to support incremental verification and validation of component-based systems;
• Case studies & applications: best practices applied to real world applications, lessons learned, success/failure stories in intertwining MDE and CBSE.