Demo Data from EDBT 2026 / reviewers in the wild / expert
Paul Adamczyk
dblp:10/6494
· DBLP profile ↗
2ranked-venue papers
1as first author
0since 2021 · last 2011
0000-0003-0976-5782ORCID · corroborated
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2 · 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 · 100% |
Topics — the 1 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering
software engineering practice |
0.1 | 1 | 2010 | The Tower of Babel did not fail · OOPSLA 2010 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2011 | Patterns Transform ArchitecturesabstractSoftware patterns have been used to guide developers and to disseminate expert knowledge. But patterns can also be thought of as program transformations. Security patterns are architectural. Therefore, program transformations derived from those patterns transform architecture. This paper describes how we used a catalog of security patterns to produce a catalog of security-oriented program transformations. These transformations can be used to make architectural changes that make systems more secure. This paper is a first example of applying patterns to actively transform architectures. Munawar Hafiz, Paul Adamczyk, Ralph E. Johnson |
WICSA | 2 |
| 2010 | The Tower of Babel did not failabstractFred Brooks' retelling of the biblical story of the Tower of Babel offers many insights into what makes building software difficult. The difficulty, according to common interpretations, comes from the communication and organizational problems in software development. But the story contains one more important lesson that people tend to miss: one cannot accomplish impossible goals, which programmers are often asked to do. Software engineering, as a discipline, can overcome poor communication; but as long as we attempt to live up to impossible expectations, we will always fail. Paul Adamczyk, Munawar Hafiz |
OOPSLA | 1 |