The microservices architectural style has become the de facto standard for large-scale cloud applications, offering numerous benefits in scalability, maintainability, and deployment flexibility. Many organizations are pursuing the migration of legacy monolithic systems to a microservices architecture. However, this process is challenging, risky, time-intensive, and prone-to-failure while several organizations lack necessary financial resources, time, or expertise to set up this migration process. So, rather than trying to migrate a legacy system where migration is risky or not feasible, we suggest exposing it as a microservice application without without having to migrate it. In this paper, we present a reusable, automated, two-phase approach that combines evolutionary algorithms with machine learning techniques. In the first phase, we identify microservices at the method level using a multi-objective genetic algorithm that considers both structural and semantic dependencies between methods. In the second phase, we generate REST APIs for each identified microservice using a classification algorithm to assign HTTP methods and endpoints. We evaluated our approach with a case study on the Spring PetClinic application, which has both monolithic and microservices implementations that serve as ground truth for comparison. Results demonstrate that our approach successfully aligns identified microservices with those in the reference microservices implementation, highlighting its effectiveness in service identification and API generation.

Service 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.

The SOA (Service Oriented Architecture) paradigm provides important advantages like interoperability, reusability and flexibility required in the area of business applications. In our research works, we focus on the use of SOA to implement inter-organizational workflows (IOWF). Our goal is to obtain IOWF models flexible enough in order to ease their adaptation at build-time and at runtime, because services are loosely coupled components, easily invoked and interoperable. This paper focuses on specific and well common IOWF-architectures defined in the literature; it deals with adaptation of IOWF process models obeying to these architectures. First, we define the concept of Service-Based Cooperation Pattern (SBCP) that supports service-based IOWF models meeting one of the specific architectures considered. Then, we state a set of recurrent operations of adaptation (attached to process and interaction aspects) that can be applied on service-based IOWF models, and we illustrate their implementation for IOWF models specified with BPEL.

Despite that reuse libraries are now well adopted during software development step, software evolution step is not yet covered by this kind of beneficial approach. In this paper we present the "evolution shelf", a generic infrastructure to achieve for-reuse and by-reuse techniques within the field of software evolution. The basic idea behind that is to propose and encourage the reuse of recurring and reliable evolution expertises to achieve the structural evolution of a software system at the architectural level. For that purpose, the shelf assists architects in classifying, storing and selecting reusable architectural evolution operations. The underlying concept that we propose to capitalize the expertises is called "evolution style" and it mixes a syntactic and a semantic description format. These ideas form a core for a long-term vision in which it is possible to build a business model of evolution-of-the-shelf (EOTS) with the special objective to decrease the efforts and the risks related to the evolution activities.

Software architecture modeling and representation became a main phase of the development process of complex systems. In fact, software architecture representation provides many advantages during all phases of software life cycle. Nevertheless, for many systems, like legacy or eroded ones, there is no available representation of their architectures. In order to benefit from this representation, we propose, in this paper, an approach called ROMANTIC which focuses on extracting a component-based architecture of an existing object-oriented system. The main idea of this approach is to propose a quasi-automatic process of architecture recovery based on semantic and structural characteristics of software architecture concepts.

This paper presents our work on component-based software evolution. More precisely, we highlight how connectors enhance component-based software architecture evolution. Indeed, connectors, by their intermediary's position between components, can play an important role for automating the propagation of evolution impacts, while preserving the architecture coherence. For that, we outline connectors' characteristics that we consider as principal for aims of evolution management. We validate and exploit these characteristics on our evolution model SAEV (software architecture evolution model). To achieve this, we need to enrich the concept of connector with information about the degree of correlation and of dependency existing between components. For that, we propose to characterize the connector concept with semantic properties, namely: exclusivity/sharing, dependency/ independency, predominance/non predominance, cardinality and reverse cardinality.

Database applications which model aspects of the real world should be able to express as accurately as possible the different nuances of reality; that includes the need to evolve internally in response to signals of updates coming from the environment. These updates are not always supplied in an ideal and complete manner and are not always predefined or precisely defined. In practice, requirements for evolution generally occur during the manipulation of objects while running the database. It is frequently necessary to change individual objects, less frequently the database schema. Database systems need to have mechanisms capable, whenever and as well as possible, of assimilating this new information correctly and diagnosing and implementing the changes necessary.