Jörg Lenhard

Jörg Lenhard

Auto-generated profile, based on publicly available information

Jörg Lenhard

Karlstad University

Research Focus & Metrics

Academic Career Length

18Years (2009-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
1 March 2018 in Future Generation Computer Systems
Verified
Journal Article
Closed access
MGMatthias Geiger
Matthias Geiger
SHSimon Harrer
Simon Harrer
JLJörg Lenhard
Jörg Lenhard
GWGuido Wirtz
Guido Wirtz

8 March 2018 in Software Quality Journal
Verified
Journal Article
Open access
PDF file
JLJörg Lenhard
Jörg Lenhard
MBMartin Blom
Martin Blom
SHSebastian Herold
Sebastian Herold
Software architecture degradation is a phenomenon that frequently occurs during software evolution. Source code anomalies are one of the several aspects that potentially contribute to software architecture degradation. Many techniques for automating the detection of such anomalies are based on source code metrics. It is, however, unclear how accurate these techniques are in identifying the architecturally relevant anomalies in a system. The objective of this paper is to shed light on the extent to which source code metrics on their own can be used to characterize classes contributing to software architecture degradation. We performed a multi-case study on three open-source systems for each of which we gathered the intended architecture and data for 49 different source code metrics taken from seven different code quality tools. This data was analyzed to explore the links between architectural inconsistencies, as detected by applying reflexion modeling, and metric values indicating potential design problems at the implementation level. The results show that there does not seem to be a direct correlation between metrics and architectural inconsistencies. For many metrics, however, classes more problematic as indicated by their metric value seem significantly more likely to contribute to inconsistencies than less problematic classes. In particular, the fan-in, a classes’ public API, and method counts seem to be suitable indicators. The fan-in metric seems to be a particularly interesting indicator, as class size does not seem to have a confounding effect on this metric. This finding may be useful for focusing code restructuring efforts on architecturally relevant metrics in case the intended architecture is not explicitly specified and to further improve architecture recovery and consistency checking tool support.

1 December 2012
Verified
Conference Paper
Closed access
SHSimon Harrer
Simon Harrer
JLJorg Lenhard
Jorg Lenhard
GWGuido Wirtz
Guido Wirtz
More than five years have passed since the final release of the long-desired OASIS standard of a process language for Web Services orchestration, the Web Services Business Process Execution Language (BPEL). The aim of this standard was to establish a universally accepted Web Services orchestration language that forms a core part of service-oriented architectures and, because of standardization, avoids vendor lock-in. By now, several fully conformant engines should have arrived in the market. It is our aim to shed light on this situation and to provide a comprehensive picture of the current state of BPEL support. We present an evaluation of the standard conformance of five open source BPEL engines. To obtain these results we have developed betsy, a tool that allows for a fully-automatic standard conformance testing of BPEL engines. The results demonstrate that full standard conformance in contemporary engines is still far from given.

1 March 2015
Verified
Conference Paper
Closed access
MGMatthias Geiger
Matthias Geiger
SHSimon Harrer
Simon Harrer
JLJorg Lenhard
Jorg Lenhard
MCMathias Casar
Mathias Casar
AVAndreas Vorndran
Andreas Vorndran
GWGuido Wirtz
Guido Wirtz
Service-oriented systems are increasingly implemented in a process-based fashion. Multiple languages for building process-based systems are available today, but the Business Process Model and Notation (BPMN) is becoming ubiquitous. With BPMN 2.0 released in 2011, execution semantics were introduced, supporting the definition of executable processes. Nowadays, more and more process engines directly support the execution of BPMN processes. However, the BPMN specification is lengthy and complex. As there are no official tests and no certification authority, it is very likely that engines a) implement only a subset of the language features and b) implement language features differently. In other words, we suspect that engines do not conform to the standard, despite the fact that they claim support for it. This prohibits the porting of processes between different BPMN vendors, which is an acclaimed goal of the language. In this paper, we investigate the standard conformance of open source BPMN engines to provide a clear picture of the current state of the implementation of BPMN. We develop a testing approach that allows us to build fully BPMN-compliant tests and automatically execute these tests on different engines. The results demonstrate that state of-the-art BPMN engines only support a subset of the language. Moreover, they indicate that porting BPMN processes is only feasible when using basic language constructs.

1 March 2016
Verified
Conference Paper
Closed access
MGMatthias Geiger
Matthias Geiger
SHSimon Harrer
Simon Harrer
JLJorg Lenhard
Jorg Lenhard
GWGuido Wirtz
Guido Wirtz
The Business Process Model and Notation 2.0 (BPMN) standard has been hailed as a major step in business process modeling and automation. Recently, it has also been accepted as an ISO standard. The expectation is that vendors of business process management systems (BPMS) will switch to the new standard and natively support its execution in process engines. This paper presents an analysis of the current state and evolution of BPMN 2.0 support and implementation. We investigate how current BPMN 2.0 implementers deal with the standard, showing that native BPMN 2.0 execution still is an exception. Most BPMS do not support the execution format, despite claiming to be BPMN 2.0 compliant. Furthermore, building on past work, we evaluate three process engines that do provide native BPMN support and examine the evolution of their degree of support over a three-year period. This lets us delimit the areas of the standard that are considered important by the implementers. Since there is hardly an increase in supported features over the past three years, it seems that the implementation of the standard is more or less seen as finished by vendors and it is unlikely that features which are not available by now will be implemented in the future.

1 January 2009
Verified
Book Chapter
Closed access
PDF file
JLJörg Lenhard
Jörg Lenhard
KLKarsten Loesing
Karsten Loesing
GWGuido Wirtz
Guido Wirtz