Lawrence Yelowitz

dblp:49/5705 · DBLP profile ↗
← Back
11ranked-venue papers
6as first author
0since 2021 · last 1984
—ORCID · none

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

Software engineering, systems software and programming languages · 4 · 1 first-authorHuman-computer interaction and ubiquitous computing · 2 · 2 first-authorTheory of computation · 2Systems, architecture and hardware · 1 · 1 first-authorSecurity and privacy · 1 · 1 first-authorDatabases, data management, data science and information retrieval · 1Applied, interdisciplinary, general and emerging computing · 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
6 papers
Program verification · 46% Requirements engineering and software design · 26% Programming languages and type systems · 20%
Theoretical computer science
3 papers
Algorithms and data structures · 39% Automated reasoning and model checking · 30% Computational complexity · 30%
Network and information security
1 paper
Systems and software security · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
formal specification
0.021984
Practical Experience with an Ada-Based Formal Specification/Language on a Large Project · S&P 1984
Observations of Fallibility in Applications of Modern Programming Methodologies · IEEE Trans. Software Eng. 1976
Program verification
security property verification
0.011984
Practical Experience with an Ada-Based Formal Specification/Language on a Large Project · S&P 1984
Program verification
correctness proof
0.021976
Observations of Fallibility in Applications of Modern Programming Methodologies · IEEE Trans. Software Eng. 1976
Control Structure Abstractions of the Backtracking Programming Technique · IEEE Trans. Software Eng. 1976
Algorithms and data structures › search algorithms
backtracking
0.021976
Control Structure Abstractions of the Backtracking Programming Technique · IEEE Trans. Software Eng. 1976
Control Structure Abstractions of the Backtracking Programming Technique (Abstract) · ICSE 1976
Programming languages and type systems › control structures
backtracking
0.011976
Control Structure Abstractions of the Backtracking Programming Technique (Abstract) · ICSE 1976
Programming languages and type systems
control flow
0.011976
Control Structure Abstractions of the Backtracking Programming Technique (Abstract) · ICSE 1976
Programming languages and type systems › control flow
control flow abstraction
0.011976
Control Structure Abstractions of the Backtracking Programming Technique · IEEE Trans. Software Eng. 1976
Computational complexity › proof complexity
resolution
0.011976
New Results and Techniques in Resolution Theory · IEEE Trans. Computers 1976
Automated reasoning and model checking
theorem proving
0.011976
New Results and Techniques in Resolution Theory · IEEE Trans. Computers 1976
Systems and software security
secure system design
0.011984
Practical Experience with an Ada-Based Formal Specification/Language on a Large Project · S&P 1984
Program analysis
control flow analysis
0.011975
Derivation of a Path-Connectivity Matrix for Tagged Flowcharts · J. ACM 1975

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

manual verification · 0.0formal specification · 0.0matrix notation · 0.0graph path enumeration · 0.0boolean matrix derivation · 0.0
YearPublicationVenuePosition
1984 Practical Experience with an Ada-Based Formal Specification/Language on a Large Project
abstract
Ford Aerospace is successfully using an Ada-based formal specification language on a large project to specify and manually verify security properties. This paper, and the associated panel presentation at the 1984 Symposium on Security and Privacy, deal with Customer requirements in the area of security, the use of "Ada Design Language Extensions" (ADLE) as the formal specification language, and the approach to demonstrating security properties.
Lawrence Yelowitz
S&P1
1979 Studies in Abstract/Concrete Mappings in Proving Algorithm Correctness
Arthur G. Duncan, Lawrence Yelowitz
ICALP2
1978 A project approach to structure and correctness in Pitt's second computer science course
abstract
The introduction of software methodological issues, including correctness and structure, into the undergraduate curriculum is aided by the availability of software projects which are not overwhelming, but nonetheless, are sufficiently complex to warrant a disciplined approach.
Lawrence Yelowitz
SIGCSE1
1978 Arthur G. Duncan: Data Structures and Program Correctness: Bridging the Gap
Lawrence Yelowitz
Comput. Lang.1
1976 Control Structure Abstractions of the Backtracking Programming Technique (Abstract)
Susan L. Gerhart, Lawrence Yelowitz
ICSE2
1976 New Results and Techniques in Resolution Theory
abstract
A concise matrix notation is introduced, leading to a very simple statement of the resolution principle of mechanical theorem proving in the propositional calculus. The refinements of general resolution can also be stated easily using this notation. In addition, the notation has lead to the development of three new techniques of theorem proving which are described and proved complete.
Lawrence Yelowitz, Abraham Kandel
IEEE Trans. Computers1
1976 Observations of Fallibility in Applications of Modern Programming Methodologies
abstract
Errors, inconsistencies, or confusing points are noted in a variety of published algorithms, many of which are being used as examples in formulating or teaching principles of such modern programming methodologies as formal specification, systematic construction, and correctness proving. Common properties of these points of contention are abstracted. These properties are then used to pinpoint possible causes of the errors and to formulate general guidelines which might help to avoid further errors. The common characteristic of mathematical rigor and reasoning in these examples is noted, leading to some discussion about fallibility in mathematics, and its relationship to fallibility in these programming methodologies. The overriding goal is to cast a more realistic perspective on the methodologies, particularly with respect to older methodologies, such as testing, and to provide constructive recommendations for their improvement.
Susan L. Gerhart, Lawrence Yelowitz
IEEE Trans. Software Eng.2
1976 Control Structure Abstractions of the Backtracking Programming Technique
abstract
Backtracking is a well-known technique for solving combinatorial problems. It is of interest to programming methodologists because 1) correctness of backtracking programs may be difficult to ascertain experimentally and 2) efficiency is often of paramount importance. This paper applies a programming methodology, which we call control structure abstraction, to the backtracking technique. The value of control structure abstraction in the context of correctness is that proofs of general properties of a class of programs with similar control structures are separated from proofs of specific properties of individual programs of the class. In the context of efficiency, it provides sufficient conditions for correctness of an initial program which may subsequently be improved for efficiency while preserving correctness.
Susan L. Gerhart, Lawrence Yelowitz
IEEE Trans. Software Eng.2
1976 An Efficient Algorithm for Constructing Hierarchical Graphs
abstract
An algorithm to delete redundant edges from a precedence graph is presented and proved correct. The algorithm is much more efficient than previous algorithms to perform the same task.
Lawrence Yelowitz
IEEE Trans. Syst. Man Cybern.1
1975 Loop Unravelling: A Practical Tool in Proving Program Correctness
Arthur G. Duncan, Lawrence Yelowitz
Inf. Process. Lett.2
1975 Derivation of a Path-Connectivity Matrix for Tagged Flowcharts
abstract
ABSTRXCT A procedure is given to derive a Boolean matrix M corresponding to a flowchart in which certain edges are dmtmgmshed as "tagged."For any pair of tagged edges z and 3, M(i, j) = 1 if and only if there is at least one flowchart path from * to 3 m which all of the mtermedmte edges are untagged Such a flowchart path is known as a "tagged path " Modifications to the procedure are then given that answer the related questions of determining the exact number of tagged paths as well as an explicit listing of these paths between two given edges.A computer representation is described which leads to efficmnt implementation of the procedure The flowcharts considered are budt only from IFTHENELSE, DOWHILE, and COMPOSITION control structures One of three possible edges from each DOWHILE is selected for tagging, in addmon, the unique input and output edge ~s tagged This procedure is useful in program certification systems, particularly mechanical systems, in which it is required to perform logical verifications over the set of all tagged paths
Lawrence Yelowitz
J. ACM1