Architecture-based Assessment and Planning of Change Requests

Rostami, Kiana; Stammel, Johannes; Heinrich, Robert; Reussner, Ralf

doi:10.1145/2737182.2737198

Cited by 31 publications

(16 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Our approach is based on KAMP to identify the relevant build components affected by a specific change request. The KAMP approach aims to "analyse the change propagation caused by a change request in a software system based on the architecture model" [12]. For this purpose, KAMP uses a change propagation algorithm, which is validated through an empirical study [12].…”

Section: Foundationsmentioning

confidence: 99%

“…The KAMP approach aims to "analyse the change propagation caused by a change request in a software system based on the architecture model" [12]. For this purpose, KAMP uses a change propagation algorithm, which is validated through an empirical study [12]. Starting with the initial change request, the change propagation algorithm calculates the affected elements in the architecture model.…”

Section: Foundationsmentioning

confidence: 99%

“…Translated into a PCM, a component can provide several interfaces, which are required by different subsets of its dependent components. If a change to one of these interfaces is made, only the components that require this interface are potentially affected by the change (i.e., not all components that require interfaces of a specific component) [12]. Figure 2 shows a simplified example from the PTV xServer.…”

Section: Approach For Build Avoidancementioning

confidence: 99%

“…The Apache Maven projects can be mapped to components in PCM, while different types of change scenarios for each Maven project represent different interfaces. Based on an initial change request, KAMP uses its change propagation algorithm to identify the affected build components [12]. KAMP's change propagation algorithm consists of a set of change propagation rules [12].…”

Section: B Utilization Of Kamp's Change Propagation Analysismentioning

confidence: 99%

“…The build experts of a development team annotate their knowledge on change-specific dependencies in the model of the software's build architecture. This model and the change scenarios are input for an existing change propagation approach for software architectures -Karlsruhe Architecture Maintainability Prediction (KAMP) [12]. The change propagation algorithm of KAMP identifies the build components to be built in order to implement the change.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

A Model-based Approach for Build Avoidance

Neumann¹,

Busch

Heinrich

2018

International Conferences on Software Engineering and Knowledge Engineering

Self Cite

View full text Add to dashboard Cite

In large software systems, we frequently encounter change scenarios which require long build times. In many cases, it would suffice to build only a subset of the dependent build components to generate sound build results. Current approaches for change-specific identification of affected build components rely on knowledge about the language-specific propagation of changes, which renders them inapplicable to multi-language systems. In this paper, we present a model-based approach to derive the affected build components for a change scenario using an existing change propagation approach. This way, we make the advantages of a set of change-specific dependencies also accessible to those members of the development team who are less knowledgeable about the build process. Our approach enables the use of change-specific dependencies in multi-language software systems and shortens build times. We implemented our approach in a productive build environment to show the feasibility and practicability in a user study.

show abstract

Section: Foundationsmentioning

confidence: 99%

Section: Foundationsmentioning

confidence: 99%

Section: Approach For Build Avoidancementioning

confidence: 99%

Section: B Utilization Of Kamp's Change Propagation Analysismentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

A Model-based Approach for Build Avoidance

Neumann¹,

Busch

Heinrich

2018

International Conferences on Software Engineering and Knowledge Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

Learning from Evolution for Evolution

Kögel

Tichy

Chakraborty

et al. 2019

Managed Software Evolution

View full text Add to dashboard Cite

Case Studies for the Community

Bougouffa

Busch

Heinrich

et al. 2019

Managed Software Evolution

View full text Add to dashboard Cite

This chapter describes the benefits and deliverables of the case studies in SPP1593 for the outside community. Section 12.1 sums up the benefits of the Common Component Modeling Example (CoCoME) case study together with the deliverables for the community. Section 12.2 describes the benefits of the Pick-and-Place Unit (PPU) and its extension (xPPU) as well as the deliverables for the outside community. Section 12.3 describes the benefits and deliverables of the industry 4.0 case study that integrates CoCoME and xPPU.

show abstract

Architecture-based Assessment and Planning of Change Requests

Abstract: Software architecture reflects important decisions on structure, used technology and resources. Architecture decisions influence to a large extent requirements on software quality.

Cited by 31 publications

References 12 publications

A Model-based Approach for Build Avoidance

A Model-based Approach for Build Avoidance

Learning from Evolution for Evolution

Case Studies for the Community

Contact Info

Product

Resources

About