Process-Aware Information Systems (PAISs) need more flexibility for supporting complex and varying human activities. PAISs usually support business process design by means of graphical graph-oriented business process modeling languages (BPMLs) in conjunction with textual executable specifications. In this paper we discuss the flexibility of such BPMLs which are the main interface for users that need to change the behavior of PAISs. In particular, we show how common BPMLs features, that seem good when considered alone, have a negative impact on flexibility when they are combined together for providing a complete executable specification. A model has to be understood before being changed and a change is made only when the benefits outweigh the effort. Two main factors have a great impact on comprehensibility and ease of change: concurrency and modularity. We show why BPMLs usually offer a limited concurrency model and lack of modularity; finally we discuss how to overcome these problems.
['Carlo Combi', 'Mauro Gambini']
Flaws in the Flow: The Weakness of Unstructured Business Process Modeling Languages Dealing with Data