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

Richard L. Wexelblat

dblp:08/3820 · DBLP profile ↗
← Back
6ranked-venue papers
4as first author
0since 2021 · last 1999
—ORCID · none

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

Software engineering, systems software and programming languages · 4 · 2 first-authorSystems, architecture and hardware · 1 · 1 first-authorDatabases, data management, data science and information retrieval · 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.

Software engineering, system software, and programming languages
2 papers
Programming languages and type systems · 100%
Human-computer interaction and pervasive computing
1 paper
Usability and user experience research · 100%
Interdisciplinary, comprehensive, and emerging computing
1 paper
Computing education · 100%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems
language design
0.011976
Maxims for Malfeasant Designers, or How to Design Languages to Make Programming as Difficult as Possible · ICSE 1976
Programming languages and type systems › programming paradigms › imperative languages
PL/I
0.011971
B71-l Problem Solving by Digital Computers with PL/I Programming · IEEE Trans. Computers 1971
YearPublicationVenuePosition
1999 Planning for information technology in a federated organization
Richard L. Wexelblat
Inf. Manag.1
1993 The role of policy in requirements definition
abstract
Three significant challenges facing the discipline of software engineering are understanding how software designers reason about policy, understanding how they define requirements based on this reasoning, and providing machine-based intelligent tools that support reasoning about policy. The authors are developing the concept of a policy workbench: knowledge-based tools that support reasoning about such properties of policies as consistency, completeness, and correctness, and the implications of policy for the behavior of a system. They discuss how such a workbench might help software designers reason about the relationships between policies and requirements.>
Edgar H. Sibley, Richard L. Wexelblat, James Bret Michael, Michael C. Tanner, David C. Littman
RE2
1982 A Test Data Synthesizer for Telephone Company Accounting Office Processing of Call Data
abstract
Abstract Testing a program designed to recognize several dozen kinds of anomalies in large volumes of input data requires test data with many combinations of the anomalies in the data stream. The large number of combinations of anomalies makes it impractical to generate test data manually. This paper describes a test data synthesizer designed to help verify the accuracy, capacity and correctness of such a program. The operation of the synthesizer is analogous to the Fourier synthesis of a periodic function. A sweep action permits test data with well known response to be combined in a methodical way to explore complicated interactions which are not well understood.
W. O. Covington Jr., Richard L. Wexelblat
Softw. Pract. Exp.2
1981 The Consequences of One's First Programming Language
abstract
Abstract After seeing many programs written in one language, but with the style and structure of another, I conducted an informal survey to determine whether this phenomenon was widespread and to determine how much a programmer's first programming language might be responsible. This paper discusses my observations, gives informal results of the survey and suggests the need for a more formal study.
Richard L. Wexelblat
Softw. Pract. Exp.1
1976 Maxims for Malfeasant Designers, or How to Design Languages to Make Programming as Difficult as Possible
Richard L. Wexelblat
ICSE1
1971 B71-l Problem Solving by Digital Computers with PL/I Programming
abstract
Mr. Vasonyi has written a book that contains something for everyone: the commercial programmer, the scientific programmer; the beginner and the experienced alike. Where then does the author fail? I found the exposition not unlike that of a cookbook—going from simple recipe to difficult recipe, giving each in detail but avoiding the general to emphasize the specific. When you have finished studying it, you may know all sorts of good recipes but that doesn't necessarily make you a chef.
Richard L. Wexelblat
IEEE Trans. Computers1