Demo Data from EDBT 2026 / reviewers in the wild / expert
John H. Sayler
dblp:06/385
· DBLP profile ↗
4ranked-venue papers
0as first author
0since 2021 · last 1988
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 4
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 |
Requirements engineering and software design · 91% Program verification · 9% |
Topics — the 2 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › software modeling
behavior modeling |
0.0 | 2 | 1978 | Behavior Modeling During Software Design · IEEE Trans. Software Eng. 1978 Behavior Modelling During Software Design · ICSE 1978 |
Requirements engineering and software design
formal specification |
0.0 | 1 | 1978 | Behavior Modeling During Software Design · IEEE Trans. Software Eng. 1978 |
Methods — techniques the papers use, named apart from their topics
formal specification · 0.0behavior modeling · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1988 | SDA: A Novel Approach to Software Environment Design and Construction
Kouichi Kishida, Takuya Katayama, Masatoshi Matsuo, Isao Miyamoto, Koichiro Ochimizu, Nobuo Saito, John H. Sayler, Koji Torii, Lloyd G. Williams |
ICSE | 7 |
| 1983 | Behavior specification in a software design system
Jack C. Wileden, John H. Sayler, William E. Riddle, Alan R. Segal, Allan M. Stavely |
J. Syst. Softw. | 2 |
| 1978 | Behavior Modelling During Software Design
William E. Riddle, Jack C. Wileden, John H. Sayler, Alan R. Segal, Allan M. Stavely |
ICSE | 3 |
| 1978 | Behavior Modeling During Software DesignabstractA modeling scheme is presented which provides a medium for the rigorous, formal, and abstract specification of large-scale software system components. The scheme allows the description of component behavior without revealing or requiring the description of a component's internal operation. Both collections of sequential processes and the data objects which they share may be described. The scheme is of particular value during the early stages of software system design, when the system's modules are being delineated and their interactions designed, and when rigorous, well-defined specification of undesigned components allows formal and informal arguments concerning the design's correctness to be formulated. William E. Riddle, Jack C. Wileden, John H. Sayler, Alan R. Segal, Allan M. Stavely |
IEEE Trans. Software Eng. | 3 |