<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Universitat Rostock, Institut fur Informatik</institution>
          ,
          <addr-line>18051 Rostock</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In many elds of science, the quality and applicability of presented approaches heavily relies on experimental results. At the same time, such experiments are only described brie y and are typically boiled down to a single diagram or table. To maintain high scienti c standards, experiments need to be transparent and repeatable. This not only provides a deeper understanding in the used tools, but also facilitates the improvement and comparison of approaches. This paper introduces service-technology.org/live, a Web site which allows to replay experiments in a Web browser. This gives colleagues and reviewers the possibility to get detailed information on the experimental setup without the need of actually installing tools. The Web site further o ers the used tools and the input data for download together with information on how to repeat the experiments locally.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The formal veri cation of business process models forms a constant stream of
research in the BPM community. With a variety of correctness criteria of which
soundness is the most popular one, also a multitude of automatic veri cation
tools were developed over the last years. The algorithms implemented by these
tools typically have a devastating worst-case complexity (usually an exponential
explosion in the size of the model) which seems to make any application beyond
toy examples unreasonable. As a matter of fact, experiences in the eld of model
checking [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] reveal that even theoretically unfeasible algorithms may perform
surprisingly well on real-world instances. Consequently, prototype implementations
need to be validated with the help of case studies or experiments.
      </p>
      <p>To follow good scienti c standards, such experiments should not only be
thoroughly described. To achieve maximal transparency and to simplify
comparison and improvements, they also need to be repeatable. That said, not only the
respective tools and input data need to be published, but also information on the
installation and invocation are required to replay experiments. Unfortunately,
only few papers provide such details and experimental results are typically boiled
down to a few tables or diagrams, making the entire experiment and hence the
implemented algorithm intransparent and vulnerable.</p>
      <p>We identi ed several problems that hinder adequate transparency:
{ Page limits. Technical details on the installation or invocation of tools can
hardly be provided within the page limit of a typical research paper. At the
same time, prototypes are often a byproduct of the respective research paper
and hence dedicated tool papers are not yet available.
{ Availability of tools. Many tools are proof-of-concept implementations for
the respective research paper and are often not publicly available. The same
holds for beta versions or commercial tools.
{ Installation of tools. Scienti c software development often lacks a professional
release and documentation process which makes the installation complex and
cumbersome.
{ Description of the experimental setup. An experiment hardly involves a single
call of a tool or \click" of a button. Often, only the interplay between several
tools or parameters realize the experiment.
{ Availability of input data. Even if all tools are available and the experimental
setup is properly described, the concrete input data are hardly available for
download. This is typically because of nondisclosure agreements or other legal
constraints on industrial process models. But even if input data are public
(e.g., published reference models), they are frequently converted beforehand
or otherwise preprocessed.</p>
      <p>This paper introduces service-technology.org/live, a Web site dedicated to the
technical aspects of the described problems. This Web site not only \outsources"
technical descriptions on the experimental setup, but also facilitates the replay of
the experiments within a Web browser. The remainder of the paper is organized
as follows. The next section gives an overview of service-technology.org/live.
Section 3 discusses technical details. Finally, Sect. 4 gives directions of future
work and concludes the paper.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Overview</title>
      <p>
        The Web site service-technology.org/live hosts with BPEL2oWFN [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], Fiona [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ],
Wendy [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], Rachel [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], Marlene [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and Mia [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] several of the tools developed
by the theory of programming research groups at the University of Rostock and
the Humboldt-Universitat zu Berlin. Their focus is the correctness of business
process and service models. We provide a detailed overview in [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. As the tools
are command-line based, their usage is | compared to tools with a graphical user
interface | rather complicated. Furthermore, the tools follow the \one purpose,
one tool" philosophy and can be combined in many ways to perform higher level
tasks. To still be able to reproduce experimental results, we xed several tool
setups and o er them at service-technology.org/live, see Fig. 1.
      </p>
      <p>In the simplest case, the user can choose an experiment which is described in
the respective paper (i.e., choosing the name of a model from a drop-down list)
and let the experiment be run \live" on the Web server. For other experiments,
also a few parameters can be set. The output (see Fig. 2 for an example) consist
of the following elements:
{ a description of the input of the experiment (e.g., the origin of the model),
{ console windows (i.e., the output of the command-line tools),
{ generated graphical representations (e.g., Petri nets or automata),
{ a summary of invoked tools with their parameters, and
{ download information for the involved models and tools.</p>
      <p>Admittedly, the current state of interactivity is limited. We believe,
however, that even this simplistic Web site already provides a decent amount of
transparency for the experimental results. With a hosted experiment, we give
colleagues and reviewers not only the opportunity to check for the existence of
the tools, but also give an idea how the results are generated and also show the
\look and feel" of the tools without the need of downloading or installing. This is,
however, still possible, because all tools and input models are available online.</p>
    </sec>
    <sec id="sec-3">
      <title>Technical realization</title>
      <p>The Web site service-technology.org/live is written in PHP, but any other language
that allows the Web server to invoke locally installed tools could be used instead.</p>
      <p>The current server is an Apple Mac mini (1.83 GHz, 1 GB RAM) running an
Apache 2.2 server with PHP 5.3.</p>
      <p>The main components such as console windows or graphics generation and
presentation have been encapsulated to facilitate extensions and the integration
of new tools and experiments. The free JavaScript library jQuery1 further realizes
basic UI concepts such as tabbed windows and asynchronous loading of images
using AJAX. The code of the Web site is free and open source.2</p>
      <p>New experiments can be quickly integrated by performing two tasks:
1. Add a form to the front page to choose the input model and parameters.
2. Create a PHP script that runs and presents the experimental results.</p>
      <p>Both steps are highly generic, and because of the encapsulation of server and
language-speci c details, we claim that anyone who is able to execute the tools
in a console is likewise able to create such les for new experiments | assuming
basic knowledge on HTML and PHP.</p>
      <p>In the current state, no user access controls are implemented. All experiments
are open for everybody. It is, however, possible to upload input models to the
1 http://jquery.com/
2 http://svn.gna.org/svn/service-tech/trunk/meta/live/
server or to provide a URL to a model. Such uploaded models are processed just
like the hosted models, but are not shared with other users, and are deleted from
the server regularly.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Conclusion</title>
      <p>
        Concrete experiments hosted by service-technology.org/live have already been
referenced in several published research papers [
        <xref ref-type="bibr" rid="ref5 ref7 ref8">5,8,7</xref>
        ]. We feel committed to use
service-technology.org/live as a part of any future research paper which involves
experimental results. By encapsulating repeatedly used functionality such as
console windows or graphics generation, new results can be added without much
programming e ort. By publishing the source code of service-technology.org/live
as open source, we hope that other research groups follow our example.
      </p>
      <p>
        In future work, we plan to continue to simplify the addition of new experiments
and tools. We also work on decoupling the hosted tools from the Web site and to
o er them as software as a service using Web service standards such as SOAP
and WSDL. Thereby, we can wrap complex veri cation tasks and allow them
to be invoked remotely over the Web from other tools. We currently evaluate
the use of the Petri net model checker LoLA [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] as soundness checker for the
modeling platform Oryx [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Clarke</surname>
            ,
            <given-names>E.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grumberg</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peled</surname>
            ,
            <given-names>D.A.</given-names>
          </string-name>
          :
          <article-title>Model Checking</article-title>
          . MIT Press (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Decker</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Overdick</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Oryx - an open modeling platform for the BPM community</article-title>
          .
          <source>In: BPM 2008</source>
          . pp.
          <volume>382</volume>
          {
          <fpage>385</fpage>
          . LNCS 5240, Springer (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Gierds</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mooij</surname>
            ,
            <given-names>A.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wolf</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Reducing adapter synthesis to controller synthesis</article-title>
          .
          <source>IEEE T. Services Computing</source>
          (
          <year>2010</year>
          ),
          <article-title>(accepted for publication in July</article-title>
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Liske</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lohmann</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stahl</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wolf</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Another approach to service instance migration</article-title>
          .
          <source>In: ICSOC 2009</source>
          . pp.
          <volume>607</volume>
          {
          <fpage>621</fpage>
          . LNCS 5900, Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Lohmann</surname>
          </string-name>
          , N.:
          <article-title>Correcting deadlocking service choreographies using a simulationbased graph edit distance</article-title>
          .
          <source>In: BPM 2008</source>
          . pp.
          <volume>132</volume>
          {
          <fpage>147</fpage>
          . LNCS 5240, Springer (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Lohmann</surname>
          </string-name>
          , N.:
          <article-title>A feature-complete Petri net semantics for WS-BPEL 2.0</article-title>
          . In: WS-FM
          <year>2007</year>
          . pp.
          <volume>77</volume>
          {
          <fpage>91</fpage>
          . LNCS 4937, Springer (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Lohmann</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weinberg</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Wendy: A tool to synthesize partners for services</article-title>
          .
          <source>In: PETRI NETS</source>
          <year>2010</year>
          . pp.
          <volume>297</volume>
          {
          <fpage>307</fpage>
          . LNCS 6128, Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Lohmann</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wolf</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Petrifying operating guidelines for services</article-title>
          .
          <source>In: ACSD 2009</source>
          . pp.
          <volume>80</volume>
          {
          <fpage>88</fpage>
          . IEEE Computer Society (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Lohmann</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wolf</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>How to implement a theory of correctness in the area of business processes and services</article-title>
          .
          <source>In: BPM 2010. LNCS</source>
          , Springer (
          <year>2010</year>
          ), (in press)
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Massuthe</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weinberg</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Fiona: A tool to analyze interacting open nets</article-title>
          .
          <source>In: AWPN 2008</source>
          . pp.
          <volume>99</volume>
          {
          <fpage>104</fpage>
          . CEUR Workshop Proceedings Vol.
          <volume>380</volume>
          ,
          <string-name>
            <surname>CEUR-WS.org</surname>
          </string-name>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Wolf</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Generating Petri net state spaces</article-title>
          .
          <source>In: ICATPN 2007</source>
          . pp.
          <volume>29</volume>
          {
          <fpage>42</fpage>
          . LNCS 4546, Springer (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>