Architectural Decision Making for Service-Based Platform Integration: A Qualitative Multi-Method Study

Lytra, Ioanna; Sobernig, Stefan; Zdun, Uwe

doi:10.1109/wicsa-ecsa.212.19

Cited by 25 publications

(22 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…While Zdun and Avgeriou use OCL to document architectural primitives [14], we express these abstractions using compounds. For a detailed description of the patterns for service-based platform integration that are included in Table 1 you can refer to [12,11].…”

Section: Recurring Pattern Primitives As Reusable Ak Transformationsmentioning

confidence: 99%

“…9 The AK transformation language (DSL) and its editor were developed with Xtext framework. 10 The Eclipse Modeling Framework (EMF) 11 project is used to create all required models (e.g., architectural decision models) and the code for editing these models. The template binding of transformation actions and constraints in template form is done by the Velocity Template Engine.…”

Section: Tool Implementationmentioning

confidence: 99%

“…In our previous work, we have introduced an ADD model to handle various integration aspects in the service-based platform integration domain, i.e., integration and adaptation, interface design, communication style, and communication flow [12,11]. We present in Table 3 an excerpt of the ADD model of the platform integration scenario consisting of questions and different alternative options (or answers) along with the corresponding transformation actions that translate the underlying decisions into elements of the C&C view.…”

Section: Case Studymentioning

confidence: 99%

“…Thus, the task of harmonizing decisions and designs remains ad hoc and tedious. Making matters worse, the actual documentation of ADDs is also time consuming [8], especially for kinds of ADDs that need to be made repeatedly throughout a software design process, such as many of the ADDs documented in [11,12].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Harmonizing architectural decisions with component view models using reusable architectural knowledge transformations and constraints

Lytra

Tran

Zdun

2015

Future Generation Computer Systems

Self Cite

View full text Add to dashboard Cite

Section: Recurring Pattern Primitives As Reusable Ak Transformationsmentioning

confidence: 99%

Section: Tool Implementationmentioning

confidence: 99%

Section: Case Studymentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Harmonizing architectural decisions with component view models using reusable architectural knowledge transformations and constraints

Lytra

Tran

Zdun

2015

Future Generation Computer Systems

Self Cite

View full text Add to dashboard Cite

“…The scenario outlined in Section II entails the following challenges that are typically encountered when engineering service-based applications: Architectural Decisions: The process of developing service platforms follows recurring architectural design decisions [7], which should be explicit, systematic, and reusable. View-Based Modeling: The platform models need to capture the architectural components and processes, thereby distinguishing multiple external (e.g., service interfaces) and internal (e.g., monitoring infrastructure) views for different stakeholders [8].…”

Section: B Challenges For Service Delivery and Evolutionmentioning

confidence: 99%

Decisions, Models, and Monitoring -- A Lifecycle Model for the Evolution of Service-Based Systems

Inzinger

Hummer

Lytra

et al. 2013

2013 17th IEEE International Enterprise Distributed Object Computing Conference

Self Cite

View full text Add to dashboard Cite

Abstract-The process of engineering and provisioning service-based systems (SBS) follows a complex and dynamic lifecycle with different phases and levels of abstraction. We tackle the problem of making this lifecycle explicit, providing development time and runtime support for evolutionary changes in such systems. SBSs are modeled as integrated ecosystems consisting of four conceptual layers (or phases): design, implementation, deployment, and runtime. Our work is driven by the notion that identifying the right changes (monitoring) and effecting of these changes (adaptation) usually takes place individually on each layer. While considering changes on a single layer (e.g., runtime adaptation) is often sufficient, some cases require systematic escalation to adjacent layers. We present a generic lifecycle model that provides an abstracted view of the problem domain and can be mapped to concrete artifacts on each individual layer. We introduce a real-life scenario taken from the telecommunications domain, which serves as the basis for discussion of the challenges and our solution. Based on the scenario and our experience from a research project on Virtual Service Platforms, we evaluate three concrete use cases which illustrate the diversity of evolutionary changes supported by the approach.

show abstract

Guiding Architectural Decision Making on Quality Aspects in Microservice APIs

Zdun

Stocker

Zimmermann

et al. 2018

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Architectural Decision Making for Service-Based Platform Integration: A Qualitative Multi-Method Study

Cited by 25 publications

References 19 publications

Harmonizing architectural decisions with component view models using reusable architectural knowledge transformations and constraints

Harmonizing architectural decisions with component view models using reusable architectural knowledge transformations and constraints

Decisions, Models, and Monitoring -- A Lifecycle Model for the Evolution of Service-Based Systems

Guiding Architectural Decision Making on Quality Aspects in Microservice APIs

Contact Info

Product

Resources

About