David F. Redmiles
Has also published under the name of:
"D. F. Redmiles", "David Redmiles", and "D. Redmiles"
About the author:
No description available of David F. Redmiles...
Publications by David F. Redmiles (bibliography)
» 2009 «
Shih, Patrick C., Nguyen, David H., Hirano, Sen H., Redmiles, David F. and Hayes, Gillian R. (2009): GroupMind: supporting idea generation through a collaborative mind-mapping tool. In: GROUP09 - International Conference on Supporting Group Work 2009. pp. 139-148. Available online
“Collaborative brainstorming can be a challenging but important part of creative group problem solving. Mind-mapping has the potential to enhance the brainstorming process but has its own challenges when used in a group. We introduce GroupMind, a collaborative mind-mapping tool that addresses these challenges and opens new opportunities for creative teamwork, including brainstorming. We present a semi-controlled evaluation of GroupMind and its impact on teamwork, problem solving and collaboration for brainstorming activities. GroupMind performs better than using a traditional whiteboard in both interaction group and nominal group settings for the task involving memory recall. The hierarchical mind-map structure also imposes important framing effects on group dynamics and idea organization during the brainstorming process. We also present design ideas to assist in the development of future tools to support creative problem solving in groups.”
Copyrights may apply
Wilensky, Hiroko N., Redmiles, David F. and Su, Norman Makoto (2009): The dissemination of knowledge management. In: GROUP09 - International Conference on Supporting Group Work 2009. pp. 199-208. Available online
“Our study on a community of knowledge management (KM) practitioners in the aerospace industry reveals challenges in the dissemination of KM concepts and tools. In this paper, we identify four reasons: (1) disparity of the community's stated purpose and the actual motives of its members; (2) multidisciplinary nature of KM; (3) unique characteristics of the aerospace industry and its engineering culture and (4) adoption of preferred or recommended solutions provided by chosen reference groups rather than a grounded approach. In particular, we address the issues in promoting recommended ideas and tools by chosen reference groups in work organizations without fully understanding work practices.”
Copyrights may apply
» 2008 «
Trainer, Erik, Quirk, Stephen, Souza, Cleidson R. B. de and Redmiles, David F. (2008): Analyzing a socio-technical visualization tool using usability inspection methods. In: VL-HCC 2008 - IEEE Symposium on Visual Languages and Human-Centric Computing 15-19 September, 2008, Herrsching am Ammersee, Germany. pp. 78-81. Available online
» 2007 «
Souza, Cleidson R. de, Quirk, Stephen, Trainer, Erik and Redmiles, David F. (2007): Supporting collaborative software development through the visualization of socio-technical dependencies. In: GROUP07: International Conference on Supporting Group Work 2007. pp. 147-156. Available online
“One of the reasons large-scale software development is difficult is the number of dependencies that software engineers face. These dependencies create a need for communication and coordination that requires continuous effort by developers. Empirical studies, including our own, suggest that technical dependencies among software components create social dependencies among the software developers implementing those components. Based on this observation, we developed Ariadne, a plug-in for Eclipse. Ariadne analyzes software projects for dependencies and collects authorship information about projects relying on configuration management repositories. Ariadne can "translate" technical dependencies among components into social dependencies among developers. We have created visualizations to convey dependency information and the presence of coordination problems identified in our previous work. We believe the information conveyed in the visualizations will prove useful for software developers.”
Copyrights may apply
Su, Norman Makoto, Wilensky, Hiroko, Redmiles, David F. and Mark, Gloria (2007): The gospel of knowledge management in and out of a professional community. In: GROUP07: International Conference on Supporting Group Work 2007. pp. 197-206. Available online
“Knowledge management (KM) remains an anomaly in most corporations today. Critics call KM a fad of the 1990s, whereas supporters claim KM is actively evolving. Our work examines the disciplinary rhetoric of KM: how is it that practitioners of KM seek to legitimize their field in the corporate world? We focus on practitioners in the aerospace industry and their forum. We argue that this forum serves as a hub for constructing KM's legitimacy. Our two year ethnography traces the rhetorical strategies utilized by informants in and out of a professional community to legitimize KM as discipline in the aerospace industry.”
Copyrights may apply
Sarma, Anita, Hoek, André van der and Redmiles, David F. (2007): A Comprehensive Evaluation of Workspace Awareness in Software Configuration Management Systems. In: VL-HCC 2007 - IEEE Symposium on Visual Languages and Human-Centric Computing 23-27 September, 2007, Coeur dAlene, Idaho, USA. pp. 23-26. Available online
» 2006 «
Rode, Jennifer Ann, Johansson, Carolina, DiGioia, Paul, Filho, Roberto Silva, Nies, Kari, Nguyen, David H., Ren, Jie, Dourish, Paul and Redmiles, David F. (2006): Seeing further: extending visualization as a basis for usable security. In: Proceedings of the 2006 Symposium on Usable Privacy and Security 2006. pp. 145-155. Available online
“The focus of our approach to the usability considerations of privacy and security has been on providing people with information they can use to understand the implications of their interactions with a system, as well as, to assess whether or not a system is secure enough for their immediate needs. To this end, we have been exploring two design principles for secure interaction: visualizing system activity and integrating configuration and action. Here we discuss the results of a user study designed as a broad formative examination of the successes and failures of an initial prototype based around these principles. Our response to the results of this study has been twofold. First, we have fixed a number of implementation and usability problems. Second, we have extended our visualizations to incorporate new considerations regarding the temporal and structural organization of interactions.”
Copyrights may apply
» 2005 «
Redmiles, David F., Wilensky, Hiroko, Kosaka, Kristie and Paula, Rogerio de (2005): What ideal end users teach us about collaborative software. In: GROUP05: International Conference on Supporting Group Work November 6-9, 2005, Sanibel Island, Florida, USA. pp. 260-263. Available online
“Many studies have evaluated different uses of collaborative software. Typically, the research has focused on the shortcomings and, sometimes, the ways end users succeed or fail to work around these shortcomings. In a recent field study, surprisingly, a group demonstrated unimpaired dexterity using a full range of collaborative software. Some interesting lessons emerged from observing these \"perfect\" collaborators. Lessons include implications for more typical or \"less than perfect\" end users, especially around the adoption of collaboration technology. Also, there is a general, but subtle, lesson that studying successful users of technology (or \"ideal end users\" as we put it) can be as valuable as studying those who struggle with technology and highlight its shortcomings.”
Copyrights may apply
Paula, Rogerio de, Ding, Xianghua, Dourish, Paul, Nies, Kari, Pillet, Ben, Redmiles, David F., Ren, Jie, Rode, Jennifer Ann and Filho, Roberto Silva (2005): In the eye of the beholder: A visualization-based approach to information system security. In International Journal of Human-Computer Studies, 63 (1) pp. 5-24
“Computer system security is traditionally regarded as a primarily technological concern; the fundamental questions to which security researchers address themselves are those of the mathematical guarantees that can be made for the performance of various communication and computational challenges. However, in our research, we focus on a different question. For us, the fundamental security question is one that end-users routinely encounter and resolve for themselves many times a day -- the question of whether a system is secure enough for their immediate needs. In this paper, we will describe our explorations of this issue. In particular, we will draw on three major elements of our research to date. The first is empirical investigation into everyday security practices, looking at how people manage security as a practical, day-to-day concern, and exploring the context in which security decisions are made. This empirical work provides a foundation for our reconsideration of the problems of security to a large degree as an interactional problem. The second is our systems approach, based on visualization and event-based architectures. This technical approach provides a broad platform for investigating security and interaction, based on a set of general principles. The third is our initial experiences in a prototype deployment of these mechanisms in an application for peer-to-peer file sharing in face-to-face collaborative settings. We have been using this application as the basis of an initial evaluation of our technology in support of everyday security practices in collaborative workgroups.”
Copyrights may apply
Paula, Rogerio de, Ding, Xianghua, Dourish, Paul, Nies, Kari, Pillet, Ben, Redmiles, David F., Ren, Jie, Rode, Jennifer Ann and Filho, Roberto Silva (2005): Two experiences designing for effective security. In: Proceedings of the 2005 Symposium on Usable Privacy and Security 2005. pp. 25-34. Available online
“In our research, we have been concerned with the question of how to make relevant features of security situations visible to users in order to allow them to make informed decisions regarding potential privacy and security problems, as well as regarding potential implications of their actions. To this end, we have designed technical infrastructures that make visible the configurations, activities, and implications of available security mechanisms. This thus allows users to make informed choices and take coordinated and appropriate actions when necessary. This work differs from the more traditional security usability work in that our focus is not only on the usability of security mechanism (e.g., the ease-of-use of an access control interface), but how security can manifest itself as part of people's interactions with and through information systems (i.e., how people experience and interpret privacy and security situations, and are enabled or constrained by existing technological mechanisms to act appropriately). In this paper, we report our experiences designing, developing, and testing two technical infrastructures for supporting this approach for usable security.”
Copyrights may apply
» 2004 «
Souza, Cleidson R. B. de, Redmiles, David F., Cheng, Li-Te, Millen, David and Patterson, John F. (2004): Sometimes you need to see through walls: a field study of application programming interfaces. In: Proceedings of ACM CSCW04 Conference on Computer-Supported Cooperative Work 2004. pp. 63-71. Available online
“Information hiding is one of the most important and influential principles in software engineering. It prescribes that software modules hide implementation details from other modules in order to decrease the dependency between them. This separation also decreases the dependency among software developers implementing modules, thus simplifying some aspects of collaboration. A common instantiation of this principle is in the form of application programming interfaces (APIs). We performed a field study of the use of APIs and observed that they served many roles. We observed that APIs were successful indeed in supporting collaboration by serving as contracts among stakeholders as well as by reifying organizational boundaries. However, the separation that they accomplished also hindered other forms of collaboration, particularly among members of different teams. Therefore, we think argue that API's do not only have beneficial purposes. Based on our results, we discuss implications for collaborative software development tools.”
Copyrights may apply
» 2003 «
Souza, Cleidson R. B. de, Redmiles, David F. and Dourish, Paul (2003): "Breaking the code", moving between private and public work in collaborative software development. In: Tremaine, Marilyn and Simone, Carla (eds.) Proceedings of the International ACM SIGGROUP Conference on Supporting Group Work 2003 November 9-12, 2003, Sanibel Island, Florida, USA. pp. 105-114. Available online
“Software development is typically cooperative endeavor where a group of engineers need to work together to achieve a common, coordinated result. As a cooperative effort, it is especially difficult because of the many interdependencies amongst the artifacts created during the process. This has lead software engineers to create tools, such as configuration management tools, that isolate developers from the effects of each other's work. In so doing, these tools create a distinction between private and public aspects of work of the developer. Technical support is provided to these aspects as well as for transitions between them. However, we present empirical material collected from a software development team that suggests that the transition from private to public work needs to be more carefully handled. Indeed, the analysis of our material suggests that different formal and informal work practices are adopted by the developers to allow a delicate transition, where software developers are not largely affected by the emergent public work. Finally, we discuss how groupware tools might support this transition.”
Copyrights may apply
Souza, Cleidson R. B. de, Redmiles, David F., Mark, Gloria, Penix, John and Sierhuis, Maarten (2003): Management of Interdependencies in Collaborative Software Development. In: ISESE 2003 - International Symposium on Empirical Software Engineering 30 September - 1 October, 2003, Rome, Italy. pp. 294-303. Available online
» 2002 «
Redmiles, David F. (2002): Introduction to the Special Issue on Activity Theory and the Practice of Design. In Computer Supported Cooperative Work, 11 (1) pp. 1-11
Collins, Patricia, Shukla, Shilpa and Redmiles, David F. (2002): Activity Theory and System Design: A View from the Trenches. In Computer Supported Cooperative Work, 11 (1) pp. 55-80
“An activity theory model and a mediating artifacts hierarchy were employed to help identify the needs for tools for customer support engineers who documented solutions to customer problems, a knowledge authoring activity. This activity also involves customer support engineers who assist Hewlett-Packard software product users. The particular tools to be designed were knowledge-authoring tools embedded in the customer support tracking application suite, SupportTracker. The research analyzed the role of tensions between the elements of Engestrom's activity theory model. The research also explored the benefits of specific interpretations of Engestrom's refinement of Wartofsky's mediating artifacts hierarchy. The hierarchy contributed to the identification of desired characteristics of mediating artifacts, particularly tools. The findings included an interpretation of the ''where-to'' artifact concept as supporting an understanding of the entire activity system as an evolving entity. Specific interventions were used to achieve a positive impact on the evolution of the activity system.”
Copyrights may apply
» 2001 «
Kantor, M. and Redmiles, David F. (2001): Creating an Infrastructure for Ubiquitous Awareness. In: Proceedings of IFIP INTERACT01: Human-Computer Interaction 2001, Tokyo, Japan. pp. 431-438.
Hilbert, D. M. and Redmiles, David F. (2001): Large-Scale Collection of Usage Data to Inform Design. In: Proceedings of IFIP INTERACT01: Human-Computer Interaction 2001, Tokyo, Japan. pp. 569-576.
» 1998 «
Hilbert, David M., Robbins, Jason E. and Redmiles, David F. (1998): EDEM: Intelligent Agents for Collecting Usage Data and Increasing User Involvement in Development. In: Marks, Joe (ed.) International Conference on Intelligent User Interfaces 1998 January 6-9, 1998, San Francisco, California, USA. pp. 73-76. Available online
“Expectation-Driven Event Monitoring (EDEM) provides developers with a platform for creating software agents to collect usage data and increase user involvement in the development of interactive systems. EDEM collects information that is currently lost regarding actual usage of applications to promote improved usability and a more empirically grounded design process.”
Copyrights may apply
Robbins, Jason E., Hilbert, David M. and Redmiles, David F. (1998): Software Architecture Critics in Argo. In: Marks, Joe (ed.) International Conference on Intelligent User Interfaces 1998 January 6-9, 1998, San Francisco, California, USA. pp. 141-144. Available online
“Software architectures are high-level design representations of software systems that focus on composition of software components and how those components interact. Software architectures abstract the details of implementation and allow the designer to focus on essential design decisions. Regardless of notation, designers are faced with the task of making good design decisions, which demands a wide range of knowledge of the problem and solution domains. Argo is a software architecture design environment that supports designers by addressing several cognitive challenges of design. In this paper we describe how Argo supports decision making by automatically supplying knowledge that is timely and relevant to decisions at hand.”
Copyrights may apply
» 1996 «
Robbins, Jason E., Morley, David J., Redmiles, David F., Filatov, Vadim and Kononov, Dima (1996): Visual Language Features Supporting Human-Human and Human-Computer Communication. In: VL 1996 1996. pp. 247-254.
» 1995 «
Fischer, Gerhard, Redmiles, David F., Williams, Lloyd, Puhr, Gretchen I., Aoki, Atsushi and Nakakoji, Kumiyo (1995): Beyond Object-Oriented Technology: Where Current Approaches Fall Short. In Human-Computer Interaction, 10 (1) pp. 79-119
“Object-oriented (OO) technology has been heralded as a solution to the problems of software engineering. The claims are that OO technology promotes understandability, extensibility, evolvability, reusability, and maintainability of systems and that OO systems are easy to understand and use. However, this technology has not been as successful as expected. An analysis of experiences and empirical studies reveals that the problem is not the technology per se but that the technology provides no support to software developers in performing the processes the technology requires. We present a cognitive model of software development that details the challenges software developers face in using OO technology. The model focuses on three aspects of software development -- evolution, reuse and redesign, and domain orientation. We motivate this model with a variety of firsthand experiences and use it to assess current OO technology. Further, we present tools and evaluations that substantiate parts of this model. The model and tools indicate directions for future software development environments, looking beyond the technological possibilities of OO languages and beyond the context of individual developers and projects.”
Copyrights may apply
» 1993 «
Redmiles, David F. (1993): Reducing the Variability of Programmers' Performance Through Explained Examples. In: Ashlund, Stacey, Mullet, Kevin, Henderson, Austin, Hollnagel, Erik and White, Ted (eds.) Proceedings of the ACM CHI 93 Human Factors in Computing Systems Conference April 24-29, 1993, Amsterdam, The Netherlands. pp. 67-73. Available online
“A software tool called EXPLAINER has been developed for helping programmers perform new tasks by exploring previously worked-out examples. EXPLAINER is based on cognitive principles of learning from examples and problem solving by analogy. The interface is based on the principle of making examples accessible through multiple presentation views and multiple representation perspectives. Empirical evaluation has shown that programmers using EXPLAINER exhibit less variability in their performance compared to programmers using a commercially available, searchable on-line manual. These results are related to other studies of programmers and to current methodologies in software engineering.”
Copyrights may apply
» 1991 «
Fischer, Gerhard, Henninger, Scott and Redmiles, David F. (1991): Intertwining Query Construction and Relevance Evaluation. In: Robertson, Scott P., Olson, Gary M. and Olson, Judith S. (eds.) Proceedings of the ACM CHI 91 Human Factors in Computing Systems Conference April 28 - June 5, 1991, New Orleans, Louisiana. pp. 55-62. Available online
“Traditional information access systems generally assume that a well-articulated query exists, and that once an object is found, it can be readily understood. Although this assumption works for retrieving text objects, in more complex domains, such as retrieving software objects for reuse, queries must be incrementally constructed and support is needed for comprehending what is retrieved. Therefore, information access methods need support for query construction and relevance evaluation as an integral part of the location process. Two prototype systems are described for supporting this need: CODEFINDER for query construction and EXPLAINER for explanations of program examples. These systems interact to support the processes of locating and comprehending software objects for reuse.”
Copyrights may apply
Redmiles, David F. (1991): Supporting Software Reuse through Examples. In: Robertson, Scott P., Olson, Gary M. and Olson, Judith S. (eds.) Proceedings of the ACM CHI 91 Human Factors in Computing Systems Conference April 28 - June 5, 1991, New Orleans, Louisiana. p. 492. Available online
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?
You say:
Mar 16th, 2010
Changes to this page (author)
14 Feb 2010: Enabled abstracts to be shown on David F. Redmiles's author page.16 Jun 2009: Author was edited 16 Jun 2009: Author was edited
16 Jun 2009: Author was edited
03 Jun 2009: Author was edited
02 Jun 2009: Author was edited
02 Jun 2009: Author was edited
12 May 2008: Author was edited
12 May 2008: Author was edited
12 May 2008: Author was edited
12 May 2008: Author was edited
24 Jul 2007: Author was added to the bibliography
24 Jul 2007: Author was added to the bibliography
27 Jun 2007: Author was edited
22 Jun 2007: Author was edited
22 Jun 2007: Author was edited
11 Jun 2007: Author was added to the bibliography
28 Apr 2003: Added the author to the bibliography
