Model-Driven Program Transformation of a Large Avionics Framework

Gray, Jeffrey G.; Zhang, Jing; Lin, Yuehua; Roychoudhury, Suman; Wu, Hui; Sudarsan, Rajesh; Gokhale, Aniruddha; Neema, Sandeep; Feng, Shi; Bapty, Ted

doi:10.1007/978-3-540-30175-2_19

Cited by 28 publications

(18 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Gray et al [44] describe another approach to supporting model-driven evolution, which they call model-driven program translation. In this approach, model evolution translates to changes in code transformation software.…”

Section: Model-driven Program Transformationmentioning

confidence: 99%

Supporting fine-grained generative model-driven evolution

et al. 2010

View full text Add to dashboard Cite

In the standard generative Model-driven Architecture (MDA), adapting the models of an existing system requires re-generation and restarting of that system. This is due to a strong separation between the modeling environment and the runtime environment. Certain current approaches remove this separation, allowing a system to be changed smoothly when the model changes. These approaches are, however, based on interpretation of modeling information rather than on generation, as in MDA. This paper describes an architecture that supports fine-grained evolution combined with generative model-driven development. Fine-grained changes are applied in a generative model-driven way to a system that has itself been developed in this way. To achieve this, model changes must be propagated correctly toward impacted elements. The impact of a model change flows along three dimensions: implementation, data (instances), and modeled dependencies. These three dimensions are explicitly represented in an integrated modeling-runtime environment to enable traceability. This implies a fundamental rethinking of MDA.

show abstract

Section: Model-driven Program Transformationmentioning

confidence: 99%

Supporting fine-grained generative model-driven evolution

et al. 2010

View full text Add to dashboard Cite

show abstract

“…-Task: extract* OR transform* OR generat* . These are simple yet sufficient to identify relevant papers since any reverse engineering objective and application must employ some sort of transformation; For example, extraction and generation can be regarded as types of vertical transformations (Gray et al 2004). …”

Section: Systematic Literature Reviewmentioning

confidence: 99%

ProMeTA: a taxonomy for program metamodels in program reverse engineering

2018

View full text Add to dashboard Cite

To support program comprehension, maintenance, and evolution, metamodels are frequently used during program reverse engineering activities to describe and analyze constituents of a program and their relations. Reverse engineering tools often define their own metamodels according to the intended purposes and features. Although each metamodel has its own advantages, its limitations may be addressed by other metamodels. Existing works have evaluated and compared metamodels and tools, but none have considered all the possible characteristics and limitations to provide a comprehensive guideline for classifying, comparing, reusing, and extending program metamodels. To aid practitioners and researchers in classifying, comparing, reusing, and extending program metamodels and their corresponding reverse engineering tools according to the intended goals, we establish a conceptual framework with definitions of program metamodels and related concepts. We confirmed that any reverse engineering activity can be clearly described as a pattern based on the framework from the viewpoint of program metamodels. Then the framework is used (2018) 23:2323-2358 to provide a comprehensive taxonomy, named Program Metamodel TAxonomy (ProMeTA), which incorporates newly identified characteristics into those stated in previous works, which were identified via a systematic literature review (SLR) on program metamodels, while keeping the orthogonality of the entire taxonomy. Additionally, we validate the taxonomy in terms of its orthogonality and usefulness through the classification of popular metamodels.Empir Software Eng

show abstract

“…The modeldriven approach for assertion checking proposed in [26] relies on the principles of aspect-oriented programming and uses a technique called two-level aspect weaving. First, crosscutting assertions defined using ECL, an extension of OCL, are weaved into a model defined within GME (Generic Modeling Environment [27]) and then the code for checking the contracts specified in the models is generated using model-driven program transformations [28]. ECL does not support the expression of temporal constraints.…”

Section: Related Workmentioning

confidence: 99%

A Model-Driven Approach to Trace Checking of Pattern-Based Temporal Properties

Wei¹,

Bianculli²,

Briand³

2017

2017 ACM/IEEE 20th International Conference on Model Driven Engineering Languages and Systems (MODELS)

View full text Add to dashboard Cite

Abstract-Trace checking is a procedure for evaluating requirements over a log of events produced by a system. This paper deals with the problem of performing trace checking of temporal properties expressed in TemPsy, a pattern-based specification language. The goal of the paper is to present a scalable and practical solution for trace checking, which can be used in contexts where relying on model-driven engineering standards and tools for property checking is a fundamental prerequisite.The main contributions of the paper are: a model-driven trace checking procedure, which relies on the efficient mapping of temporal requirements written in TemPsy into OCL constraints on a meta-model of execution traces; the implementation of this trace checking procedure in the TEMPSY-CHECK tool; the evaluation of the scalability of TEMPSY-CHECK, applied to the verification of real properties derived from a case study of our industrial partner, including a comparison with a state-of-theart alternative technology based on temporal logic. The results of the evaluation show the feasibility of applying our modeldriven approach for trace checking in realistic settings: TEMPSY-CHECK scales linearly with respect to the length of the input trace and can analyze traces with one million events in about two seconds.

show abstract

Model-Driven Program Transformation of a Large Avionics Framework

Cited by 28 publications

References 20 publications

Supporting fine-grained generative model-driven evolution

Supporting fine-grained generative model-driven evolution

ProMeTA: a taxonomy for program metamodels in program reverse engineering

A Model-Driven Approach to Trace Checking of Pattern-Based Temporal Properties

Contact Info

Product

Resources

About