Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

E. Timothy Morgan

dblp:24/4793 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1987
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 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.

Theoretical computer science
1 paper
Automated reasoning and model checking · 100%
Software engineering, system software, and programming languages
1 paper
Concurrent programming · 50% Software testing · 50%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Automated reasoning and model checking
state space analysis
0.011987
Interactive State-Space Analysis of Concurrent Systems · IEEE Trans. Software Eng. 1987
Concurrent programming
concurrency bugs
0.011987
Interactive State-Space Analysis of Concurrent Systems · IEEE Trans. Software Eng. 1987
Software testing › specification-based testing › conformance testing
protocol conformance testing
0.011987
Interactive State-Space Analysis of Concurrent Systems · IEEE Trans. Software Eng. 1987

Methods — techniques the papers use, named apart from their topics

computer-aided verification · 0.0
YearPublicationVenuePosition
1987 Interactive State-Space Analysis of Concurrent Systems
abstract
The introduction of concurrency into programs has added to the complexity of the software design process. This is most evident in the design of communications protocols where concurrency is inherent to the behavior of the system. The complexity exhibited by such software systems makes more evident the need for computer-aided tools for automatically analyzing behavior.
E. Timothy Morgan, Rami R. Razouk
IEEE Trans. Software Eng.1