On tracing reactive systems

Maoz, Shahar; Harel, David

doi:10.1007/s10270-010-0151-2

Cited by 22 publications

(8 citation statements)

References 48 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The approach was also inspiration for our works. It is worth to note that application of Live Sequence Charts is further developed in (Maoz & Harel, 2011).…”

Section: Discussionmentioning

confidence: 99%

Specification and Validation of Real-Time Systems Using UML Sequence Diagrams

Huzar¹,

Walkowiak²

2012

Real-Time Systems, Architecture, Scheduling, and Application

View full text Add to dashboard Cite

“…The approach was also inspiration for our works. It is worth to note that application of Live Sequence Charts is further developed in (Maoz & Harel, 2011).…”

Section: Discussionmentioning

confidence: 99%

Specification and Validation of Real-Time Systems Using UML Sequence Diagrams

Huzar¹,

Walkowiak²

2012

Real-Time Systems, Architecture, Scheduling, and Application

View full text Add to dashboard Cite

“…Maoz and Harel developed a technique based on live sequence charts to analyze, visualize, and explore execution traces of reactive systems [19]. They follow a goal similar to our work by finding occurrences of scenarios in a larger trace, and checking whether the specification is fulfilled.…”

Section: Related Workmentioning

confidence: 94%

Analyzing Long-Running Controller Applications for Specification Violations Based on Deterministic Replay

Schatz

Prähofer

2012

2012 38th Euromicro Conference on Software Engineering and Advanced Applications

View full text Add to dashboard Cite

Deterministic replay debugging is a technique aimed at finding and debugging software failures occurring in field operation that are usually hard to reproduce. With deterministic replay debugging a software run is recorded, so that it can be reproduced deterministically in a debugger. While deterministic replay debugging is capable of reproducing a failure, in practice, especially in the case of a long-running application, it is still hard for the developer to locate the exact position of the failure in the trace log. Based on our previous work on deterministic replay debugging, we propose an approach to use behavior specifications in the form of test cases to search a recorded trace log. We first present a formal approach for the specification of test cases for PLC applications based on hybrid automata. Then we present a method for searching a recorded program trace for occurrences of the test scenario. That way, we can not only identify regions where a specification violation occurred, but also the corresponding regions in the trace where the test case passed, which can then be further used for comparison. We present the theoretical background of our approach, an implementation of the trace search algorithm, and an example application.

show abstract

“…Moreover, we see an instance of diagram D2 (lines 26-27, 29, and Scenario-based traces, such as the ones discussed above, are difficult to analyze manually and in textual format. Instead, they can be visualized and interactively explored in a prototype tool called the Tracer [32] (first presented in [34]), developed at the Weizmann Institute of Science. It is outside the scope of this paper to present the Tracer in detail.…”

Section: Polymorphic Scenario-based Testingmentioning

confidence: 99%

Polymorphic scenario-based specification models: semantics and applications

Maoz

2010

Softw Syst Model

Self Cite

View full text Add to dashboard Cite

We present polymorphic scenarios, a generalization of a UML2-compliant variant of Damm and Harel's live sequence charts (LSC) in the context of objectorientation. Polymorphic scenarios are visualized using (modal) sequence diagrams where lifelines may represent classes and interfaces rather than concrete objects. Their semantics takes advantage of inheritance and interface realization to allow the specification of most expressive, succinct, and reusable universal and existential inter-object scenarios for object-oriented system models. We motivate the use of polymorphic scenarios, formally define their trace-based semantics, and present their application for scenario-based testing and execution, as implemented in the S2A compiler developed at the Weizmann Institute of Science. We further discuss advanced semantic issues arising from the use of scenarios in a polymorphic setting, suggest possible extensions, present a UML profile to support polymorphic scenarios, consider the application of the polymorphic semantics to other variants of scenario-based specification languages, and position our work in the broader context of behavioral subtyping.

show abstract

On tracing reactive systems

Cited by 22 publications

References 48 publications

Specification and Validation of Real-Time Systems Using UML Sequence Diagrams

Specification and Validation of Real-Time Systems Using UML Sequence Diagrams

Analyzing Long-Running Controller Applications for Specification Violations Based on Deterministic Replay

Polymorphic scenario-based specification models: semantics and applications

Contact Info

Product

Resources

About