<!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>
      <title-group>
        <article-title>Working Sessions as an Evaluation Technique for Research in SPE: Experience and Lessons Learned</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Floriment Klinaku</string-name>
          <email>lforiment.klinaku@iste.uni-stuttgart.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alireza Hakamian</string-name>
          <email>alireza.hakamian@stud.uni-stuttgart.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefen</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Becker</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Workshop Proceedings</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Software Quality and Architecture, University of Stuttgart</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>online working sessions, model-based software engineering, software performance engineering, lunch” part. Evaluating tools, languages and frameworks is crucial in software engineering research. A common user group for such evaluations are bachelor and master students studying related courses. Two problems with such studies remain: the incentive and the format. The recent pandemic afected both; especially the format of the study. In this talk we will share our experience and lessons learned with designing and conducting an online working session for master students in the Model Driven Software Engineering course. Our design decisions were based on two requirements: (1) students should strengthen the lecture material and (2) evaluate a language for modelling scaling policies for cloud applications. The first requirement was the incentive for the students whereas the second was the ”no free We designed a two-day working sessions with two diferent goals: strengthening the course material and evaluating a prototype language for modelling scaling policies for cloud applications. We avoided using multiple sheets and instead we used only one shared document for collaborative working. Hence, there was no screen sharing and all material was stored in one document. The collaborative document started empty and was filled incrementally where in some parts students had to contribute.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Objective</title>
    </sec>
    <sec id="sec-2">
      <title>Method</title>
      <p>On the first and second day we had 5 and 7 participants respectively. At the end of each day we
ask students to fill a survey which contains question of interests for both goals.</p>
      <p>The results are promising for both requirements. For lessons learned we emphasize on:
• Such a hands on workshop with two goals requires efort in design but is beneficial if
content-wise the goals align.
• Two working sessions of 90 minutes length each, resulted to be enough to reach teaching
and evaluation goals with a group of students.
• An important aspect is the expected level of skills and domain expertise for the target
users of the artefact being evaluated. If this contradicts with the teaching goals then such
working sessions are not the way to go.
• The main efort should go in preparing simple examples and tooling to support the online
session.</p>
      <p>Furthermore, in the talk we will share feedback given by students on both goals. To emphasize
on the feedback:
• One or more students (1) were not able to complete the hands on due to overloaded
content, (2) had technical problems with their development environment and (3) managed
to follow through the end with all tasks completed.
• All students were able to follow the rationale of the modelling language.
• Most students (1) were able to come up with examples for diferent language concepts,
(2) found the format of the workshop suitable.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>