<!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>Indicator-based Policy Compliance of Business Processes</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Introduction to Research Questions</institution>
        </aff>
        <aff id="aff1">
          <label>1</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>Business process compliance management has recently grabbed a lot of attention in both business and academia as it helps organizations not only to control and monitor their business processes from a legal point of view but also to avoid financial penalties and undesirable consequences to their reputation. Balancing compliance obligations with business objectives remains however a difficult challenge. We believe goal-oriented compliance management using Key Performance Indicators (KPIs) to measure the compliance level of organizations is an area that can be further developed to tackle this challenge. Goaloriented compliance management concepts have been explored before. However, there is little research on how to measure and improve the compliance level of organizations using KPIs while considering the impact of candidate adjustments on business goals. We discuss a proposal toward a framework to address the aforementioned problems.</p>
      </abstract>
      <kwd-group>
        <kwd>Business Process</kwd>
        <kwd>Goal Modeling</kwd>
        <kwd>Legal Compliance</kwd>
        <kwd>Key Performance Indicator</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>In this context, it is necessary to develop a framework that would allow
organizations to address the above issues. Such a framework should help organizations answer
the following questions: How can we establish simple traceability between policies,
laws, regulations in general, business processes, and organization goals? How can
organizations constantly monitor the level of compliance of business processes to
avoid audit failures? How does making a process compliant with a particular
regulation impact organizations goals including goals of different stakeholders? What is the
overall compliance level of the organization with respect to one or multiple
regulations? What if modifications to a process improve compliance with a regulation while
degrading compliance with other regulations? How can organizations select the most
important compliance issues to address given their limited resources?
2</p>
    </sec>
    <sec id="sec-2">
      <title>Analysis of Related Work</title>
      <p>In recent years, much work has been done to improve business process compliance
management and measure business process compliance levels. We only describe the
most significant research in this section. However, we have conducted a systematic
literature review in this area [‎10].</p>
      <p>Lu et al. [‎4] propose a method for measuring business process compliance against
control rules defined using control objectives from different sources (e.g., regulations
or partner contracts) and modeled using FCL (Formal Contract Language). They
define concepts of ideal semantics for control rules in order to categorize various
degrees of compliance between processes and rules. They categorize them into four
groups including ideal, sub-ideal, irrelevant, and non-compliant situations. They
calculate both ideal and sub-ideal compliance degrees of businesses processes against
control rules to evaluate how well the process model supports control rules. The end
result of this method can be utilized by process designers to improve the compliance
degree, but the complexity of the method may be an impediment for regular business
users.</p>
      <p>Silveira et al. [‎8] suggest a compliance governance dashboard (CGD), with key
compliance indicators (KCI) used to measure the compliance level of processes. Their
CGD consists of different levels of abstraction. The top-level view shows the most
critical regulatory and policy indicators, the compliance level of the main processes,
as well as an overall compliance level for the organization. One can drill down to see
more details and analyze the compliance of individual process atomic units in various
business units. Furthermore, one can view compliance violation reports consisting of
all the information reported to internal and external auditors. However, their
framework does not identify the impact of regulations on organizations goals.</p>
      <p>Rifaut and Dubois [‎7] propose a method to combine and model the regulations and
business requirements for processes. They combine tabular requirements with i* goal
models, where they model purposes, and decompose them all the way down to
indicators used to assess and measure the success of processes. This framework can be used
prior to the design and implementation of a process, as well as later on for monitoring
and controlling the compliance of processes. However, the proposed framework does
not identify how KPI values are measured and does not suggest a method for
measuring the overall compliance level of the organization</p>
      <p>Morrison et al. [‎5] define a method for measuring the degree of compliance of
processes with respect to both crisp and imprecise compliance requirements. Their
method relies on creating a compliance scale model that allows measurement of both
qualitative and quantitative values for a particular process instance. Although this
method can assess the level of compliance of a process, it requires a lot of preparatory
work to determine the compliance scales.</p>
      <p>Much work related to compliance audits of business process instances has been
done. However, modeling the intents and objectives of regulations, organization
goals, and key performance indicators for measuring compliance level of regulations
as an integrated framework has not been explored yet. A goal view with associated
compliance KPIs integrated with a process view allow for reasoning about what to do
next as well as about the impact of candidate improvements on organization goals,
hence providing a holistic view.</p>
      <p>Our proposed framework is based on the User Requirements Notation (URN), the
first international standard to combine goal modeling (Goal-oriented Requirement
Language — GRL) with scenario modeling (Use Case Map notation — UCM) [‎2].
URN was created for modeling telecommunication services and reactive systems, but
it was shown to be a competitive language for business process modeling [‎11].
jUCMNav [‎3], a free Eclipse-based tool, is used to analyze and manage URN models.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Sketch of Proposed Solution</title>
      <p>To address the problems mentioned in Section ‎1, we propose a goal-oriented
modelbased framework for measuring the level of business process compliance with respect
to regulations, laws, standards, and policies. This framework consists of the elements
illustrated in Fig. 1. We model regulations, starting at high-level (i.e., policy). Then,
we decompose the policies down to operational/control rules level. These rules
control the processes meant to be compliant with the policies and regulations. We define
a set of KPIs for each rule that measure the level of compliance for the rules by
comparing the desired target value with the current value of each KPI. Furthermore, we
also model organization goals and business processes, hence providing a more holistic
view. Rules are associated with related organization business processes through URN
traceability links. A set of KPIs is defined to help analyze the impact on the
organization goals of changes made to business processes for improving the compliance level.</p>
      <p>The first step of the framework is modeling all the aforementioned elements
required by the framework. This step helps us to simplify traceability between policies,
regulations, business processes, and organization goals.</p>
      <p>Legal Model
Contribution Link</p>
      <sec id="sec-3-1">
        <title>Goals KPI</title>
        <p>URN Link</p>
      </sec>
      <sec id="sec-3-2">
        <title>Business</title>
      </sec>
      <sec id="sec-3-3">
        <title>Process</title>
        <p>Contribution Link
Contribution Link</p>
      </sec>
      <sec id="sec-3-4">
        <title>Policy</title>
      </sec>
      <sec id="sec-3-5">
        <title>Rule KPI</title>
        <p>Organization goals, policies, and rules are modeled using the GRL notation while
business processes are modeled using the UCM notation. The KPIs are, however,
modeled using an extension of URN introduced in [‎6]. Finally, we associate the
business processes in the organization model to related business goals and KPIs using
URN links. We use the same method to associate the control rules in the regulation
model with corresponding business processes in the organization model.</p>
        <p>
          In the next step we evaluate the model to find the overall compliance level of the
organization with respect to one or multiple regulations. We perform this assessment
using the designed model and GRL strategies, usually used to initialize the leaf
elements of GRL models in order to compute the satisfaction level of the higher level
nodes using a bottom-up propagation algorithm [‎1]. In our application, GRL
strategies initialize the KPI value sets (i.e., target value, threshold value, worst value,
evaluation value). An evaluation value is the actual value of a KPI at the time of the
evaluation. The evaluation values can be entered manually like other value sets (which is
useful for the analysis of what-if situations) or automatically obtained from various
data sources such as a Business Intelligence (BI) systems. A GRL KPI maps the
evaluation value to a satisfaction level (on a scale from -100 to 100, by linear
interpolation considering the target, threshold, and worst values)‎that can then be propagated to
other elements (rules, policies) in the goal model according to the goal evaluation
algorithms presented in [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ].
        </p>
        <p>In order to find out how organizations can select the most important compliance
issues to address given their limited resources, we define the importance values of the
high-level business goals that will be propagated using a top-down importance
algorithm to business processes and associated policies/rules through the URN links.</p>
        <p>In the improvement step, we illustrate the rules on a quadrant diagram based on
their compliance level (satisfaction level) and importance value. We then highlight
the critical rules with low satisfaction levels and high importance value and track
down the associated processes for improvement.</p>
        <p>Finally, in the last step, we monitor the business processes to observe not only the
expected changes on the modified process but also to detect potential side effects on
organization goals and compliance levels of other control rules in the organization.</p>
        <p>This framework already addresses some of the problems mentioned in
section 1 [‎9]. In the next phase of our research, we plan to extend the framework in order
to find solutions for the following problems as well.</p>
        <p>In the suggested approach, it could be challenging to determine appropriate targets
required for KPI values to make the high-level business goals and compliance
objectives reach a desired satisfaction level. The current GRL evaluation algorithms are all
bottom-up, and hence can only be used to assess an explicit strategy. In order to be
able to solve the mentioned problem, a top-down algorithm (i.e., a search algorithm)
should be designed to suggest appropriate KPI target values given the satisfaction
values required for the high-level goal in the model. Coming up with an algorithm to
find the answers for the small model can be done using approaches like game theory
or constraint solving. However, coming up with a scalable algorithm that can be used
in complex situations (e.g., large organizations with hundreds of processes and many
policies and regulations) could quickly become very challenging.</p>
        <p>Moreover, we will improve the precision of models by defining appropriate
stereotypes (e.g., policies and rules) and by adding constraints to the metamodel elements of
the framework. These constraints can help the modelers deal with common
complexities‎in‎large‎models.‎The‎constraints‎will‎be‎formalized‎with‎UML’s‎Object‎Constraint
Language (OCL) and checked against the model. For instance, these rules will check
that ―policies‎ cannot‎ have‎ KPIs‖‎ or‎ that ―rules‎ can‎ only‎ influence‎ policies‖.
Userdefined OCL rules can already be verified on URN models with jUCMNav.</p>
        <p>Moreover, we also plan to further analyze the impact of making a process
compliant with regulations on organization goals, including goals of different
stakeholders. We believe the current framework already supports this to some extent using the
KPIs in the organization model. However, we have not validated the use of these
KPIs in a case study and we think there is more work to be done on that front.</p>
        <p>In addition, we plan to further develop our approach for selecting the most
important compliance issues. The current proposed algorithm needs improvement in order
to support importance values for business goals and policies/regulations. Furthermore,
implementing the proposed quadrant-based visualization and bringing it to the
business users can help with the validation of this approach.</p>
        <p>Finally, the constant monitoring of the changes in compliance levels and observing
the positive and negative impacts of the changes made to the processes on the
business context are other areas of interest.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Contributions</title>
      <p>While doing research on the proposed framework, several papers have been
published [‎9, ‎10] and the following contributions have been done:
 Modeled legal requirement and policies/rules using URN.
 Measured the level of business process compliance for one or multiple
regulations or policies (in a Human Resource example).






</p>
      <p>Calculated the importance level of processes and rules considering high-level
business goals.</p>
      <p>Discovered the business processes that violate the rules derived from
regulations and policies.</p>
      <p>Systematically reviewed compliance measurement approaches based on
goals and indicators (with 32 publications selected from four search engines
and the study of specialized conferences).</p>
      <p>We plan to work toward the following contributions:
 Determining the impact of compliance-related process modifications on
business goals, including conflicting goals between stakeholders, and on
conflicting rules.</p>
      <p>Determining the target value of selected KPIs given the desired satisfaction
value of high-level organization and compliance goals.</p>
      <p>Using the importance level of processes and compliance level to come up
with a prioritized list of improvements required for business processes.
Using Business Intelligence tools as the infrastructure for extracting the KPI
values.</p>
      <p>Validating the framework with case studies related to human resources and
airport security policies and business processes.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Progress and Evaluation</title>
      <p>The groundwork for this framework has been already established. We have published
a paper on business process compliance tracking using KPIs [‎9] as well as a
systematic literature review on compliance measurement based on goals and indicators [‎10].
In [‎9], we used a case study related to human resource policies to explore the benefits
and shortcomings of the framework. In the future, we are going to further expand and
analyze the human resource policies to have a better enterprise-level scenario for
validation purposes. The expanded model will allow us to broaden the validation of
the framework by examining some of the future work suggested in section 4. We will
then address the inadequacies of the suggested framework according to the initial
results and feedback on the human resource scenario. Finally, we will use a second
case study on airport security policies and business processes in collaboration with
Transport Canada (the national regulator) to complete the validation of the improved
framework by using it in a realistic and different context.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghanavati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horkoff</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mussbacher</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peyton</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>Evaluating Goal Models within the Goal-oriented Requirement Language</article-title>
          .
          <source>International Journal of Intelligent Systems</source>
          , Vol.
          <volume>25</volume>
          , Issue 8, pp.
          <fpage>841</fpage>
          -
          <lpage>877</lpage>
          . Wiley (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. International Telecommunication Union: Recommendation Z.
          <volume>151</volume>
          (
          <issue>11</issue>
          /08),
          <article-title>User Requirements Notation (URN) - Language definition</article-title>
          , http://www.itu.int/rec/T-REC-Z.
          <volume>151</volume>
          /en.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. jUCMNav,
          <source>Version 4.2</source>
          .1, University of Ottawa (
          <year>2010</year>
          ) http://softwareengineering.ca/jucmnav
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Lu</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sadiq</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Governatori</surname>
          </string-name>
          , G.:
          <article-title>Measurement of Compliance Distance in Business Processes</article-title>
          .
          <source>In: Info. Sys. Management</source>
          , vol.
          <volume>25</volume>
          , pp.
          <fpage>344</fpage>
          -
          <lpage>355</lpage>
          . Taylor &amp; Francis, USA (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Morrison</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghose</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Koliadis</surname>
          </string-name>
          , G.:
          <article-title>Dealing With Imprecise Compliance Requirements</article-title>
          . In: EDOCW, pp.
          <fpage>6</fpage>
          -
          <lpage>14</lpage>
          . IEEE CS,
          <article-title>New Zealand (</article-title>
          <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>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>
          ,
          <string-name>
            <surname>Weiss</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Business Process Management with the User Requirements Notation</article-title>
          .
          <source>Electronic Commerce Research</source>
          ,
          <volume>9</volume>
          (
          <issue>4</issue>
          ), pp.
          <fpage>269</fpage>
          -
          <lpage>316</lpage>
          . Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Rifaut</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Dubois</surname>
          </string-name>
          , E.:
          <article-title>Using Goal-Oriented Requirements Engineering for Improving the Quality of ISO/IEC 15504 based Compliance Assessment Frameworks</article-title>
          . In: RE'08, IEEE, pp.
          <fpage>33</fpage>
          -
          <lpage>42</lpage>
          . Barcelona, Catalunya, Spain (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. Silveira.‎ P.,‎ Rodriguez,‎ C.,‎ Casati,‎ F.,‎ Daniel,‎ F.,
          <string-name>
            <surname>‎ D'Andrea.</surname>
          </string-name>
          ‎ V.,
          <string-name>
            <surname>Worledge</surname>
            , C and Taheri,
            <given-names>Z.</given-names>
          </string-name>
          :
          <article-title>On the Design of Compliance Governance Dashboards for Effective Compliance and Audit Management</article-title>
          . In: ICSOC-ServiceWave
          <year>2009</year>
          , Stockholm, Sweden. LNCS, vol.
          <volume>5900</volume>
          , pp.
          <fpage>208</fpage>
          -
          <lpage>217</lpage>
          . Springer (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <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>
          .
          <source>BPD</source>
          <year>2010</year>
          ,
          <article-title>Hoboken</article-title>
          , USA.
          <source>BPM 2010 Workshops. LNBIP</source>
          , vol.
          <volume>66</volume>
          , pp.
          <fpage>73</fpage>
          -
          <lpage>84</lpage>
          . Springer (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Shamsaei</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Pourshahid</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A Systematic Review of Compliance Measurement Based on Goals and Indicators</article-title>
          .
          <source>In: GRCIS</source>
          <year>2011</year>
          , London, UK.
          <source>CAiSE 2011 Workshops, LNBIP</source>
          , vol.
          <volume>83</volume>
          , pp.
          <fpage>228</fpage>
          -
          <lpage>237</lpage>
          . Springer (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Weiss</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Business process modeling with URN</article-title>
          .
          <source>International Journal of EBusiness Research</source>
          <volume>1</volume>
          (
          <issue>3</issue>
          ), pp.
          <fpage>63</fpage>
          -
          <lpage>90</lpage>
          . IGI Global,
          <string-name>
            <surname>Hershey</surname>
          </string-name>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>