Towards a tracing framework for Model-Driven software systems

Fazilat Hojaji, Bahman Zamani, Abdelwahab Hamou-Lhadj

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Understanding software behavior by analyzing its execution traces is an important enabler for many software engineering tasks. In Model-Driven Development (MDD), dynamic analysis methods are often used to analyze executable models to enable the understanding of software behavior in early stages of the development process. An execution trace of a model can provide information to help reason about executable models. However, understanding an execution trace is not an easy task due to the size and complexity of typical traces. In this work, we aim at tackling this problem by proposing a model tracing framework, comprising compaction techniques to simplify the analysis of large traces at a higher level of abstraction, and a model tracing language, to capture run-time behavior of the executed model adequately.

Original languageEnglish
Title of host publication2016 6th International Conference on Computer and Knowledge Engineering, ICCKE 2016
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages298-303
Number of pages6
ISBN (Electronic)9781509035861
DOIs
Publication statusPublished - 29 Dec 2016
Externally publishedYes
Event6th International Conference on Computer and Knowledge Engineering, ICCKE 2016 - Mashhad, Iran, Islamic Republic of
Duration: 20 Oct 2016 → …

Publication series

Name2016 6th International Conference on Computer and Knowledge Engineering, ICCKE 2016

Conference

Conference6th International Conference on Computer and Knowledge Engineering, ICCKE 2016
Country/TerritoryIran, Islamic Republic of
CityMashhad
Period20/10/16 → …

Keywords

  • Dynamic Analysis
  • Executable Model
  • Model Driven Development
  • Model Tracing

Fingerprint

Dive into the research topics of 'Towards a tracing framework for Model-Driven software systems'. Together they form a unique fingerprint.

Cite this