Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data.

Moritz Eck

dblp:244/2473 · DBLP profile ↗
← Back
3ranked-venue papers
1as first author
1since 2021 · last 2022
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 2 · 1 first-author · 1 since 2021Computer networks · 1Security and privacy · 1 · 1 since 2021

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
Software testing · 56% Empirical software engineering · 44%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering
developer studies
0.412019
Understanding flaky tests: the developer's perspective · ESEC/SIGSOFT FSE 2019
Software testing
flaky test
0.412019
Understanding flaky tests: the developer's perspective · ESEC/SIGSOFT FSE 2019
Software testing › flaky test
test reliability
0.112019
Understanding flaky tests: the developer's perspective · ESEC/SIGSOFT FSE 2019

Methods — techniques the papers use, named apart from their topics

survey · 0.4interview study · 0.4
YearPublicationVenuePosition
2022 ProvotuMN: Decentralized, Mix-Net-based, and Receipt-free Voting System
abstract
Recent years saw an increase in voting systems using public permissionless blockchains. Although public blockchains offer transparency and immutability, permissioned consensus is better suited for voting systems’ requirements, because an initial level of trust in authorities is always required. Hence, a permissioned Distributed Ledger (DL) immutably storing the voting system’s audit trail satisfies demands measurably.ProvotuMN 3.0 is a decentralized and receipt-Free (RF) voting system based on an end-to-end verifiable Re-Encryption Mixnet (RMN). RMNs allow for flexible votes and elections and decouple the ballot structure from the cryptographic voting protocol. Thus, ProvotuMN decentralizes trust (i) through the use of cryptographic shuffles and Non-Interactive Zero-Knowledge Proofs (NIZKP) in an RMN executed among DL nodes, (ii) by employing a distributed key generation for election keys, and (iii) by offering a decentralized re-encryption service assuring RF. Performance evaluations performed indicate that the voting scheme is scalable for large-scale voting.
Christian Killer, Moritz Eck, Bruno Rodrigues 0001, Jan von der Assen, Roger Staubli, Burkhard Stiller
ICBC2
2020 Provotum: A Blockchain-based and End-to-end Verifiable Remote Electronic Voting System
abstract
While the existence of Public Bulletin Boards (PBB) is often formulated as an assumption in related work on Remote Electronic Voting (REV) systems, this work here on Provotum focuses on the practical design and architecture of such a PBB, including its distributed execution. Further, Provotum leverages a public permissioned Blockchain (BC) as a PBB, where only authorized entities can sign blocks, while the general public can verify all BC data. Therefore, Provotum defines a new and fully decentralized BC-based REV system, which deploys a permissioned BC as a PBB and allows for the explicit distribution of trust across different permissioned BC nodes. Provotum is operated in a fully distributed fashion by using Smart Contracts (SC), Distributed Key Generation (DKG), Homomorphic Encryption (HE), and Cooperative Decryption (CD), as well as employing client-side encryption, which enables ballot secrecy, while the BC forms an audit trail, enabling public and End-to-end Verifiability (E2E-V).
Christian Killer, Bruno Rodrigues 0001, Eder J. Scheid, Muriel Figueredo Franco, Moritz Eck, Nik Zaugg, Alex Scheitlin, Burkhard Stiller
LCN5
2019 Understanding flaky tests: the developer's perspective
abstract
Flaky tests are software tests that exhibit a seemingly random outcome (pass or fail) despite exercising unchanged code. In this work, we examine the perceptions of software developers about the nature, relevance, and challenges of flaky tests.
Moritz Eck, Fabio Palomba, Marco Castelluccio, Alberto Bacchelli
ESEC/SIGSOFT FSE1