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

Charlotte D. Mooers

dblp:297/2142 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1983
—ORCID · none

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

Human-computer interaction and ubiquitous 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.

Human-computer interaction and pervasive computing
1 paper
User interface design and tools · 61% Usability and user experience research · 30% Collaborative and social computing · 9%

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

TopicWeightPapersLastEvidence papers
User interface design and tools › interaction design
command language design
0.011983
Changes that users demanded in the human interface to the Hermes Message System · CHI 1983
User interface design and tools
user interface design
0.011983
Changes that users demanded in the human interface to the Hermes Message System · CHI 1983
Collaborative and social computing › computer-mediated communication
messaging
0.011983
Changes that users demanded in the human interface to the Hermes Message System · CHI 1983

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

user feedback analysis · 0.0design principles · 0.0
YearPublicationVenuePosition
1983 Changes that users demanded in the human interface to the Hermes Message System
abstract
The Hermes Message System has evolved in response to the needs and criticisms of users. This paper gives examples of some less than successful features, many of which have been changed, so that future designers will know what didn't work, as well as what does. Principles derived from this experience are: (a) What you see should be what you can type. (b) Commands and syntax should be uniform. (c) Commands and objects should be organized into groups. (d) Hierarchy is great for organizing things you know about but much less useful for finding things you don't know. Even with careful design, it is impossible to predict what users will dislike so it is important to design programs so they can be easily changed.
Charlotte D. Mooers
CHI1