Organizations are struggling to choose from or combine the different business process management paradigms offered in today's BPM landscape, such as workflow management, dynamic case management and straight through processing. The field of declarative processes seems to be able to address this challenge by offering a unified approach to business process modeling, providing variable amounts of flow at execution time and different levels of autonomy to the actors based on models using a single formalism. The notion of declarativity in business processes seems to be ill defined and is often treated as a black and white distinction. However, a number of quite different formalisms have been developed that are broadly agreed to be declarative. This paper proposes a number of qualitative characteristics to characterize the declarative nature of process modeling formalisms. The characteristics are evaluated by applying them to a number of relevant process modeling formalisms, both imperative and declarative, and we discuss how these characteristics can be utilized to create business processes that offer activity flows that are known up front where needed, and allow ad hoc approaches to offer experts freedom and to support impediment driven approaches in an STP context.
DOCUMENT
Managing and supporting the collaboration between different actors is key in any organizational context, whether of a hierarchical or a networked nature. In the networked context of ecosystems of service providers and other stakeholders, BPM is faced with different challenges than in a conventional hierarchical model, based on up front consolidation and consensus on the process flows used in collaboration. In networked ecosystems of potential business partners, designing collaboration upfront is not feasible. Coalitions are formed situationally, and sometimes even ad-hoc. This paper presents a number of challenges for conventional BPM in such environments, and explores how declarative process management technology could address them, indicating topics for further research.
MULTIFILE
Agile software development has evolved into an increasingly mature software development approach and has been applied successfully in many software vendors’ development departments. In this position paper, we address the broader agile service development. Based on method engineering principles we define a framework that conceptualizes an operational way of working for the development of services, emphatically taking into account agility. As a first level of agility, the framework contains situational project factors that influence the choice of method fragments; secondly, increased agility is proposed by describing and operationalizing these method fragments not as imperative steps or activities, but instead by means of sets of minimally specified, declarative rules that determine the context and constraints within which goals are to be reached. This approach borrows concepts from rules management, organizational patterns, and game design theory. Keywordsmethod engineering–agile service development–business rules–business rules management–product management–game design
DOCUMENT
