Detecting Implied Scenarios from Execution Traces

Abstract

Proposes and tests a process of combining expert knowledge of a system with dynamically extracted information in order to produce implied scenarios. Implied scenarios are unforeseen ways that components are expected to interact in their participant scenarios. I.e. the scenarios as designed may imply other scenarios as side-effects.


Notes

  • Scenarios describe system interactions. A sequence diagram is a scenario.
  • Some focus on how different parts of the system, in different scenarios, might cause unforeseen interactions that aren't completely described in individual scenarios.
  • The above are called implied scenarios
  • Both positive and negative implied scenarios. Positive: valid interactions; negative: invalid, and undesired, originating from unexpected interactions.
  • Deals with concurrency
  • Not a single tool, but a pipeline of tools formed into a process.
  • 4-step process (1) select scenarios of interest from documentation, and execution of the scenario using the system; (2) Extract scenario elements from traces; (3) detect implied scenarios; (4) visualize the scenario (using sequence diagrams).
  • requires expert knowlege
  • iterative process of refining scenarios.

BibTeX Reference

@ARTICLE{desousa07wcre, 
title={Detecting Implied Scenarios from Execution Traces}, 
author={Cantal de Sousa, F. and Mendonca, N.C. and Uchitel, S. and Kramer, J.}, 
journal={Reverse Engineering, 2007. WCRE 2007. 14th Working Conference on}, 
year={2007}, 
month={Oct.}, 
volume={}, 
number={}, 
pages={50-59}, 
abstract={A scenario describes how one or more system components interact to provide a certain set of functionalities. Because each scenario only represents a partial view of the overall system behavior, scenario-based specifications may hide unexpected interactions (called implied scenarios) which are not part of any scenario individually. Implied scenarios may either indicate gaps in the original scenario specification, or undesired behavior that should be avoided during scenario implementation. This paper presents a reverse engineering environment to support extraction and detection of implied scenarios from execution traces. The main contribution of the paper is to demonstrate how the concept of implied scenarios, thus far restricted to early phases of the software life-cycle, such as requirements elaboration and reliability prediction, can also be applied to support comprehension and testing of existing systems.}, 
keywords={formal specification, program diagnostics, program testing, reverse engineering, software prototypingexecution trace, formal specification, implied scenario detection, program comprehension, program testing, reverse engineering, software life-cycle}, 
doi={10.1109/WCRE.2007.19}, 
ISSN={1095-1350}, }
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License