Unique identification of elements in evolving software models

Wenzel, Sven

doi:10.1007/s10270-012-0311-7

Cited by 10 publications

(3 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, approaches to history analysis [8], which are yet restricted to the tracing of single entities, could be extended to trace sets of related elements, e.g. all elements that are affected by a complex refactoring, change request or a bug fix.…”

Section: Discussionmentioning

confidence: 99%

Detection of High-Level Changes in Evolving Java Software

Kehrer¹,

Pietsch²,

Yazdi³

et al. 2013

Softwaretechnik-Trends

View full text Add to dashboard Cite

Software re-engineering is faced with the huge challenge of understanding the structure and behavior of complex programs. In case of legacy systems, understanding the past of a system is often required to understand certain design rationales that help to understand the system itself.In this paper, we report about our ongoing work on analyzing the evolution of Java programs using techniques from the domain of comparison and versioning of software models. Working on reverse-engineered class diagrams, a model matching algorithm is used to identify differences on the design-level. Based on that, a highly customizable operation detection engine is used to derive the actual changes between revisions. Our experience has shown that the approach is capable of identifying high-level software changes such as refactorings or the introduction of design patterns.

show abstract

Section: Discussionmentioning

confidence: 99%

Detection of High-Level Changes in Evolving Java Software

Kehrer¹,

Pietsch²,

Yazdi³

et al. 2013

Softwaretechnik-Trends

View full text Add to dashboard Cite

show abstract

“…Reliable identifiers are hardly available across sets of variants, and names are not sufficiently eligible for taking an informed matching decision without considering other properties. In particular, names are not necessarily unique, and some model elements do not have names at all [44].…”

Section: N-way Model Matchingmentioning

confidence: 99%

RaQuN: a generic and scalable n-way model matching algorithm

et al. 2022

View full text Add to dashboard Cite

Model matching algorithms are used to identify common elements in input models, which is a fundamental precondition for many software engineering tasks, such as merging software variants or views. If there are multiple input models, an n-way matching algorithm that simultaneously processes all models typically produces better results than the sequential application of two-way matching algorithms. However, existing algorithms for n-way matching do not scale well, as the computational effort grows fast in the number of models and their size. We propose a scalable n-way model matching algorithm, which uses multi-dimensional search trees for efficiently finding suitable match candidates through range queries. We implemented our generic algorithm named RaQuN (Range Queries on $$\text {N}$$ N input models) in Java and empirically evaluate the matching quality and runtime performance on several datasets of different origins and model types. Compared to the state of the art, our experimental results show a performance improvement by an order of magnitude, while delivering matching results of better quality.

show abstract

“…Apparently, this algorithm performs poorly for models with a high number of elements. Although some optimizations of the pairwise comparison have been implemented (Brun, 2008;Wenzel, 2014) they perform well under the assumption that not many differences exist between two versions of a model. This assumption is not true in our case because we compare large models at a time interval of several weeks (an agile iteration).…”

Section: Emf Compare Customizationmentioning

confidence: 99%

Balancing Product and Process Assurance for Evolving Security Systems

Raschke

Zilli

Baumgartner³

et al. 2015

International Journal of Secure Software Engineering

View full text Add to dashboard Cite

At present, security-related engineering usually requires a big up-front design (BUFD) regarding security requirements and security design. In addition to the BUFD, at the end of the development, a security evaluation process can take up to several months. In today's volatile markets customers want to be able to influence the software design during the development process. Agile processes have proven to support these demands. Nevertheless, there is a clash between traditional security design and evaluation processes. In this paper, the authors propose an agile security evaluation method for the Common Criteria standard. This method is complemented by an implementation of a change detection analysis for model-based security requirements. This system facilitates the agile security evaluation process to a high degree. However, the application of the proposed evaluation method is limited by several constraints. The authors discuss these constraints and show how traditional certification schemes could be extended to better support modern industrial software development processes.

show abstract

Unique identification of elements in evolving software models

Cited by 10 publications

References 35 publications

Detection of High-Level Changes in Evolving Java Software

Detection of High-Level Changes in Evolving Java Software

RaQuN: a generic and scalable n-way model matching algorithm

Balancing Product and Process Assurance for Evolving Security Systems

Contact Info

Product

Resources

About