Present and Ulterior Software Engineering 2017
DOI: 10.1007/978-3-319-67425-4_7
|View full text |Cite
|
Sign up to set email alerts
|

The Changing Face of Model-Driven Engineering

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
3
1
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(3 citation statements)
references
References 20 publications
0
3
0
Order By: Relevance
“…The third benefit relates to addressing the need of assuring a number of "-ilities" within the metamodel, which must take a central role in the design of CPS where undesired behaviors can lead to accidents. These three benefits summarize the difference between the Vitech MBSE metamodel and the metamodel presented in this paper and ultimately our contributions to model federation, a significant challenge facing MBSE at large [61].…”
Section: Itemmentioning
confidence: 86%
“…The third benefit relates to addressing the need of assuring a number of "-ilities" within the metamodel, which must take a central role in the design of CPS where undesired behaviors can lead to accidents. These three benefits summarize the difference between the Vitech MBSE metamodel and the metamodel presented in this paper and ultimately our contributions to model federation, a significant challenge facing MBSE at large [61].…”
Section: Itemmentioning
confidence: 86%
“…The third benefit relates to addressing the need of assuring a number of "-ilities" within the metamodel, which must take a central role in the design of CPS where undesired behaviors can lead to accidents. These three benefits summarize the difference between the Vitech MBSE metamodel and the metamodel presented in this paper and ultimately our contributions to model federation, a significant challenge facing MBSE at large [48].…”
Section: Ontological Metamodel For Safety Security and Resiliencementioning
confidence: 86%
“…In particular, there exist no methodological considerations on how and when new or adaptations of existing modeling languages have to be introduced into a development process. (Paige et al 2017) present four steps of a quasi typical model-driven engineering process: to construct, or to select modeling languages, to build, persist, and manage models. This suggested process is limited to the handling of models and lacks concrete activities for problem decomposition and assessment, as well as DSL engineering and generator engineering.…”
Section: Related Workmentioning
confidence: 99%