Details
| Original language | English |
|---|---|
| Title of host publication | MODELSWARD 2018 - Proceedings of the 6th International Conference on Model-Driven Engineering and Software Development |
| Editors | Slimane Hammoudi, Luis Ferreira Pires, Bran Selic |
| Pages | 560-566 |
| Number of pages | 7 |
| ISBN (electronic) | 9789897582837 |
| Publication status | Published - 2018 |
| Event | 6th International Conference on Model-Driven Engineering and Software Development, MODELSWARD 2018 - Funchal, Portugal Duration: 22 Jan 2018 → 24 Jan 2018 |
Abstract
Scenario-based specification approaches offer system engineering advantages with their intuitiveness, exe-cutability, and amenability to formal verification and synthesis. However, many engineering tasks such as debugging or maintenance are still far from trivial even when using such specifications. Specifically, it is hard to find out why a complex system behaves as it does, or how it would behave under certain conditions. Here, we present work in progress towards the (semi-)automatic analysis of event traces emanating from simulation runs and actual executions. These traces may be large, yet developers are often interested only in specific properties thereof, like is any specification property violated? are particular properties demonstrated? is there a smaller sub-sequence of events that violates or demonstrates the same properties? which trace properties are common to multiple traces and which are unique? etc. Our approach includes automatic techniques for discovering and distilling relevant properties of traces, analyzing properties of sets of traces, using (sets of) execution traces for understanding specified and actual system behavior and problems therein, planning system enhancement and repair, and more. Our work leverages and extends existing work on trace summarization, formal methods for model analysis, specification mining from execution traces, and others, in the context of scenario-based specifications. A key guiding perspective for this research is that interesting properties of a trace often can be associated with one or very few concise scenarios, depicting desired or forbidden behavior, which are already in the specification, or should be added to it.
Keywords
- Abstraction, Behavioral Programming, Debugging, Event Log, Execution Trace, Program Repair, Scenario-based Programming, Software Engineering, System Engineering
ASJC Scopus subject areas
- Computer Science(all)
- Software
Cite this
- Standard
- Harvard
- Apa
- Vancouver
- BibTeX
- RIS
MODELSWARD 2018 - Proceedings of the 6th International Conference on Model-Driven Engineering and Software Development. ed. / Slimane Hammoudi; Luis Ferreira Pires; Bran Selic. 2018. p. 560-566.
Research output: Chapter in book/report/conference proceeding › Conference contribution › Research › peer review
}
TY - GEN
T1 - Towards systematic and automatic handling of execution traces associated with scenario-based models
AU - Greenyer, Joel
AU - Gritzner, Daniel
AU - Harel, David
AU - Marron, Assaf
N1 - Funding information: This work has been funded in part by grants from the German-Israeli Foundation for Scientific Research and Development (GIF) and from the Israel Science Foundation (ISF).
PY - 2018
Y1 - 2018
N2 - Scenario-based specification approaches offer system engineering advantages with their intuitiveness, exe-cutability, and amenability to formal verification and synthesis. However, many engineering tasks such as debugging or maintenance are still far from trivial even when using such specifications. Specifically, it is hard to find out why a complex system behaves as it does, or how it would behave under certain conditions. Here, we present work in progress towards the (semi-)automatic analysis of event traces emanating from simulation runs and actual executions. These traces may be large, yet developers are often interested only in specific properties thereof, like is any specification property violated? are particular properties demonstrated? is there a smaller sub-sequence of events that violates or demonstrates the same properties? which trace properties are common to multiple traces and which are unique? etc. Our approach includes automatic techniques for discovering and distilling relevant properties of traces, analyzing properties of sets of traces, using (sets of) execution traces for understanding specified and actual system behavior and problems therein, planning system enhancement and repair, and more. Our work leverages and extends existing work on trace summarization, formal methods for model analysis, specification mining from execution traces, and others, in the context of scenario-based specifications. A key guiding perspective for this research is that interesting properties of a trace often can be associated with one or very few concise scenarios, depicting desired or forbidden behavior, which are already in the specification, or should be added to it.
AB - Scenario-based specification approaches offer system engineering advantages with their intuitiveness, exe-cutability, and amenability to formal verification and synthesis. However, many engineering tasks such as debugging or maintenance are still far from trivial even when using such specifications. Specifically, it is hard to find out why a complex system behaves as it does, or how it would behave under certain conditions. Here, we present work in progress towards the (semi-)automatic analysis of event traces emanating from simulation runs and actual executions. These traces may be large, yet developers are often interested only in specific properties thereof, like is any specification property violated? are particular properties demonstrated? is there a smaller sub-sequence of events that violates or demonstrates the same properties? which trace properties are common to multiple traces and which are unique? etc. Our approach includes automatic techniques for discovering and distilling relevant properties of traces, analyzing properties of sets of traces, using (sets of) execution traces for understanding specified and actual system behavior and problems therein, planning system enhancement and repair, and more. Our work leverages and extends existing work on trace summarization, formal methods for model analysis, specification mining from execution traces, and others, in the context of scenario-based specifications. A key guiding perspective for this research is that interesting properties of a trace often can be associated with one or very few concise scenarios, depicting desired or forbidden behavior, which are already in the specification, or should be added to it.
KW - Abstraction
KW - Behavioral Programming
KW - Debugging
KW - Event Log
KW - Execution Trace
KW - Program Repair
KW - Scenario-based Programming
KW - Software Engineering
KW - System Engineering
UR - http://www.scopus.com/inward/record.url?scp=85052012739&partnerID=8YFLogxK
U2 - 10.5220/0006671105600566
DO - 10.5220/0006671105600566
M3 - Conference contribution
AN - SCOPUS:85052012739
SP - 560
EP - 566
BT - MODELSWARD 2018 - Proceedings of the 6th International Conference on Model-Driven Engineering and Software Development
A2 - Hammoudi, Slimane
A2 - Pires, Luis Ferreira
A2 - Selic, Bran
T2 - 6th International Conference on Model-Driven Engineering and Software Development, MODELSWARD 2018
Y2 - 22 January 2018 through 24 January 2018
ER -