<!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>Business Service Modeling for the Service-Oriented Enterprise 1(Extended Abstract)</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jeewanie Jayasinghe Arachchige</string-name>
          <email>J.JayasingheArachchig@uvt.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hans Weigand</string-name>
          <email>H.Weigand@uvt.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Manfred Jeusfeld</string-name>
          <email>Manfred.Jeusfeld@uvt.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Tilburg University</institution>
          ,
          <addr-line>P.O.Box 90153, 5000 LE Tilburg</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <fpage>61</fpage>
      <lpage>62</lpage>
      <abstract>
        <p>Service-oriented architectures are the upcoming business standard for realizing enterprise information systems, thus creating a need for analysis and design methods that are truly service-oriented. Most research on this topic so far takes a strict software engineering perspective. For a proper alignment between the business and the IT, a service perspective at the business level is needed as well. Although few researchers realized the importance of business thinking at service design, notation for service design is still lacking. Using an MDA approach, [1] introduces a new business service and resource modeling language - BSRM based on the Resource-Event-Agent (REA) business ontology. The constructs of the BSRM language and their relationships are grounded in a meta-model which provides comprehensive specification using UML notation. Following the REA, we defined the service as a specialization of economic resource in the meta-model. As the resources are first class citizen of REA, BSRM gives a better insight to the value co-creation which is the main focus of services. Further, we distinguish two service specializations: exchange service and conversion service, corresponding to the two basic REA dualities. Each of them corresponds to a group of decrement and increment economic events in REA. The service classification model developed in [2], categorizes services into several categories. Among these service categories enhancing services and the sub-services which have part of relationship to the core services are special types of services that play a major role in service modeling at business level. These service categories correspond to different roles of the service type in our model. The concept of enhancing services which adds value to the any other service, is introduced as another service category in our model. Considering the situation where core-service realization involves multiple value activities and it makes sense to view these value activities as independent services that are shared by different contexts, we identified the forth category of services as sub-services. Sub- service can be a part-of 1 Jayasinghe Arachchige J., Weigand, H., and Jeusfeld, M.: Business Service Modeling for the Service-Oriented Enterprise. International Journal of Information System Modeling and Design, Vol. 3(1) - 2012, (accepted).</p>
      </abstract>
      <kwd-group>
        <kwd>Business Services</kwd>
        <kwd>REA</kwd>
        <kwd>Service-Oriented Design</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        service of core service which is called core sub-service, or enhancing sub-service
which is called coordination service. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] extended the basic REA stockflow concept
by adding specialization to the stockflow relationship as inflow and outflow. We
adopt this specialization into our model as a relationship between Economic Resource
Type and Service Type.
      </p>
      <p>
        All these concepts which are defined in the meta-model, are denoted with a simple
modeling notation called -BSRM in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. A major difference of BSRM with other
service modeling approaches is the resource perspective of services. We have
included resources not only because they are needed to describe service effects, but
also since resources play a prominent role in new service design [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Secondly, in
contrast to most other approaches that only consider one type of relationship between
services, we identify many service linkages, in order to catch more semantics, keeping
in mind the tenet that meaning is captured in structural relationships. The BSRM
design steps provide a simple direction to a designer to use this modeling language at
CIM level in any real situation.
      </p>
      <p>As it is not feasible to grasp all relevant concerns to a single model, we mapped the
service modeling language with complimentary models, in particular value network
(e3value), data model (ER) and process models (BPMN). By mapping the
metamodel with other model types at CIM and PIM level, we have shown how it can
support truly service-oriented IS development.</p>
      <p>
        BSRM is not only guided by meta-model, it has been formalized using the
metamodeling facilities of Conceptbase[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. This does not only ensure formal validation but
has also provided us immediately with a workable BSRM modeling tool. Further, we
evaluated the viability of BSRM by feature comparison and applying to a real world
case study in the logistic domain.
      </p>
      <p>BSRM is not only a vehicle for communication with business analysts but also a
basis for service-oriented value analysis. All in all, we have described and evaluated
BSRM that we claim to be the first specific service modeling language at CIM level.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. Jayasinghe Arachchige J.,
          <string-name>
            <surname>Weigand</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Jeusfeld</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2012</year>
          )
          <article-title>: Business Service Modeling for the Service-Oriented Enterprise</article-title>
          .
          <source>International Journal of Information System Modeling and Design</source>
          , Vol.
          <volume>3</volume>
          (
          <issue>1</issue>
          ), (accepted).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Weigand</surname>
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johannesson</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Andersson</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Bergholtz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2009</year>
          ).
          <article-title>Valuebased Service Modeling and Design: Toward a Unified View of Services</article-title>
          .
          <source>In Proc. of CAiSE '09</source>
          , Springer,
          <fpage>410</fpage>
          -
          <lpage>424</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Gailly</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Laurier</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Poels</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          (
          <year>2008</year>
          ).
          <article-title>Positioning and Formalizing the REA enterprise ontology</article-title>
          ,
          <source>International Journal of Information Systems</source>
          <volume>22</volume>
          ,
          <fpage>219</fpage>
          -
          <lpage>248</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Froehle</surname>
            ,
            <given-names>C.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Roth</surname>
            ,
            <given-names>A.V.</given-names>
          </string-name>
          (
          <year>2007</year>
          ).
          <article-title>A Resource-Process Framework of New Service Development, Production</article-title>
          and
          <string-name>
            <given-names>Operations</given-names>
            <surname>Management</surname>
          </string-name>
          ,
          <volume>16</volume>
          (
          <issue>2</issue>
          ),
          <fpage>169</fpage>
          -
          <lpage>181</lpage>
          ,
          <fpage>183</fpage>
          -
          <lpage>188</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Jeusfeld</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jarke</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Mylopoulos</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          (
          <year>2009</year>
          ).
          <article-title>Metamodeling for Method Engineering</article-title>
          . MIT Press.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>