A Conceptual Framework and Experimental Workbench for Architectures

Konersmann, Marco; Goedicke, Michael

doi:10.1007/978-3-642-30835-2_4

Cited by 6 publications

(9 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The approach extends and combines our previous work [4,12] and consists of (1) an architecture language supporting evolution, (2) a catalogue of reusable solutions with question annotations to evaluate the solutions, (3) a method to documents decisions together with rationale and to establish trace links between artefacts, and (4) explicitly integrated architecture. We structure the related work according to these four aspects.…”

Section: Related Workmentioning

confidence: 98%

“…We create bidirectional transformations between ADLs and the IL, and between the IL and the CMs (e.g. see [12]). To address (2), the IL and their relationship to ADLs and CMs have to respect the variability of these languages.…”

Section: Explicitly Integrated Architecturementioning

confidence: 99%

“…These two representations have to be synchronised to avoid misinformation, because they share information. The goal of the Explicitly Integrated Architecture approach (presented formerly in [12]) is to avoid differences between these representations. To achieve this goal, the specification is explicitly integrated into the program code in such a way that it complies a CM, and at the same time includes the additional information from the architecture specification (e.g.…”

Section: Explicitly Integrated Architecturementioning

confidence: 99%

See 2 more Smart Citations

Towards architecture-centric evolution of long-living systems (the ADVERT approach)

Konersmann

Durdik

Goedicke

et al. 2013

Proceedings of the 9th International ACM Sigsoft Conference on Quality of Software Architectures

Self Cite

View full text Add to dashboard Cite

Although an intensive research attention has been paid to software evolution, there is no established approach which supports a software development and evolution round-trip between requirements, design decisions, architectural elements, and code. The ADVERT approach shall provide support for software evolution on an architectural level. AD-VERT is based on two core ideas: (1) Maintaining trace links between requirements, design decisions, and architecture elements, and (2) explicitly integrating software architecture information into the code. The expected benefits of the approach are: (1) Eased understanding of the relationship between requirements and design, and (2) assured compliance between architectural design and implementation. In this position paper we explain our envisioned approach and demonstrate it on a CoCoME-based example, which is a benchmark for component-based modelling approaches.

show abstract

Section: Related Workmentioning

confidence: 98%

Section: Explicitly Integrated Architecturementioning

confidence: 99%

Section: Explicitly Integrated Architecturementioning

confidence: 99%

See 1 more Smart Citation

Towards architecture-centric evolution of long-living systems (the ADVERT approach)

Konersmann

Durdik

Goedicke

et al. 2013

Proceedings of the 9th International ACM Sigsoft Conference on Quality of Software Architectures

Self Cite

View full text Add to dashboard Cite

show abstract

“…The technique is based on architecture-carrying code [4]. The idea of architecture-carrying code is to represent architectural models in source code with sophisticated code structures.…”

Section: Architecture-carrying Codementioning

confidence: 99%

“…For systematically storing model-based usage scenarios, we extend the use of architecture-carrying code [4]. First, we create a model of the software architecture.…”

Section: Run Time Monitoringmentioning

confidence: 99%

Rapidly locating and understanding errors using runtime monitoring of architecture-carrying code

Konersmann

2014

Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering

Self Cite

View full text Add to dashboard Cite

Finding and understanding errors in software that is deployed in the field and tested by beta testers or used in production is a difficult and often time consuming task. If the feedback to the developers is naïvely composed of log messages, stack traces, and informal user feedback, it might not contain enough information to locate the erroneous fragments efficiently. It is thus slowing the dynamics in rapid continuous software engineering scenarios. These errors can more easily be found when the code is explicitly designed to carry architectural specifications by intertwining structure and behavior models with the rest of the code. With architecture-carrying code, (1) the steps leading to single errors can be replayed for understanding and debugging;(2) statistical information about errors can be related to structure elements and behavior branches. In this paper we present our idea of architecture-carrying code and its application for error understanding to support rapid continuous software engineering.

show abstract

Integrating Protocol Contracts with Program Code – A Leightweight Approach for Applied Behaviour Models that Respect Their Execution Context

Konersmann

Goedicke

2015

Behavior Modeling -- Foundations and Applications

View full text Add to dashboard Cite

A Conceptual Framework and Experimental Workbench for Architectures

Cited by 6 publications

References 3 publications

Towards architecture-centric evolution of long-living systems (the ADVERT approach)

Towards architecture-centric evolution of long-living systems (the ADVERT approach)

Rapidly locating and understanding errors using runtime monitoring of architecture-carrying code

Integrating Protocol Contracts with Program Code – A Leightweight Approach for Applied Behaviour Models that Respect Their Execution Context

Contact Info

Product

Resources

About