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

Thomas J. McCabe

dblp:43/4196 · DBLP profile ↗
← Back
4ranked-venue papers
4as 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 · 4 · 4 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
3 papers
Software testing · 40% Empirical software engineering · 34% Requirements engineering and software design · 12%

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

TopicWeightPapersLastEvidence papers
Software testing
system testing
0.011985
System Testing Aided by Structured Analysis: A Practical Experience · IEEE Trans. Software Eng. 1985
Empirical software engineering › software metrics
software complexity metrics
0.021976
A Complexity Measure · IEEE Trans. Software Eng. 1976
A Complexity Measure (Abstract) · ICSE 1976
Program analysis
control flow analysis
0.011976
A Complexity Measure · IEEE Trans. Software Eng. 1976
Empirical software engineering
software metrics
0.011976
A Complexity Measure (Abstract) · ICSE 1976
Requirements engineering and software design › requirements analysis
structured analysis
0.011985
System Testing Aided by Structured Analysis: A Practical Experience · IEEE Trans. Software Eng. 1985
Software maintenance and evolution
program comprehension
0.011976
A Complexity Measure (Abstract) · ICSE 1976

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

data flow diagrams · 0.0graph theory · 0.0
YearPublicationVenuePosition
2000 Software Life Cycles for e-Commerce Businesses
Thomas J. McCabe
ICSM1
1985 System Testing Aided by Structured Analysis: A Practical Experience
abstract
This paper deals with the use of Structured Analysis just prior to system acceptance testing. Specifically, the drawing of data flow diagrams (DFD) was done after integration testing. The DFD's provided a picture of the logical flow through the integrated system for thorough system acceptance testing. System test sets, were derived from the flows in the DFD's. System test repeatability was enhanced by the matrix which flowed from the test sets.
Thomas J. McCabe, G. Gordon Schulmeyer
IEEE Trans. Software Eng.1
1976 A Complexity Measure (Abstract)
Thomas J. McCabe
ICSE1
1976 A Complexity Measure
abstract
This paper describes a graph-theoretic complexity measure and illustrates how it can be used to manage and control program complexity. The paper first explains how the graph-theory concepts apply and gives an intuitive explanation of the graph concepts in programming terms. The control graphs of several actual Fortran programs are then presented to illustrate the correlation between intuitive complexity and the graph-theoretic complexity. Several properties of the graph-theoretic complexity are then proved which show, for example, that complexity is independent of physical size (adding or subtracting functional statements leaves complexity unchanged) and complexity depends only on the decision structure of a program.
Thomas J. McCabe
IEEE Trans. Software Eng.1