The MegaM@Rt2 ECSEL project: MegaModelling at Runtime – Scalable model-based framework for continuous development and runtime validation of complex systems

TLDR: This paper presents an overview of the ECSEL 1 project entitled “MegaModelling at runtime – Scalable model-based framework for continuous development and runtime validation of complex systems” (MegaM@Rt2), whose aim is to address the above mentioned challenges facing MDE.

About: This article is published in Microprocessors and Microsystems.The article was published on 2018-09-01 and is currently open access. It has received 30 citations till now. The article focuses on the topics: System lifecycle & Model-driven architecture.

Figures

Figure 2: The MegaM@Rt2 Consortium.

Figure 5: WP4 – Model and Traceability Management approach.

Table 1: Case studies from MegaM@Rt2 Partners.

Figure 2.1: Market & technology Value Chains - In order to deliver excellent results the MegaM@Rt project involves partners covering the market and technology value chains.

Figure 1: The MegaM@Rt2 Overall Approach.

Table 2: MegaM@Rt2 Research Partners.

Frequently asked questions

Q1. What are the contributions mentioned in the paper "Ecsel project: megamodelling at runtime - scalable model-based framework for continuous development" ?

This paper presents an overview of the ECSEL project entitled “ MegaModelling at runtime – Scalable model-based framework for continuous development and runtime validation of complex systems ” ( MegaM @ Rt2 ), whose aim is to address the above mentioned challenges facing MDE. Driven by both large and small industrial enterprises, with the support of research partners and technology providers, MegaM @ Rt2 aims to deliver a framework of tools and methods for: 1 ) system engineering/design and continuous development, 2 ) related runtime analysis and 3 ) global models and traceability management. This paper provides an overview of the MegaM @ Rt2 project with respect to its approach, mission, objectives as well as to its implementation details. It further introduces the consortium as well as describes the work packages and few already produced deliverables. 

Q2. What are the future works mentioned in the paper "Ecsel project: megamodelling at runtime - scalable model-based framework for continuous development" ?

The authors plan to practically realize this by providing the required management and traceability support between all590 the involved models ( both at design time and runtime ). 

Q3. What is the main role of ATOS?

ATOS will contribute to model simulation task force and code generation by providing development for Foundational UML (fUML) and AspectJ. 

Q4. who will contribute to the MegaM@Rt2 framework?

Space Systems Finland Ltd. – SSF (FI) will contribute to the MegaM@Rt2280framework with the LIME toolset for runtime monitoring of the implementations and automatic test generation, which was partially funded by SSF. 

Q5. What can be done to solve problems at runtime?

Verification and validation issues can be managed directly at runtime, enabling the detection of problems that can be solved at runtime or propagated back to design level. 

Q6. What are the main challenges identified in the WP4 deliverable?

Among others,525the following big challenges have been identified as important in their respective research areas: scalable model storage and querying, well-synchronized and verified model views, performant and decentralized global model management, efficient integration of inter-model traceability and interoperability support. 

Q7. What are the main objectives of the MegaM@Rt2 project?

Tool vendors, engineering tools and technology providers, will integrate their existing products with the MegaM@Rt technologies and will build new products based on the open source results from MegaM@Rt. 

Q8. What is the main focus of FTS?

Fent Innovative Software Solutions – FTS (ES) expertise is focused on265the development of execution platforms for mixed criticality systems. 

Q9. What is the main expected result of MegaM@Rt2?

The main expected result of MegaM@Rt2 is a practical framework incor-porating methods and tools for continuous system engineering and validation. 

Q10. What is the main objective of the MegaM@Rt2?

Technology availability and support during extended period (e.g., up to30 years in the railways).– MegaM@Rt2 open source solutions support this requirement. 

Q11. What is the main objective of MegaM@Rt2?

MegaM@Rt2 achieves this in part through reducing development and exploitation costs and in part by allowing mastery of more complex systems. 

Q12. What are the specific views of the MegaM@Rt2?

Specific views focus on specific areas of the development from system to software level, including the system functional, logical and physical decomposition, identification of software and hardware components, definition of functional and non-functional proper-410ties, software architecture, data, behavior and algorithmic modeling. 

Q13. What is the main challenge in the MDE of critical software systems?

The system behavior at runtime has to be matched with the design in order to fully understand critical situations, failures in design, and deviations from requirements. 

Q14. What is the main goal of the WP4 deliverable?

The main goal of WP4 is to elaborate on the required glue between the artifacts produced in WP2 (e.g., design models) and the ones produced in WP3 (e.g., runtime models). 

Q15. What are the main components of the MegaM@Rt Framework?

The Framework regroups several interconnected tool sets including tool sets for Holistic System Engineering, Model and Traceability Management as well as for Runtime Analysis. 

Q16. What is the main theme of the MegaM@Rt2?

190• Convergent combination of multi-domains industrial practices.– MegaM@Rt2 supports this challenge with multi-domain case studies.• 

Q17. How is the project designed to de-500liver its results?

WP4 is designed to de-500liver its results incrementally, notably by collecting progressively feedback on the developed features from their application to the project use cases. 

Q18. What is the purpose of the megamodeling?

a scalable megamodelling ap-125proach is required to manage all the involved artifacts e.g., the many different models, corresponding work flows, configurations, etc. and to better tackle their large diversity in terms of nature, number, size, complexity, etc. 

Q19. What motivated the consortium to continue with MegaM@Rt2?

The overly positive and instructive remarks motivated us to continue with MegaM@Rt2 in 2016, and a proposal was submitted for the research and innovation action in the call H2020-ECSEL2016-RIA, by reinforcing the consortium and clearing the project details. 

Q20. What is the main argument of the MegaM@Rt2 consortium?

The MegaM@Rt2 consortium argues that investment in capabil-160ity of the software development tools market, although only a fraction, has a very large pay-off.