<!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>PACAS: A Gami ed Platform for Participatory Change Management in ATM Systems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Elda Paja</string-name>
          <email>elda.paja@unitn.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mauro Poggianella</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Fatma Basak Aydemir</string-name>
          <email>f.b.aydemir@uu.nl</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Paolo Giorgini</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Trento</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Utrecht University</institution>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this paper, we report on the development of a webbased platform for Participatory Architectural Change Management in Air Tra c Management Systems (ATM) as part of the SESAR H2020 project PACAS. The platform is the result of an iterative requirements engineering process that actively involves ATM domain experts, starting from stakeholder analysis, to requirements elicitation, scenario de nition, and validation.</p>
      </abstract>
      <kwd-group>
        <kwd>Requirements Engineering</kwd>
        <kwd>Gami cation</kwd>
        <kwd>Automated Reasoning</kwd>
        <kwd>Air Tra c Management</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Most of today's software systems are part of larger complex systems, that include
not only technical components, but also humans and organizations. These larger
systems are otherwise known as socio-technical systems [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] and they stand at
the core of how people work and collaborate with others while using the technical
systems to get things done. Examples include healthcare systems, e-commerce
sites, and air tra c management to mention a few.
      </p>
      <p>Change is inevitable, and socio-technical systems make no exception to the
rule. Therefore, they are continuously evolving due to various possible changes:
(i) system and subsystems changes, (ii) organizational and domain changes, (iii)
normative and regulatory changes, and/or (iii) assets changes. Any of these
changes may a ect the ability of the socio-technical system to satisfy its intended
requirements and function well.</p>
      <p>Dealing with change is an important activity in order to understand the
implications of change, how it a ects the rest of the system, whether it introduces
new requirements, and so on. In order to build a Change Management Platform,
which will facilitate understanding, modeling and analyzing changes at di erent
layers of abstraction, it is important to have the active participation of domain
Copyright 2018 for this paper by its authors. Copying permitted for private and
academic purposes.
experts who can analyze the impact of change from di erent perspectives. Most
importantly, this should be done in an iterative fashion in reingineering an
already running system, so that new requirements dictated by a given change issue
do not con ict with existing ones or cause problems on the rest of the system.</p>
      <p>In this paper, we report on the development of a web-based platform for
Participatory Architectural Change MAnagement which is triggered by a real case
concerning the evolution of Air Tra c Management (ATM) Systems as part of
the SESAR H2020 project PACAS 1. Given that decision-making involves the
consideration of more high-level objectives, such as safety, performance,
economic e ciency, etc., the change management process should involve multiple
ATM domain stakeholders, one for each given objective, in order to explore a
vast space of alternatives and agreeing on optimal solutions. It becomes, thus,
crucial the active participation of stakeholders. Indeed, in ATM di erent experts
from di erent companies across Europe collaborate to design the future
European ATM which is intended to improve safety, while cutting down costs and
environmental impacts. However, given the variety of experts, their di erent
areas of expertise, as well as their geographical distribution, participatory change
management requires user engagement and tools to support and facilitate the
work of experts along their interaction. To address the rst concern, in recent
years, gami cation is broadly used as a tool to engage participation with the
help of game elements, such as leader-boards or challenges between users. On
the other hand, a multi-perspective, model-based approach provides important
bene ts in that: (i) it allows analyzing individual perspectives without the need
of a holistic representation; (ii) it handles complexity through automated
reasoning techniques in a transparent way to nd optimal solutions as a trade-o
among di erent objectives.</p>
      <p>Therefore, the platform we present is a gami ed one, and relies on the work
of experts that capture the implications of change with the help of a multi-view
modelling environment, which supports four default languages to allows the
analysis of these four perspectives: safety, security, economic and organizational. The
collaboration of experts and decision-making, on the other hand, are supported
by automated reasoning techniques within each model and across models with
the help of natural language processing.</p>
      <p>The paper is structured as follows. We brie y describe the PACAS project in
Section 2, while in Section 3 we describe the change management process, while
Section 4 presents the platform. Section 5 discusses related work and concludes.</p>
    </sec>
    <sec id="sec-2">
      <title>2 PACAS</title>
      <p>Air Tra c Management (ATM) systems are complex systems of systems.
Participatory Architectural Change MAnagement in ATM Systems (PACAS) is a
Horizon 2020 project in the framework of the SESAR Research and Innovation
Action (RIA). The main objective is to better understand, model and analyze</p>
      <sec id="sec-2-1">
        <title>1 http://www.pacasproject.eu/</title>
        <p>changes at di erent layers of the Air Tra c Management (ATM) system to
support change management, while capturing how architectural and design choices
in uence the overall system. Understanding all possible consequences of a design
decision in an ATM system is a challenge due to the complexity of ATM
systems and the existence of tight interdependencies within the ATM architecture.
Knowing the implications of change(s) over the whole system is crucial to
support decision-making, while making sure that the ATM system does not su er
from any issues with respect to functionality, safety, security, performance, cost
e ciency, or other desired characteristics of a well-functioning ATM system. The
project aims at developing an innovative participatory change management
process wherein heterogeneous stakeholders actively participate in the architectural
evolution of the ATM system.</p>
        <p>We provide an overview of the participatory change management process,
emphasizing the importance of active stakeholder participation. We describe
the two main support tools, i.e. gami cation for stakeholder engagement, and
automated reasoning techniques for handling complexity.</p>
        <p>During the demo, we will introduce the PACAS approach, expressly created
for architectural change management in ATM systems, and we brie y describe an
ATM example case study dealing with the Sectorless change issue, and conclude
with a demo of the framework.</p>
        <p>In dealing with change, we use the following terminology:
{ Change Issue: refers to a planned change under evaluation. For instance,
Sectorless is an ongoing change in ATM that considers moving to a sectorless
approach ATM is a novel way to tackle air tra c management in upper
airspace without conventional sectors that has already been proved feasible.
This change is expected to improve performance and organizational aspects,
with signi cant increase in capacity and controller e ciency, although safety
and security issues require more investigation.
{ Decision point - we analyze a given change issue splitting it into several
decision points. For instance, in Sectorless there are several questions one needs
to answer, such as How many aircrafts should be assigned to each air tra c
controller (ATC)?, or What criteria should be used to assign an aircraft to
a controller?, and so on. The rst question is captured by the decision point
Number of ights per ATC as opposed to the existing Handover of aircrafts.
{ Solution - within each decision point, we analyze di erent options, aka
solutions. In Sectorless, automatic assignment is envisioned.
{ View - each solution is analyzed from a given expert perspective, aka view.</p>
        <p>
          In PACAS we support these four views: safety, organizational, security and
economic.
{ Contribution - in order to assess how well a given solution fares with respect
to already set objectives, we capture how a solution contributes to overall
validation targets laid down by Eurocontrol and SESAR. Example validation
targets include Increased safety and Triple capacity.
{ Model - For each view, we support default modeling notations to allow
experts to represent but also analyze a given solution from their perspective,
alongside the possibility to upload les should di erent languages or
notations be used by the experts. The default languages in PACAS are: Fault
Tree [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] for safety, STS-ml [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] for security, BIM [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] for the organizational,
and an income statement (costs/revenues) for the economic view.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3 The Change Management Process</title>
      <p>The change management of complex systems, such as ATM systems, cannot be
handled by a single person. For each change issue, i.e., for each planned change
to be done in an ATM system from the implementation of a single component in
the cocKPIt to a new way of managing tra c in the airspace, teams of experts
need to collaborate in order to specify the best modi cations of the system.</p>
      <p>As such, we support the interaction of these main types of users, namely
experts, team leaders, builders, company representatives and a game master.</p>
      <p>The Game Master has the power to start a change issue, i.e., ask di erent
companies to study how to apply the change and propose the best modi cations
(solutions). The Company Representatives serve as contact points in the various
companies involved in the analysis of a change issue. Thus, they deal with the
creation of teams. In PACAS teams are created per area of expertise (view).</p>
      <p>Team Leaders will choose the best modi cation(s) of the ATM system for a
change issue. They will study the diagrams/models developed or adopted by the
Experts, who represent domain experts that know at least one of the modeling
languages used to specify and analyze changes and their implications. Team
leaders interact with experts, and decide which solution provided by Builders (see
below) is the best for the change issue. Similarly to Experts, they are experienced
in at least one of the perspectives supported by the PACAS web platform, and
have a good knowledge on the part of the ATM system involved in the change
issue. Thus, a Team Leader could be an expert too. Finally, Builders are not
only domain experts, but have also a wide knowledge of the overall system. They
specify the solutions that are to be analyzed by Team Leaders and Experts.</p>
      <p>They all interact following the process in Fig. 1 to make a decision.</p>
    </sec>
    <sec id="sec-4">
      <title>4 The PACAS Platform</title>
      <p>The novelty of the PACAS platform (Fig. 2) relies on these three main pillars:</p>
      <p>
        Gami cation . In order to drive collaboration and keep users engaged,
PACAS makes use of psychological and social drivers for interaction [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. In
designing the gami cation solution for PACAS, we have performed stakeholder
characterization in better understanding the motivations of the PACAS end
users. Additionally, we have performed a deep study of the context, in order to
understand the ATM change management process, and most importantly the
roles involved, their tasks, goals, social structure and the nature of good
being produced following the MAF framework [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. From our analysis as well as
through interviews, workshops and questionnaires lled out by ATM domain
stakeholders, we have identi ed a number of requirements for the PACAS
gami cation solution, including Coverage of all aspects supported in PACAS,
Collaboration, Participation, Stakeholder identi cation, and Communication, among
others. At the same time, we have identi ed two important anti-requirements,
namely Competition, which can lead to con icts among participants
obstructing collaboration, and Time pressure, which can lead to rushing work and poor
quality to meet deadlines. As a result the PACAS gami cation solutions builds
around three paths, that, while orchestrating the other gami cation elements,
foster user progression along the three paths reaching di erent levels while
using the platform. Speci cally, we have de ned mechanisms of challenges among
di erent roles, at the completion of which and after reciprocal evaluation they
gain badges to further progress. A smart avatar is used to display messages and
suggestions to users, providing timely information at all times. Finally, we
support gami ed tutorials for users to follow and improve their level of knowledge
and expertise regarding the PACAS platform.
      </p>
      <p>Multi-view modeling . Integration of the re ned modeling notations and an
automatically generated shared model for decision-making, in which contribution
links from solutions to validation targets are drawn taking into account the result
of the automated reasoning on multi-criteria decision analysis. The platform is
modular, in the sense that new modeling environments can be integrated to
support experts using di erent languages in representing and further analysing
aspects related to their area of expertise.</p>
      <p>
        Automated reasoning techniques . PACAS supports local reasoning
techniques for the security view, namely well-formedness, security and threat analysis
for STS-ml [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. In addition, to aid decision-making, the platform integrates two
reasoning services: (i) intelligent cross-view alignment (ICVA) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], which with
the help of NLP provides suggestions to experts in verifying whether changes in
one view impact other models and views, and (ii) multi-criteria decision-making
analysis (MCDA), which allows identifying rst the best solutions per
validation target to then propose the best overall solution, which is a trade-o among
various aspects, in order to support making an informed decision.
      </p>
    </sec>
    <sec id="sec-5">
      <title>5 Conclusions</title>
      <p>In this paper we have reported on a gami ed collaborative platform for
participatory change management in ATM system. The resulting platform is the result
of the end-to-end inclusion of ATM domain stakeholders, who have actively
participated starting from early requirements the nal release of the platform,
through a number of iterations where we have presented mockups and performed
prototype validations.</p>
      <p>
        As far as our knowledge goes, there is little work that reports on such gami ed
platform, the creation of which involves stakeholders active participation.
REne (Snijders et al. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]) is a gami ed online platform for requirements elicitation
and re nement by involving a crowd of stakeholders: users, developers, analysts,
etc. Similarly to our approach, this is tailored to promote the long-term,
sustainable collaboration among stakeholders. However, while RE ne is speci cally
thought for requirements engineering for software products, the PACAS platform
is concerned with supporting change management in large-scale socio-technical
systems. Helms et al. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], on the other hand, explore how class or computer-based
trainings can be (re)designed using gami cation to increase student engagement
and motivation. They propose a method for the design of gami ed training for
Dutsch railways. The method is based on design science research, and extends
the instructional design model ADDIE and uses a database of educational game
elements to select the latter. The PACAS gami ed solution on the other hand is
based on goal models created in the context of the AGON [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] framework while
capturing acceptance and gami cation knowledge.
      </p>
      <p>In developing the PACAS platform we have faced several challenges, such as
the need for vast amount of domain speci c knowledge to tailor a customized
platform for the ATM domain, identifying the right domain stakeholders,
terminology alignment, and last but not least characterizing stakeholders for the
gami cation solution starting from a small representative set.</p>
      <p>Future work considers the application of the PACAS platform in other
domains and scenarios requiring collaborative decision-making among di erent
stakeholders, studying the impact of new solutions on the strategic layer
considered by PACAS, considering not only economic, organizational, security, and
safety aspects, but also integrating new ones. Potential domains include
healthcare where privacy issues need to be dealt with and supported by already running
systems, especially after the latest General Data Privacy Regulation 2.
Acknowledgments. This project has received funding from the SESAR Joint
Undertaking under grant agreement No 699306 under European Union's Horizon
2020 research and innovation programme.</p>
      <sec id="sec-5-1">
        <title>2 https://www.eugdpr.org/</title>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>F. B.</given-names>
            <surname>Aydemir</surname>
          </string-name>
          and
          <string-name>
            <given-names>F.</given-names>
            <surname>Dalpiaz</surname>
          </string-name>
          .
          <article-title>Towards aligning multi-concern models via nlp</article-title>
          .
          <source>In 25th RE Conference Workshops</source>
          , pages
          <volume>46</volume>
          {
          <fpage>50</fpage>
          . IEEE,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>F.</given-names>
            <surname>Dalpiaz</surname>
          </string-name>
          , E. Paja, and
          <string-name>
            <given-names>P.</given-names>
            <surname>Giorgini</surname>
          </string-name>
          . Security Requirements Engineering:
          <article-title>Designing Secure Socio-Technical Systems</article-title>
          . MIT Press,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Remko</surname>
            <given-names>W Helms</given-names>
          </string-name>
          , Rick Barneveld, and
          <string-name>
            <given-names>Fabiano</given-names>
            <surname>Dalpiaz</surname>
          </string-name>
          .
          <article-title>A method for the design of gami ed trainings</article-title>
          .
          <source>In PACIS, page 59</source>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>J.</given-names>
            <surname>Horko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Barone</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Jiang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Amyot</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Borgida</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          .
          <article-title>Strategic business modeling: representation and reasoning</article-title>
          .
          <source>SoSYM</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>W.S.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. L</given-names>
            <surname>Grosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. A</given-names>
            <surname>Tillman</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C. H.</given-names>
            <surname>Lie</surname>
          </string-name>
          .
          <article-title>Fault tree analysis, methods, and applications ? a review</article-title>
          .
          <source>IEEE transactions on reliability</source>
          ,
          <volume>34</volume>
          (
          <issue>3</issue>
          ):
          <volume>194</volume>
          {
          <fpage>203</fpage>
          ,
          <year>1985</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>E.</given-names>
            <surname>Paja</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Dalpiaz</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Giorgini</surname>
          </string-name>
          .
          <article-title>Managing security requirements con icts in socio-technical systems</article-title>
          .
          <source>In ER</source>
          , volume
          <volume>8217</volume>
          <source>of LNCS</source>
          , pages
          <volume>270</volume>
          {
          <fpage>283</fpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>L.</given-names>
            <surname>Piras</surname>
          </string-name>
          , E. Paja,
          <string-name>
            <given-names>P.</given-names>
            <surname>Giorgini</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          .
          <article-title>Goal models for acceptance requirements analysis and gami cation design</article-title>
          .
          <source>In ER</source>
          , pages
          <volume>223</volume>
          {
          <fpage>230</fpage>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>E.</given-names>
            <surname>Simperl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Cuel</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Stein</surname>
          </string-name>
          . Incentive{Centric Semantic Web Application Engineering. Semantic
          <source>Web Journal</source>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>R.</given-names>
            <surname>Snijders</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Dalpiaz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Brinkkemper</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Hosseini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Ali</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Ozum</surname>
          </string-name>
          .
          <article-title>Re ne: A gami ed platform for participatory requirements engineering</article-title>
          . In CrowdRE, pages
          <fpage>1</fpage>
          <article-title>{6</article-title>
          . IEEE,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10. I.
          <string-name>
            <surname>Sommerville</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Cli</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Calinescu</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Keen</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Kelly</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Kwiatkowska</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Mcdermid</surname>
            ,
            <given-names>and R.</given-names>
          </string-name>
          <string-name>
            <surname>Paige</surname>
          </string-name>
          .
          <article-title>Large-scale complex IT systems</article-title>
          .
          <volume>55</volume>
          (
          <issue>7</issue>
          ):
          <volume>71</volume>
          {
          <fpage>77</fpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>