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

David M. Steier

dblp:88/4274 · DBLP profile ↗
← Back
9ranked-venue papers
5as first author
0since 2021 · last 2009
—ORCID · none

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

Artificial intelligence and machine learning · 6 · 4 first-authorDatabases, data management, data science and information retrieval · 3Graphics, computer vision, multimedia, augmented reality and games · 3 · 3 first-authorSoftware engineering, systems software and programming languages · 1 · 1 first-authorTheory of computation · 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.

Databases, data mining, and information retrieval
2 papers
Data mining · 80% Graph data management · 14% Web and social media mining · 4%
Software engineering, system software, and programming languages
2 papers
Program analysis · 33% Program synthesis and code generation · 33% Software testing · 33%

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

TopicWeightPapersLastEvidence papers
Data mining
anomaly detection
0.222009
SNARE: a link analytic system for graph labeling and risk detection · KDD 2009
Large Scale Detection of Irregularities in Accounting Data · ICDM 2006
Data mining › anomaly detection › fraud detection
collusion detection
0.112009
SNARE: a link analytic system for graph labeling and risk detection · KDD 2009
Data mining › anomaly detection
fraud detection
0.112009
SNARE: a link analytic system for graph labeling and risk detection · KDD 2009
Graph data management › graph indexing
graph labeling
0.112009
SNARE: a link analytic system for graph labeling and risk detection · KDD 2009
Data mining › structured data mining
graph mining
0.112009
SNARE: a link analytic system for graph labeling and risk detection · KDD 2009
Data mining › structured data mining › graph mining › graph learning
node classification
0.112009
SNARE: a link analytic system for graph labeling and risk detection · KDD 2009
Web and social media mining
social network analysis
0.012009
SNARE: a link analytic system for graph labeling and risk detection · KDD 2009
Data mining › predictive modeling
classification
0.012006
Large Scale Detection of Irregularities in Accounting Data · ICDM 2006
Machine learning and data management › weak supervision
positive-unlabeled learning
0.012006
Large Scale Detection of Irregularities in Accounting Data · ICDM 2006
Mathematical optimization
automated algorithm design
0.011988
Integrating Multiple Sources of Knowledge Into Designer Soar, an Automatic Algorithm Designer · AAAI 1988
Program analysis
symbolic execution
0.011985
Symbolic Execution in Algorithm Design · IJCAI 1985

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

link analysis · 0.1belief propagation · 0.1outlier detection · 0.1heterogeneous data integration · 0.1classification · 0.1execution and analysis of partial algorithms · 0.0developmental evaluation · 0.0
YearPublicationVenuePosition
2009 SNARE: a link analytic system for graph labeling and risk detection
abstract
Classifying nodes in networks is a task with a wide range of applications. It can be particularly useful in anomaly and fraud detection. Many resources are invested in the task of fraud detection due to the high cost of fraud, and being able to automatically detect potential fraud quickly and precisely allows human investigators to work more efficiently. Many data analytic schemes have been put into use; however, schemes that bolster link analysis prove promising. This work builds upon the belief propagation algorithm for use in detecting collusion and other fraud schemes. We propose an algorithm called SNARE (Social Network Analysis for Risk Evaluation). By allowing one to use domain knowledge as well as link knowledge, the method was very successful for pinpointing misstated accounts in our sample of general ledger data, with a significant improvement over the default heuristic in true positive rates, and a lift factor of up to 6.5 (more than twice that of the default heuristic). We also apply SNARE to the task of graph labeling in general on publicly-available datasets. We show that with only some information about the nodes themselves in a network, we get surprisingly high accuracy of labels. Not only is SNARE applicable in a wide variety of domains, but it is also robust to the choice of parameters and highly scalable-linearly with the number of edges in a graph.
Mary McGlohon, Stephen Bay, Markus G. Anderle, David M. Steier, Christos Faloutsos
KDD4
2006 Large Scale Detection of Irregularities in Accounting Data
abstract
In recent years, there have been several large accounting frauds where a company's financial results have been intentionally misrepresented by billions of dollars. In response, regulatory bodies have mandated that auditors perform analytics on detailed financial data with the intent of discovering such misstatements. For a large auditing firm, this may mean analyzing millions of records from thousands of clients. This paper proposes techniques for automatic analysis of company general ledgers on such a large scale, identifying irregularities - which may indicate fraud or just honest errors - for additional review by auditors. These techniques have been implemented in a prototype system, called Sherlock, which combines aspects of both outlier detection and classification. In developing Sherlock, we faced three major challenges: developing an efficient process for obtaining data from many heterogeneous sources, training classifiers with only positive and unlabeled examples, and presenting information to auditors in an easily interpretable manner. In this paper, we describe how we addressed these challenges over the past two years and report on experiments evaluating Sherlock.
Stephen Bay, Krishna Kumaraswamy, Markus G. Anderle, David M. Steier
ICDM5
1993 Intelligent control of external software systems
Allen Newell, David M. Steier
Artif. Intell. Eng.2
1993 Applying an Architecture for General Intelligence to Reduce Scheduling Effort
abstract
A system called Merle-Soar is described which demonstrates how a specific architecture for general intelligence and learning (Soar) can be used to reduce scheduling effort when solving simple scheduling problems. In particular, we describe how Merle-Soar schedules sequences of jobs on a single bottleneck machine in a job shop. The knowledge of dispatching, acquired from examining how a human expert performs the task, is cast as search rules. A study was conducted which examined the extent to which learning could contribute to decreases in scheduling effort; specifically, the contribution of learning within-tasks was explored—the change in reasoning effort while solving a particular scheduling problem as knowledge is accumulated from successive trials. The results indicated that dramatic reductions in scheduling effort (in terms of the Soar architecture) were obtained. Knowledge gained early in the scheduling task was subsequently applied later in the task to reduce deliberation, and knowledge gained from one trial successfully reduced deliberation effort in subsequent trials. Additionally, the reduction exhibited the general power law of learning documented in psychological studies of skill acquisition. INFORMS Journal on Computing, ISSN 1091-9856, was published as ORSA Journal on Computing from 1989 to 1995 under ISSN 0899-1499.
Michael J. Prietula, Wen Ling Hsu, David M. Steier, Allen Newell
INFORMS J. Comput.3
1992 A Strategy for Research Model Formulation
abstract
The starting point for this commentary is Sacks’ and Doyle's conclusion that a central problem for qualitative physics is automating mathematical model formulation. We believe that model formulation is also a central problem for operations research, and although we have focused on models for production planning rather than for engineering systems analysis, our experience confirms that of Sacks and Doyle, that at least parts of model formulation are amenable to automation. In terms of their recommendations for future research, their strategy seems to emphasize the formalization of mathematical knowledge. We wish to stress that understanding the design or analysis context, the problem domain, and resource constraints on the modeling process is equally important. Methods used in cognitive psychology for understanding human problem solving, such as protocol analysis, can complement mathematical study by helping us understanding the processing that human modelers use to bring mathematical knowledge to bear. We have been using the results of such analyses to guide the creation of a model formulation system (MFS) within the Soar architecture. The use of cognitive studies and computer models in tandem seems to represent a viable strategy for making progress in this area.
David M. Steier
Comput. Intell.1
1988 Integrating Multiple Sources of Knowledge Into Designer Soar, an Automatic Algorithm Designer
David M. Steier, Allen Newell
AAAI1
1987 CYPRESS-Soar: A Case Study in Search and Learning in Algorithm Design
David M. Steier
IJCAI1
1985 Symbolic Execution in Algorithm Design
David M. Steier, Elaine Kant
IJCAI1
1985 The Roles of Execution and Analysis in Algorithm Design
abstract
The analysis and execution of partial algorithm descriptions is an important part of the algorithm design process (as is borne out by studying the behavior of human algorithm designers). In this paper, we describe a language for representing partially designed algorithms and a process, developmental evaluation, that can discover useful knowledge to guide design. Using these and other results from our research in artificial intelligence, we are building a system, DESIGNER, that automatically designs algorithms. This paper also compares developmental evaluation to execution and analysis techniques used for testing complete programs and for validation of abstract specifications; concepts similar to those found in developmental evaluation are thus shown to apply to all stages of the software life cycle.
David M. Steier, Elaine Kant
IEEE Trans. Software Eng.1