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

Carl G. Davis

dblp:74/1383 · DBLP profile ↗
← Back
9ranked-venue papers
3as 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 · 7 · 3 first-authorArtificial intelligence and machine learning · 2Applied, 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
3 papers
Requirements engineering and software design · 44% Empirical software engineering · 42% Software maintenance and evolution · 14%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software design quality
design quality assessment
0.012002
A Hierarchical Model for Object-Oriented Design Quality Assessment · IEEE Trans. Software Eng. 2002
Empirical software engineering › software metrics
object-oriented design metrics
0.012002
A Hierarchical Model for Object-Oriented Design Quality Assessment · IEEE Trans. Software Eng. 2002
Software maintenance and evolution › software reuse
software reusability
0.012002
A Hierarchical Model for Object-Oriented Design Quality Assessment · IEEE Trans. Software Eng. 2002
Requirements engineering and software design
software design methodology
0.011977
The Software Development System · IEEE Trans. Software Eng. 1977

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

hierarchical quality model · 0.0
YearPublicationVenuePosition
2002 A Hierarchical Model for Object-Oriented Design Quality Assessment
abstract
The paper describes an improved hierarchical model for the assessment of high-level design quality attributes in object-oriented designs. In this model, structural and behavioral design properties of classes, objects, and their relationships are evaluated using a suite of object-oriented design metrics. This model relates design properties such as encapsulation, modularity, coupling, and cohesion to high-level quality attributes such as reusability, flexibility, and complexity using empirical and anecdotal information. The relationship or links from design properties to quality attributes are weighted in accordance with their influence and importance. The model is validated by using empirical and expert opinion to compare with the model results on several large commercial object-oriented systems. A key attribute of the model is that it can be easily modified to include different relationships and weights, thus providing a practical quality assessment tool adaptable to a variety of demands.
Jagdish Bansiya, Carl G. Davis
IEEE Trans. Software Eng.2
2001 Automated reusability quality analysis of OO legacy software
Letha H. Etzkorn, William E. Hughes Jr., Carl G. Davis
Inf. Softw. Technol.3
2000 An empirical study of object-oriented system evolution
Wei Li 0014, Letha H. Etzkorn, Carl G. Davis, John R. Talburt
Inf. Softw. Technol.3
1999 An approach to program understanding by natural language understanding
abstract
An automated tool to assist in the understanding of legacy code components can be useful both in the areas of software reuse and software maintenance. Most previous work in this area has concentrated on functionally-oriented code. Whereas object-oriented code has been shown to be inherently more reusable than functionally-oriented code, in many cases the eventual reuse of the object-oriented code was not considered during development. A knowledge-based, natural language processing approach to the automated understanding of object-oriented code as an aid to the reuse of object-oriented code is described. A system, called the PATRicia system (Program Analysis Tool for Reuse) that implements the approach is examined. The natural language processing/information extraction system that comprises a large part of the PATRicia system is discussed and the knowledge-base of the PATRicia system, in the form of conceptual graphs, is described. Reports provided by natural language-generation in the PATRicia system are described.
Letha H. Etzkorn, Lisa L. Bowen, Carl G. Davis
Nat. Lang. Eng.3
1996 A knowledge-based approach to object-oriented legacy code reuse
abstract
Software reuse has been demonstrated to increase productivity, reduce costs and improve software quality. Most research in the area of extraction of reusable code from legacy code has concentrated on code created in the functional decomposition paradigm. However, in recent years much object-oriented code has been written. This paper describes a knowledge-based approach to the identification of reusable components in object-oriented legacy code.
Letha H. Etzkorn, Carl G. Davis, Lisa L. Bowen, David B. Etzkorn, L. W. Lewis, Bradley L. Vinz, Janet C. Wolf
ICECCS2
1996 Automated object-oriented reusable component identification
Letha H. Etzkorn, Carl G. Davis
Knowl. Based Syst.2
1978 The software development system: Status and evolution
abstract
The Software Development System (SDS), a research program designed for the development of software for Ballistic Missile Defense software, is evolving toward increased capability in the areas of testing, quality assurance, and system-level definition. This paper discusses the evolution of SDS and plans for future development.
Carl G. Davis, Charles R. Vick
COMPSAC1
1977 The Software Development System
abstract
This paper contains a discussion of the Software Development System (SDS), a methodology addressing the problems involved in the development of software for ballistic missile defense systems. These are large real-time, automated systems with a requirement for high reliability. The SDS is a broad approach attacking problems arising in requirements generation, software design, coding, and testing. The approach is highly requirements oriented and has resulted in the formulation of structuring concepts, a requirements statement language, process design language, and support software to be used throughout the development cycle. This methodology represents a significant advance in software technology for the development of software for a class of systems such as BMD. The support software has been implemented and is undergoing evaluation.
Carl G. Davis, Charles R. Vick
IEEE Trans. Software Eng.1
1976 The Software Development System (Abstract)
Carl G. Davis, Charles R. Vick
ICSE1