Towards Consistency Management for a Business-Driven Development of SOA

The usage of the Service Oriented Architecture (SOA) along with the Business Process Management has emerged as a valuable solution for the complex (business process driven) system engineering. With a Model Driven Engineering where the business process models drive the supporting service component architectures, less effort is gone into the Business/IT alignment during the initial development activities, and the IT developers can rapidly proceed with the SOA implementation. However, the difference between the design principles of the emerging domainspecific languages imposes serious challenges in the following re-design phases. Moreover, enabling evolutions on the business process models while keeping them synchronized with the underlying software architecture models is of high relevance to the key elements of any Business Driven Development (BDD). Given a business process update, this paper introduces an incremental model transformation approach that propagates this update to the related service component configurations. It, therefore, supports the change propagation among heterogenous domainspecific languages, e.g., the BPMN and the SCA. As a major contribution, our approach makes model transformation more tractable to reconfigure system architecture without disrupting its structural consistency. We propose a synchronizer that provides the BPMN-to-SCA model synchronization with the help of the conditional graph rewriting

Towards Consistency Management for a Business-Driven Development of SOA

International audienceThe usage of the Service Oriented Architecture (SOA) along with the Business Process Management has emerged as a valuable solution for the complex (business process driven) system engineering. With a Model Driven Engineering where the business process models drive the supporting service component architectures, less effort is gone into the Business/IT alignment during the initial development activities, and the IT developers can rapidly proceed with the SOA implementation. However, the difference between the design principles of the emerging domain-specific languages imposes serious challenges in the following re-design phases. Moreover, enabling evolutions on the business process models while keeping them synchronized with the underlying software architecture models is of high relevance to the key elements of any Business Driven Development (BDD). Given a business process update, this paper introduces an incremental model transformation approach that propagates this update to the related service component configurations. It, therefore, supports the change propagation among heterogenous domain-specific languages, e.g., the BPMN and the SCA. As a major contribution, our approach makes model transformation more tractable to reconfigure system architecture without disrupting its structural consistency. We propose a synchronizer that provides the BPMN-to-SCA model synchronization with the help of the conditional graph rewriting

Model-driven design of context-aware applications

In many cases, in order to be effective, software applications need to allow sensitivity to context changes. This implies however additional complexity associated with the need for applications’ adaptability (being capable of capturing context, interpreting it and reacting on it). Hence, we envision 3 ‘musts’ that, in combination, are especially relevant to the design of context-aware applications. Firstly, at the business modeling level, it is considered crucial that the different possible context states can be properly captured and modeled, states that correspond to certain desirable behaviors. Secondly, it must be known what are the dependencies between the two, namely between states and behaviors. And finally, what is valid for application design in general, business needs are to be aligned to application solutions. In this work, we address the mentioned challenges, by approaching the notion of context and extending from this perspective a previously proposed business-software alignment approach. We illustrate our achieved results by means of a small example. It is expected that this research contribution will be useful as an additional result concerning the alignment between business modeling and software design

SOA-Driven Business-Software Alignment

The alignment of business processes and their supporting application software is a major concern during the initial software design phases. This paper proposes a design approach addressing this problem of business-software alignment. The approach takes an initial business model as a basis in deriving refined models that target a service-oriented software implementation. The approach explicitly identifies a software modeling level at which software modules are represented as services in a technology-platformindependent way. This model-driven service-oriented approach has the following properties: (i) there is a forced alignment (consistency) between business processes and supporting applications; (ii) changes in the business environment can be traced to the application and vice versa, via model relationships; (iii) the software modules modeled as services have a high degree of autonomy; (iv) migration to new technology platforms can be supported through the platform independent software model

Exploring Maintainability Assurance Research for Service- and Microservice-Based Systems: Directions and Differences

To ensure sustainable software maintenance and evolution, a diverse set of activities and concepts like metrics, change impact analysis, or antipattern detection can be used. Special maintainability assurance techniques have been proposed for service- and microservice-based systems, but it is difficult to get a comprehensive overview of this publication landscape. We therefore conducted a systematic literature review (SLR) to collect and categorize maintainability assurance approaches for service-oriented architecture (SOA) and microservices. Our search strategy led to the selection of 223 primary studies from 2007 to 2018 which we categorized with a threefold taxonomy: a) architectural (SOA, microservices, both), b) methodical (method or contribution of the study), and c) thematic (maintainability assurance subfield). We discuss the distribution among these categories and present different research directions as well as exemplary studies per thematic category. The primary finding of our SLR is that, while very few approaches have been suggested for microservices so far (24 of 223, ?11%), we identified several thematic categories where existing SOA techniques could be adapted for the maintainability assurance of microservices

Ontology-based patterns for the integration of business processes and enterprise application architectures

Increasingly, enterprises are using Service-Oriented Architecture (SOA) as an approach to Enterprise Application Integration (EAI). SOA has the potential to bridge the gap between business and technology and to improve the reuse of existing applications and the interoperability with new ones. In addition to service architecture descriptions, architecture abstractions like patterns and styles capture design knowledge and allow the reuse of successfully applied designs, thus improving the quality of software. Knowledge gained from integration projects can be captured to build a repository of semantically enriched, experience-based solutions. Business patterns identify the interaction and structure between users, business processes, and data. Specific integration and composition patterns at a more technical level address enterprise application integration and capture reliable architecture solutions. We use an ontology-based approach to capture architecture and process patterns. Ontology techniques for pattern definition, extension and composition are developed and their applicability in business process-driven application integration is demonstrated

SOA, SoBI & EDA - Paradigms for Integration Capabilities of BI Platform

A Business Intelligence (BI) provider may offer a basic solution, a packed application or a comprising BI platform which integrates components from individual technologies in a synergic system. The providers’ tendency is to standardize the instruments offered on a single server platform. The article analyzes the integration capabilities and problems of BI platforms, emphasizes the differences between emergent technologies and suggests integration solutions. The analysis is useful both to the providers of BI solutions - in order to develop some agile platforms, as well as to their users - representing an important factor in selecting the solution. In addition, the conclusions to be drawn will emphasize the tendencies from the BI market and will represent the support in creating some agile platforms.Business Intelligence, agile platform, integration, metadata management, Service Oriented Architecture (SOA), Event Driven Architecture (EDA)

A Model-Driven Architecture Approach to the Efficient Identification of Services on Service-oriented Enterprise Architecture

Service-Oriented Enterprise Architecture requires the efficient development of loosely-coupled and interoperable sets of services. Existing design approaches do not always take full advantage of the value and importance of the engineering invested in existing legacy systems. This paper proposes an approach to define the key services from such legacy systems effectively. The approach focuses on identifying these services based on a Model-Driven Architecture approach supported by guidelines over a wide range of possible service types