<!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 Process Compliance with the User Requirements Notation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Daniel Amyot</string-name>
          <email>damyot@site.uottawa.ca</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>SITE, University of Ottawa</institution>
          ,
          <addr-line>800 King Edward, Ottawa, ON, K1N 6N5</addr-line>
          ,
          <country country="CA">Canada</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The User Requirements Notation (URN) [3,8], standardized by ITU-T in November 2008, aims to support the elicitation, modeling, analysis, specification, and validation of requirements, particularly for reactive and telecommunications systems. URN combines a goal view, expressed with the Goal-oriented Requirement Language, with a scenario view, expressed with the Use Case Maps notation. This unique combination proved to be useful in the description of business processes as well as of legislation and organization policies [5]. In this presentation, we will explore the modelling and evolution of business processes and policies and how several compliance issues can be addressed [1,2]. We will also discuss how recent extensions for key performance indicators [5,7] and aspect-oriented modeling [6], together with tool support [4], can be exploited in a compliance context. Examples from the healthcare domain will be used for illustrative purposes.</p>
      </abstract>
    </article-meta>
  </front>
  <body />
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Ghanavati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            <given-names>D.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Peyton</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Towards a Framework for Tracking Legal Compliance in Healthcare</article-title>
          .
          <source>19th Int. Conf. on Advanced Information Systems Engineering (CAiSE'07)</source>
          , Trondheim, Norway, June. LNCS 4495, Springer, pp.
          <fpage>218</fpage>
          -
          <lpage>232</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Ghanavati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Peyton</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Compliance Analysis Based on a Goal-oriented Requirement Language Evaluation Methodology</article-title>
          .
          <source>17th IEEE Int. Requirements Engineering Conference (RE'09)</source>
          , Atlanta, USA, September.
          <source>IEEE CS</source>
          , pp.
          <fpage>133</fpage>
          -
          <lpage>142</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. International Telecommunication Union: Recommendation Z.
          <volume>151</volume>
          (
          <issue>11</issue>
          /08),
          <article-title>User Requirements Notation (URN) - Language definition (</article-title>
          <year>2008</year>
          ) http://www.itu.int/rec/T-REC-Z.
          <volume>151</volume>
          /en
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. jUCMNav, v.
          <volume>4</volume>
          .3, http://jucmnav.softwareengineering.ca/jucmnav/, September (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Pourshahid</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Forster</surname>
            ,
            <given-names>A.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghanavati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peyton</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Weiss</surname>
          </string-name>
          , M.:
          <article-title>Business Process Management with the User Requirements Notation</article-title>
          .
          <source>Electronic Commerce Research</source>
          ,
          <volume>9</volume>
          (
          <issue>4</issue>
          ). Springer, pp.
          <fpage>269</fpage>
          -
          <lpage>316</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Pourshahid</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mussbacher</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Weiss</surname>
          </string-name>
          , M.:
          <article-title>Toward an Aspect-Oriented Framework for Business Process Improvement</article-title>
          .
          <source>International Journal of Electronic Business (IJEB)</source>
          , Inderscience Publishers, Vol.
          <volume>8</volume>
          :
          <issue>3</issue>
          , pp.
          <fpage>233</fpage>
          -
          <lpage>259</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Shamsaei</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pourshahid</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Business Process Compliance Tracking Using Key Performance Indicators</article-title>
          . To appear
          <source>in: 6th Int. Workshop on Business Process Design (BPD</source>
          <year>2010</year>
          ), Hoboken, USA, September. LNBIP, Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>URN</given-names>
            <surname>Virtual</surname>
          </string-name>
          <article-title>Library</article-title>
          . http://www.usecasemaps.org/pub
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>