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

Leonard L. Tripp

dblp:57/4816 · DBLP profile ↗
← Back
6ranked-venue papers
1as first author
0since 2021 · last 2002
—ORCID · none

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

Software engineering, systems software and programming languages · 3Human-computer interaction and ubiquitous computing · 2 · 1 first-authorSystems, architecture and hardware · 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.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
requirements verification
0.011978
Requirements Expression and Verification Aid · ICSE 1978
YearPublicationVenuePosition
2002 Fundamental principles of software engineering - a journey
Pierre Bourque, Robert Dupuis, Alain Abran, James W. Moore, Leonard L. Tripp, Sybille Wolff
J. Syst. Softw.5
2000 Software Engineering - Coming of Age or Reaching Too Far? (panel)
abstract
Some say there is an emerging consensus among us about what a good software development process is, and for that reason we are on the brink of being able to declare ourselves a mature field. In this presentation, I will critically examine the claims and assumptions behind that notion. I will try to show that the emerging consensus is an illusion caused by systematically excluding different ideas. What we need to do is better define and acknowledge the various sub-communities of software engineering, identify the major competing paradigms of software engineering, and find ways to constructively engage each other in real discussion and exchanges of experience. I will offer an example of at least one forum that is doing just that.
Dennis J. Frailey, James Bach, Dave Dorchester, B. Carroll, Leonard L. Tripp
CSEE&T5
1999 Professionalization of Software Engineering: Next Steps
Leonard L. Tripp
CSEE&T1
1980 A tool to support design automation in batch manufacturing
abstract
The development of integrated computer-aided manufacturing systems demands that the generic functions and common information be identified and classified. This paper presents an automated approach for modeling the functional aspect of an integrated manufacturing system. The approach is called IDEF0 and is being used by the Air Force ICAM program for all system development. The rationale, design approach and implementation of the automated tool AUTOIDEF0, which supports the use of IDEF0, is presented.
Gregory L. Smith, Sharon A. Stephens, Leonard L. Tripp, Wayne L. Warren
DAC3
1978 A Model of Software Engineering
Lawrence J. Peters, Leonard L. Tripp
ICSE2
1978 Requirements Expression and Verification Aid
Sharon A. Stephens, Leonard L. Tripp
ICSE2