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

Ting-Kau Leung

dblp:63/5130 · DBLP profile ↗
← Back
3ranked-venue papers
0as first author
0since 2021 · last 1989
—ORCID · none

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

Computer networks · 2Software engineering, systems software and programming languages · 1

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.

Computer networks
3 papers
Network management and operations · 95% Internet architecture and protocols · 5%
Software engineering, system software, and programming languages
2 papers
Software testing · 100%

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

TopicWeightPapersLastEvidence papers
Network management and operations › network testing › protocol conformance testing
fault coverage
0.021989
Formal Methods for Protocol Testing: A Detailed Study · IEEE Trans. Software Eng. 1989
Fault coverage of protocol test methods · INFOCOM 1988
Network management and operations › network testing
protocol conformance testing
0.021989
Formal Methods for Protocol Testing: A Detailed Study · IEEE Trans. Software Eng. 1989
Fault coverage of protocol test methods · INFOCOM 1988
Software testing
test generation
0.021988
Experience with test generation for real protocols · SIGCOMM 1988
Fault coverage of protocol test methods · INFOCOM 1988
Network management and operations › network testing › protocol conformance testing
test sequence generation
0.011989
Formal Methods for Protocol Testing: A Detailed Study · IEEE Trans. Software Eng. 1989
Software testing › specification-based testing › conformance testing
protocol conformance testing
0.011988
Experience with test generation for real protocols · SIGCOMM 1988
Software testing › test generation
test sequence generation
0.011988
Experience with test generation for real protocols · SIGCOMM 1988

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

monte carlo simulation · 0.0w-method · 0.0u-method · 0.0t-method · 0.0d-method · 0.0
YearPublicationVenuePosition
1989 Formal Methods for Protocol Testing: A Detailed Study
abstract
The authors present a detailed study of four formal methods (T-, U-, D-, and W-methods) for generating test sequences for protocols. Applications of these methods to the NBS Class 4 Transport Protocol are discussed. An estimation of fault coverage of four protocol-test-sequence generation techniques using Monte Carlo simulation is also presented. The ability of a test sequence to decide whether a protocol implementation conforms to its specification heavily relies on the range of faults that it can capture. Conformance is defined at two levels, namely, weak and strong conformance. This study shows that a test sequence produced by T-method has a poor fault detection capability, whereas test sequences produced by U-, D-, and W-methods have comparable (superior to that for T-method) fault coverage on several classes of randomly generated machines used in this study. Also, some problems with a straightforward application of the four protocol-test-sequence generation methods to real-world communication protocols are pointed out.>
Deepinder P. Sidhu, Ting-Kau Leung
IEEE Trans. Software Eng.2
1988 Fault coverage of protocol test methods
abstract
The authors present an estimation of fault coverage of four protocol test sequences generation techniques (T-, U-, D-, and W-methods) using Monte Carlo simulation on a simple protocol machine. The ability of a test sequence to decide whether a protocol implementation conforms to its specification heavily relies upon the range of faults that it can capture. This study shows that a test sequence produced by T-method has a poor fault detection capability whereas test sequences produced by U-, D- and W-methods have fault coverage comparable to each other and superior to that for T-method on several classes of randomly generated machines used.>
Deepinder P. Sidhu, Ting-Kau Leung
INFOCOM2
1988 Experience with test generation for real protocols
abstract
This paper presents results on the application of four protocol test sequence generation techniques (T-, U-, D-, and W-methods) to the NBS Class 4 transport protocol (TP4). The ability of a test sequence to decide whether a protocol implementation conforms to its specification depend on the range of faults that it can capture. The study shows that a test sequence produced by the T-method has a poor fault detection capability whereas test sequences produced by the U-, D- and W-methods have comparable (superior to that for T-method) fault coverage on several classes of randomly generated machines. The lengths of test sequences produced by the four methods tend to be different. The length of a test sequence produced by the T-method (W-method) is the smallest (largest). The length of a test sequence from the U-method is smaller than that for the D-method and lengths for both are greater than that for the T-method and less than that for the W-method.
Deepinder P. Sidhu, Ting-Kau Leung
SIGCOMM2