Editorial to theme section on interplay of model-driven and component-based software engineering
- PDF / 555,910 Bytes
- 3 Pages / 595.276 x 790.866 pts Page_size
- 21 Downloads / 135 Views
GUEST EDITORIAL
Editorial to theme section on interplay of model‑driven and component‑based software engineering Federico Ciccozzi1 · Antonio Cicchetti1 · Andreas Wortmann2 Received: 8 June 2020 / Accepted: 10 June 2020 © Springer-Verlag GmbH Germany, part of Springer Nature 2020
This theme section aims to disseminate the latest trends in the use and combination of Model-Driven Engineering (MDE) and Component-Based Software Engineering (CBSE). On the one hand, MDE aims to increase productivity in the development of complex systems while reducing the time to market. On the other hand, CBSE aims to deliver and then support the exploitation of reusable “off-the-shelf” software components that can be incorporated into larger applications. An effective interplay of MDE and CBSE can yield benefits to both communities: the CBSE community would benefit from implementation and automation capabilities of MDE, the MDE community would benefit from the foundational nature of CBSE. In total, we accepted three submissions for publication in the theme section after a thorough peer-reviewing process.
1 Model‑driven engineering MDE is an established methodology to increase the productivity of complex systems while reducing the time to market. It enables and suggests a shift from code-centric approaches to a more human-centric development, where models represent artefacts closer to human terminology and understanding. These models can be programmatically read and exploited for simplifying the design, implementation, execution, and evolution of software systems. Models are defined with concepts that are less bound to the underlying implementation technology but closer to the * Federico Ciccozzi [email protected] Antonio Cicchetti [email protected] 1
School of Innovation, Design and Engineering, Mälardalen University, Västerås, Sweden
Software Engineering, Department of Computer Science, RWTH Aachen University, Aachen, Germany
2
problem domain, i.e. the concepts the modellers are familiar with. This makes the models easier to specify, understand, and maintain, which facilitates the understanding of complex problems and their potential solutions through abstraction. By leveraging abstract models as primary development artefacts, MDE enables to systematically concentrate on different levels of abstractions, each providing a view for specific stakeholders, for instance (i) improving usability, (ii) enabling customizability in different and specific domains, (iii) promoting reusability of the different algorithms, methods, and techniques, (iv) managing variability and complexity both at design time and run-time, and (v) handling qualities like evolvability, changeability and configurability, modifiability, scalability, power consumption, and dependability. Models and model transformations are the core development artefacts in MDE. In particular, MDE promotes shifting from source code specified in general-purpose programming languages to models expressed in explicit domain-specific modelling languages (DSMLs). DS
Data Loading...
