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

David T. Shewmake

dblp:01/6586 · DBLP profile ↗
← Back
3ranked-venue papers
0as first author
0since 2021 · last 1988
—ORCID · none

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

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

Human-computer interaction and pervasive computing
1 paper
User interface design and tools · 100%
Software engineering, system software, and programming languages
3 papers
Software maintenance and evolution · 30% Software testing · 23% Empirical software engineering · 23%

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

TopicWeightPapersLastEvidence papers
User interface design and tools › user interface architecture
user interface management system
0.011988
UIMSs: threat or menace? · CHI 1988
Software maintenance and evolution
software reuse
0.011988
UIMSs: threat or menace? · CHI 1988
Empirical software engineering › software analytics
logging analysis
0.011986
Building Reliable Interactive Information Systems · IEEE Trans. Software Eng. 1986
Software testing
system testing
0.011986
Building Reliable Interactive Information Systems · IEEE Trans. Software Eng. 1986
Requirements engineering and software design › requirements elicitation
user participation
0.011986
Developing Interactive Information Systems with the User Software Engineering Methodology · IEEE Trans. Software Eng. 1986

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

state transition diagram · 0.0prototyping · 0.0precondition-postcondition · 0.0graphical tools · 0.0formal specification · 0.0
YearPublicationVenuePosition
1988 UIMSs: threat or menace?
abstract
Article Free Access Share on UIMSs: threat or menace? Authors: J. Rosenberg Hewlett-Packard Laboratories Hewlett-Packard LaboratoriesView Profile , R. Hill European Computer-Industry Research Center European Computer-Industry Research CenterView Profile , J. Miller Microelectronics and Computer Technology Corporation Microelectronics and Computer Technology CorporationView Profile , A. Schulert Apollo Computer Apollo ComputerView Profile , D. Shewmake Interactive Development Environments Interactive Development EnvironmentsView Profile Authors Info & Claims CHI '88: Proceedings of the SIGCHI Conference on Human Factors in Computing SystemsMay 1988 Pages 197–200https://doi.org/10.1145/57167.57200Online:01 May 1988Publication History 13citation212DownloadsMetricsTotal Citations13Total Downloads212Last 12 Months5Last 6 weeks1 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF
Jarrett Rosenberg, Ralph D. Hill, Jim Miller, Andrew Schulert, David T. Shewmake
CHI5
1986 Building Reliable Interactive Information Systems
abstract
User software engineering (USE) is a methodology, with supporting tools, for the specification, design, and implementation of interactive information systems. With the USE approach, the user interface is formally specified with augmented state transition diagrams, and the operations may be formally specified with preconditions and postconditions. The USE state transition diagrams may be directly executed with the application development tool RAPID/USE. RAPID/USE and its associated tool RAPSUM create and analyze logging information that is useful for system testing, and for evaluation and modification of the user interface. The authors briefly describe the USE transition diagrams and the formal specification approach, and show how these tools and techniques aid in the creation of reliable interactive information systems.
Anthony I. Wasserman, Peter A. Pircher, David T. Shewmake
IEEE Trans. Software Eng.3
1986 Developing Interactive Information Systems with the User Software Engineering Methodology
abstract
User software engineering (USE) is a methodology, supported by automated tools, for the systematic development of interactive information systems. The USE methodology gives particular attention to effective user involvement in the early stages of the software development process, concentrating on external design and the use of rapidly created and modified prototypes of the user interface. The USE methodology is supported by an integrated set of graphically based tools. The USE methodology and the tools that support it are described.
Anthony I. Wasserman, Peter A. Pircher, David T. Shewmake, Martin L. Kersten
IEEE Trans. Software Eng.3