Demo Data from EDBT 2026 / reviewers in the wild / expert
Allan M. Stavely
dblp:44/3893
· DBLP profile ↗
12ranked-venue papers
7as first author
0since 2021 · last 2000
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 10 · 6 first-authorHuman-computer interaction and ubiquitous computing · 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
4 papers |
Program verification · 69% Requirements engineering and software design · 15% Program analysis · 13% |
Topics — the 6 heaviest of 8, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Program verification
loop verification |
0.0 | 1 | 1995 | Verifying Definite Iteration Over Data Structures · IEEE Trans. Software Eng. 1995 |
Program verification › hardware verification
functional verification |
0.0 | 1 | 1995 | Verifying Definite Iteration Over Data Structures · IEEE Trans. Software Eng. 1995 |
Program analysis › concurrent program analysis
static analysis of concurrent programs |
0.0 | 1 | 1985 | A Collection of Software Tools for Analyzing Design of Concurrent Software Systems · ICSE 1985 |
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 |
Concurrent programming
concurrency bugs |
0.0 | 1 | 1985 | A Collection of Software Tools for Analyzing Design of Concurrent Software Systems · ICSE 1985 |
Methods — techniques the papers use, named apart from their topics
functional verification · 0.0data structure iteration reasoning · 0.0formal specification · 0.0behavior modeling · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2000 | Teaching Formal Methods Early in the Software Engineering Curriculum (panel)abstractnecessity of formal methods education has developed from its increasing assimilation into systems development within industry. Organizations responsible for a wide range of applications have found it necessary to find an improved means of intellectual control over their complex system development and that formal methods can meet this need. To this end, the International Survey of Industrial Applications of Formal Methods concluded and recommended: The current educational base in the US is weak in teaching formal methods in the context of software engineering . . . There is a clear need for improved integration of formal methods techniques with other software engineering practices[2]There exists a number of articles in the current literature expressing the belief that the current educational program offered for a computer science degree does not stress the fundamental mathematical and engineering principles that should form the basis of software engineering[3,4,5,6]. theory learned in mathematics and science classes is applied in other engineering classes, but unfortunately has not been applied in software engineering. inability to apply logic in practical circumstances prevents the student from doing the systematic analysis necessary to solve practical problems.For these reasons, it is desirable to include the definition and application of a formal method into the undergraduate curriculum with the goal of increasing the complex problem solving skills of the software engineer. Formal analysis should be introduced early into the undergraduate curriculum to ensure substantial learning, use, and training in formal methods application. Ann E. Kelley Sobel, Hossein Saiedian, Allan M. Stavely, Peter B. Henderson |
CSEE&T | 3 |
| 1999 | High-Quality Software through Semiformal Specification and VerificationabstractSemi-formal specification and verification in the style of the cleanroom method, combined with testing, have proven to be exceptionally effective in reducing the number of defects in software, as well as being cost-effective in practice. A course based on these principles is described, and the results of class projects and projects by graduates of the course are presented. These results provide evidence that cleanroom techniques, as adapted for the course, are indeed effective, and that these techniques can be taught successfully, even to undergraduates. Allan M. Stavely |
CSEE&T | 1 |
| 1995 | Verifying Definite Iteration Over Data StructuresabstractMethods are presented for verifying loops which iterate over elements of data structures. This verification is done in the functional style developed by Mills and others, in which code is verified against the function that the code is intended to compute. The methods allow the verifier to concentrate on the essential computation performed on each element of the structure, and separate out such concerns as data-structure access and termination so that they do not need to be verified again for every loop in the program. The methods are applicable to a large class of data structures and iterations over them.> Allan M. Stavely |
IEEE Trans. Software Eng. | 1 |
| 1993 | An empirical study of iteration in applications software
Allan M. Stavely |
J. Syst. Softw. | 1 |
| 1990 | Algorithms for analyzing concurrent software systems using derivatives
Allan M. Stavely |
J. Syst. Softw. | 1 |
| 1989 | Finding reachable states of finite-state concurrent systems
Gregory B. Titus, Allan M. Stavely |
J. Syst. Softw. | 2 |
| 1985 | A Collection of Software Tools for Analyzing Design of Concurrent Software Systems
Allan M. Stavely, D. C. Becker, S. P. Orr, Gregory B. Titus |
ICSE | 1 |
| 1985 | Inference from models of software systems
Allan M. Stavely |
J. Syst. Softw. | 1 |
| 1983 | Modeling and projection in software development
Allan M. Stavely |
J. Syst. Softw. | 1 |
| 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. | 5 |
| 1978 | Behavior Modelling During Software Design
William E. Riddle, Jack C. Wileden, John H. Sayler, Alan R. Segal, Allan M. Stavely |
ICSE | 5 |
| 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. | 5 |