Demo Data from EDBT 2026 / reviewers in the wild / expert
Matej Hertis
dblp:150/0613
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 2014
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Empirical software engineering · 67% Services computing and microservices · 33% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Services computing and microservices
business process management |
0.2 | 1 | 2014 | An Empirical Analysis of Business Process Execution Language Usage · IEEE Trans. Software Eng. 2014 |
Empirical software engineering
mining software repositories |
0.2 | 1 | 2014 | An Empirical Analysis of Business Process Execution Language Usage · IEEE Trans. Software Eng. 2014 |
Empirical software engineering
process mining |
0.2 | 1 | 2014 | An Empirical Analysis of Business Process Execution Language Usage · IEEE Trans. Software Eng. 2014 |
Methods — techniques the papers use, named apart from their topics
empirical analysis · 0.2complexity metrics · 0.2
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2014 | An Empirical Analysis of Business Process Execution Language UsageabstractThe current state of executable business process languages allows for and demands optimization of design practices and specifications. In this paper, we present the first empirical study that analyses Web Services Business Process Execution Language (WS-BPEL or BPEL) usage and characteristics of real world executable business processes. We have analysed 1,145 BPEL processes by measuring activity usage and process complexity. In addition, we investigated the occurrence of activity usage patterns. The results revealed that the usage frequency of BPEL activities varies and that some activities have a strong co-occurrence. BPEL activities often appear in activity patterns that are repeated in multiple processes. Furthermore, the current process complexity metrics have proved to be inadequate for measuring BPEL process complexity. The empirical results provide fundamental knowledge on how BPEL specification and process design practices can be improved. We propose BPEL design guidelines and BPEL language improvements for the design of more understandable and less complex processes. The results are of interest to business process language designers, business process tool developers, business process designers and developers, and software engineering researchers, and contribute to the general understanding of BPEL and service-oriented architecture. Matej Hertis, Matjaz B. Juric |
IEEE Trans. Software Eng. | 1 |