Scenario-Based Monitoring and Testing of Real-Time UML Models

Lettrari, Marc; Klose, Jochen

doi:10.1007/3-540-45441-1_24

Cited by 40 publications

(23 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Live sequence charts have been used for testing and verification of system models. Lettrari and Klose [20] present a methodology supported by a tool called TestConductor, which is integrated into Rhapsody [18]. The tool is used for monitoring and testing a model using a restricted subset of LSCs.…”

Section: Related Workmentioning

confidence: 99%

Temporal Logic for Scenario-Based Specifications

Kugler

Harel

Pnueli

et al. 2005

Tools and Algorithms for the Construction and Analysis of Systems

View full text Add to dashboard Cite

Abstract. We provide semantics for the powerful scenario-based language of live sequence charts (LSCs). We show how the semantics of live sequence charts can be captured using temporal logic. This is done by studying various subsets of the LSC language and providing an explicit translation into temporal logic. We show how a kernel subset of the LSC language (which omits variables, for example) can be embedded within the temporal logic CTL * . For this kernel subset the embedding is a strict inclusion. We show that existential charts can be expressed using the branching temporal logic CTL while universal charts are in the intersection of linear temporal logic and branching temporal logic LTL ∩ CTL. Since our translations are efficient, the work described here may be used in the development of tools for analyzing and executing scenario-based requirements and for verifying systems against such requirements.

show abstract

Section: Related Workmentioning

confidence: 99%

Temporal Logic for Scenario-Based Specifications

Kugler

Harel

Pnueli

et al. 2005

Tools and Algorithms for the Construction and Analysis of Systems

View full text Add to dashboard Cite

show abstract

“…The popularity and intuitive visual nature of sequence diagrams as a specification language in general, together with the additional unique features of LSC -in particular, the universal interpretation and its expressive power, motivate our choice for the target formalism of our mining work. Moreover, the choice is supported by previous work on LSC (see, e.g., [20,24,32]), which can potentially be used to visualize, analyze, manipulate, test, and verify the specifications we mine (see [29]). Still, one may consider other scenario-based formalisms with different semantics as targets for mining (e.g., [38]), or, more generally, the mining of other useful behavioral patterns [11].…”

Section: Discussionmentioning

confidence: 99%

Scenario-based and value-based specification mining: better together

Maoz

2012

Autom Softw Eng

View full text Add to dashboard Cite

Specification mining takes execution traces as input and extracts likely program invariants, which can be used for comprehension, verification, and evolution related tasks. In this work we integrate scenario-based specification mining, which uses data-mining algorithms to suggest ordering constraints in the form of live sequence charts, an inter-object, visual, modal, scenario-based specification language, with mining of value-based invariants, which detects likely invariants holding at specific program points. The key to the integration is a technique we call scenario-based slicing, running on top of the mining algorithms to distinguish the scenario-specific invariants from the general ones. The resulting suggested specifications are rich, consisting of modal scenarios annotated with scenario-specific value-based invariants, referring to event parameters and participating object properties.An evaluation of our work over a number of case studies shows promising results in extracting expressive specifications from real programs, which could not be extracted previously. The more expressive the mined specifications, the higher their potential to support program comprehension and testing.

show abstract

“…An operational semantics for LCS, termed play-out, was defined and implemented in [26,27]. The language has been the subject of research in the areas of scenario-based programming, synthesis, verification, specification mining, and testing (see, e.g., [23,36,40,42,45]). …”

Section: Live Sequence Chartsmentioning

confidence: 99%

On tracing reactive systems

Maoz

Harel

2010

Softw Syst Model

View full text Add to dashboard Cite

We present a rich and highly dynamic technique for analyzing, visualizing, and exploring the execution traces of reactive systems. The two inputs are a designer's interobject scenario-based behavioral model, visually described using a UML2-compliant dialect of live sequence charts (LSC), and an execution trace of the system. Our method allows one to visualize, navigate through, and explore, the activation and progress of the scenarios as they "come to life" during execution. Thus, a concrete system's runtime is recorded and viewed through abstractions provided by behavioral models used for its design, tying the visualization and exploration of system execution traces to model-driven engineering. We support both event-based and real-time-based tracing, and use details-on-demand mechanisms, multi-scaling grids, and gradient coloring methods. Novel model exploration techniques include semanticsbased navigation, filtering, and trace comparison. The ideas are implemented and tested in a prototype tool called the Tracer.

show abstract

Scenario-Based Monitoring and Testing of Real-Time UML Models

Cited by 40 publications

References 3 publications

Temporal Logic for Scenario-Based Specifications

Temporal Logic for Scenario-Based Specifications

Scenario-based and value-based specification mining: better together

On tracing reactive systems

Contact Info

Product

Resources

About