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

Cheryl D. Kelly

dblp:18/3093 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 1992
—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 · 82% Requirements engineering and software design · 12% Concurrent programming · 6%
Human-computer interaction and pervasive computing
1 paper
User interface design and tools · 100%

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

TopicWeightPapersLastEvidence papers
Software testing
concurrency testing
0.011992
Structural Testing of Concurrent Programs · IEEE Trans. Software Eng. 1992
Software testing › test adequacy
coverage criteria
0.011992
Structural Testing of Concurrent Programs · IEEE Trans. Software Eng. 1992
Software testing
structural testing
0.011992
Structural Testing of Concurrent Programs · IEEE Trans. Software Eng. 1992
Software testing
test coverage
0.011992
Structural Testing of Concurrent Programs · IEEE Trans. Software Eng. 1992
User interface design and tools › user interface architecture
user interface management system
0.011988
Design Principles behind Chiron: A UIMS for Software Environments · ICSE 1988
Requirements engineering and software design
software design principles
0.011988
Design Principles behind Chiron: A UIMS for Software Environments · ICSE 1988
Concurrent programming
concurrency bugs
0.011992
Structural Testing of Concurrent Programs · IEEE Trans. Software Eng. 1992

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

static concurrency analysis · 0.0runtime monitoring · 0.0
YearPublicationVenuePosition
1992 Structural Testing of Concurrent Programs
abstract
Although structural testing techniques are among the weakest available with regard to developing confidence in sequential programs, they are not without merit. The authors extend the notion of structural testing criteria to concurrent programs and propose a hierarchy of supporting structural testing techniques. Coverage criteria described include concurrency state coverage, state transition coverage and synchronization coverage. Requisite support tools include a static concurrency analyzer and either a program transformation system or a powerful run-time monitor. Also helpful is a controllable run-time scheduler. The techniques proposed are suitable for Ada or CSP-like languages. Best results are obtained for programs having only static naming of tasking objects.>
Richard N. Taylor, David L. Levine, Cheryl D. Kelly
IEEE Trans. Software Eng.3
1988 Design Principles behind Chiron: A UIMS for Software Environments
Michal Young, Richard N. Taylor, Dennis B. Troup, Cheryl D. Kelly
ICSE4