WeizmannWiki - User contributions [en]

PlayGo

2010-10-18T13:42:57Z

Shahar.maoz:

Welcome to PlayGo, a comprehensive tool for scenario-based programming, built around the language of [[live sequence charts| live sequence charts (LSC)]] and its Java derivative, and the Play-in/Play-out approach.

PlayGo is intended to constitute extensive support to the vision of [http://www.wisdom.weizmann.ac.il/~harel/papers/LiberatingProgramming.pdf Liberating Programming]

* [[About PlayGo]]
* [[PlayGo Screenshots]]
* [[PlayGo Demos]]
* [[Download PlayGo]]
* [[Getting Started with PlayGo]]
* [[PlayGo HowTo]]

== Related Tools ==
* [[The Tracer]], a prototype tool for scenario-based trace visualization and exploration.
* [[S2A]], a compiler for multi-modal UML sequence diagrams.

== Contact Information ==
E-mail us to: [mailto:playgo@weizmann.ac.il playgo@weizmann.ac.il]

The LSC Compiler

2010-10-18T13:38:31Z

Shahar.maoz:

S2A, standing for Scenarios to Aspects, is a compiler that translates Modal UML Sequence Diagrams (MSDs), a UML-compliant variant of [[live sequence charts]] (LSCs), into [http://www.eclipse.org/aspectj/ AspectJ] code. It thus provides full code generation of reactive behavior from visual inter-object scenario-based specifications. The compilation scheme for S2A was presented by [http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel] in 2006.

More about S2A can be found in the references below. As of 2010, S2A is part of [[PlayGo]].

== References ==

*[http://www.se-rwth.de/~maoz/ Shahar Maoz], [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], and Asaf Kleinbort, '''A Compiler for Multi-Modal Scenarios: Transforming LSCs into AspectJ''', ''ACM Trans. on Soft. Eng. and Method.'' (TOSEM). Accepted November 2009. To appear.

*Yoram Atir, [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], Asaf Kleinbort, and [http://www.se-rwth.de/~maoz/ Shahar Maoz], '''Object Composition in Scenario-Based Programming''', ''Proc. 11th Int. Conf. on Fundamental Approaches to Software Engineering'' (FASE'08), vol. 4961 of LNCS, Springer-Verlag, 2008, pp. 301-316.

*[http://www.wisdom.weizmann.ac.il/~harel/ David Harel], Asaf Kelinbort, and [http://www.se-rwth.de/~maoz/ Shahar Maoz], '''S2A: A Compiler for Multi-Modal UML Sequence Diagrams''', ''Proc. 10th Int. Conf. on Fundamental Approaches to Soft. Eng.'' (FASE'07), vol. 4422 of LNCS, Springer, 2007, pp. 121-124.

*[http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], '''From Multi-Modal Scenarios to Code: Compiling LSCs into AspectJ''', ''Proc. 14th ACM SIGSOFT Symp. on Foundations of Software Engineering'' (SIGSOFT FSE'06), ACM, 2006, pp. 219-230.

Tracer's gellary: C. elegans case study

2010-10-18T13:32:04Z

Shahar.maoz: C. elegans moved to Tracer's gellary: C. elegans case study

We have used [[the Tracer]] to visualize and explore different execution traces of the biological system model described in Kam, N., Harel, D., Kugler, H., Marelly, R., Pnueli, A., Hubbard, E.J.A., Stern, M.J.: Formal Modeling of C. elegans Development: A Scenario-Based Approach (C. Priami (ed.) Proc. 1st Int. Workshop on Computational Methods in Systems Biology (CMSB'03), Lecture Notes in Computer Science, vol. 2602, pp. 4-20. Springer (2003)). The model deals with the process of vulval precursor cell fate determination in the development of the C. elegans nematode worm. The model was implemented in the Play-Engine tool. It consists of more than 400 scenarios, divided into 22 use cases. Typical traces are 300-400 events long, and involve 40-80 different scenarios from the model.

Due to the large number of scenarios in the C. elegans model, using the various horizontal filters proved crucial. Moreover, typical traces included several periods with large numbers of multiple active instances of the same scenario (up to 30 such). The Multiplicities supporting view helped us in exploring the details of these multiple copies.

We examined a number of execution traces of this model. Differences between the traces were due to the probabilistic choices inside the LSCs in the model, as played-out by the Play-Engine, and due to our use of different initial configurations, simulating experiments with the worm's wild-type and the various mutations and cell ablations that appear in the C. elegans literature. Using the trace comparison features, we were able to find where such different `experiments' show different behavior and where their behaviors are equivalent.

We thank Itai Segall for implementing trace generation in the Play-Engine and for his help with using this model.

Main view and overview:

[[Image: tracer-celegans-mainviewandoverview.PNG]]

Comparing traces:

[[Image: tracer-celegans-comparingtraces.PNG]]

C. elegans

2010-10-18T13:32:04Z

Shahar.maoz: C. elegans moved to Tracer's gellary: C. elegans case study

#REDIRECT [[Tracer's gellary: C. elegans case study]]

Tracer's gallery: RSS news ticker case study

2010-10-18T13:31:30Z

Shahar.maoz: Tracer's gellary: RSS news ticker case study moved to Tracer's gallery: RSS news ticker case study

We have used [[the Tracer]] to visualize some execution traces of an RSS News Ticker application, previously developed as an example case study for scenario-based execution using the [[S2A]] compiler. The News Ticker is a small desktop application; it downloads RSS news from user defined websites and presents them to the user as continuously scrolling text. Additional features include switching between horizontal and vertical presentation modes, switching between several predefined scrolling speeds, changing the URL for the RSS feeds, and, when a headline is clicked, opening the corresponding news item in the browser window. The model and source code for the News Ticker are available from the S2A website.

The model for the News Ticker application consists of seven scenarios divided into two use cases. The typical traces we used were 8K-10K events long. These rather long traces are due mainly to repeated time tick and text scrolling events. Other events, such as the ones involved in changing the scrolling speed, are relatively rare. By applying the pre-defined vertical filter option `hide inactive ranges' to the use case in which these more rare scenarios are grouped, we were able to automatically exclude most of the trace from the view, leaving a filtered trace showing only the very few and relatively short ranges where the scenarios of interest were active. When this filter was not applied, given the length of the trace, the overview supporting view and the semantics-based navigation options such as `go to next instance' were helpful in browsing the lengthy trace and looking for locations of interest.

Main view:

[[Image: tracer-newsticker-mainview.PNG]]

Vertical filters and metrics:

[[Image: tracer-newsticker-verticalfiltersandmetrics.PNG]]

Tracer's gellary: RSS news ticker case study

2010-10-18T13:31:30Z

Shahar.maoz: Tracer's gellary: RSS news ticker case study moved to Tracer's gallery: RSS news ticker case study

#REDIRECT [[Tracer's gallery: RSS news ticker case study]]

Tracer's gallery: RSS news ticker case study

2010-10-18T13:30:44Z

Shahar.maoz: RSS news ticker moved to Tracer's gellary: RSS news ticker case study

RSS news ticker

2010-10-18T13:30:44Z

Shahar.maoz: RSS news ticker moved to Tracer's gellary: RSS news ticker case study

#REDIRECT [[Tracer's gellary: RSS news ticker case study]]

Smartphone

2010-10-18T13:30:05Z

Shahar.maoz: Smartphone moved to Tracer's gellary: smartphone case study

#REDIRECT [[Tracer's gellary: smartphone case study]]

Tracer's gellary: smartphone case study

2010-10-18T13:30:05Z

Shahar.maoz: Smartphone moved to Tracer's gellary: smartphone case study

In recent work by [http://www.se-rwth.de/~maoz/ Shahar Maoz], Jani Metsä, and [http://www.cs.tut.fi/~clark/ Mika Katara] (MoDELS'09), a modified version of the [[S2A]] compiler, which generates AspectC++ code rather than AspectJ code, was used to execute and monitor scenario-based test cases of a C++ application running on Symbian OS inside a Nokia smartphone (specifically, Nokia model N96). In this work, [[the Tracer]] was used to visualize and explore the progress and results of the different test execution traces.

Most relevant features in this context included the Completions view, which allowed us to identify completed, violated, and vacuous test scenarios, and the Model and Trace Properties window, showing aggregated completion-related information for the entire trace. Thus, we could easily answer questions such as which test scenarios have been violated (if any), how many times has each test scenario been completed, etc. The semantics-based filters, specifically the ones related to completion metrics, allowed us to hide the completed scenarios from the view and focus on the violated ones - those representing tests that have failed and hence require further investigation.

Due to confidentiality restrictions, some details of the study cannot be made public. Thus, all class names, method names, scenario and use case names in the examples we show are obfuscated using generic names.

Main view and overview:

[[Image: tracer-smartphone-mainviewandoverview.PNG]]

Vertical filters:

[[Image: tracer-smartphone-verticalfilters.PNG]]

Comparing global cuts:

[[Image: tracer-smartphone-comparingglobalcuts.PNG]]

Tracer's gellary: C. elegans case study

2010-10-18T13:28:57Z

Shahar.maoz:

Tracer's gellary: C. elegans case study

2010-10-18T13:28:27Z

Shahar.maoz:

We have used [[the Tracer]] to visualize and explore different execution traces of the biological system model described in Kam, N., Harel, D., Kugler, H., Marelly, R., Pnueli, A., Hubbard, E.J.A., Stern, M.J.: Formal Modeling of C. elegans Development: A Scenario-Based Approach (C. Priami (ed.) Proc. 1st Int. Workshop on Computational Methods in Systems Biology (CMSB'03), Lecture Notes in Computer Science, vol. 2602, pp. 4-20. Springer (2003)). The model deals with the process of vulval precursor cell fate determination in the development of the C. elegans nematode worm. The model was implemented in the Play-Engine tool. It consists of more than 400 scenarios, divided into 22 use cases. Typical traces are 300-400 events long, and involve 40-80 different scenarios from the model.

Due to the large number of scenarios in the C. elegans model, using the various horizontal filters proved crucial. Moreover, typical traces included several periods with large numbers of multiple active instances of the same scenario (up to 30 such). The Multiplicities supporting view helped us in exploring the details of these multiple copies.

We examined a number of execution traces of this model. Differences between the traces were due to the probabilistic choices inside the LSCs in the model, as played-out by the Play-Engine, and due to our use of dif- ferent initial congurations, simulating experiments with the worm's wild-type and the various mutations and cell ablations that appear in the C. elegans literature. Using the trace comparison features, we were able to find where such different `experiments' show di erent behavior and where their behaviors are equivalent.

We thank Itai Segall for implementing trace generation in the Play-Engine and for his help with using this model.

Main view and overview:

[[Image: tracer-celegans-mainviewandoverview.PNG]]

Comparing traces:

[[Image: tracer-celegans-comparingtraces.PNG]]

File:Tracer-celegans-comparingtraces.PNG

2010-10-18T13:27:46Z

Shahar.maoz: Trace comparison in the Tracer showing the c. elegans case study

Trace comparison in the Tracer showing the c. elegans case study

File:Tracer-celegans-mainviewandoverview.PNG

2010-10-18T13:27:20Z

Shahar.maoz: Main view and overview of the Tracer showing the c. elegans case study

Main view and overview of the Tracer showing the c. elegans case study

Tracer's gellary: C. elegans case study

2010-10-18T13:26:41Z

Shahar.maoz: New page: We have used the Tracer to visualize and explore different execution traces of the biological system model described in Kam, N., Harel, D., Kugler, H., Marelly, R., Pnueli, A., Hubbard...

We have used [[the Tracer]] to visualize and explore different execution traces of the biological system model described in Kam, N., Harel, D., Kugler, H., Marelly, R., Pnueli, A., Hubbard, E.J.A., Stern, M.J.: Formal Modeling of C. elegans Development: A Scenario-Based Approach (C. Priami (ed.) Proc. 1st Int. Workshop on Computational Methods in Systems Biology (CMSB'03), Lecture Notes in Computer Science, vol. 2602, pp. 4-20. Springer (2003)). The model deals with the process of vulval precursor cell fate determination in the development of the C. elegans nematode worm. The model was implemented in the Play-Engine tool. It consists of more than 400 scenarios, divided into 22 use cases. Typical traces are 300-400 events long, and involve 40-80 different scenarios from the model.

Due to the large number of scenarios in the C. elegans model, using the various horizontal �lters proved crucial. Moreover, typical traces included several periods with large numbers of multiple active instances of the same scenario (up to 30 such). The Multiplicities supporting view helped us in exploring the details of these multiple copies.

We examined a number of execution traces of this model. Differences between the traces were due to the probabilistic choices inside the LSCs in the model, as played-out by the Play-Engine, and due to our use of dif- ferent initial congurations, simulating experiments with the worm's wild-type and the various mutations and cell ablations that appear in the C. elegans literature. Using the trace comparison features, we were able to �nd where such different `experiments' show di erent behavior and where their behaviors are equivalent.

We thank Itai Segall for implementing trace generation in the Play-Engine and for his help with using this model.

Main view and overview:

[[Image: tracer-celegans-mainviewandoverview.PNG]]

Comparing traces:

[[Image: tracer-celegans-comparingtraces.PNG]]

File:Tracer-newsticker-verticalfiltersandmetrics.PNG

2010-10-18T13:23:28Z

Shahar.maoz: Vertical filters and metrics view from the Tracer showing the News Ticker case study

Vertical filters and metrics view from the Tracer showing the News Ticker case study

File:Tracer-newsticker-mainview.PNG

2010-10-18T13:22:50Z

Shahar.maoz: Main view from the Tracer showing the News Ticker case study

Main view from the Tracer showing the News Ticker case study

Tracer's gallery: RSS news ticker case study

2010-10-18T13:22:13Z

Shahar.maoz: New page: We have used the Tracer to visualize some execution traces of an RSS News Ticker application, previously developed as an example case study for scenario-based execution using the [[S2A...

File:Tracer-smartphone-comparingglobalcuts.PNG

2010-10-18T13:18:16Z

Shahar.maoz: Global cuts comparison screen capture from the Tracer's smartphone case study

Global cuts comparison screen capture from the Tracer's smartphone case study

File:Tracer-smartphone-verticalfilters.PNG

2010-10-18T13:17:42Z

Shahar.maoz: Vertical filters screen capture from the Tracer's smartphone case study

Vertical filters screen capture from the Tracer's smartphone case study

File:Tracer-smartphone-mainviewandoverview.PNG

2010-10-18T13:16:48Z

Shahar.maoz: Main view and overview from the Tracer's smartphone case study

Main view and overview from the Tracer's smartphone case study

Tracer's gellary: smartphone case study

2010-10-18T13:16:08Z

Shahar.maoz:

Tracer's gellary: smartphone case study

2010-10-18T12:07:00Z

Shahar.maoz: New page: In recent work by Maoz, Metsä, and Katara (MoDELS'09), a modified version of the S2A compiler, which generates AspectC++ code rather than AspectJ code, was used to execute and monitor sce...

In recent work by Maoz, Metsä, and Katara (MoDELS'09), a modified version of the S2A compiler, which generates AspectC++ code rather than AspectJ code, was used to execute and monitor scenario-based test cases of a C++ application running on Symbian OS inside a Nokia smartphone (specifically, Nokia model N96). In this work, [[the Tracer]] was used to visualize and explore the progress and results of the different test execution traces.

Most relevant features in this context included the Completions view, which allowed us to identify completed, violated, and vacuous test scenarios, and the Model and Trace Properties window, showing aggregated completion-related information for the entire trace. Thus, we could easily answer questions such as which test scenarios have been violated (if any), how many times has each test scenario been completed, etc. The semantics-based filters, specifically the ones related to completion metrics, allowed us to hide the completed scenarios from the view and focus on the violated ones - those representing tests that have failed and hence require further investigation.

Due to confidentiality restrictions, some details of the study cannot be made public. Thus, all class names, method names, scenario and use case names in the examples we show are obfuscated using generic names.

Main view and overview:

[[Image: tracer-smartphone-mainviewandoverview.PNG]]

Tracer's gallery: PacMan game

2010-10-18T11:50:59Z

Shahar.maoz:

The scenario-based execution traces for the examples below were generated for [[the Tracer]] using the [[S2A]] compiler. The program traced for the examples below is adopted from a publicly available Java implementation of the classic [http://www.bennychow.com/ PacMan game].

Main view and overview:

[[Image: mainviewandoverview.PNG]]

Filters:

[[Image: filters.PNG]]

Multiplicity:

[[Image: multiplicity.PNG]]

Comparing traces:

[[Image: comparemainview.PNG]]

Completion information:

[[Image: completioninfo.PNG]]

Event-normalized view:

[[Image: eventnormalized.PNG]]

File:Eventnormalized.PNG

2010-10-18T11:50:14Z

Shahar.maoz: Event normalized view screen capture from the Tracer's PacMan case study

Event normalized view screen capture from the Tracer's PacMan case study

File:Completioninfo.PNG

2010-10-18T11:49:41Z

Shahar.maoz: Completion information screen capture from the Tracer's PacMan case study

Completion information screen capture from the Tracer's PacMan case study

File:Comparemainview.PNG

2010-10-18T11:49:17Z

Shahar.maoz: Compare view screen capture from the Tracer's PacMan case study

Compare view screen capture from the Tracer's PacMan case study

File:Multiplicity.PNG

2010-10-18T11:48:44Z

Shahar.maoz: Multiplicity screen capture from the Tracer's PacMan case study

Multiplicity screen capture from the Tracer's PacMan case study

File:Filters.PNG

2010-10-18T11:48:11Z

Shahar.maoz: Filters screen capture from the Tracer's PacMan case study

Filters screen capture from the Tracer's PacMan case study

Tracer's gallery: PacMan game

2010-10-18T11:47:35Z

Shahar.maoz:

The scenario-based execution traces for the examples below were generated for [[the Tracer]] using the [[S2A]] compiler. The program traced for the examples below is adopted from a publicly available Java implementation of the classic [http://www.bennychow.com/ PacMan game].

Main view and overview:
[[Image: mainviewandoverview.PNG]]

Filters:
[[Image: filters.PNG]]

Multiplicity:
[[Image: multiplicity.PNG]]

Comparing traces:
[[Image: comparemainview.PNG]]

Completion information:
[[Image: completioninfo.PNG]]

Event-normalized view:
[[Image: eventnormalized.PNG]]

File:Mainviewandoverview.PNG

2010-10-18T11:45:03Z

Shahar.maoz: Main view and overview screen capture from the Tracer's PacMan case study.

Main view and overview screen capture from the Tracer's PacMan case study.

Tracer's gallery: PacMan game

2010-10-18T11:35:07Z

Shahar.maoz: New page: The scenario-based execution traces for the examples below were generated for the Tracer using the S2A compiler. The program traced for the examples below is adopted from a public...

The scenario-based execution traces for the examples below were generated for [[the Tracer]] using the [[S2A]] compiler. The program traced for the examples below is adopted from a publicly available Java implementation of the classic [http://www.bennychow.com/ PacMan game].

Main view and overview:
[[Image: mainviewandoverview.PNG]]

Filters:
[[Image:Example.jpg]]

Multiplicity:
[[Image:Example.jpg]]

Comparing traces:
[[Image:Example.jpg]]

Completion information:
[[Image:Example.jpg]]

Event-normalized view:
[[Image:Example.jpg]]

Tracer's gallery

2010-10-18T11:32:17Z

Shahar.maoz:

This page provides links to screen captures of [[the Tracer]], from several case study applications:

* [[Tracer's gallery: PacMan game|PacMan game]]
* [[Smartphone]], scenario-based testing of a Nokia smartphone
* [[RSS news ticker]]
* [[C. elegans]], a biological system

Live sequence charts

2010-10-18T09:29:16Z

Shahar.maoz:

Live sequence charts (LSC) constitute a visual formalism for inter-object scenario-based specification and programming, which extends the partial-order semantics of classical message sequence charts (MSC) mainly by adding universal and existential modalities. It thus allows the definition of inter-object scenarios that specify, among other things,possible, mandatory, and forbidden behavior. LSC was introduced by Werner Damm and David Harel in 2001.

An executable semantics for LSCs, termed play-out, was presented by David Harel and Rami Marelly in 2003, together with a tool called Play-Engine. A translation of LSC into various temporal logics was defined by Hillel Kugler et al. in 2005. A UML2-compliant variant of LSC was defined by David Harel and Shahar Maoz in 2006. The language has been the subject of research in the areas of verification and testing , in the areas of scenario-based execution (playout) and synthesis, and in the areas of specification mining and software visualization. Initial projects that use LSC have been carried out recently in the automotive, telecommunication, and hardware domains.

More about LSC can be found in the references below and in [http://www.wisdom.weizmann.ac.il/~harel/ David Harel]'s website.

== Selected references on LSC ==

=== Language definitions ===

*Werner Damm and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], '''LSCs: Breathing Life into Message Sequence Charts''', ''Formal Methods in System Design'', 19(1): 45-80 (2001).

*[http://www.wisdom.weizmann.ac.il/~harel/ David Harel] and [http://www.se-rwth.de/~maoz/ Shahar Maoz], '''Assert and Negate Revisited: Modal Semantics for UML Sequence Diagrams''', ''Software and Systems Modeling'' (SoSyM), 7(2): 237-252 (2008).

=== Scenario-based execution (play-out) and synthesis ===

*[http://www.se-rwth.de/~maoz/ Shahar Maoz], [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], and Asaf Kleinbort, '''A Compiler for Multi-Modal Scenarios: Transforming LSCs into AspectJ''', ''ACM Trans. on Soft. Eng. and Method.'' (TOSEM). Accepted November 2009. To appear.

*[http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], '''From Multi-Modal Scenarios to Code: Compiling LSCs into AspectJ''', ''Proc. 14th ACM SIGSOFT Symp. on Foundations of Software Engineering'' (SIGSOFT FSE'06), ACM, 2006, pp. 219-230.

*[http://www.wisdom.weizmann.ac.il/~harel/ David Harel], Hillel Kugler, Rami Marelly, Amir Pnueli, '''Smart Play-out of Behavioral Requirements''', ''Proc. of Formal Methods in Computer Aided Design'' (FMCAD) 2002, pp. 378-398.

*[http://www.wisdom.weizmann.ac.il/~harel/ David Harel] and Rami Marelly, '''Specifying and executing behavioral requirements: the play-in/play-out approach''', ''Software and Systems Modeling'' (SoSyM), 2(2): 82-107 (2003)

PacMan game

2010-10-17T21:04:09Z

The scenario-based execution traces for the examples below were generated for [[the Tracer]] using the [[S2A]] compiler. The program traced for the examples below is adopted from a publicly available Java implementation of the classic [http://www.bennychow.com/ PacMan game].

Main view and overview:
[[Image:Example.jpg]]

Filters:
[[Image:Example.jpg]]

Multiplicity:
[[Image:Example.jpg]]

Comparing traces:
[[Image:Example.jpg]]

Completion information:
[[Image:Example.jpg]]

Event-normalized view:
[[Image:Example.jpg]]

Tracer's gallery

2010-10-17T20:58:54Z

Shahar.maoz: New page: This page provides links to screen captures of the Tracer, from several case study applications: * PacMan game * Smartphone, scenario-based testing of a Nokia smartphone * [[R...

This page provides links to screen captures of [[the Tracer]], from several case study applications:

* [[PacMan game]]
* [[Smartphone]], scenario-based testing of a Nokia smartphone
* [[RSS news ticker]]
* [[C. elegans]], a biological system

The Tracer

2010-10-17T20:52:39Z

Shahar.maoz:

The Tracer is a prototype tool for scenario-based trace visualization and exploration.

The Tracer presents a rich and highly dynamic technique for analyzing, visualizing, and exploring the execution traces of reactive systems. The two inputs are a designer's inter-object 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. The Tracer supports 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 semantics-based navigation, filtering, and trace comparison.

The Gantt views are implemented using the open source [http://www.jaret.de/timebars/ jaret timebars]. We thank Peter Kliem for his support.

The first version of the Tracer prototype was designed and programmed by Asaf Kleinbort and [http://www.se-rwth.de/~maoz/ Shahar Maoz] (2007). A second major version was programmed by Evyatar Shoresh (2009).

The [[Tracer's gallery]] features screen captures from several case study applications.

More on the Tracer can be found in the references below. As of 2010, the Tracer is integrated into [[PlayGo]].

== References ==

*[http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel]: '''On tracing reactive systems'''. ''Software and Systems Modeling'' (SoSyM), 2010. DOI= 10.1007/s10270-010-0151-2

*[http://www.se-rwth.de/~maoz/ Shahar Maoz]: '''Using Model-Based Traces as Runtime Models'''. ''IEEE Computer'' 42(10): 28-36 (2009)

*[http://www.se-rwth.de/~maoz/ Shahar Maoz]: '''Model-Based Traces'''. ''MoDELS Workshops'' 2008: 109-119

*[http://www.se-rwth.de/~maoz/ Shahar Maoz], Asaf Kleinbort, and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel]: '''Towards Trace Visualization and Exploration for Reactive Systems'''. ''VL/HCC'' 2007: 153-156

The Tracer

2010-10-17T20:51:03Z

Shahar.maoz:

The Tracer is a prototype tool for scenario-based trace visualization and exploration.

The Tracer presents a rich and highly dynamic technique for analyzing, visualizing, and exploring the execution traces of reactive systems. The two inputs are a designer's inter-object 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. The Tracer supports 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 semantics-based navigation, filtering, and trace comparison.

The Gantt views are implemented using the open source [http://www.jaret.de/timebars/ jaret timebars]. We thank Peter Kliem for his support.

The first version of the Tracer prototype was designed and programmed by Asaf Kleinbort and [http://www.se-rwth.de/~maoz/ Shahar Maoz] (2007). A second major version was programmed by Evyatar Shoresh (2009).

The [[Tracer's gallery]] features screen captures from several case study applications.

More on the Tracer can be found in the references below. As of 2010, the Tracer is integrated into [[PlayGo]].

== References ==

*[http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel]: On tracing reactive systems. ''Software and Systems Modeling'' (SoSyM), 2010. DOI= 10.1007/s10270-010-0151-2

*[http://www.se-rwth.de/~maoz/ Shahar Maoz]: Using Model-Based Traces as Runtime Models. IEEE Computer 42(10): 28-36 (2009)

*[http://www.se-rwth.de/~maoz/ Shahar Maoz]: Model-Based Traces. MoDELS Workshops 2008: 109-119

*[http://www.se-rwth.de/~maoz/ Shahar Maoz], Asaf Kleinbort, and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel]: Towards Trace Visualization and Exploration for Reactive Systems. VL/HCC 2007: 153-156

The Tracer

2010-10-17T20:50:43Z

Shahar.maoz:

The Tracer is a prototype tool for scenario-based trace visualization and exploration.

The Tracer presents a rich and highly dynamic technique for analyzing, visualizing, and exploring the execution traces of reactive systems. The two inputs are a designer's inter-object 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. The Tracer supports 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 semantics-based navigation, filtering, and trace comparison.

The Gantt views are implemented using the open source [http://www.jaret.de/timebars/ jaret timebars]. We thank Peter Kliem for his support.

The first version of the Tracer prototype was designed and programmed by Asaf Kleinbort and [http://www.se-rwth.de/~maoz/ Shahar Maoz] (2007). A second major version was programmed by Evyatar Shoresh (2009).

The [[Tracer's gallery]] features screen captures from several case study applications.

More on the Tracer can be found in the references below. As of 2010, the Tracer is integrated into [[PlayGo]].

== References ==

*[http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel]: On tracing reactive systems. ''Software and Systems Modeling'' (SoSyM), 2010. DOI= 10.1007/s10270-010-0151-2

*[http://www.se-rwth.de/~maoz/ Shahar Maoz]: Using Model-Based Traces as Runtime Models. IEEE Computer 42(10): 28-36 (2009)

*[http://www.se-rwth.de/~maoz/ Shahar Maoz]: Model-Based Traces. MoDELS Workshops 2008: 109-119

*[http://www.se-rwth.de/~maoz/ Shahar Maoz], Asaf Kleinbort, [http://www.wisdom.weizmann.ac.il/~harel/ David Harel]: Towards Trace Visualization and Exploration for Reactive Systems. VL/HCC 2007: 153-156

PlayGo

2010-10-17T20:34:47Z

Shahar.maoz:

Welcome to PlayGo, a comprehensive tool for scenario-based programming, built around the language of [[live sequence charts]] (LSC) and its Java derivative, and the Play-in/Play-out approach.

PlayGo is intended to constitute extensive support to the vision of [http://www.wisdom.weizmann.ac.il/~harel/papers/LiberatingProgramming.pdf Liberating Programming]

* [[About PlayGo]]
* [[PlayGo Screenshots]]
* [[PlayGo Demos]]
* [[Download PlayGo]]
* [[Getting Started with PlayGo]]
* [[PlayGo HowTo]]

== Related Tools ==
* [[The Tracer]], a prototype tool for scenario-based trace visualization and exploration.
* [[S2A]], a compiler for multi-modal UML sequence diagrams.

== Contact Information ==
E-mail us to: [mailto:playgo@weizmann.ac.il playgo@weizmann.ac.il]

Live sequence charts

2010-10-17T20:32:12Z

Shahar.maoz:

Live sequence charts (LSC) constitute a visual formalism for inter-object scenario-based specification and programming, which extends the partial-order semantics of classical message sequence charts (MSC) mainly by adding universal and existential modalities. It thus allows the definition of inter-object scenarios that specify, among other things,possible, mandatory, and forbidden behavior. LSC was introduced by Werner Damm and David Harel in 2001.

An executable semantics for LSCs, termed play-out, was presented by David Harel and Rami Marelly in 2003, together with a tool called Play-Engine. A translation of LSC into various temporal logics was defined by Hillel Kugler et al. in 2005. A UML2-compliant variant of LSC was defined by David Harel and Shahar Maoz in 2006. The language has been the subject of research in the areas of verification and testing , in the areas of scenario-based execution (playout) and synthesis, and in the areas of specification mining and software visualization. Initial projects that use LSC have been carried out recently in the automotive, telecommunication, and hardware domains.

More about LSC can be found in the references below in the [http://www.wisdom.weizmann.ac.il/~harel/ David Harel]'s website.

== Selected references on LSC ==

=== Language definitions ===

*Werner Damm and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], '''LSCs: Breathing Life into Message Sequence Charts''', ''Formal Methods in System Design'', 19(1): 45-80 (2001).

*[http://www.wisdom.weizmann.ac.il/~harel/ David Harel] and [http://www.se-rwth.de/~maoz/ Shahar Maoz], '''Assert and Negate Revisited: Modal Semantics for UML Sequence Diagrams''', ''Software and Systems Modeling'' (SoSyM), 7(2): 237-252 (2008).

=== Scenario-based execution (play-out) and synthesis ===

*[http://www.se-rwth.de/~maoz/ Shahar Maoz], [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], and Asaf Kleinbort, '''A Compiler for Multi-Modal Scenarios: Transforming LSCs into AspectJ''', ''ACM Trans. on Soft. Eng. and Method.'' (TOSEM). Accepted November 2009. To appear.

*[http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], '''From Multi-Modal Scenarios to Code: Compiling LSCs into AspectJ''', ''Proc. 14th ACM SIGSOFT Symp. on Foundations of Software Engineering'' (SIGSOFT FSE'06), ACM, 2006, pp. 219-230.

*[http://www.wisdom.weizmann.ac.il/~harel/ David Harel], Hillel Kugler, Rami Marelly, Amir Pnueli, '''Smart Play-out of Behavioral Requirements''', ''Proc. of Formal Methods in Computer Aided Design'' (FMCAD) 2002, pp. 378-398.

*[http://www.wisdom.weizmann.ac.il/~harel/ David Harel] and Rami Marelly, '''Specifying and executing behavioral requirements: the play-in/play-out approach''', ''Software and Systems Modeling'' (SoSyM), 2(2): 82-107 (2003)

Live sequence charts

2010-10-17T20:17:05Z

Shahar.maoz:

Live sequence charts (LSC) constitute a visual formalism for inter-object scenario-based speci�cation and programming, which extends the partial-order semantics of classical message sequence charts (MSC) mainly by adding universal and existential modalities. It thus allows the de�nition of inter-object scenarios that specify, among other things, possible, mandatory, and forbidden behavior.  LSC was introduced by Werner Damm and David Harel in 2001.

 

An executable semantics for LSCs, termed play-out, was presented by David Harel and Rami Marelly in 2003, together with a tool called Play-Engine.  A translation of LSC into various temporal logics was defined by Hillel Kugler et al. in 2005.   A UML2-compliant variant of LSC was defined by David Harel and Shahar Maoz in 2006.    The language has been the subject of research in the areas of verification and testing , in the areas of scenario-based execution (playout) and synthesis, and in the areas of specification mining and software visualization.  Initial projects that use LSC have been carried out recently in the automotive, telecommunication, and hardware domains. 

 

More about LSC can be found in the references below.

Live sequence charts

2010-10-17T20:15:21Z

Shahar.maoz: New page: Live sequence charts (LSC) constitute a visual formalism for inter-object scenario-based speci�cation and programming, which extends the partial-order semantics of classical message sequ...

Live sequence charts (LSC) constitute a visual formalism for inter-object scenario-based speci�cation and programming, which extends the partial-order semantics of classical message sequence charts (MSC) mainly by adding universal and existential modalities. It thus allows the de�nition of inter-object scenarios that specify, among other things, possible, mandatory, and forbidden behavior.  LSC was introduced by Werner Damm and David Harel in 2001.

An executable semantics for LSCs, termed play-out, was presented by David Harel and Rami Marelly in 2003, together with a tool called Play-Engine.  A translation of LSC into various temporal logics was defined by Hillel Kugler et al. in 2005.   A UML2-compliant variant of LSC was defined by David Harel and Shahar Maoz in 2006.    The language has been the subject of research in the areas of veri�cation and testing , and in the areas of scenario-based execution (playout) and synthesis.  Initial projects that use LSC have been carried out recently in the automotive, telecommunication, and hardware domains. 

More about LSC can be found in the references below.

The LSC Compiler

2010-10-17T20:06:05Z

Shahar.maoz: /* References */

S2A, standing for Scenarios to Aspects, is a compiler that translates Modal UML Sequence Diagrams (MSDs), a UML-compliant variant of [[live sequence charts]] (LSCs), into [http://www.eclipse.org/aspectj/ AspectJ] code. It thus provides full code generation of reactive behavior from visual inter-object scenario-based specifications. The S2A compiler is based on a compilation scheme which was presented by [http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel] in 2006.

More about S2A can be found in the references below. As of 2010, S2A is part of [[PlayGo]].

== References ==

*[http://www.se-rwth.de/~maoz/ Shahar Maoz], [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], and Asaf Kleinbort, '''A Compiler for Multi-Modal Scenarios: Transforming LSCs into AspectJ''', ''ACM Trans. on Soft. Eng. and Method.'' (TOSEM). Accepted November 2009. To appear.

*Yoram Atir, [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], Asaf Kleinbort, and [http://www.se-rwth.de/~maoz/ Shahar Maoz], '''Object Composition in Scenario-Based Programming''', ''Proc. 11th Int. Conf. on Fundamental Approaches to Software Engineering'' (FASE'08), vol. 4961 of LNCS, Springer-Verlag, 2008, pp. 301-316.

*[http://www.wisdom.weizmann.ac.il/~harel/ David Harel], Asaf Kelinbort, and [http://www.se-rwth.de/~maoz/ Shahar Maoz], '''S2A: A Compiler for Multi-Modal UML Sequence Diagrams''', ''Proc. 10th Int. Conf. on Fundamental Approaches to Soft. Eng.'' (FASE'07), vol. 4422 of LNCS, Springer, 2007, pp. 121-124.

*[http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], '''From Multi-Modal Scenarios to Code: Compiling LSCs into AspectJ''', ''Proc. 14th ACM SIGSOFT Symp. on Foundations of Software Engineering'' (SIGSOFT FSE'06), ACM, 2006, pp. 219-230.

The LSC Compiler

2010-10-17T19:57:36Z

Shahar.maoz:

S2A, standing for Scenarios to Aspects, is a compiler that translates Modal UML Sequence Diagrams (MSDs), a UML-compliant variant of [[live sequence charts]] (LSCs), into [http://www.eclipse.org/aspectj/ AspectJ] code. It thus provides full code generation of reactive behavior from visual inter-object scenario-based specifications. The S2A compiler is based on a compilation scheme which was presented by [http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel] in 2006.

More about S2A can be found in the references below. As of 2010, S2A is part of [[PlayGo]].

== References ==

* [http://www.se-rwth.de/~maoz/ Shahar Maoz], [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], and Asaf Kleinbort, A Compiler for Multi-Modal Scenarios: Transforming LSCs into AspectJ, ''ACM Trans. on Software Eng. and Method.'' (TOSEM). To appear.
* [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], Asaf Kelinbort, and [http://www.se-rwth.de/~maoz/ Shahar Maoz], S2A: A Compiler for Multi-Modal UML Sequence Diagrams, ''Proc. 10th Int. Conf. on Fundamental Approaches to Soft. Eng.'' (FASE'07), Vol. 4422 of LNCS, pp. 121-124, Springer.
* [http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], From Multi-Modal Scenarios to Code: Compiling LSCs into AspectJ, ''Proc. 14th ACM SIGSOFT Symp. on Foundations of Software Engineering'' (SIGSOFT FSE'06), pp. 219-230, ACM, 2006.

The LSC Compiler

2010-09-05T02:54:56Z

Shahar.maoz: /* References */

S2A, standing for Scenarios to Aspects, is a compiler that translates Modal UML Sequence Diagrams (MSDs), a UML-compliant version of [[live sequence charts]] (LSCs), into [http://www.eclipse.org/aspectj/ AspectJ] code. It thus provides full code generation of reactive behavior from visual inter-object scenario-based specifications. The S2A compiler is based on a compilation scheme which was presented by [http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel] in 2006.

More about S2A can be found in the references below. As of 2010, S2A is part of [[PlayGo]].

== References ==

* [http://www.se-rwth.de/~maoz/ Shahar Maoz], [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], and Asaf Kleinbort, A Compiler for Multi-Modal Scenarios: Transforming LSCs into AspectJ, ''ACM Trans. on Software Eng. and Method.'' (TOSEM). To appear.
* [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], Asaf Kelinbort, and [http://www.se-rwth.de/~maoz/ Shahar Maoz], S2A: A Compiler for Multi-Modal UML Sequence Diagrams, ''Proc. 10th Int. Conf. on Fundamental Approaches to Soft. Eng.'' (FASE'07), Vol. 4422 of LNCS, pp. 121-124, Springer.
* [http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], From Multi-Modal Scenarios to Code: Compiling LSCs into AspectJ, ''Proc. 14th ACM SIGSOFT Symp. on Foundations of Software Engineering'' (SIGSOFT FSE'06), pp. 219-230, ACM, 2006.

The LSC Compiler

2010-09-05T02:54:26Z

Shahar.maoz:

PlayGo

2010-09-04T20:21:29Z

Shahar.maoz: /* Related Tools */

Welcome to PlayGo, a comprehensive tool for scenario-based programming, built around the language of [http://www.wisdom.weizmann.ac.il/~harel Live Sequence Charts (LSC)] and its Java derivative, and the Play-in/Play-out approach.

PlayGo is intended to constitute extensive support to the vision of [http://www.wisdom.weizmann.ac.il/~harel/papers/LiberatingProgramming.pdf Liberating Programming]

* [[About PlayGo]]
* [[Screenshots]]
* [[Demos]]
* [[Getting Started with PlayGo]]

== Related Tools ==
* [[The Tracer]], a prototype tool for scenario-based trace visualization and exploration.
* [[S2A]], a compiler for multi-modal UML sequence diagrams.

== Contact Information ==
E-mail us to: [mailto:playgo@weizmann.ac.il playgo@weizmann.ac.il]

The LSC Compiler

2010-09-04T20:20:15Z

Shahar.maoz: /* References */

S2A, standing for Scenarios to Aspects, is a compiler that translates Modal UML Sequence Diagrams (MSDs), a UML-compliant version of live sequence charts (LSCs), into AspectJ code. It thus provides full code generation of reactive behavior from visual inter-object scenario-based specifications. The S2A compiler is based on a compilation scheme which was presented by [http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel] in 2006.

As of 2010, S2A is part of [[PlayGo]].

== References ==

* [http://www.se-rwth.de/~maoz/ Shahar Maoz], [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], and Asaf Kleinbort, A Compiler for Multi-Modal Scenarios: Transforming LSCs into AspectJ, ''ACM Trans. on Software Eng. and Method.'' (TOSEM). To appear.
* [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], Asaf Kelinbort, and [http://www.se-rwth.de/~maoz/ Shahar Maoz], S2A: A Compiler for Multi-Modal UML Sequence Diagrams, ''Proc. 10th Int. Conf. on Fundamental Approaches to Soft. Eng.'' (FASE'07), Vol. 4422 of LNCS, pp. 121-124, Springer.
* [http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], From Multi-Modal Scenarios to Code: Compiling LSCs into AspectJ, ''Proc. 14th ACM SIGSOFT Symp. on Foundations of Software Engineering'' (SIFSOFT FSE'06), pp. 219-230, ACM, 2006.

The Tracer

2010-09-04T20:15:22Z

Shahar.maoz: /* References */

The Tracer is a prototype tool for scenario-based trace visualization and exploration.

 

A screenshot of the main view of the Tracer is shown below. 

[[Image:Tracer Main View and Overview.PNG]]

== References ==

[http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel]: On tracing reactive systems. ''Software and Systems Modeling'' (SoSyM), 2010. DOI= 10.1007/s10270-010-0151-2

The LSC Compiler

2010-09-04T20:14:24Z

Shahar.maoz:

S2A, standing for Scenarios to Aspects, is a compiler that translates Modal UML Sequence Diagrams (MSDs), a UML-compliant version of live sequence charts (LSCs), into AspectJ code. It thus provides full code generation of reactive behavior from visual inter-object scenario-based specifications. The S2A compiler is based on a compilation scheme which was presented by [http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel] in 2006.

As of 2010, S2A is part of [[PlayGo]].

== References ==

* [http://www.se-rwth.de/~maoz/ Shahar Maoz], [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], and Asaf Kleinbort, A Compiler for Multi-Modal Scenarios: Transforming LSCs into AspectJ, ACM TOSEM. To appear.
* [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], Asaf Kelinbort, and [http://www.se-rwth.de/~maoz/ Shahar Maoz], S2A: A Compiler for Multi-Modal UML Sequence Diagrams, FASE'07, Vol. 4422 of LNCS, pp. 121-124, Springer.
* [http://www.se-rwth.de/~maoz/ Shahar Maoz] and [http://www.wisdom.weizmann.ac.il/~harel/ David Harel], From Multi-Modal Scenarios to Code: Compiling LSCs into AspectJ, SIFSOFT FSE'06, pp. 219-230, ACM, 2006.