David A. Nichols

No picture of David A. Nichols available - click to provide one

About the author:
No description available of David A. Nichols...
ADD DESCRIPTION
ADD PUBLICATION
SHARE YOUR RESEARCH

Publications by David A. Nichols (bibliography)

 what's this?

» 1998 «

Edit | Del

Twidale, Michael and Nichols, David A. (1998): Designing Interfaces to Support Collaboration in Information Retrieval. In Interacting with Computers, 10 (2) pp. 177-193

Information retrieval systems should acknowledge the existence of collaboration in the search process. Collaboration can help users to be more effective in both learning systems and in using them. We consider how to build systems that more actively support collaboration. We describe a system that embodies just one kind of explicit support; a graphical representation of the search process that can be manipulated and discussed by users. A consideration of this system leads to an analysis of designing systems to support coping behaviour by users; including the need to support both help-giving by people, and recovery from the failure of intelligent agents. We also discuss the idea of interfaces as notations for supporting dialogues between people.

Copyrights may apply

» 1995 «

Edit | Del

Nichols, David A., Curtis, Pavel, Dixon, Michael and Lamping, John (1995): High-Latency, Low-Bandwidth Windowing in the Jupiter Collaboration System. In: Robertson, George G. (ed.) Proceedings of the 8th annual ACM symposium on User interface and software technology November 15 - 17, 1995, Pittsburgh, Pennsylvania, United States. pp. 111-120. Available online

Jupiter is a multi-user, multimedia virtual world intended to support long-term remote collaboration. In particular, it supports shared documents, shared tools, and, optionally, live audio/video communication. Users who program can, with only moderate effort, create new kinds of shared tools using a high-level windowing toolkit; the toolkit provides transparent support for fully-shared widgets by default. This paper describes the low-level communications facilities used by the implementation of the toolkit to enable that support. The state of the Jupiter virtual world, including application code written by users, is stored and (for code) executed in a central server shared by all of the users. This architecture, along with our desire to support multiple client platforms and high-latency networks, led us to a design in which the server and clients communicate in terms of high-level widgets and user events. As in other groupware toolkits, we need a concurrency-control algorithm to maintain common values for all instances of the shared widgets. Our algorithm is derived from a fully distributed, optimistic algorithm developed by Ellis and Gibbs [12]. Jupiter's centralized architecture allows us to substantially simplify their algorithm. This combination of a centralized architecture and optimistic concurrency control gives us both easy serializability of concurrent update streams and fast response to user actions. The algorithm relies on operation transformations to fix up conflicting messages. The best transformations are not always obvious, though, and several conflicting concerns are involved in choosing them. We present our experience with choosing transformations for our widget set, which includes a text editor, a graphical drawing widget, and a number of simpler widgets such as buttons and sliders.

Copyrights may apply

Edit | Del

Curtis, Pavel, Dixon, Michael, Frederick, Ron and Nichols, David A. (1995): The Jupiter Audio/Video Architecture: Secure Multimedia in Network Places. In: ACM Multimedia 1995 1995. pp. 79-90. Available online

» 1992 «

Edit | Del

Goldberg, David, Nichols, David A., Oki, Brian M. and Terry, Douglas B. (1992): Using Collaborative Filtering to Weave an Information Tapestry. In Communications of the ACM, 35 (12) pp. 61-70

ADD PUBLICATION
SHOW THIS LIST ON YOUR HOMEPAGE

What do YOU think?

Give us your opinion! Do you have any comments/additions
that you would like other visitors to see?

 
comment You say: Mar 21st, 2010
#1
Be the first to add a thoughtful note to this page ! 

  will be spam-protected
 

 
How many?
=
e.g. "6"
 

Changes to this page (author)

11 Feb 2010: Enabled abstracts to be shown on David A. Nichols's author page.
17 Aug 2009: Author was edited
17 Jun 2009: Author was edited
28 Apr 2003: Added the author to the bibliography

Publication statistics

Publication period:1992-1998
Publication count:4
Number of co-authors:8



Productive colleagues

David A. Nichols's 3 most productive colleagues in number of publications:

Michael Twidale:15
John Lamping:7
Douglas B. Terry:6


Collaboration count

Number of publications with 3 favourite co-authors:

Pavel Curtis:2
Michael Dixon:2
Brian M. Oki:1

 

Other options

Learn more about David A. Nichols:
- Google Scholar
- ACM
- CSB

Mar 21

Software design is the act of determining the user's experience with a piece of software. It has nothing to do with how the code works inside, or how big or small the code is. The designer's task is to specify completely and unambiguously the user's whole experience.

-- David Liddle, From Bringing Design to Software, edited by Terry Winograd, 1996

  • Share this quote on... Bookmark and Share
  • Get more quotes

Eva Hornecker on Tangible Interaction

Eva Hornecker explains the evolving concept of Tangible Interaction.

Read Eva's insightful entry here..

Help us help you!

  • Spread the word: Bookmark and Share
  • Donate
  • Other ways to help
 

Page information

Page maintainer: The Editorial Team
How to cite/reference this page
URL: http://www.interaction-design.org/references/authors/david_a__nichols.html