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

SOA and BPM, a Partnership for Successful Organizations

In order to stay effective and competitive, companies have to be able to adapt themselves to permanent market requirements, to improve constantly their business process, to act as flexible and proactive economic agents. To achieve these goals, the IT systems within the organization have to be standardized and integrated, in order to provide fast and reliable data access to users both inside and outside the company. A proper system architecture for integrating company’s IT assets is a service oriented one. A service-oriented architecture (SOA) is an IT architectural style that allows integration of the company’s business as linked, repeatable tasks called services. A subject closely related to SOA is Business Process Management (BPM), an approach that aims to improve business processes. The paper also presents some aspects of this topic, as well as the relationship between SOA and BPM. They complement each other and help companies improve their business performance.Information Systems, SOA, Web Services, BPM

Shifting Complexity: The Impact of Modularization on IS Complexity

Many organizations strive to reduce the complexity of their IS architecture. One frequently used intervention is to minimize IS complexity by applying modularization. With modularization, systems are decomposed into modules to maximize IT flexibility. However, very few organizations achieve the anticipated benefits when introducing modularization. Therefore, our aim in this paper is to increase our understanding of the effects of modularization on IS complexity. Through a case study, we explore the relation between modularization and IS complexity. The results show three design choices through which modularization affects IS complexity: (1) the degree of granularity, (2) unification of terminology, and (3) the centralization of connections. The results also show that IS complexity is often shifted instead of reduced. Complexity seems to shift as a ‘waterbed effect’ across the IS architecture and across the different conceptualizations of complexity. With that understanding, IS complexity can be moved to a location in an organization better suited to deal with it

Audit Techniques for Service Oriented Architecture Applications

The Service Oriented Architecture (SOA) approach enables the development of flexible distributed applications. Auditing such applications implies several specific challenges related to interoperability, performance and security. The service oriented architecture model is described and the advantages of this approach are analyzed. We also highlight several quality attributes and potential risks in SOA applications that an architect should be aware when designing a distributed system. Key risk factors are identified and a model for risk evaluation is introduced. The top reasons for auditing SOA applications are presented as well as the most important standards. The steps for a successful audit process are given and discussed.Service Oriented Architecture, Audit, Quality Attributes, Interoperability, Performance, Security

Combining SAWSDL, OWL-DL and UDDI for Semantically Enhanced Web Service Discovery

UDDI registries are included as a standard offering within the product suite of any major SOA vendor, serving as the foundation for establishing design-time and run-time SOA governance. Despite the success of the UDDI specification and its rapid uptake by the industry, the capabilities of its offered service discovery facilities are rather limited. The lack of machine-understandable semantics in the technical specifications and classification schemes used for retrieving services, prevent UDDI registries from supporting fully automated and thus truly effective service discovery. This paper presents the implementation of a semantically-enhanced registry that builds on the UDDI specification and augments its service publication and discovery facilities to overcome the aforementioned limitations. The proposed solution combines the use of SAWSDL for creating semantically annotated descriptions of service interfaces and the use of OWL-DL for modelling service capabilities and for performing matchmaking via DL reasoning