<!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>Designing MAS Organisation through an integrated MDA/Ontology Approach?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Daniel Okouya</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Loris Penserini</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sebastien Saudrais</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Athanasios Staikopoulos</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Virginia Dignum</string-name>
          <email>virginiag@cs.uu.nl</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Siobhan Clarke</string-name>
          <email>Siobhan.Clarkeg@cs.tcd.ie</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Athanasios.Staikopoulos</institution>
          ,
          <addr-line>Sebastien.Saudrais, Siobhan.Clarke</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Trinity College Dublin</institution>
          ,
          <addr-line>Computer Science</addr-line>
          ,
          <country country="IE">Ireland</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Universiteit Utrecht</institution>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The increasing complexity of distributed applications, software services that can be dynamically deployed, adjusted and composed, paves the way for new challenges in software and service engineering. This paper describes a novel approach that combines the exibility of MDE techniques to deal with the conceptual modelling of MAS and the expressive power of OWL based ontologies to deal with semantics constraints veri cation as well as domain knowledge provision of MAS models. We will illustrate these ideas through the modeling of a crisis management scenario, using a rst prototype of our future Design tool: OperettA.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Nowadays' distributed applications based on the notion of service-oriented
systems {which can dynamically adapt, organise, and compose to satisfy with their
networked stakeholders' needs{ are fostering the software engineering research
area with new challenges. As these distributed systems have to be deployed
within real organisational contexts, adhering with organisational rules, and
meeting stakeholders' expectations, it is crucial to characterise the software
architectural and functional requirements in terms of their correlations with the actual
environment. To deliver on this aim, a promising approach in software
engineering has been to build methodologies along with conceptual modelling languages
that better re ect and describe the complex social and human organisational
context where the system-to-be has to be deployed [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ][
        <xref ref-type="bibr" rid="ref2">2</xref>
        ][
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. For example, in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]
and [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], an ontology based on the Telos language has been presented to describe
the conceptual model of the Tropos methodology.
      </p>
      <p>
        In this paper, we describe some achievements and future improvements of
a MAS development framework, OperettA [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], which is based on the OperA
methodology [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Using a simpli ed crisis management scenario, we will
illustrate how the Operetta's conceptual modelling language {which adheres to a
? This work has been performed in the framework of the FP7 project ALIVE
IST215890, which is funded by the European Community. The authors would like
to acknowledge the contributions of their colleagues from ALIVE Consortium
(http://www.ist-alive.eu)
Model Driven Engineering approach{ can be integrated with ontology
representation languages as OWL. Moreover, this approach allows designers for both the
veri cation of the semantics and the provision of domain speci c knowledge of
the MAS design models.
      </p>
      <p>
        Model Driven Engineering (MDE) refers to the systematic use of models as
primary artefacts throughout the Software Engineering lifecycle. The de ning
characteristic of MDE [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] is the use of models to represent the important artefacts
in a system, be they requirements, high-level designs, user data structures, views,
interoperability interfaces, test cases, or implementation-level artefacts such as
pieces of source code. The Model Driven Development promotes the automatic
transformation of abstracted models into speci c implementation technologies,
by a series of pre-de ned model transformations.
      </p>
      <p>The paper is organised as follows: Section 2 presents the methodological
context of our approach with a motivation example. Section 3 provides an overview
of our approach. Section 4 summarises the main characteristics and bene ts of
the approach adopted, which is partially implemented within the OperettA tool.
2
2.1</p>
    </sec>
    <sec id="sec-2">
      <title>A Methodological Context</title>
      <sec id="sec-2-1">
        <title>OperA overview</title>
        <p>
          OperA [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] is an engineering methodology based on organisational abstractions,
suitable both to model and study existing societies, as well as to develop new
systems that participate in an organisational context. The main focus of OperA
enable a suitable balance between global aims and requirements agent autonomy,
their coordination needs, and environmental stakeholders' needs.
        </p>
        <p>
          The development framework for agent societies, proposed in OperA, is
composed of three conceptual design models: Organisational Model, Social Model,
and Interaction Model, as detailed in [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. In this paper, we illustrate our ideas by
only using some concepts and diagrams belonging to theOrganisational Model. It
contains the description of the roles, relations and interactions in the
organisation. It is constructed based on the functional requirements of the organisation.
The social model and the interaction model are the link between the
organisational description and the executing agents.
2.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Running scenario</title>
        <p>
          Using an example taken from the Dutch procedures for crisis management, we
provide a conceptual model based on organisational and social concepts. The
modelling phase is conducted according to the OperA methodology [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] using
the OperettA tool [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] for graphical representation and veri cation of the model.
This scenario will be used along the paper to explain the development framework
properties.
        </p>
        <p>
          The structure diagram depicted in Figure 1 represents the crisis situation. It
speci es the responsibilities and goals of each role, e.g., each time an emergency
call occurs to the Emergency Call Center, this role alerts the Fire Station entity,
informing about the location in which the (possible) disaster is taking place. The
Fire Station is responsible to build the appropriate re brigade and depends on
the established Fire ghter Team in order to achieve the objective extinguish the
re. When the team arrives at the accident location, it has to decide (based on
its personal experience) the severity of the disaster. Only after this evaluation
is reported, an intervention decision is taken. For example, according to local
rules, the evaluation should comply with some standardised emergency levels,
as established by the Dutch Ministry of Internal A airs. For the sake of
simplicity, we consider that Fire ghter Team sets up a strategic intervention based
on the results of two evaluation criteria: damage evaluation and re evaluation.
Based on the number of wounded, Fire ghter Team decides on the necessity or
not to ask for ambulance service. Moreover, the Fire ghter Team checks if the
damage involves building structures in which case police intervention is
necessary to deviate tra c. From the re evaluation criterion, Fire ghter Team can
decide whether it is the case or not to ask Fire Station for a Fire ghting Truck
intervention. As described in [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], the Social Structure is further detailed by
interaction structure diagrams to model activities among and within roles in order
to achieve their objectives. Such activities are called scenes.
        </p>
        <p>First_Aid_
Station
(fas)</p>
        <p>(as)
Police_Station
(ps)</p>
        <p>Firefighter_</p>
        <p>Team
(ft)
(dt)
(dbf)</p>
        <p>Fire_Station</p>
        <p>(fs)
(ef)</p>
        <p>(el)
Firefighting
_Truck
(fft)</p>
        <p>Emergency
_Cal _Center
(ecc)</p>
        <p>Notice that, the speci cation provided at this time is not su cient to give a
complete picture about the know how required to software systems to achieve
the modelled organisational objectives. Nevertheless, the level of abstraction
achieved provides enough anchor points for agents to coordinate their activity
without fully pre-specifying the capabilities of the agents and therefore limiting
exibility.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Approach overview</title>
      <sec id="sec-3-1">
        <title>A meta-level view of conceptual models</title>
        <p>In order to e ectively deal with the MAS development, the proposed approach
takes into account both the syntax and the semantics of a MAS, through an
integration of MDA with Reasoning and Domain Knowledge speci cation Based
on Ontology. Fig. 2 illustrates the architecture of our approach. The central
part corresponds to the OperA metamodel, which provides the syntax of MAS.
The right part provides the actual semantics of MAS, which is described by
the OperA ontology. The MAS ontology instantiation will be automatically
produced from the MAS model, which is created with the OperettA tool. Next,
the MAS ontology instantiation will be semantically checked against the OperA
ontology, see section 3.2. The left part provides an interaction between existing
domain ontologies and MAS models. The interaction is maintained by de ning
transformations relation between the OperA metamodel and EODM3. EODM is
an implementation of the ODM standard from OMG, de ning metamodels for
RDF(S) and OWL, see section 3.3.</p>
        <sec id="sec-3-1-1">
          <title>EODM</title>
          <p>Metamodel
o
t
s
m
fr
o
n
o
C</p>
        </sec>
        <sec id="sec-3-1-2">
          <title>Domain ontology</title>
        </sec>
        <sec id="sec-3-1-3">
          <title>Model</title>
        </sec>
        <sec id="sec-3-1-4">
          <title>Relations</title>
        </sec>
        <sec id="sec-3-1-5">
          <title>Associated with</title>
        </sec>
        <sec id="sec-3-1-6">
          <title>Opera Metamodel</title>
        </sec>
        <sec id="sec-3-1-7">
          <title>Opera Ontology M2</title>
        </sec>
        <sec id="sec-3-1-8">
          <title>Ontology</title>
          <p>Import/export
o
t
s
m
fr
o
n
o</p>
          <p>C</p>
          <p>MAS Model
(e.g.: FireStation)
o
t
s
m
fr
o
n
o
C</p>
        </sec>
        <sec id="sec-3-1-9">
          <title>Produces</title>
        </sec>
        <sec id="sec-3-1-10">
          <title>MAS ontology instantiation (e.g.: FireStation) M1</title>
        </sec>
        <sec id="sec-3-1-11">
          <title>External domain modelling</title>
        </sec>
        <sec id="sec-3-1-12">
          <title>MAS modelling</title>
        </sec>
        <sec id="sec-3-1-13">
          <title>Semantic constraints verification</title>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>Reasoning with models compliant with OperA ontology</title>
        <p>The rst aspect of our integrated approach is directed toward reasoning on our
models using logics, with description logic as our language mainly dedicated
at reasoning on the structural aspect of our models. This will provide us with
the ability to use the power of descriptive logic along with associated reasoners,
combined with techniques to formally analyse our models and enhance their
quality.</p>
        <p>At the meta-level, the abstract syntax is de ned through metamodelling and
the semantics is based on description logic. This results in the OperA ontology,
which formalises OperA conceptual framework concepts and their relationships,
as well as domain independent OperA semantics constraints. Meanwhile, the
integration of the metamodelling and ontologies supports domain speci c
languages and also o ers the opportunity to query the models. Indeed, as the OperA
metamodel is associated to the OperA ontology, a MAS model is associated to
a MAS ontology instantiation. Consequently, the semantics of our models are
stored in the MAS ontology instantiation, which is automatically produced using
3 http://www.eclipse.org/modeling/mdt/?project=eodm
the MAS model (following a straightforward transformation). Hence, it allows for
the designer, the veri cation and validation of models using ontologies; namely,
the application of description logics for reasoning about the OperA language. In
the following, some examples of semantics constraints, that we are interested in
verifying, have been proposed.</p>
        <p>{ Checking if the objective of a dependency is an objective or a sub-objective
of the dependency's initiator. For instance, in the running scenario, this
would mean verifying that the role re-station possesses an objective or
subobjective extinguish re as it appears to be dependent on Fire ghter Team
for it.
{ Checking if each dependency is realised by at least one scene.
{ Checking if roles are involved in a dependency, do indeed cooperate in at least
one realisation scene of that dependency. Again, referring to the scenario,
there must be at least one realisation scene of objective deal with big res
dependency in which Fire ghter Team and Fire ghter Truck must cooperate.
{ Checking that each role posses at least one dependency link.</p>
        <p>
          The approach described above has been partly implemented in and illustrated
by the OperettA prototype [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. The results obtained with that prototype have
encouraged us to move towards a more standardised and accessible version of
the tool. The actual version is currently under development using Eclipse.
3.3
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>Conforming design models to domain ontology</title>
        <p>The second aspect of our approach permits the use of ontology within our models
as the source of domain speci c related knowledge, necessary for the description
and support of roles interaction and communication in OperA organisation and
at a lesser extend, domain speci c semantics constraints enrichment. That is,
domain ontologies are integrated at the model level. They are de ned, used and
imported within the OperA modelling language as well as exported from it.
For the latter two, a relation is de ned at the meta-level, between the Eclipse
Ontology De nition Metamodel and the OperA metamodel enabling the interaction
with standard ontology representation languages like OWL. Meanwhile, in the
ontological world the integration is at the same level. That is, the OperA ontology
and domain ontology are at the same level within logic hierarchy; paving the way
for the analysis of the overall structural aspect of the organisation, consisting in
querying one knowledge base being the combination of the OperA ontology, the
Domain Ontology and the derived MAS ontology instantiation.</p>
        <p>Firstly, a vocabulary is available for describing interactions and supporting
communications related to a domain. Referring back to our Fire Station
organisation, given the equivalent formal notation for the objective extinguish {e.g.,
Extinguish-Fire(L : location){ of the Fire gther Team role, the concept of
Location must be de ned in the Domain ontology, otherwise the parameter type
will not be available when de ning the objective. Furthermore, at run-time, this
ontology will be used by members of the organisation in order to communicate.</p>
        <p>Secondly, the OperA Ontology can be enlarged by further modelling
domainspeci c constraints enriching the generic semantic constraints. It provides the
opportunity to de ne modelling rules within the domain ontology as (re)con guration
rules e.g., a speci c domain could forbid more than 2 dependencies between two
speci c roles.</p>
        <p>This second aspect provides a separation of concerns for knowledge taking
into account its domain speci c part and enabling at the same time the tool to
tailor himself based on it.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusions</title>
      <p>This paper describes the features of an implemented design tool, OperettA,
based on the OperA methodology. This enables the construction of a
development framework to support software and services engineering. Besides, this
contributes to the achievements of a more general research objective established
within the ALIVE project. Speci cally, the ALIVE project combines cutting
edge Coordination technology and Organisation theory mechanisms to provide
exible, high-level means to model the structure of inter-actions between services
in the environment.</p>
      <p>The proposed approach (partly) implemented in OperettA deals with
techniques to integrate features of the model driven architecture (MDA) with
features of the ontology languages (OWL). Main bene ts of our approach come
from the fact that it provides a model driven approach for the speci cation of a
MAS dealing with its semantics and its provision of domain speci c knowledge.
Hence, our approach allows designers for powerful reasoning mechanisms to be
employed as well as a smart integration of domain speci c knowledge that comes
rst to re ne and enrich (along with further constraints) the speci cation of the
design model.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>V.</given-names>
            <surname>Dignum</surname>
          </string-name>
          .
          <article-title>A Model for Organizational Interaction: based on Agents, founded in Logic</article-title>
          .
          <source>PhD thesis</source>
          , Universiteit Utrecht,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Brian</surname>
          </string-name>
          Henderson-Sellers and Paolo Giorgini, editors.
          <source>Agent-Oriented Methodologies</source>
          . Idea Group Inc.,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>A.</given-names>
            <surname>Fuxman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Giorgini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kolp</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          .
          <article-title>Information systems as social structures</article-title>
          .
          <source>In FOIS '01: Proceedings of the international conference on Formal Ontology in Information Systems</source>
          , pages
          <fpage>10</fpage>
          {
          <fpage>21</fpage>
          , New York, NY, USA,
          <year>2001</year>
          . ACM.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Borgida</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Jarke</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Koubarakis</surname>
          </string-name>
          .
          <article-title>Telos: representing knowledge about information systems</article-title>
          .
          <source>ACM Trans. Inf</source>
          . Syst.,
          <volume>8</volume>
          (
          <issue>4</issue>
          ):
          <volume>325</volume>
          {
          <fpage>362</fpage>
          ,
          <year>1990</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>D. M.</given-names>
            <surname>Okouya</surname>
          </string-name>
          and
          <string-name>
            <given-names>V.</given-names>
            <surname>Dignum</surname>
          </string-name>
          .
          <article-title>A prototype tool for the design, analysis and development of multi-agent organizations</article-title>
          .
          <source>In DEMO Session: Proc. of the 7th Int. Joint Conf. on Autonomous Agents and Multiagent Systems (AAMAS-08)</source>
          . ACM,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>J.</given-names>
            <surname>Bezivin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Farcet</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.-M. Jezequel</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Langlois</surname>
            , and
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Pollet</surname>
          </string-name>
          .
          <article-title>Re ective model driven engineering</article-title>
          .
          <source>In UML</source>
          , pages
          <volume>175</volume>
          {
          <fpage>189</fpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>