Demo Data from EDBT 2026 / reviewers in the wild / expert
Pam Rostal
dblp:60/7473
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2009
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
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 |
Requirements engineering and software design · 68% Empirical software engineering · 32% |
Topics — the 4 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design
software architecture |
0.1 | 1 | 2009 | Agile anthropology and Alexander's architecture: an essay in three voices · OOPSLA 2009 |
Empirical software engineering
agile software development |
0.0 | 1 | 2009 | Agile anthropology and Alexander's architecture: an essay in three voices · OOPSLA 2009 |
Requirements engineering and software design › software design
software design theory |
0.0 | 1 | 2009 | Agile anthropology and Alexander's architecture: an essay in three voices · OOPSLA 2009 |
Empirical software engineering
software engineering practice |
0.0 | 1 | 2009 | Agile anthropology and Alexander's architecture: an essay in three voices · OOPSLA 2009 |
Methods — techniques the papers use, named apart from their topics
theory building · 0.1ethnography · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2009 | Agile anthropology and Alexander's architecture: an essay in three voicesabstractDuring its formative decades the software community looked twice to the theories of Christopher Alexander for inspiration, both times failing to completely master the architect's most useful insights. Now a third opportunity presents itself with Alexander's recent publication, The Nature of Order. Serious apprenticeship, however, imposes a prerequisite of sober self-reflection and evaluation. What, really, is the nature of the developer's tasks? Under what philosophical umbrella has the software community matured until now? Do other philosophical traditions offer alternative and perhaps more pertinent epistemologies? What voices, besides Alexander's, might contribute to the community's evolution? We address these questions along with theory building, ethnography, weak links, design heuristics, agility, and complex systems, all of which combine with Alexander's new theories to suggest different ways of doing what we do, better. Jenny Quillien, Pam Rostal, Dave West |
OOPSLA | 2 |