Mining modal scenarios from execution traces

David Lo*, Shahar Maoz, Siau Cheng Khoo

*Corresponding author for this work

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

Abstract

Specification mining is a dynamic analysis process aimed at automatically inferring suggested specifications of a program from its execution traces. We describe a method, a framework, and a tool, for mining inter-object scenariobased specifications in the form of a UML2-compliant variant of Damm and Harel's Live Sequence Charts (LSC), which extends the classical partial order semantics of sequence diagrams with temporal liveness and symbolic class level lifelines, in order to generate compact and expressive specifications. Moreover, we use previous research work and tools developed for LSC to visualize, analyze, manipulate, test, and thus evaluate the scenario-based specifications we mine. Our mining framework is supported by statistically sound metrics. We demonstrate and evaluate our work using a case study.

Original languageEnglish
Title of host publicationProceedings of the Conference on Object-Oriented Programming Systems, Languages, and Applications, OOPSLA 2007 - Companion
Pages777-778
Number of pages2
DOIs
StatePublished - 2007
Externally publishedYes
Event22nd International Conference on Object-Oriented Programming Systems, Languages, and Applications, OOPSLA 2007 - Companion - Montreal, QC, Canada
Duration: 21 Oct 200725 Oct 2007

Publication series

NameProceedings of the Conference on Object-Oriented Programming Systems, Languages, and Applications, OOPSLA

Conference

Conference22nd International Conference on Object-Oriented Programming Systems, Languages, and Applications, OOPSLA 2007 - Companion
Country/TerritoryCanada
CityMontreal, QC
Period21/10/0725/10/07

Keywords

  • Live sequence charts
  • Specification mining
  • UML sequence diagrams

Fingerprint

Dive into the research topics of 'Mining modal scenarios from execution traces'. Together they form a unique fingerprint.

Cite this