<!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 and Regulations Compliance Management Technology</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ilze Buksa</string-name>
          <email>ilze.buksa@rtu.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Riga Technical University, Institute of Applied Computer Systems</institution>
          ,
          <addr-line>Meza street 1/4, LV-1048, Riga</addr-line>
          ,
          <country country="LV">Latvia</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Organisations are more and more under pressure to comply with an increasing number of external and internal regulations for business governance and must ensure that their processes are running accordingly to requirements of regulations. Therefore business process and regulations compliance analysis, audit and management tasks take very important role in daily operational activities of each organisation. Due to high complexity and weak support of IT tools this task can become challenging. During my Phd studies I want to develop business process and regulations compliance management technology. To reach this goal current activity in progress is to develop software prototype to link business processes to regulations.</p>
      </abstract>
      <kwd-group>
        <kwd>business process</kwd>
        <kwd>compliance</kwd>
        <kwd>regulations</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Research question</title>
      <p>Usually business processes in organisation are affected by requirements of
regulations. Many organisations use business process management to model,
simulate, execute, change, monitor and optimize business processes. Business process
management can also serve as a proof that organisation is running accordingly to
regulations. To ensure such proof organisation must form and manage linkage
between regulations and business processes.</p>
      <p>In many cases organisations have their business processes specified
independently or not specifically linked with regulations, even if business processes
are directly impacted by regulations. Reasons for such situation can be lack of widely
known and applicable methodologies and weak business process management suite
support to link business processes to regulations. Currently no business process
management suite supports business process linkage specifically to regulations and
relevant change management of regulations and impacted business processes.</p>
      <p>Goal of doctoral work is to develop business process and regulations compliance
management technology. As a result developed technology should address and have
solutions for the following main topics:
(1) management of regulations (approach and solution for retrieval, storing,
updating, and versioning of regulations),
(2) extraction of requirements from regulations (approach and solution for
capturing requirements from regulations which are affecting business
processes),
(3) linkage of business processes and regulations (prototype of technical
solution to ensure linkage),
(4) business process and regulations mutual change management and
ontime compliance monitoring (methodology and prototype of technical
solution).</p>
      <p>To reach these goals current activity in progress is to develop solution prototype
to link business process activities to the structural parts of regulation. Solution will
use in most of the business process management suits existing business process and
document linkage functionality.</p>
      <p>Users of business process and regulation linkage and management solution
would be:
(1) leadership and compliance auditors will gain real time transparency and
proof that business processes are running accordingly to regulations,
(2) process executors will gain visible processes thus facilitating process
execution, re-engineering and optimisation,
(3) lawyers will gain illustration of regulations as a running business
processes which will allow to identify gaps in regulations and optimize
requirements made in regulations as well as any changes in regulations
will allow to see impacted business processes,
(4) software engineers will gain documented processes with specified
regulatory requirements according to which processes are executed, thus
facilitating and speeding-up development of new systems or
maintenance of existing systems to make sure that systems are fulfilling
requirements of regulations.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Significant problems in the field of research</title>
      <p>
        From organisations’ point of view challenge is traditional approach of treating
regulations separately from business processes. Usually organisations ensure business
processes compliance with regulations through audits. Due to the need to provide
regular updates on compliance, a more strategic approach to compliance management
is needed. This implies a shift from regular reviews to continual assurance and
introduces a need for advanced compliance management systems that reflect and
ensure real time compliance management [
        <xref ref-type="bibr" rid="ref10 ref2">2, 10</xref>
        ].
      </p>
      <p>Currently there are not many specific researches available with focus on
business process and regulations compliance management in order to provide
solutions for existing challenges: lack of methodologies and IT tool support.
However in publications of the latest years, topics on business processes and
regulations provide insight in wider researches in these domains. Lack of specific
researches leads to lack of tested and applicable guidelines and specific IT tool
solutions to support linkage of business processes to regulations.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Current knowledge of the</title>
      <p>existing solutions
problem
domain
and state of</p>
      <p>
        There are number of researches available which propose approaches for
analysing regulations [
        <xref ref-type="bibr" rid="ref1 ref10 ref15 ref6 ref9">1, 6, 9, 10, 15</xref>
        ], capturing requirements from regulation [
        <xref ref-type="bibr" rid="ref13 ref14 ref19 ref20 ref21">13, 14,
19, 20, 21</xref>
        ], facilitating understanding of regulations by graphical representation [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]
and managing compliance with requirements and business processes [
        <xref ref-type="bibr" rid="ref16 ref17 ref2 ref3 ref4 ref5 ref7">2, 3, 4, 5, 7, 16,
17</xref>
        ]. Also researches made in document engineering domain [
        <xref ref-type="bibr" rid="ref1 ref11 ref18 ref8">1, 8, 11, 18</xref>
        ] are
applicable since regulations basically are documents with specific content –
regulatory requirements.
      </p>
      <p>
        Regarding requirement engineering authors [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] present their survey of
researches in handling regulations for information system development. Summarised
approaches [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] can be used in practical case studies to identify which methods can
be expanded and be applicable to extract requirements from regulations for business
process management.
      </p>
      <p>
        Authors [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] have proposed method for extracting rights and obligations from
regulations and further [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] have examined tool support for this by applying Cerno
framework for textual semantic annotation and proposed tool for semi-automatic
semantic annotation of concepts. In theses researches authors have focused on limited
scope on alignment of information system requirements with regulations. Output of
these researches can be analysed and expanded with focus to align requirements with
business processes since approach has already proved itself in a practice and is
supported by the tool.
      </p>
      <p>
        Authors [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] have pointed out ontological differences between legal concepts
and requirements, and have set decision making process about requirements from
regulations for law compliant information systems. Like previous research also here
authors are focusing on requirements for information system, thus showing that some
statements are limited and not applicable in case where requirement engineering is
used to model business processes. Newertheless this approach can be used as a basis
to distinguish between legal concepts and requirements.
      </p>
      <p>
        Authors [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] introduce a method to prioritize legal requirements to determinate
order in which requirements should be implemented in information systems. Research
is not applicable in a direct way as in business processes all requirements from
regulations should be implemented and presented at the moment when regulations
come in force, however research is applicable and gives base to prioritize
requirements to denote requirements which have the highest impact level; and such
prioritization can be used for handling contradictory requirements.
      </p>
      <p>
        Authors [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] specifically present a method for validating business processes with
respect to business rules which are captured from regulations. Method does not
address challenges of extracting requirements from regulations, however it is practical
and applicable approach to trace and visualize basic compliance.
      </p>
      <p>
        Authors [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] introduce approach to help achieve business process flexibility with
business rules and workflow patterns. Research do not cover compliance issues
directly, however it is applicable as it provides approach based on assumption that
changes in a business process can be confined to the variable isolated parts of the
processes. This assumption is important since ordinary or regular changes of some
regulations most likely will impact some parts of the process not a whole process
itself.
      </p>
      <p>
        Author [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] validates business processes with business contracts by providing
logic based formalism for describing both the semantics of contract and the semantics
of compliance checking procedures. Results described in the paper are promising,
therefore this approach is valid in scope of author’s research and will be applied in
further case studies by testing it to regulations as both, regulations and contracts,
contain requirements for business processes.
4
      </p>
    </sec>
    <sec id="sec-4">
      <title>Preliminary ideas</title>
      <p>Following domains are selected for further investigations in order to address
business process and regulations compliance management:
(1) management of regulations (main topics: extraction of regulatory
requirements; development of regulatory document generation and
update algorithm, solutions for versioning of regulations (and
requirements of regulations)),
(2) management of business processes (main topics: solutions to link
business processes with regulations and representation capabilities),
(3) management of compliance (main topics: existing solutions for
compliance governance in business process management suites).</p>
      <p>Research is not limited to listed research domains and can be expanded to other
domains.</p>
    </sec>
    <sec id="sec-5">
      <title>Proposed approach</title>
      <p>
        Since requirements under which organisation must operate are expressed in
regulations and business processes represent procedure how these requirements
should be executed [
        <xref ref-type="bibr" rid="ref5 ref7">5, 7</xref>
        ], it is rational need to find a way to link these two concepts.
Characteristics of regulations make them challenging to use and directly apply in
business processes, therefore captured requirements (perhaps, in a form of business
rules) can be a link to link regulatory document with business process model [
        <xref ref-type="bibr" rid="ref5 ref7">5, 7</xref>
        ].
      </p>
      <p>To run approach to represent requirements of regulations in the business process
model the following scenario (general steps) should be performed:
(1) determinate applicable regulations,
(2) classify and structure regulation,
(3) ensure traceability
regulations,</p>
      <p>within regulation itself and other applicable
(4) extract (capture) requirements from applicable regulations,
(5) ensure traceability between requirement and regulation and its sections,
(6) handle inconsistencies between requirement,
(7) model business process incorporating requirements,
(8) ensure traceability between business process and its steps with
requirements, to ensure that all applicable requirements are present,
(9) link business process model and steps with regulatory document,
(10) provide real time compliance monitoring.</p>
      <p>IT tool support is highly needed to execute above mentioned scenario.</p>
    </sec>
    <sec id="sec-6">
      <title>Sketch of the research methodology 6 7</title>
      <p>Primary research methodologies are collation, summary and synthesis of
existing researches and information, and constructive research to develop solutions
for identified problems through creating and validating new approaches and
prototyping of technology.</p>
    </sec>
    <sec id="sec-7">
      <title>Contributions of the author to the solution of the problem</title>
      <p>Currently ongoing work is to develop approach and technology prototype to link
business processes and regulatory documents using existing capabilities of business
process management suits. Developed approach will be tested also in SAP
Composition Environment. This work has been supported by Accenture Latvia and
Riga Technical University in the context of research project No ZP-2010/7
“Development of linkage technology prototype for business process and normative
documents bond”.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Amato</surname>
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mazzeo</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Penta</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Picariello</surname>
            <given-names>A</given-names>
          </string-name>
          .
          <article-title>Building RDF Ontologies from semistructured legal documents</article-title>
          .
          <source>International Conference on Complex, Intelligent and Software Intensive System</source>
          . p.
          <fpage>997</fpage>
          -
          <lpage>1002</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Araujo</surname>
            <given-names>B.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schmitz</surname>
            <given-names>E.A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Correa</surname>
            <given-names>A.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alencar</surname>
            <given-names>A.J.</given-names>
          </string-name>
          <article-title>A method for Validating the Compliance of Business Processes to Business Rules</article-title>
          .
          <source>Proceedings of the ACM Symposium on Applied Computing SAC'10</source>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Breaux</surname>
            <given-names>T.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Powers</surname>
            <given-names>C</given-names>
          </string-name>
          .
          <article-title>Early Studies in Acquiring Evidentiary, Reusable Business Process Models for Legal Compliance</article-title>
          .
          <source>6th International Conference on Information Technology: New Generations</source>
          . p.
          <fpage>272</fpage>
          -
          <lpage>277</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Eijndhoven</surname>
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Iacob</surname>
            <given-names>M.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ponisio</surname>
            <given-names>M.L.</given-names>
          </string-name>
          <article-title>Achieving business process flexibility with business rules</article-title>
          .
          <source>Proceedings of the 12th International IEEE Enterprise Distributed Object Computing Conference EDOC'08</source>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Fiorini</surname>
            <given-names>S.T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sampaio J.C.</surname>
          </string-name>
          <article-title>Integrating Business Processes with Requirements Elicitation</article-title>
          .
          <source>Proceedings of the 5th International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises WET ICE'96</source>
          . p.
          <volume>226</volume>
          (
          <year>1996</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Ghanavati</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            <given-names>D.</given-names>
          </string-name>
          , Peyton L.
          <article-title>Compliance Analysis Based on a Goal-oriented Requirement Language Evaluation Methodology</article-title>
          .
          <source>Proceedings of the 17th International IEEE Requirements Engineering Conference RE'09</source>
          . p.
          <fpage>133</fpage>
          -
          <lpage>142</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Governatori</surname>
            <given-names>G.</given-names>
          </string-name>
          , Milosevic
          <string-name>
            <given-names>Z.</given-names>
            ,
            <surname>Sadiq</surname>
          </string-name>
          <string-name>
            <surname>S.</surname>
          </string-name>
          <article-title>Compliance checking between business processes and business contracts</article-title>
          .
          <source>Proceedings of the 10th International IEEE Enterprise Distributed Object Computing Conference EDOC'06</source>
          . p.
          <fpage>221</fpage>
          -
          <lpage>232</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Guo</surname>
            <given-names>J</given-names>
          </string-name>
          .
          <source>Achieving Transparent Integration of Information, Documents and Processes. Proceedings of the International IEEE Conference on e-Business Engineering ICEBE'06</source>
          . p.
          <fpage>558</fpage>
          -
          <lpage>562</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Hamdaqa</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hamou-Lhadj</surname>
            <given-names>A</given-names>
          </string-name>
          .
          <article-title>Citation Analysis: An Approach for Facilitating the Understanding and the Analysis of Regulatory Compliance Documents</article-title>
          .
          <source>Proceedings of the 6th International Conference on Information Technology: New Generations</source>
          . p.
          <fpage>278</fpage>
          -
          <lpage>283</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Hassan</surname>
            <given-names>W.</given-names>
          </string-name>
          , Logrippo L.
          <article-title>Requirements and compliance in legal systems: a logic approach</article-title>
          .
          <source>Proceedings of the International IEEE Requirements Engineering and Law Conference RELAW'08</source>
          . p
          <fpage>40</fpage>
          -
          <lpage>44</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Janiesch</surname>
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dreiling</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Greiner</surname>
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lippe</surname>
            <given-names>S. Integrated</given-names>
          </string-name>
          <article-title>Configuration of Enterprise Systems for Interoperability - Towards Process Model and Business Document Specification Alignment</article-title>
          .
          <source>Proceedings of the International 10th IEEE Enterprise Distributed Object Computing Conference EDOC'06</source>
          . p.
          <fpage>445</fpage>
          -
          <lpage>448</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Kirikova M. Facilitating</surname>
          </string-name>
          <article-title>Comprehension of Normative Documents by Graphical Representations</article-title>
          .
          <source>Practical Aspects of Knowledge Management</source>
          , Springer Verlag, Berlin Heidelberg. p.
          <fpage>369</fpage>
          -
          <lpage>376</lpage>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Kiyavitskaya</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zeni</surname>
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Breaux</surname>
            <given-names>T.D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Anton</surname>
            <given-names>A.I.</given-names>
          </string-name>
          <article-title>Extracting Rights and Obligations from Regulations: Toward a Tool-Supported Process</article-title>
          .
          <source>Proceedings of the 22nd International IEEE/ACM conference on Automated software engineering ASE'07</source>
          . p.
          <fpage>429</fpage>
          -
          <lpage>432</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Kiyavitskaya</surname>
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zeni</surname>
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Breaux</surname>
            <given-names>T.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Anton</surname>
            <given-names>A.I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cordy</surname>
            <given-names>J.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mich</surname>
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mylopouslos</surname>
            <given-names>J</given-names>
          </string-name>
          .
          <article-title>Towards regulatory compliance: Extracting rights and obligations to align requirements with regulations</article-title>
          .
          <source>Proceedings of the 14t h International IEEE Requirements Engineering Conference RE'06</source>
          . p.
          <fpage>49</fpage>
          -
          <lpage>58</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Massey</surname>
            <given-names>A.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Otto</surname>
            <given-names>P.N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Anton</surname>
            <given-names>A.I.</given-names>
          </string-name>
          <article-title>Prioritizing Legal Requirements</article-title>
          .
          <source>Proceedings of the 2nd International Workshop on Requirements Engineering and Law</source>
          . p.
          <fpage>27</fpage>
          -
          <lpage>32</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. Milosevic
          <string-name>
            <given-names>Z.</given-names>
            ,
            <surname>Orlowska</surname>
          </string-name>
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Sadiq</surname>
          </string-name>
          <string-name>
            <surname>S.</surname>
          </string-name>
          <article-title>Linking contracts, processes and services: an eventdriven approach</article-title>
          .
          <source>Proceedings of the IEEE International Conference on Services Computing SCC'06</source>
          . p.
          <fpage>390</fpage>
          -
          <lpage>397</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Muehlen</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Indulska</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kamp</surname>
            <given-names>G</given-names>
          </string-name>
          .
          <article-title>Business Process and Business Rule Modeling Languages for Compliance Management: A Representational Analysis</article-title>
          .
          <article-title>Tutorials, posters, panels and industrial contributions at the 26th international conference on Conceptual modeling ER'07 (</article-title>
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Noronha</surname>
            <given-names>M.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goldstein</surname>
          </string-name>
          Golendziner L.,
          <string-name>
            <surname>Santos</surname>
            <given-names>C.S.</given-names>
          </string-name>
          <string-name>
            <surname>Extending</surname>
          </string-name>
          <article-title>a Structured Document Model with Version Control</article-title>
          .
          <source>Proceedings of the International Database Engineering and Applications Symposium IDEAS'98</source>
          . p.
          <fpage>234</fpage>
          -
          <lpage>242</lpage>
          (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Otto</surname>
            <given-names>P.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Anton</surname>
            <given-names>A.I.</given-names>
          </string-name>
          <article-title>Addressing Legal Requirements in Requirements Engineering</article-title>
          .
          <source>Proceedings of the 15th International IEEE Requirements Engineering Conference RE'07</source>
          . p.
          <fpage>5</fpage>
          -
          <lpage>14</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Siena</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mylopoulos</surname>
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Perini</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Susi</surname>
            <given-names>A</given-names>
          </string-name>
          . From Laws to Requirements.
          <source>Proceedings of the International IEEE Requirements Engineering and Law Conference RELAW'08</source>
          . p.
          <fpage>6</fpage>
          -
          <lpage>10</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Siena</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Perini</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Susi</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mylopoulos</surname>
            <given-names>J.</given-names>
          </string-name>
          <article-title>A Meta-Model for Modelling Law-Compliant Requirements</article-title>
          .
          <source>Proceedings of the 2nd International Workshop on Requirements Engineering and Law RELAW'09</source>
          . p.
          <fpage>45</fpage>
          -
          <lpage>51</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Steinke</surname>
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Colleen</surname>
            <given-names>N.</given-names>
          </string-name>
          <article-title>Business rules as the basis of an organisation's information systems</article-title>
          .
          <source>Industrial Management &amp; Data Systems</source>
          , Vol.
          <volume>103</volume>
          Iss: 1, p.
          <fpage>52</fpage>
          -
          <lpage>63</lpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>