The Internet of Things (IoT) refers to a network of connected devices that collects and exchanges data through the Internet. These things can be artificial or natural and interact as autonomous agents that form a complex system. In turn, business process management (BPM) was established to analyze, discover, design, implement, execute, monitor, and evolve collaborative business processes within and across organizations. While the IoT and BPM have been regarded as separate topics in research and in practice, we strongly believe that, on the one hand, the management of IoT applications will greatly benefit from BPM concepts, methods, and technologies. On the other hand, the IoT poses challenges that will require enhancements and extensions of the current state of the art in the BPM field. In this article, we question the extent to which these two paradigms can be combined, and we discuss emerging challenges and intersections from a research and practitioner's point of view in terms of complex software systems development.
In his book Thinking, Fast and Slow, Daniel Kahneman presented a model of human cognition based on two modes or ‘systems’ of thinking: system 1 thinking that is fast and intuitive and system 2 thinking that is slow and tedious. This paper proposes a framework for applying Kahneman’s model to designing based on the function–behaviour–structure ontology. It casts four instances of designing in this framework: design fixation, case-based design, pattern-language-based design and brainstorming.
15 January 2010 in IEEE Transactions on Software Engineering
Process modeling allows for analysis and improvement of processes that coordinate multiple people and tools working together to carry out a task. Process modeling typically focuses on the normative process, that is, how the collaboration transpires when everything goes as desired. Unfortunately, real-world processes rarely proceed that smoothly. A more complete analysis of a process requires that the process model also include details about what to do when exceptional situations arise. We have found that, in many cases, there are abstract patterns that capture the relationship between exception handling tasks and the normative process. Just as object-oriented design patterns facilitate the development, documentation, and maintenance of object-oriented programs, we believe that process patterns can facilitate the development, documentation, and maintenance of process models. In this paper, we focus on the exception handling patterns that we have observed over many years of process modeling. We describe these patterns using three process modeling notations: UML 2.0 Activity Diagrams, BPMN, and Little-JIL. We present both the abstract structure of the pattern as well as examples of the pattern in use. We also provide some preliminary statistical survey data to support the claim that these patterns are found commonly in actual use and discuss the relative merits of the three notations with respect to their ability to represent these patterns.
1 April 2007 in Artificial Intelligence for Engineering Design, Analysis and Manufacturing
This paper presents how the function–behavior–structure (FBS) ontology can be used to represent processes despite its original focus on representing objects. The FBS ontology provides a uniform framework for classifying processes, and includes higher level semantics in their representation. We show that this ontology supports a situated view of processes based on a model of three interacting worlds. The situated FBS framework is then used to describe the situated design of processes.
This paper addresses a gap in handling multi-agent business processes that has prevented their larger-scale adoption in practice: the lack of a conceptual modeling approach that is easily understandable by business domain experts and sufficiently formal for direct transformation into executable systems. The emerging paradigm of subject-oriented business process management (S-BPM), which has been evaluated through academic research and is increasingly deployed in commercial applications, has the potential to augment multi-agent system (MAS) models with a process-centric layer that preserves autonomy and concurrent interaction of agents as essential system characteristics. In this paper we provide an aligned meta-model and illustrate its operational benefits with examples from business process applications.