Compliance of business processes is becoming increasingly important in the domain of business process design. Despite that, human process designers must be able to concentrate on the business goals which a business process needs to fulfil. Compliance aspects of the business process should not be in the main focus of the human process designer during the development phase. Therefore, tools must support human process designers in developing compliant business processes. In this paper we introduce the concept of compliance scopes. Compliance scopes are areas in a business process where certain compliance conditions must hold. These conditions are attached to the compliance scopes. Compliance scopes can be applied to existing business process models as well as to process templates. In this way compliance rules are applied to certain areas of a business process. During design time, compliance scopes can be used in graphical workbenches to evaluate modifications to business processes

Management of business processes is typically performed on multiple levels, each with different granularity, language constructs, and abstraction. Starting from an initial sketch of the activities to be performed, several refinements are made to entirely specify the business process, its artifacts, and participants. Then, information relevant for process execution can be added to enable efficient automation in the context of a service-oriented architecture (SOA). However, dealing with changes initiated by business or technology is a key difficulty in this approach. If change management is not performed properly then process models become out of sync which results in losing the alignment of business and IT. To address this challenge, we propose a synchronization method based on model element correspondence that considers change management between process models on different abstraction levels. We show how synchronization can be established and changes are propagated using a change queue for synchronization continuity. Finally we present a prototypical implementation of the key concepts

No abstract

No abstract