<!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>Developing Virtual Organizations Using MDD</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jorge Aguero</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Miguel Rebollo</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Carlos Carrascosa</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vicente Julian</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Departamento de Sistemas Informaticos y Computacion Universidad Politecnica de Valencia Camino de Vera</institution>
          <addr-line>S/N 46022 Valencia</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <fpage>130</fpage>
      <lpage>141</lpage>
      <abstract>
        <p>Virtual Organizations are novel mechanisms where agents can demonstrate their social skills, due to the fact that they can work in a cooperative and collaborative way. Furthermore, organizations are frameworks where agents can achieve different types of agreements. But the development of organizations in MAS (Multi-Agent Systems) requires extensive experience in different methodologies and platforms. MDD (Model Driven Development) is a technique for generating application code developed from basic models and meta-models using a variety of automatic transformations. This paper presents a meta-model of Virtual Organization (of agents) using concepts and components at a suitable level of abstraction so that it can be implemented on different systems following a MDD approach. Based on this idea, a service-oriented organizations meta-model that is platform independent is presented. As an example, two model transformations that allow the uni ed model of the virtual organization to be translated into two different platforms are shown, facilitating the development process of agent-based software from the point of view of the user.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Advances in new technologies based mainly on the Internet and the Web, such
as electronic commerce, mobile/ubiquitous computing, social networks, etc.,
demonstrate the need to develop distributed applications with some intelligent
capabilities. Multi-Agent Systems (MAS) are a powerful technology with very
signi cant applications in distributed systems and arti cial intelligence[
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
Supporting all of these developments requires the creation of platforms of highly
heterogeneous agents, where agents work together through different interactions
to support complex tasks, in a collaborative and dynamic way. Bearing this in
mind, it is suitable for agents to display characteristics such as sociability,
autonomy, self-organization, etc. Therefore, it is necessary to create open systems
composed of a group of cooperative and heterogeneous agents, which work with
local or individual goals and that must ful ll global goals. That is, a set of agents
can reach agreements to achieve the group goals. The concepts of organization
allow individual and group entities to be modelled in a very abstract way[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The
organization describes the main aspects of a society based on different
viewpoints, such as: structure, functionality, norms, interactions, and environment.
This type of organization is called Virtual Organization[
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
      </p>
      <p>
        However, to implement an Agents Virtual Organization requires vast
experience in one or more design platforms. A major challenge when designing MAS
is to provide efficient tools that can be used by any user (non-expert users). The
MDD approach can facilitate and simplify the design process and the quality of
agent-based software[
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], since it allows the reuse of software and transformation
between models. MDD basically proposes the automatic generation of code from
the models using the transformations. In other words, using models that have
components that are platform independent, and by means of the
transformations, those models are translated into components (or code) that depend on the
execution platform, which integrates speci c details about the system. Recently
some proposals to implement these ideas (MDD techniques) have been proposed
in MAS[
        <xref ref-type="bibr" rid="ref14 ref16 ref17 ref2">16, 14, 17, 2</xref>
        ], but none of these proposals focus on organization design.
      </p>
      <p>
        Our purpose is to use the MDD approach for the design of organizations,
taking the core and fundamental concepts, to specify an organization
metamodel that is platform independent, and then use the translation mechanism to
convert the uni ed meta-model into platform speci c models for the execution
of the agents. This paper presents a Virtual Organization meta-model, focused
mainly on the integration of service-oriented technology and MAS, which allows
support (from a very high level of abstraction) to be given to dynamic and open
agent societies. Two transformation models for moving the uni ed model of the
Virtual Organization to two different platforms are also proposed, allowing the
feasibility of the proposal to be veri ed. These target platforms are: THOMAS1
[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and E-Institutions2[
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>This paper is structured as follows. A brief summary of relevant works and
their problems are discussed in Section 2. Section 3 presents MDD concepts and
how to apply these concepts to the MAS paradigm. Section 4 explains how to
design a virtual organization from the MDD viewpoint. Finally, the conclusions
of this work are presented in Section 5.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>This section presents some related contributions with respect to organization
modeling in agent-based systems, and discusses some problems. Furthermore,
this section explains how, using the MDD approach, these problems can be
addressed.</p>
      <p>
        MAS development needs methodologies that allow the design of agent-based
software to be optimized. The rst methodologies that emerged can be classi ed
as agent-oriented, without describing the organization explicitly. These systems
are generally closed and external agents are prohibited. But in recent times, new
organizational-oriented methodologies have emerged, which allow (partially) the
1 http://users.dsic.upv.es/grupos/ia/sma/tools/Thomas
2 http://e-institutions.iiia.csic.es
design of open MAS, leading to the development heterogeneous systems. These
organizational-oriented methodologies allow external agents to access the system
functionality, but the agents are obliged to adhere to the social norms of the
system. Among the most important methodologies which allow the design of
virtual organizations are: PASSI[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], MOISE[
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], OperA[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] and GORMAS[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>Now, with respect to the application of MDD for MAS, all of the above
commented methodologies allow (to a major or minor extent) the design of agent
organizations using their own set of speci cations. But, in general, these
proposals only use speci c aspects of the platforms, which are in the majority of
cases very different. This situation can create an added complexity for
developers which try to employ these approaches. Moreover, some of them do not
have an implementation phase, only de ning high-level models, and difficulting
enormously the developer work when tries to obtain executable code. But with
the appearance of the MDD, it is possible to take advantage the exibility
provided by this approach to solve \some" of the problems found in the design of
organizations in MAS.</p>
      <p>
        The purpose of MDD is to create models legible by computers that can be
understood by automatic tools to generate templates, proof models and even code,
integrating them in multiple platforms[
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. From the viewpoint of the
development of agent oriented systems, application development consists of obtaining
the agent code that can be executed in different platforms. That is, to
concentrate on the development of the application from a uni ed agent model and
apply different transformations to get implementations for different platforms.
Currently, the most common methodologies for MAS have an identi ed set of
models that specify their characteristics. These models can be adjusted as MDD
models that specify the concepts of the MAS as roles, behaviors, tasks,
interactions or protocols. The models can be used to model a MAS without focusing on
platform-speci c details and requirements. After this, it is possible to transform
any agent model into agent implementations for different platforms.
      </p>
      <p>
        Only a few agent development methodologies have integrated the MDD
techniques in the MAS design. The most relevant are MetaDIMA[
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], TROPOS[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ],
PIM4AGENT[
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], INGENIAS[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], AML [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] and AUML [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. All of this work is for
the application of MDD to the agent modeling process, but the biggest problem
found, is that they do not consider the development of virtual organizations.
      </p>
      <p>Therefore, our purpose is to apply the MDD approach to
organizationaloriented methodologies. In other words, the contribution of this paper is to take
as a starting point previous works of organization design in MAS, to develop
a Uni ed Model of Virtual Organization which allows exible implementation
(including deployment) on different agent platforms with support for
organizations.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Modeling Virtual Organizations with MDD</title>
      <p>This section presents how to use the MDD approach to model organizations. In
order to do this, the core concepts of MDD are presented rst. Then, the
metamodels for the organization and the process of creating Virtual Organization
using the MDD approach is explained.
3.1</p>
      <sec id="sec-3-1">
        <title>MDD: Core Concepts</title>
        <p>
          The MDD approach uses and creates different models at different abstraction
levels, combining them when the application has to be implemented [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. At
high abstraction levels, the models are known as meta-models and they de ne
the structure, semantics and constraints for a family of models (they are the
model of a model). Models can be classi ed into three groups depending on
their abstraction level: Computation Independent Model (CIM), which details
the general concepts independently whether they are going to be implemented
by a machine or not; Platform Independent Model (PIM), which represents the
system functionalities without considering the nal implementation platform;
and the Platform Speci c Model (PSM), obtained by combining the PIM with
speci c details about the selected platform.
        </p>
        <p>
          A fundamental aspect of the MDD is the de nition of sets of transformation
rules between models, which allows the models to be automatically converted.
Transformations are relational entities that describe how to map the rules
concerning how the concepts of one model are transformed into the concepts of
another model. These transformations can be applied at different abstraction
levels. Horizontal transformations are applied over models that belong to the
same level: PIM-to-PIM or PSM-to-PSM. Vertical transformations turn a
general model into a more speci c one (PIM-to-PSM) [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. In general, all
transformations are known as model-to-model transformations. Additionally, executable
code can be automatically generated from a PSM. These transformations are
known as model-to-code or model-to-text.
3.2
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>Using MDD to de ne an Agent Virtual Organization</title>
        <p>One fundamental challenge when de ning a platform independent meta-model
in an organization is selecting which concepts or components will be included in
order to model the organization. It is almost too obvious to mention that this
is not a trivial task, since it must de ne the minimum components necessary
for the organization. To achieve this objective, some of the most well-known
approaches in the area of MAS organizations were studied (mentioned in
Section 2). The purpose of this analysis is to extract the common features from
the methodologies studied and adapt them to the current proposal, specifying a
platform independent meta-model of the organization. Therefore, the
transformation mechanism turns the platform independent model (PIM) into platform
speci c models (PSM's). Figure 1 shows diagram that illustrates the relationship
among the meta-models.</p>
        <p>
          In these methodologies, an agent organization is considered a social entity
consisting of a speci c number of members which carry out different tasks or
functions, and that are structured according to communication patterns and
topology speci c interactions, to achieve the global objective of the
organization, based on behavior rules. The main aspects or factors of an organizations
are the structure, functionality, dynamic, normative and its environment. So, to
model the characteristics of these components ve key concepts are used:
Organizational Unit, Service, Environment, Norm and Agent [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. These concepts make
it possible to represent: (i) how the entities are grouped with each other, de ning
the relationship between the elements and their environment; (ii) what
functionality they offer, including services for the dynamic entry and exit of agents in the
organization, and (iii) what restrictions exist regarding the behaviors of system
entities[
          <xref ref-type="bibr" rid="ref10">10</xref>
          ].
3.3
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>Organization Meta-model</title>
        <p>This section presents our proposal for modeling agent organizations, based on
ve key concepts(previously mentioned): Organizational Unit, Service,
Environment, Norm and Agent. The proposal is presented de ning a set of meta-models,
which provide the necessary concepts and primitives to describe structure,
functionality, dynamism, environment and normative behaviors of the organization.
This set of meta-models will be called VOM (Platform Independent Virtual
Organization Model ) and is structured in different views or perspectives. The
motivation for this is to support the evolution of the meta-model and to allow
its possible growth in the future. The different views give complementary
approaches which, when superposing themselves, generate the complete view of the
system. Below, the different views proposed are brie y detailed due to the space
limitations of the paper.</p>
        <p>
          Structural view: This view includes all those elements that persist in the
organization (see Figure 2(a)). The main concept employed in this view is the
Organizational unit (OU). An OU is a group of agents who carry out speci c
and differentiated tasks and follow a certain prede ned communication and
cooperation pattern[
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. This clustering can be seen externally as a single entity
that pursues certain objectives, offers and/or requires certain services, and even
plays a speci c role in order to interact with other entities. Therefore, the
organizational unit has a recursive nature and will not only contain agents but also
other organizational units acting as atomic entities.
        </p>
        <p>Functional view: This view details system functionality, based on services,
tasks and objectives. This view shows the general behavior desired by the
system. Thus, Services represent a certain functionality that an entity (Agent or
OU) provides other entities, see the meta-model in Figure 2(b). The provider
of a Service is always associated with a speci c Role. Service functionality is
carried out through the execution of certain Tasks, typically executed by the
entity providing the service or delegated to other entities. The services can also
be composed of several sub-services, and it is possible to de ne a \work ow"
between them using (RelationType).</p>
        <p>Environment view: This perspective details the elements (Resources) of
the system. The resources are accessed and perceived through an
EnvironmentPort (see the meta-model in Figure 2(c)). A Resource is an object in the
environment that will be consumed by its members. A Port represents a point of
interaction between the entity and other elements of the model and serves as an
interface to the real world.</p>
        <p>Normative view: This model assumes that the organization is managed
according to norms. Norms are used as mechanisms to limit the autonomy of
agents in large systems and solve complex problems of coordination. This view
speci es the set of rules and actions de ned to control the behavior of
members of the organization, speci cally the roles of the organization (see Figure
2(d)). These rules correspond to obligations, permissions and prohibitions; also
as sanctions and rewards to carry out on its members.</p>
        <p>
          Agent view: A Agent is the basic entity of MAS which is within the
organization and uses a series of interrelated components, shown in Figure 3. Our
Agent has a set of basic components: Capabilities represent the know-how of
the Agent and follow a pattern of event-condition-action. The Behaviours
implement the roles that the agent can play. The Task is the component where the
code base of the agent actions is written. For a more detailed explanation of the
components of the agent meta-model, please refer to Aguero at el[
          <xref ref-type="bibr" rid="ref1">1</xref>
          ].
        </p>
        <p>
          Developing an organization with a MDD approach
Once the set of models that characterize our proposed model of Virtual
Organization platform-independent has been presented, the process for transforming
the Virtual Organization into different platforms must be de ned. The design
process begins by selecting how abstract concepts (which are part of the uni ed
organization model) are mapped to the target platforms. For this paper, we focus
on the study of transformations on two platforms that support agents
organizations: THOMAS[
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] and E-Institutions[
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. The transformation de nes a set
of mapping rules. The rst mapping rules de ne which concepts of the source
meta-model ( VOM) are transformed to which concepts of the target
metamodel, a model-to-model transformation (PIM-to-PSM). This is illustrated by
dotted lines in Figure 4. The second transformation translate the models into the
code templates of the organization, which can be optionally combined with code
written manually by the user. This is a model-to-text transformation
(PSM-tocode).
The VOM meta-model is very similar to the model of the organization
programmed in THOMAS, since both works are based (partially) on the
methodology and artifacts proposed by GORMAS. For this reason, the automatic
transformations are relatively easy to describe. Almost all of the abstract concepts
of VOM are represented in THOMAS, so the model-to-model transformation
rules are expressed almost as a one-to-one relationship. It is convenient to
notice that some concepts in THOMAS have a more detailed feature than VOM,
because THOMAS is a platform-speci c model. The transformation rules that
must perform the translation between different models are shown in Table 1
(from rule 1 to rule 8).
4.2
        </p>
      </sec>
      <sec id="sec-3-4">
        <title>Development Process Using the E-Institutions Platform</title>
        <p>
          E-institutions provide a set of tools that are widely used in the area of agents to
model organizations, which are de ned as a Multi-Agent Systems and can be
effectively designed and implemented as electronic institutions composed of a vast
amount of heterogeneous (human and software) agents playing different roles and
interacting by means of speech acts[
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. They take inspiration from traditional
human institutions, and offer a general agent-mediated computational model
Rule
        </p>
        <p>Concept
1 Organizational Unit
2 Agent
3 Role
4 Service
5 Norm
6 RelationType
7 Resource
8 Goal
9 Organizational Unit
10 Agent
11 Role</p>
        <p>Transformation
THOMAS</p>
        <p>VOM.OU ) THOMAS.OU
VOM.Agent ) THOMAS.Agent</p>
        <p>VOM.Role ) THOMAS.Role
VOM.Service ) THOMAS.Service</p>
        <p>VOM.Norm ) THOMAS.Norm
VOM.RelationType ) THOMAS.Process</p>
        <p>VOM.Resource ) THOMAS.Resource</p>
        <p>VOM.Goal ) THOMAS.Goal
E-INSTITUTIONS
∪</p>
        <p>VOM.OU ) ∪ EI.Scene
VOM.Agent ) EI.Agent</p>
        <p>
          VOM.Role ) EI.Role
that serves to realize an agent-mediated electronic institutions. In Figure 5, the
main meta-model components of E-Institutions are presented. Transformation
rules for E-Institutions are shown in Table 1 (from rule 9 to rule 16). Due to
the space limitations of this paper, each transformation rule cannot be detailed.
Instead, in order to illustrate its use to the reader, an application scenario of
core rules is described in the next section.
To illustrate the use of the rules, a case scenario for making ight and hotel
arrangements is utilized. This is a well known example that has been modeled
by means of electronic institutions in previous works (Dignum [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]; Argente et al
[
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]). The Travel Agency example is an application that facilitates the
interconnection between clients (individuals, companies, travel agencies) and providers
(hotel chains, airlines); delimiting services that each one can request or offer.
The system controls which services must be provided by each entity. Provider
entities are responsible for the internal functionality of these services. However,
the system imposes some restrictions on service pro les, service requesting
orders and service results. In this system, agents can search for and make hotel
and ight reservations, and pay in advance for bookings. This case study is
modeled as an organization (TravelAgency ) inside which there are two organizational
units (HotelUnit and FlightUnit) which represent a group of agents. Each unit is
dedicated to hotels or ights, respectively. Three kind of roles can interact in the
Travel Agency example: customer, provider and payee roles. The Customer role
requests system services. More speci cally, it can request hotel or ight search
services, booking services for hotel rooms or ight seats, and payment services.
The Provider role is in charge of performing the service. Finally, the Payee role
gives the advanced payment service. Figure 6 shows the TravelAgency structure,
with its units, roles and relationships between them.
        </p>
        <p>The process begins by modeling the Travel Agency (structural and functional
models, see Figure 6(a)(b)), and applying the rules mentioned previously, in
order to obtain the organizations on THOMAS and E-Institutions. In the case
of THOMAS the models are very similar and their transformation in almost
direct (see in Figure 7(a)). But, getting the organization in E-Institutions and
creating the core templates of PerformativeStructure seen in gure 7(b), requires
the application of the rule 9 and rule 13.</p>
        <p>Rule 9 allows all of the Scenes in the E-Institutions that correspond to the
OU of VOM (3 in total) to be obtained. Additionally the Scenes for entrance
and exit are needed (root and output). After the application of Rule 13, as the
Services are composed in the order given by the RelationType, we can specify the
type of Transitions between the different Scenes in the E-Institutions, which in
this case correspond to Transitions of type OR. As previously mentioned, this
mapping generates the basic template of the PerformativeStructure of the
EInstitutions (Figure 7(b)). With the application of the remaining rules, a more
detailed description of the PerformativeStructure is obtained, but due to the
limitations of space in this paper, they are not explained.
This work presents a meta-model of Virtual Organization (called VOM) which
allows organizations in MAS to be modeled using abstract components which are
independent of the implementation platform following a MDD approach. This
meta-model is divided into ve views that focus on the most important aspects
of the Virtual Organizations and these views can easily be extended if required
to a speci c domain.</p>
        <p>From uni ed meta-model, creating code templates for speci c platforms of
organizations is possible. This was discussed and exempli ed using
transformations on the THOMAS and E-Institutions platforms. These transformations
show that the meta-model can be considered platform independent. As future
work, we will propose additional transformations in order to obtain the agent
instances (to generate the agent code) in the proposal and other frameworks. We
will propose the introduction of speci c components/views (additional) to reach
agreements. We propose that the Virtual Organization provides the framework
and components required to model agreements, or in other words, use the MDD
approach to drive design-oriented agreements.</p>
        <p>Acknowledgment: This work was partially supported by
TIN2006-14630C03-01 and PROMETEO/2008/051 projects of the Spanish government and
CONSOLIDER-INGENIO 2010 under grant CSD2007-00022.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. J. Aguero, M. Rebollo,
          <string-name>
            <given-names>C.</given-names>
            <surname>Carrascosa</surname>
          </string-name>
          , and
          <string-name>
            <given-names>V.</given-names>
            <surname>Julian</surname>
          </string-name>
          .
          <article-title>Does android dream with intelligent agents?</article-title>
          <source>In Int. Symposium on Distributed Computing and Arti cial Intelligence</source>
          <year>2008</year>
          (
          <issue>DCAI2008</issue>
          ),
          <source>ISBN: 978-3-540-85862-1</source>
          , pages
          <fpage>194</fpage>
          {
          <fpage>204</fpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. J. Aguero, M. Rebollo,
          <string-name>
            <given-names>C.</given-names>
            <surname>Carrascosa</surname>
          </string-name>
          , and
          <string-name>
            <given-names>V.</given-names>
            <surname>Julian</surname>
          </string-name>
          .
          <source>Agent design using Model Driven Development In 7th Int. Conference on Practical Applications of Agents and Multi-Agent Systems(PAAMS2009)</source>
          ,
          <source>ISBN 978-3-642-00486-5</source>
          , pages
          <fpage>60</fpage>
          {
          <fpage>69</fpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>E.</given-names>
            <surname>Argente</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Julian</surname>
          </string-name>
          , and
          <string-name>
            <given-names>V.</given-names>
            <surname>Botti</surname>
          </string-name>
          .
          <article-title>Mas modelling based on organizations</article-title>
          .
          <source>In 9th Int. Workshop on Agent Oriented Software Engineering</source>
          , pages
          <volume>1</volume>
          {
          <fpage>12</fpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>E. Argente</given-names>
            <surname>Villaplana</surname>
          </string-name>
          . Gormas:
          <article-title>Gu as para el desarrollo de sistemas multiagente abiertos basados en organizaciones</article-title>
          .
          <source>PhD thesis</source>
          , UPV, Spain,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>B.</given-names>
            <surname>Bauer</surname>
          </string-name>
          .
          <article-title>Uml class diagrams revisited in the context of agent-based systems</article-title>
          .
          <source>Proceedings Agent-Oriented Software Engineering</source>
          , pages
          <volume>101</volume>
          {
          <fpage>118</fpage>
          ,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>P.</given-names>
            <surname>Bresciani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Perini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Giorgini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Giunchiglia</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          . Tropos:
          <article-title>An agent-oriented software development methodology</article-title>
          .
          <source>Autonomous Agents and Multi-Agent Systems</source>
          ,
          <volume>8</volume>
          (
          <issue>3</issue>
          ):
          <volume>203</volume>
          {
          <fpage>236</fpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>C.</given-names>
            <surname>Carrascosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Giret</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Julian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Rebollo</surname>
          </string-name>
          , E. Argente, and
          <string-name>
            <given-names>V.</given-names>
            <surname>Botti</surname>
          </string-name>
          .
          <article-title>Service oriented multi-agent systems: An open architecture</article-title>
          .
          <source>In Autonomous Agents and Multiagent Systems (AAMAS)</source>
          , pages
          <fpage>1</fpage>
          <issue>{2</issue>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>R.</given-names>
            <surname>Cervenka</surname>
          </string-name>
          and
          <string-name>
            <given-names>I.</given-names>
            <surname>Trencansky</surname>
          </string-name>
          .
          <source>The Agent Modeling Language { AML. Whitestein Series in Software Agent Technologies and Autonomic Computing</source>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>M.</given-names>
            <surname>Cossentino</surname>
          </string-name>
          and
          <string-name>
            <given-names>C.</given-names>
            <surname>Potts</surname>
          </string-name>
          .
          <article-title>Passi: A process for specifying and implementing multi-agent systems using uml</article-title>
          .
          <source>Technical report</source>
          , University of Palermo,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <given-names>N.</given-names>
            <surname>Craido</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Argente</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Julian</surname>
          </string-name>
          , and
          <string-name>
            <given-names>V.</given-names>
            <surname>Botti</surname>
          </string-name>
          .
          <article-title>Designing virtual organizations</article-title>
          .
          <source>In 7th Int. Conference on Practical Applications of Agents and Multi-Agent Systems(PAAMS2009)</source>
          ,
          <source>ISBN 978-3-642-00486-5</source>
          , pages
          <fpage>440</fpage>
          {
          <fpage>449</fpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <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 dissertation</source>
          , Utrecht University,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>M. Esteva</surname>
            ,
            <given-names>J. A.</given-names>
          </string-name>
          <string-name>
            <surname>Rodr</surname>
            guez-Aguilar,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Sierra</surname>
            , and
            <given-names>J. L.</given-names>
          </string-name>
          <string-name>
            <surname>Arcos</surname>
          </string-name>
          .
          <article-title>On the formal speci cations of electronic institutions</article-title>
          .
          <source>Lecture Notes in Computer Science</source>
          , pages
          <volume>126</volume>
          {
          <fpage>147</fpage>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>J. Ferber</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          <string-name>
            <surname>Gutknecht</surname>
            , and
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Michel</surname>
          </string-name>
          .
          <article-title>From agents to organizations: an organizational view of multi-agent systems</article-title>
          .
          <source>Lecture Notes in Computer Science</source>
          , pages
          <volume>214</volume>
          {
          <fpage>230</fpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. I.
          <string-name>
            <surname>Garca-Magario</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Gomez-Sanz</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>R.</given-names>
            <surname>Fuentes</surname>
          </string-name>
          .
          <article-title>Ingenias development assisted with model transformation by-example: A practical case</article-title>
          .
          <source>In 7th Int. Conf. on Practical Applications of Agents and MultiAgent Systems</source>
          , pages
          <fpage>40</fpage>
          {
          <fpage>49</fpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <given-names>B.</given-names>
            <surname>Gateau</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Boissier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Khadraoui</surname>
          </string-name>
          , and
          <string-name>
            <surname>E. Dubois. Moiseinst:</surname>
          </string-name>
          <article-title>An organizational model for specifying rights and duties of autonomous agents</article-title>
          .
          <source>In Third European Workshop on Multi-Agent Systems (EUMAS2005)</source>
          , pages
          <fpage>484</fpage>
          {
          <fpage>485</fpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <given-names>Z.</given-names>
            <surname>Guessoum</surname>
          </string-name>
          and
          <string-name>
            <given-names>T.</given-names>
            <surname>Jarraya</surname>
          </string-name>
          .
          <article-title>Meta-models &amp; model-driven architectures. In Contribution to the AOSE TFG AgentLink3 meeting</article-title>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>C. Hahn</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Madrigal-Mora</surname>
            , and
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Fischer</surname>
          </string-name>
          .
          <article-title>A platform-independent metamodel for multiagent systems</article-title>
          . In Autonomous Agents and
          <string-name>
            <surname>Multi-Agent</surname>
            <given-names>Systems</given-names>
          </string-name>
          ,
          <volume>18</volume>
          (
          <issue>3</issue>
          ):
          <volume>239</volume>
          {
          <fpage>266</fpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <given-names>N.</given-names>
            <surname>Jennings</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Wooldridge</surname>
          </string-name>
          .
          <article-title>Applications of intelligent agents</article-title>
          .
          <source>In Agent Technology: Foundations, Applications, and Markets</source>
          , pages
          <volume>3</volume>
          {
          <fpage>28</fpage>
          ,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <given-names>A.</given-names>
            <surname>Kleppe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. B.</given-names>
            <surname>Warmer</surname>
          </string-name>
          , and
          <string-name>
            <given-names>W.</given-names>
            <surname>Bast</surname>
          </string-name>
          . MDA Explained:
          <article-title>The Model Driven Architecture: Practice and Promise</article-title>
          .
          <string-name>
            <surname>Addison-Wesley Professional</surname>
          </string-name>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>