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

Deborah A. Boehm-Davis

dblp:02/2659 · DBLP profile ↗
← Back
8ranked-venue papers
4as first author
0since 2021 · last 1995
0000-0002-7731-9963ORCID · reported

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

Human-computer interaction and ubiquitous computing · 7 · 4 first-authorSoftware engineering, systems software and programming languages · 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
4 papers
Requirements engineering and software design · 59% Software maintenance and evolution · 28% Empirical software engineering · 7%
Human-computer interaction and pervasive computing
1 paper
User interface design and tools · 77% Usability and user experience research · 23%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
program comprehension
0.011992
The Role of Program Structure in Software Maintenance · Int. J. Man Mach. Stud. 1992
Requirements engineering and software design › design process
program design
0.011992
Program Design Methodologies and the Software Development Process · Int. J. Man Mach. Stud. 1992
Requirements engineering and software design
software design methodology
0.011992
Program Design Methodologies and the Software Development Process · Int. J. Man Mach. Stud. 1992
User interface design and tools
documentation design
0.011986
The effects of structured, multi-level documentation · CHI 1986
Software maintenance and evolution
software documentation
0.011983
Documentation of concurrent programs · CHI 1983
Requirements engineering and software design › software design representation
design documentation
0.011987
Program Design Languages: How Much Detail Should They Include? · Int. J. Man Mach. Stud. 1987

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

empirical study · 0.0survey · 0.0comparative analysis · 0.0controlled experiment · 0.0
YearPublicationVenuePosition
1995 The effects of mice and pull-down menus versus command-driven interfaces on writing
abstract
The effects of two different computer user interfaces on the process of writing are examined. English composition students (matched on computer experience) used a computer and keyboard (either with function keys or with a mouse) to write essays during their English classes. Essays generated using either a mouse or command‐driven interface were compared across different stages of writing. The impact of using a mouse versus command‐driven interface is described by analyzing the differences in the process used to create the essays and the quality of the essays produced by each group. Results indicate that students who used the command‐driven interface scored better on organization of the paper, creativity, number of supporting arguments, grammar/spelling, and letter grade than did their mouse counterparts, as perceived by graders. However, there were no significant differences between the two interface conditions on any grammatical indices.
Karen R. Mahach, Deborah A. Boehm-Davis, Robert W. Holt
Int. J. Hum. Comput. Interact.2
1993 User interface development processes and methodologies
abstract
Abstract
H. Rex Hartson, Deborah A. Boehm-Davis
Behav. Inf. Technol.2
1992 The Role of Program Structure in Software Maintenance
Deborah A. Boehm-Davis, Robert W. Holt, Alan C. Schultz
Int. J. Man Mach. Stud.1
1992 Program Design Methodologies and the Software Development Process
Deborah A. Boehm-Davis, Lyle S. Ross
Int. J. Man Mach. Stud.1
1989 Experimental evaluation of software documentation formats
Bill Curtis, Sylvia B. Sheppard, Elizabeth Kruesi-Bailey, John W. Bailey, Deborah A. Boehm-Davis
J. Syst. Softw.5
1987 Program Design Languages: How Much Detail Should They Include?
Deborah A. Boehm-Davis, Sylvia B. Sheppard, John W. Bailey
Int. J. Man Mach. Stud.1
1986 The effects of structured, multi-level documentation
Robert W. Holt, Deborah A. Boehm-Davis, Alan C. Schultz
CHI2
1983 Documentation of concurrent programs
abstract
A complete software package always includes documentation. Although its importance is often overlooked, documentation may be the only source of program design information. Major tasks in the software life cycle, such as design, coding, testing and maintenance, are often performed by different individuals. Lientz and Swanson (1979) found that, typically, only about half of a software system's maintenance personnel had been involved in its development. Poor documentation techniques can, therefore, dramatically increase labor costs throughout the labor intensive software life cycle by making both development and maintenance tasks more difficult.
Deborah A. Boehm-Davis, Andrew M. Fregly
CHI1