Flexible Loosely Coupled Inter-Organizational Workflows using SOA

8International audienceService Oriented Architecture (SOA) is a paradigm that provides important properties for the development of business applications like flexibility and loose coupling. In our research work, we focus on the use of SOA to implement specific architectures of inter-organizational workflows (IOWF). The current paper deals with the "Loosely Coupled Workflow" specifying an IOWF-architecture that connects two or more workflows -attached to a set of business partners- communicating in an asynchronous manner according to a public communication protocol conjointly defined by all partners. The first issue of this work is to define a service based cooperation pattern called LC-IOWF pattern suitable to the architecture considered in order to obtain IOWF models flexible enough to ease their adaptation. The proposed LC-IOWF pattern is based on three main dimensions: services, control of execution and interactions. Then, we define three categories of adaptation patterns corresponding to the three dimensions exhibited. Particularly, the third category of these patterns called "Interaction adaptation patterns" concerns adaptations affecting the communication protocol and constitutes a specific type of adaptation compared with other IOWF-architectures. For implementation, we consider IOWF models specified with BPEL

Cooperation Patterns and Adaptation Patterns for Service-Based Inter-Organizational Workflows

International audienceModernization is an effective approach to making existing mainframe and distributed systems more responsive to business needs. SOA (service-oriented architecture) is an adequate paradigm that allows companies to tap into the business value in their current systems and position IT for rapid future changes to the business model. In our research works, we focus on the use of SOA to implement Inter- Organizational WorkFlows (IOWF). The goal is to take benefits from the advantages offered by the SOA paradigm like interoperability, reusability and flexibility in order to deal with workflow models easily adaptable, evolvable and reusable. This paper focuses on two specific architectures of IOWF which are the "chained execution" and the "subcontracting"; the first issue of this work is to define Service-Based Cooperation Patterns (SBCP) suitable to the two architectures considered. A SBCP is based on SOA; it is defined through three main dimensions: the distribution of services among the partner's sites, the control of instance execution and the structure of interaction between the workflows involved in the cooperation. The second issue of the paper consists of adaptation and evolution of IOWF process models obeying to the defined SBCP. Then, we state the main operations of adaptation that can be applied on these models; we focus on adaptation at process and interactional levels. Conformably to the three dimensions of SBCP, we define three classes of adaptation patterns: "service adaptation", "control flow adaptation" and "interaction adaptation" patterns. Also, we particularly distinguish some operations of adaptation called evolution of process models based on two perspectives: the expansion of the global functionality of the process and the expansion of the cooperation; we show that some evolutions are realized by reuse of existing IOWF models. For implementation, we consider IOWF process models specified with BPEL

Addressing inter-organisational process flexibility using versions: The VP2M approach

Process flexibility has been investigated in depth in the context of intra-organisational processes, but it is still an open issue when processes cross the boundaries of companies. In this paper, we address the modelling of flexible inter-organisational processes using a version-based approach. Indeed, versions are known to be a powerful technique to deal with variability, evolution and adaptation of processes, which are the three main needs of process flexibility. More precisely, this paper presents VP2M (Version of Process Meta-Model), a meta-model supporting the modelling of versions of inter-organisational processes, addressing both static and dynamic aspects of VP2M. It also illustrates process version modelling within the Subsea Pipeline process example

Addressing inter-organisational process flexibility using versions: The VP2M approach

Process flexibility has been investigated in depth in the context of intra-organisational processes, but it is still an open issue when processes cross the boundaries of companies. In this paper, we address the modelling of flexible inter-organisational processes using a version-based approach. Indeed, versions are known to be a powerful technique to deal with variability, evolution and adaptation of processes, which are the three main needs of process flexibility. More precisely, this paper presents VP2M (Version of Process Meta-Model), a meta-model supporting the modelling of versions of inter-organisational processes, addressing both static and dynamic aspects of VP2M. It also illustrates process version modelling within the Subsea Pipeline process example

Service-Oriented Process Models in Telecommunication Business

The thesis concentrates on to evaluate challenges in the business process management and the need for Service-oriented process models in telecommunication business to alleviate the integration work efforts and to reduce total costs of ownership. The business aspect concentrates on operations and business support systems which are tailored for communication service providers. Business processes should be designed in conformance with TeleManagement Forum's integrated business architecture framework. The thesis rationalizes the need to transform organizations and their way of working from vertical silos to horizontal layers and to understand transformational efforts which are needed to adopt a new strategy. Furthermore, the thesis introduces service characterizations and goes deeper into technical requirements that a service compliant middleware system needs to support. At the end of the thesis Nokia Siemens Networks proprietary approach – Process Automation Enabling Suite is introduced, and finally the thesis performs two case studies. The first one is Nokia Siemens Networks proprietary survey which highlights the importance of customer experience management and the second one is an overall research study whose results have been derived from other public surveys covering application integration efforts

Dynamic Multilevel Workflow Management Concept for Industrial IoT Systems

Workflow management is implemented in manufacturing at many levels. The nature of processes variesat each level, hindering the use of a standard modeling orimplementation solution. The creation of a flexible workflow management framework that overarches the heterogeneous business process levels is challenging. Still, one of the promisesof the Industry 4.0 initiative is precisely this: to provideeasy-to-use models and solutions that enable efficient execution of enterprise targets. By addressing this challenge, this articleproposes a workflow execution model that integrates information and control flows of these levels while keeping their hierarchy. The overall model builds on the business process model andnotation (BPMN) for modeling at the enterprise level and recipemodeling based on colored Petri net (CPN) at the production level. Models produced with both alternatives are implemented and executed in a framework supported by an enterprise servicebus (ESB). Loosely coupled, late-bound system elements are connected through the arrowhead framework, which is builtupon the service-oriented architecture (SOA) concept. To proveits feasibility, this article presents the practical application ofthe model via an automotive production scenario

Size Matters: Microservices Research and Applications

In this chapter we offer an overview of microservices providing the introductory information that a reader should know before continuing reading this book. We introduce the idea of microservices and we discuss some of the current research challenges and real-life software applications where the microservice paradigm play a key role. We have identified a set of areas where both researcher and developer can propose new ideas and technical solutions.Comment: arXiv admin note: text overlap with arXiv:1706.0735

Microservice API Evolution in Practice: A Study on Strategies and Challenges

Nowadays, many companies design and develop their software systems as a set of loosely coupled microservices that communicate via their Application Programming Interfaces (APIs). While the loose coupling improves maintainability, scalability, and fault tolerance, it poses new challenges to the API evolution process. Related works identified communication and integration as major API evolution challenges but did not provide the underlying reasons and research directions to mitigate them. In this paper, we aim to identify microservice API evolution strategies and challenges in practice and gain a broader perspective of their relationships. We conducted 17 semi-structured interviews with developers, architects, and managers in 11 companies and analyzed the interviews with open coding used in grounded theory. In total, we identified six strategies and six challenges for REpresentational State Transfer (REST) and event-driven communication via message brokers. The strategies mainly focus on API backward compatibility, versioning, and close collaboration between teams. The challenges include change impact analysis efforts, ineffective communication of changes, and consumer reliance on outdated versions, leading to API design degradation. We defined two important problems in microservice API evolution resulting from the challenges and their coping strategies: tight organizational coupling and consumer lock-in. To mitigate these two problems, we propose automating the change impact analysis and investigating effective communication of changes as open research directions