Demo Data from VLDB 2026 / reviewers in the wild / expert
Peter A. Pircher
dblp:48/4476
· DBLP profile ↗
2ranked-venue papers
0as first author
0since 2021 · last 1986
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2
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
2 papers |
Software testing · 33% Empirical software engineering · 33% Requirements engineering and software design · 33% |
Topics — the 3 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering › software analytics
logging analysis |
0.0 | 1 | 1986 | Building Reliable Interactive Information Systems · IEEE Trans. Software Eng. 1986 |
Software testing
system testing |
0.0 | 1 | 1986 | Building Reliable Interactive Information Systems · IEEE Trans. Software Eng. 1986 |
Requirements engineering and software design › requirements elicitation
user participation |
0.0 | 1 | 1986 | Developing Interactive Information Systems with the User Software Engineering Methodology · IEEE Trans. Software Eng. 1986 |
Methods — techniques the papers use, named apart from their topics
state transition diagram · 0.0prototyping · 0.0precondition-postcondition · 0.0graphical tools · 0.0formal specification · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1986 | Building Reliable Interactive Information SystemsabstractUser software engineering (USE) is a methodology, with supporting tools, for the specification, design, and implementation of interactive information systems. With the USE approach, the user interface is formally specified with augmented state transition diagrams, and the operations may be formally specified with preconditions and postconditions. The USE state transition diagrams may be directly executed with the application development tool RAPID/USE. RAPID/USE and its associated tool RAPSUM create and analyze logging information that is useful for system testing, and for evaluation and modification of the user interface. The authors briefly describe the USE transition diagrams and the formal specification approach, and show how these tools and techniques aid in the creation of reliable interactive information systems. Anthony I. Wasserman, Peter A. Pircher, David T. Shewmake |
IEEE Trans. Software Eng. | 2 |
| 1986 | Developing Interactive Information Systems with the User Software Engineering MethodologyabstractUser software engineering (USE) is a methodology, supported by automated tools, for the systematic development of interactive information systems. The USE methodology gives particular attention to effective user involvement in the early stages of the software development process, concentrating on external design and the use of rapidly created and modified prototypes of the user interface. The USE methodology is supported by an integrated set of graphically based tools. The USE methodology and the tools that support it are described. Anthony I. Wasserman, Peter A. Pircher, David T. Shewmake, Martin L. Kersten |
IEEE Trans. Software Eng. | 2 |