Concept-Based Engineering of Situation-Specific Migration Methods

Grieger, Marvin; Fazal-Baqaie, Masud; Engels, Gregor; Klenke, Markus

doi:10.1007/978-3-319-35122-3_14

Cited by 8 publications

(3 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A method pattern provides construction guidelines for a method by specifying which method fragments to use and how to assemble them [20]. In this paper, we present every method pattern with an Intent, the concern or problem that it addresses, and a Strategy, the methodological solution it follows [20].…”

Section: Methods Patterns For Consistency Managementmentioning

confidence: 99%

Description Languages for Consistency Management Scenarios Based on Examples from the Industry Automation Domain

et al. 2018

View full text Add to dashboard Cite

To cope with the increasing complexity of developing and maintaining modern (software) systems, multiple abstractions (models) of the same system can be established and used to allow different domain experts to collaborate and contribute their respective expertise. This divide-and-conquer, model-based approach requires, however, support for a concurrent engineering process, i.e., providing a means of checking, restoring, and ensuring the consistency of all involved and concurrently maintained models. The task of providing such support is often referred to as consistency management.Although there exist various approaches to consistency management and numerous (industrial) case studies described in the literature on bidirectional transformations (bx), there is currently no uniform description of diverse but related industrial applications of model synchronisation and other forms of consistency management. This makes it challenging to detect similarities and differences related to requirements, constraints, applied techniques and tools. It is thus difficult to compare and transfer knowledge gained from (successful) projects to other bx approaches or even other bx tools for the same general approach.In this paper, therefore, we propose a description language for envisioned scenarios in the problem domain of consistency management, as well as a complementary description language for solution strategies in terms of method fragments and method patterns in the solution domain of Model-Driven Engineering (MDE). Our work is inspired by previous research in the bx and MDE communities, and is also based on our collective experience from over ten years of investigating a series of application scenarios in the industry automation section together with Siemens AG as an industrial partner.We use our proposed description languages to discuss a series of application scenarios that are diverse but all require varying forms of support for consistency management. By using a common notation and focusing only on aspects directly related to consistency management, we are able to abstract from project-specific details and uniformly describe how consistency management is required and can be currently supported in the industry automation sector. Based on this formal and macroscopic view of the projects, we provide a systematic discussion of our experience and results applying Triple Graph Grammars (TGGs) as a concrete bx approach in the industry automation domain. ACM CCS 2012 1 Introduction and MotivationThe development and maintenance of increasingly complex software systems often requires a suitable decomposition of the system into multiple abstractions (models), which can be concurrently maintained by experts in their respective domains. Such a concurrent engineering process can be well supported by model-based approaches and techniques, especially approaches to ensure that the consistency of all related models, representing views of the same system, can be maintained via suitable change propagation and synchronisation. Numerous, diver...

show abstract

Section: Methods Patterns For Consistency Managementmentioning

confidence: 99%

Description Languages for Consistency Management Scenarios Based on Examples from the Industry Automation Domain

et al. 2018

View full text Add to dashboard Cite

show abstract

“…The developer and designer must carefully consider the fundamental properties of microservices, which include low coupling, high cohesion, scalability, independence, maintainability, modularity, and deployability [10]. These properties are closely related to architectural design [11], [12].…”

Section: B Microservicementioning

confidence: 99%

“…Each microservice is responsible for specific business capabilities, strong component separation, and independent deployability execution [1], [5], [10]. Other fundamental properties of microservice architectural design are low coupling, high cohesion, and modularity [10] must be carefully considered by developers and designers [11], [12] during the design phase.…”

Section: Introductionmentioning

confidence: 99%

From Monolith to Microservice: Measuring Architecture Maintainability

Hasan¹,

Osman²,

Admodisastro³

et al. 2023

IJACSA

View full text Add to dashboard Cite

The migration of monolithic applications to the cloud is a popular trend, with microservice architecture being a commonly targeted architectural pattern. The motivation behind this migration is often rooted in the challenges associated with maintaining legacy applications and the need to adapt to rapidly changing business requirements. To ensure that the migration to microservices is a sound decision for enhancing maintainability, designers must carefully consider the underlying factors driving this software architecture migration. This study proposes a set of software architecture metrics for evaluating the maintainability of microservice architectural designs for monolith to microservice architecture migration. These metrics consider various factors, such as coupling, complexity, cohesion, and size, which are crucial for ensuring that the software architecture remains maintainable in the long term. Drawing upon previous product quality models that share similar design properties with microservice, we have derived maintainability metrics that can help measure the quality of microservice architecture. In this work, we introduced our first version of structural metrics for measuring the maintainability quality of microservice architecture concerning its cloud-native characteristics. This work allows us to get early feedback on proposed metrics before a detailed evaluation. With these metrics, designers can measure their microservice architecture quality to fully leverage the benefits of the cloud environment, thus ensuring that the migration to microservice is a beneficial decision for enhancing the maintainability of their software architecture applications.

show abstract