On the Support of Workflow Activity Patterns in Process Modeling Tools: Purpose and Requirements

Patterns increase the reuse of existing knowledge (e.g., design solutions, source code) within organizations and help to achieve consistency between applications. Patterns for process design have received considerable attention by both business analysts and researchers. Several pattern categories have been proposed including patterns for control and data flow, resources, process change, and exception handling. Workflow activity patterns, which can be used as building blocks for business process models (e.g., approval, task execution request), however, have not been explored in-depth so far. Related to this problem we have proposed a set of workflow activity patterns in the ProWAP project. Each activity pattern represents a recurrent business function as it can be frequently found in business processes. The completeness and existence of our activity patterns has been evaluated through an extensive analysis of real process models. In this paper we discuss how to implement activity patterns within a BPM tool. In particular, we describe major goals and requirements of the BPM tool we are currently developing and in which we apply workflow activity patterns. In this context, we also provide a discussion regarding the notion we use for representing activity patterns (BPMN 1.2 vs. UML 2.0)

Embedding Requirements within the Model Driven Architecture

The Model Driven Architecture (MDA) brings benefits to software development, among them the potential for connecting software models with the business domain. This paper focuses on the upstream or Computation Independent Model (CIM) phase of the MDA. Our contention is that, whilst there are many models and notations available within the CIM Phase, those that are currently popular and supported by the Object Management Group (OMG), may not be the most useful notations for business analysts nor sufficient to fully support software requirements and specification. Therefore, with specific emphasis on the value of the Business Process Modelling Notation (BPMN) for business analysts, this paper provides an example of a typical CIM approach before describing an approach which incorporates specific requirements techniques. A framework extension to the MDA is then introduced; which embeds requirements and specification within the CIM, thus further enhancing the utility of MDA by providing a more complete method for business analysis

Supporting the Design of Privacy-Aware Business Processes via Privacy Process Patterns

Privacy is an increasingly important concern for modern software systems which handle personal and sensitive user information. Privacy by design has been established in order to highlight the path to be followed during a system’s design phase ensuring the appropriate level of privacy for the information it handles. Nonetheless, transitioning between privacy concerns identified early during the system’s design phase, and privacy implementing technologies to satisfy such concerns at the later development stages, remains a challenge. In order to overcome this issue, mainly caused by the lack of privacy-related expertise of software systems engineers, this work proposes a series of privacy process patterns. The proposed patterns encapsulate expert knowledge and provide predefined solutions for the satisfaction of different types of privacy concerns. The patterns presented in this work are used as a component of an existing privacy-aware system design methodology, through which they are applied to a real life system

Adaptive Process Management in Cyber-Physical Domains

The increasing application of process-oriented approaches in new challenging cyber-physical domains beyond business computing (e.g., personalized healthcare, emergency management, factories of the future, home automation, etc.) has led to reconsider the level of flexibility and support required to manage complex processes in such domains. A cyber-physical domain is characterized by the presence of a cyber-physical system coordinating heterogeneous ICT components (PCs, smartphones, sensors, actuators) and involving real world entities (humans, machines, agents, robots, etc.) that perform complex tasks in the “physical” real world to achieve a common goal. The physical world, however, is not entirely predictable, and processes enacted in cyber-physical domains must be robust to unexpected conditions and adaptable to unanticipated exceptions. This demands a more flexible approach in process design and enactment, recognizing that in real-world environments it is not adequate to assume that all possible recovery activities can be predefined for dealing with the exceptions that can ensue. In this chapter, we tackle the above issue and we propose a general approach, a concrete framework and a process management system implementation, called SmartPM, for automatically adapting processes enacted in cyber-physical domains in case of unanticipated exceptions and exogenous events. The adaptation mechanism provided by SmartPM is based on declarative task specifications, execution monitoring for detecting failures and context changes at run-time, and automated planning techniques to self-repair the running process, without requiring to predefine any specific adaptation policy or exception handler at design-time

Modelling the business structure of a digital health ecosystem

[EN]The current trend in digital solutions for the health sector is to move from fragmented services to progressively more integrated services provided by multiple stakeholders through technological ecosystem platforms. However, the business model is scarcely taken into account at the early stages of development of this type of ecosystems specially in the health sector. In the present paper a general approach towards the exploitation of a technological ecosystem focused on caregivers is presented. It follows the Business Process Model and Notation (BPMN) in order to develop different ecosystem’s exploitation alternatives, taking into account the ecosystem stakeholders and their main value propositions. This serves as a starting data model in the software development process from which different business exploitation alternatives can be elaborated

Modelling Collaboration Processes Through Design Patterns

Enterprise 2.0 has been introduced in the SME (Small Medium Enterprise) modifying common organizational and operative practices. This brings the `knowledge workers' to change their working practices through the use of web 2.0 communication tools. Unfortunately, these tools do not allow intercepting and tracing the exchanged data, which can produce a loss of information. This is an important problem in an enterprise context because knowledge of the exchanged information can increase the efficiency and competitiveness of the company. In this article we demonstrate that it is possible to extract this knowledge by an abstraction process of the new operative practices, named collaboration processes, thanks to the use of design patterns. Therefore, we propose design patterns for the collaboration processes useful for modelling typical Enterprise 2.0 activities, having the goal of making more flexible and traceable the use of emerging operative practices

Bridging the Gap Between Business Process Models and Service Composition Specifications

Fundamental goals of any Service Oriented Architecture (SOA) include the flexible support and adaptability of business processes as well as improved business-IT alignment. Existing approaches, however, have failed to fully meet these goals. One of the major reasons for this deficiency is the gap that exists between business process models on the one hand and workflow specifications and implementations (e.g., service composition schemes) on the other hand. In practice, each of these two perspectives has to be regarded separately. In addition, even simple changes to one perspective (e.g. due to new regulations or organizational change) require error-prone, manual re-editing of the other one. Over time, this leads to degeneration and divergence of the respective models and specifications. This aggravates maintenance and makes expensive refactoring inevitable. This chapter presents a flexible approach for aligning business process models with workflow specifications. In order to maintain the complex dependencies that exist between high-level business process models (as used by domain experts) and technical workflow specifications (i.e., service composition schemas), respectively, (as used in IT departments) we introduce an additional model layer – the so-called system model. Furthermore, we explicitly document the mappings between the different levels (e.g., between business process model and system model). This simplifies model adoptions by orders of magnitudes when compared to existing approaches

Integrating Safety Assessment into the Design of Healthcare Service-Oriented Architectures

Most healthcare organisations are service-oriented, fundamentally centred on critical services provided by medical and nursing staff. Increasingly, these human-centric services rely on software-intensive systems, i.e. medical devices and health informatics, for improving different aspects of healthcare, e.g. enhancing efficiency through automation and patient safety through smart alarm systems. However, many healthcare services are categorised as high risk and as such it is vital to analyse the ways in which the software-based systems can contribute to unintentional harm and potentially compromise patient safety. This paper proposes an approach to modelling and analysing Service-Oriented Architectures (SOAs) used in healthcare, with emphasis on identifying and classifying potential hazardous behaviour. The paper also considers how the safety case for these SOAs can be developed in a modular manner. The approach is illustrated through a case study based on three services: ambulance, electronic health records and childbirth services