Number of co-authors:18
Number of publications with 3 favourite co-authors:John Karat:1Susan B. Hornstein:1Richard L. Henneman:1
Andrew M. Cohill's 3 most productive colleagues in number of publications:John M. Carroll:209Mary Beth Rosson:142Susan M. Dray:51
For a list of all the ways technology has failed to improve the quality of life, please press three.
-- Alice Kahn
Read the fascinating history of Wearable Computing, told by its father, Steve Mann
Read Steve's chapter !
Andrew M. Cohill
Publications by Andrew M. Cohill (bibliography)
Carroll, John M., Rosson, Mary Beth, Cohill, Andrew M. and Schorger, John R. (1995): Building a History of the Blacksburg Electronic Village. In: Proceedings of DIS95: Designing Interactive Systems: Processes, Practices, Methods, & Techniques 1995. pp. 1-6.
We are developing a history of the Blacksburg Electronic Village community network; gathering a broad spectrum of materials from and about the development process. We are providing browsing and authoring access to these materials through a World-Wide Web-based information system. The system is at once both a tool for the technical work of developing design-history, and a highly democratic forum for evolving a community-history. We believe this project raises fundamental questions and possibilities regarding the concept of history itself.
© All rights reserved Carroll et al. and/or ACM Press
Dayton, Tom, Barr, Bob, Burke, Pamela A., Cohill, Andrew M., Day, Mary Carol, Dray, Susan M., Ehrlich, Kate, Fitzsimmons, Lynne Axel, Henneman, Richard L., Hornstein, Susan B., Karat, John and Kliger, Jill (1993): Skills Needed by User-Centered Design Practitioners in Real Software Development Environments: Report on the CHI'92 Workshop. In ACM SIGCHI Bulletin, 25 (3) pp. 16-31.
User-centered design (UCD) of human-computer interfaces-including task flow and documentation-is gaining acceptance in software development organizations. But managers who want their organizations to start using UCD often do not know what characteristics to look for, in candidates for hiring or retraining to fill UCD roles; this article can help. It has the recommendations from participants in a CHI '92 conference workshop on this topic. The 16 workshop participants were UCD practitioners and managers from companies and a few universities across the United States, Canada, and Sweden. This article first describes some typical roles of UCD practitioners in software development organizations. There follows a list of attributes that UCD practitioners should have. Some attributes should be had by all practitioners, regardless of their subspecialties. The most important of those universal attributes are of three types: knowledge that can be acquired formally (e.g., of the human-computer interaction literature, cognitive processes, experimental design, rapid prototyping), skill that can be gotten from experience (e.g., estimating resources needed to do a job, commitment to users, understanding of the software development process, negotiating ability, enjoyment of working on teams, ability to really listen), and attributes that are harder to acquire (e.g., tenacity, flexibility). Every practitioner needs other characteristics as well, but their importances differ by the practitioners' subspecialties (e.g., a design team leader needs team management skills).
© All rights reserved Dayton et al. and/or ACM Press
Cohill, Andrew M. (1992): Architects at Work: The Structure of Design Information. In: Proceedings of the Human Factors Society 36th Annual Meeting 1992. pp. 389-393.
Cohill, Andrew M. (1989): The Human Factors Design Process in Software Development. In: Proceedings of the Third International Conference on Human-Computer Interaction 1989. pp. 19-27.
Method and process are often confused in software development. This paper discusses the differences between the two, and why an emphasis on process is more likely to lead to systems that meet user needs and expectations. The root of the confusion lies in a mis-understanding of method and process. A model is presented that views system development as a design process that may include the use of several different methods, each chosen for the appropriateness of the task requirements. The ecology of the workplace is discussed as an appropriate way for human factors engineers to the environmental and behavioral effects of new systems on users. Finally, the concept of information architecture is presented as a new way of thinking about high-level system design.
© All rights reserved Cohill and/or Lawrence Erlbaum Associates
Cohill, Andrew M. (1987): Two Models of User Assistance. In: Proceedings of the Human Factors Society 31st Annual Meeting 1987. pp. 46-50.
This paper discusses two general models of user interaction in the context of user assistance (HELP) and their implications for design. Conceptual and quantitative models provide software engineers with tools that can aid them in the interface design process. The conceptual model presented is derived using a hermeneutic approach to the analysis of human-computer interaction. The interaction is modeled as a set of states and transitions between states. This suggests that user assistance should have a more central role in the design of the system. The quantitative model is derived from a study of the existing literature, and provides a framework for analyzing performance issues at the human-computer interface, using metrics like response time, keystrokes, error rates, and task completion rates. The model contains seven components, covering user characteristics, information type, structure, user knowledge, presentation, control, and access.
© All rights reserved Cohill and/or Human Factors Society
Cohill, Andrew M., Billingsley, Patricia, Williams, Evelyn, Gilmore, Walter and Williams, James (1987): Human Factors Society Human-Computer Interaction Standards Committee Draft Proposal Version 1.2. In: Proceedings of the Human Factors Society 31st Annual Meeting 1987. pp. 871-873.
The purpose of this reference model is to identify all topic areas that might be covered by guidelines or standards relating to the human-computer interface and to provide an organizational structure for those topics that will allow guidelines or standards to be developed in an incremental yet systematic fashion. By "human-computer interface" we mean those aspects of a computer system that both affect the user and have implications for software design. Our approach to the development of guidelines will be based on an attempt to determine those areas of the human interface which have sufficient importance and data available to merit an attempt to standardize.
© All rights reserved Cohill et al. and/or Human Factors Society
Show this list on your homepage
Join the technology elite and advance:
Changes to this page (author)21 Feb 2010: Modified28 Jun 2007: Added
26 Jun 2007: Added
25 Jun 2007: Added
25 Jun 2007: Added
24 Jun 2007: Added
22 Jun 2007: Added
Page maintainer: The Editorial Team