Demo Data from EDBT 2026 / reviewers in the wild / expert
Tony Moynihan
dblp:22/4970
· DBLP profile ↗
8ranked-venue papers
7as first author
0since 2021 · last 2002
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 4 · 3 first-authorDatabases, data management, data science and information retrieval · 4 · 4 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 |
Requirements engineering and software design · 77% Empirical software engineering · 23% |
Topics — the 1 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › software process
project planning |
0.0 | 1 | 2000 | Prompter - a project planning assistant · ICSE 2000 |
Methods — techniques the papers use, named apart from their topics
expert critiquing · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2002 | Coping with client-based 'people-problems': the theories-of-action of experienced IS/software project managers
Tony Moynihan |
Inf. Manag. | 1 |
| 2000 | Prompter - a project planning assistantabstractThe aim of the Prompter project was to develop the Prompter tool, a “decision-support tool to assist in the planning and managing of a software project”. Prompter has the ability to help software project planners assimilate best practice and 'know how' in the field of software project planning and incorporate expert critiquing which will assist project planners in solving the complex problems associated with the planning of a software project. Rory O'Connor, Robert Cochran, Tony Moynihan |
ICSE | 3 |
| 2000 | 'Requirements-Uncertainty': Is it best formulated as a latent, aggregate or profile construct?abstractThis paper identifies the strategies that experienced information systems (IS) project managers say they use to cope with requirements-uncertainty (RU) when managing development projects for external clients. It is shown that project managers (PMs) claim to use different strategies for coping with the different dimensions of requirements-uncertainty, as this notion has been formulated in IS literature. Based on this finding, it is proposed that perhaps requirements-uncertainty should be formulated as a profile construct, and not as a latent or aggregate construct, if it is to have pragmatic validity as a guide to action for project managers. Tony Moynihan |
Eur. J. Inf. Syst. | 1 |
| 2000 | Coping with 'requirements-uncertainty': the theories-of-action of experienced IS/software project managers
Tony Moynihan |
J. Syst. Softw. | 1 |
| 1996 | An experimental comparison of object-orientation and functional-decomposition as paradigms for communicating system functionality to users
Tony Moynihan |
J. Syst. Softw. | 1 |
| 1993 | Modelling the software process in terms of the system representations and transformation steps used
Tony Moynihan |
Inf. Softw. Technol. | 1 |
| 1982 | Information Systems as aids to achieving organizational integration
Tony Moynihan |
Inf. Manag. | 1 |
| 1981 | The 'orientation' of the organization's computer-based systems: Is it appropriate?
Tony Moynihan |
Inf. Manag. | 1 |