Business process compliance through reusable units of compliant processes

D. Schumm, O. Turetken, N. Kokash, A. El Gammal, F. Leymann, W.J.A.M. van den Heuvel

    Research output: Chapter in Book/Report/Conference proceedingConference contributionScientificpeer-review

    50 Citations (Scopus)
    717 Downloads (Pure)

    Abstract

    Compliance management is essential for ensuring that organizational business processes and supporting information systems are in accordance with a set of prescribed requirements originating from laws, regulations, and various legislative or technical documents such as Sarbanes-Oxley Act or ISO 17799. As the violation of such requirements may lead to significant punishment for an organization, compliance management should be supported at the very early stages of business process development. In this paper, we present an integrated approach to compliance management that helps process designers to adhere to compliance requirements relevant for their processes. Firstly, we introduce a conceptual model for specifying compliance requirements originating from various compliance sources. Secondly, we propose a framework for augmenting business processes with reusable fragments to ensure process compliance to certain requirements by design. Furthermore, we discuss the formalization of compliance requirements using mathematical logics and integrate the framework for process reuse with automated software verification tools.
    Original languageEnglish
    Title of host publicationProceedings of the 1st International Workshop on Engineering SOA and the Web (ESW '10) Austria, Vienna
    EditorsF. Daniel, F.M. Facca
    Place of PublicationHeidelberg
    PublisherSpringer Verlag
    Pages325-337
    Volume6385
    Publication statusPublished - 2010

    Publication series

    NameLecture Notes in Computer Science
    Volume6385

    Fingerprint

    Dive into the research topics of 'Business process compliance through reusable units of compliant processes'. Together they form a unique fingerprint.

    Cite this