<!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>CREATING A COMPREHENSIVE AGENT-ORIENTED METHODOLOGY - EXTENDED ABSTRACT</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Brian Henderson-Sellers</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Information Technology, University of Technology</institution>
          ,
          <addr-line>Sydney, PO Box 123, Broadway, NSW 2007</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        While individual agent-oriented methodologies are useful for restricted situations, for wider industry
adoption it is useful to create a methodological framework that provides method fragments from which
situationally specific methodologies can be constructed. Such a flexible approach can be found in the
use of situational method engineering (SME). In this context, this article describes the details of SME
and its embodiment in the OPEN Process Framework (OPF) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The OPF uses an underpinning
metamodel, a repository (a.k.a. methodbase) of method fragments and guidelines to assist method
engineers create the final methodological approach from a selected number of fragments to form an
organization-specific or project-specific methodology.
      </p>
      <p>Having described SME with the OPF, we then show how this basis is suitable not only for objects
but also for agents and discuss agent-specific method fragments. We then demonstrate how it becomes
possible not only to recreate whole agent-oriented methodologies such as Prometheus or Gaia or
Tropos but how it is also possible to create an enhanced methodology such as might be obtained, for
instance, by adding Tropos method fragments into a Prometheus-style methodology in order to tailor
Prometheus to situations for which it was not originally designed.</p>
      <p>
        This paper was originally published as Chapter XIII in a book entitled Agent-Oriented
Methodologies (edited by B. Henderson-Sellers and P. Giorgini) by Idea Group in July 2005. The aim
of the book was to present a significant number of agent-oriented methodologies, written by the
original developers, but in a standard format. They were asked to not only describe their approaches
but also highlight specific positive features and areas not addressed in their methodologies. These were
followed by a chapter evaluating these 10 approaches objectively [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and then this final chapter [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
The overall aim is to encourage “convergence” between methodologies so that when industry en masse
adopts agents there will be an agreed methodological offering. The idea is to avoid the errors of OO
wherein industry sought an OO methodology to adopt in the early 1990s and were offered between 20
and 60 (depending upon which author you read) – this was tantamount to an admission that OO was
not ready for industry usage.
      </p>
      <p>
        The way forward is proposed to be Situational Method Engineering (SME) [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Rather than
seeking a single unified methodology, unification occurs at the metamethodology level [e.g. 5] and
method fragments are generated from concepts in this metamodel [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and stored in a repository or
methodbase [
        <xref ref-type="bibr" rid="ref4 ref6 ref7">4,6,7</xref>
        ]. Construction guidelines [
        <xref ref-type="bibr" rid="ref1 ref7 ref8 ref9">1,7-9</xref>
        ] are then followed in order to create a methodology
that takes into account the many industry situational factors, including, for instance, security,
reliability, real-time, safety criticality, organizational maturity, project size and developers’ skills
levels. This approach is technology agnostic and all these elements are as suitable for agent technology
as for object technology.
      </p>
      <p>
        The sources for fragments are largely existing methodologies [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] plus best practice. For agents,
there are around a dozen or so extant methodologies that have provided fragments to enhance the
original OO-focussed repository of the OPF so that it can offer full support for the re-creation of AO
methodologies. The fragments have thus far been gleaned from each individual AO methodology and
are summarized in the book chapter [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Future work, under way, is to investigate possible (and likely)
overlaps between various method fragments across the various AO methodologies. This is particularly
evident in the proferred AO work products i.e. diagrams to represent various AO features not found in
traditional OO diagrams such as those provided by the UML [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>
        As well as proposing a community effort to create a merger of methodological ideas, there are
other interesting research issues raised. In particular, how does one measure the quality of the
constructed methodology, both in terms of internal qualities such as consistency, but also external
quality in terms of its suitability for a particular situation? Evaluating how a methodology works in
practice requires liaison with industry, possibly using an Action Research style of investigation [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
Other possible community efforts could also be instigated. For example, intercomparison of
approaches, not only theoretically as, for instance, in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and other similar studies [e.g. 13], but also on
a test example (e.g. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]) and, preferably, in industry situations, might yield significantly improved
understanding of what works and what is less successful. Similarly, such intercomparison could reveal
any significant weak points in agent-oriented methodology research and help researchers target areas
where results are likely to be the most fruitful.
      </p>
      <p>The ultimate result of the substantial efforts of the various AO methodology teams,
complemented by method engineering techniques will be the consolidation of the agent-oriented
methodological community’s contribution to the better development of commercial software systems
and the provision of an agreed and widely supported methodological approach to the development of
agent-oriented applications in the future.</p>
      <p>References</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.G.</given-names>
            <surname>Firesmith</surname>
          </string-name>
          and
          <string-name>
            <given-names>B.</given-names>
            <surname>Henderson-Sellers</surname>
          </string-name>
          .
          <article-title>The OPEN process framework</article-title>
          . Harlow, UK: Addison Wesley,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Q.-N.N.</given-names>
            <surname>Tran</surname>
          </string-name>
          and
          <string-name>
            <given-names>G.C.</given-names>
            <surname>Low</surname>
          </string-name>
          .
          <article-title>Comparison of ten agent-oriented methodologies. Chapter XII In Agent-Oriented Methodologies (edited by B</article-title>
          .
          <string-name>
            <surname>Henderson-Sellers</surname>
            and
            <given-names>P. Giorgini)</given-names>
          </string-name>
          , Idea Group, Hershey, PA, USA,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>B.</given-names>
            <surname>Henderson-Sellers</surname>
          </string-name>
          .
          <article-title>Creating a comprehensive agent-oriented methodology - using method engineering and the open metamodel. Chapter XIII In Agent-Oriented Methodologies (edited by B</article-title>
          .
          <string-name>
            <surname>Henderson-Sellers</surname>
            and
            <given-names>P. Giorgini)</given-names>
          </string-name>
          , Idea Group, Hershey, PA, USA,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>A.H.M. Ter Hofstede</surname>
            and
            <given-names>T.F.</given-names>
          </string-name>
          <string-name>
            <surname>Verhoef</surname>
          </string-name>
          .
          <article-title>On the feasibility of situational method engineering</article-title>
          .
          <source>Information Systems</source>
          ,
          <volume>22</volume>
          :
          <fpage>401</fpage>
          -
          <lpage>422</lpage>
          ,
          <year>1997</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Standards</given-names>
            <surname>Australia</surname>
          </string-name>
          .
          <article-title>Standard metamodel for software development methodologies</article-title>
          ,
          <source>AS4651-2004</source>
          ,
          <volume>23</volume>
          August. Sydney, NSW: Standards Australia International,
          <year>2004</year>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>S.</given-names>
            <surname>Brinkkemper</surname>
          </string-name>
          .
          <article-title>Method engineering: engineering of information systems development methods and tools</article-title>
          .
          <source>Inf. Software Technol.</source>
          ,
          <volume>38</volume>
          (
          <issue>4</issue>
          ):
          <fpage>275</fpage>
          -
          <lpage>280</lpage>
          ,
          <year>1996</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>J.</given-names>
            <surname>Ralyté</surname>
          </string-name>
          and
          <string-name>
            <given-names>C.</given-names>
            <surname>Rolland</surname>
          </string-name>
          .
          <article-title>An assembly process model for method engineering</article-title>
          .
          <source>In Proceedings of the 13th Multi International Conference on Advanced Information Systems Engineering</source>
          , CAISE'01,
          <string-name>
            <surname>Interlaken</surname>
          </string-name>
          , Switzerland. June 6-8. LNCS2068, Berlin: Springer-Verlag,
          <fpage>267</fpage>
          -
          <lpage>283</lpage>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>S.</given-names>
            <surname>Brinkkemper</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Saeki</surname>
          </string-name>
          and
          <string-name>
            <given-names>F.</given-names>
            <surname>Harmsen</surname>
          </string-name>
          .
          <article-title>Assembly techniques for method engineering</article-title>
          .
          <source>In Proceedings of CAISE</source>
          <year>1998</year>
          , Berlin: Springer-Verlag,
          <fpage>381</fpage>
          -
          <lpage>400</lpage>
          ,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>J.</given-names>
            <surname>Ralyté</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Rolland</surname>
          </string-name>
          and
          <string-name>
            <given-names>R.</given-names>
            <surname>Deneckère</surname>
          </string-name>
          .
          <article-title>Towards a meta-tool for change-centric method engineering: A typology of generic operators</article-title>
          .
          <source>In Proceedings of CAiSE2004 (eds. A. Persson and J. Stirna)</source>
          .
          <source>LNCS 3084</source>
          , Berlin: Springer-Verlag,
          <fpage>202</fpage>
          -
          <lpage>218</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>J.</given-names>
            <surname>Ralyte</surname>
          </string-name>
          .
          <article-title>Towards situational methods for information systems development: engineering reusable method chunks</article-title>
          .
          <source>Procs. 13th Int. Conf. on Information Systems Development. Advances in Theory, Practice</source>
          and Education (eds. O.
          <string-name>
            <surname>Vasilecas</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Caplinskas</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          <string-name>
            <surname>Wojtkowski</surname>
            ,
            <given-names>W.G.</given-names>
          </string-name>
          <string-name>
            <surname>Wojtkowski</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Zupancic</surname>
            and
            <given-names>S. Wrycza)</given-names>
          </string-name>
          , Vilnius Gediminas Technical University, Vilnius, Lithuania,
          <fpage>271</fpage>
          -
          <lpage>282</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11] Object Management Group.
          <source>OMG: Unified Modeling Language Superstructure, Version</source>
          <volume>2</volume>
          .0,
          <string-name>
            <surname>August</surname>
            <given-names>2005</given-names>
          </string-name>
          , OMG document formal/05-07-04 [Online]. Available http://www.omg.org/cgi-bin/doc ?formal/05-07-
          <fpage>04</fpage>
          (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>D.E.</given-names>
            <surname>Avison</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Lau</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Myers</surname>
          </string-name>
          and
          <string-name>
            <given-names>P.A.</given-names>
            <surname>Nielsen</surname>
          </string-name>
          . Making academic research more relevant.
          <source>Communications of the ACM</source>
          ,
          <volume>42</volume>
          (
          <issue>1</issue>
          ):
          <fpage>94</fpage>
          -
          <lpage>97</lpage>
          ,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>K.H.</given-names>
            <surname>Dam</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Winikoff</surname>
          </string-name>
          .
          <article-title>Comparing agent-oriented methodologies</article-title>
          . In AgentOriented Systems (eds. P. Giorgini,
          <string-name>
            <given-names>B.</given-names>
            <surname>Henderson-Sellers</surname>
          </string-name>
          and
          <string-name>
            <surname>M. Winikoff)</surname>
          </string-name>
          ,
          <source>LNAI 3030</source>
          , Berlin: Springer-Verlag,
          <fpage>778</fpage>
          -
          <lpage>793</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>E.</given-names>
            <surname>Yu</surname>
          </string-name>
          and
          <string-name>
            <given-names>L.</given-names>
            <surname>Cysneiros</surname>
          </string-name>
          .
          <article-title>Agent-oriented methodologies - Towards a challenge exemplar</article-title>
          .
          <source>In Agent-Oriented Information Systems</source>
          <year>2002</year>
          ,
          <article-title>Procs</article-title>
          .AOIS-2002 (eds. P. Giorgini,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Lespérance</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Wagner</surname>
          </string-name>
          and
          <string-name>
            <surname>E. Yu)</surname>
          </string-name>
          ,
          <fpage>47</fpage>
          -
          <lpage>63</lpage>
          ,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>