Fragmento for COMPAS





About Fragmento

As described in the related documents, companies increasingly have to pay attention to compliance. Flexibly reacting to requirements coming from laws, regulations, and internal policies becomes an essential part of business process management. Compliance refers to the measures that need to be taken in order to adhere to these requirements. In order to comply, companies need to perform profound changes in their organizational structure, processes and their supporting infrastructure. At this, process-awareness is a basic prerequisite for ascertaining to operate in a compliant way.


The Fragmento repository focuses on the application of the emerging concept of process fragments in the field of compliance management in process-based applications. We propose to specify compliance controls as reusable process fragments. We understand a process fragment as a connected, possibly incomplete process graph which may also contain additional artefacts like the fragment context. A process fragment is not necessarily directly executable as some parts may be explicitly stated as opaque in order to mark points of variability.


Conceptual Model for Fragmento
A repository for process artefacts needs to account for persistence, storage, retrieval and version management of all artefacts related to a process. We can distinguish different types of artefacts that are related to a process or to a process fragment in a service-oriented environment.
  • A process or process fragment model, either in standard BPEL or in an extended or modified version of BPEL
  • An according WSDL document (for specifying the interface)
  • A deployment descriptor according to the process or the process fragment
  • Additional information for a process modelling tool for instance to store X and Y coordinates of activities
  • A view transformation rule for process view transformations
  • Annotation documents (e.g., a policy specified in WS-SecurityPolicy)
The repository assigns unique identifier to each artefact being stored. The usage of unique identifiers allows creating arbitrary relations between artefacts. The above listed types of artefacts are typically serializable to XML, therefore the repository mainly needs to store XML artefacts. Additional metadata, such as a description, keywords and a name are also applicable to all of the listed types.





Contributors
  • David Schumm (Main Contributor)
  • Tobias Anstett (XMLO Repository)
  • Dimitrios Dentsas (Eclipse Integration)
  • Michael Hahn (BPEL Designer Integration)
  • Mirko Sonntag (BPEL Designer Integration Lead)


Related Documents
  • D. Schumm, D. Karastoyanova, O. Kopp, F. Leymann, M. Sonntag, S. Strauch: Process Fragment Libraries for Easier and Faster Development of Process-based Applications. In: Czech Society for Systems Integration (CSSI) (Hrsg): Journal of Systems Integration. Vol. 2(1), Online, 2011. ( pdf)
  • D. Schumm, D. Karastoyanova, F. Leymann, S. Strauch: Fragmento: Advanced Process Fragment Library. Proc. of the 19th International Conference on Information Systems Development (ISD'10), 2010. ( pdf)
  • D. Schumm, F. Leymann, Z. Ma, T. Scheibler, S. Strauch: Integrating Compliance into Business Processes: Process Fragments as Reusable Compliance Controls. Proc. of the Multikonferenz Wirtschaftsinformatik (MKWI'10), 2010. ( pdf)
  • F. Daniel, F. Casati, V. D'Andrea, S. Strauch, D. Schumm, F. Leymann, E. Mulo, U. Zdun, S. Dustdar, S. Sebahi, F. de Marchi, M.S. Hacid. Business Compliance Governance in Service-Oriented Architectures. Proc. of the 23rd IEEE International Conference on Advanced Information Networking and Applications (AINA), IEEE Press, 2009. ( pdf)
  • European Project COMPAS: Supporting Infrastructure - Process Engine, Process Artefact Repository, Process Generation Tool. Project Deliverable D4.4, 2009.
  • European Project MASTER: Technical Architecture and APIs for Single Trust Domain. Project Deliverable D2.3.1, 2009.




(c) 2008-2011 David Schumm as part of my work at IAAS, University of Stuttgart