Designing human-computer interaction can be a large and complex task. One way to manage that complexity is to divide design into smaller interrelated subcomponents; this is called the structured approach. It is an excellent way for
PURPOSEOur purpose is to establish an ongoing community of practitioners who will support each other in applying knowledge gained f?om research and practice in HCI. Reflective pmctitionersvalue dialog with the research emmmmity, ideas from published reports of mccessM practice, individual discussionswith other practitioners, and caretid evaluation of the results of their own work. They are interested in articulating design rationate as well as in producing design results. They are interested in sharing the resultsof their practice with others. At this meeting, we plan to follow up on the IC'93 workshop, Re@ective Practitioners, by welcoming a larger group of participan~identifying our common needs and problems, and developing ideas for an action plan for cooperation. The three main outcomes of this years meeting are to articulate a shared understwding of who we are, what we~and how we can help each othec to create an e-mail distribution list that we can use to stay in communication between SIGCI-H confer~, and to plan activities for the coming year, including organizing the SIG meeting at CHI'95. WHO ARE WE?Our current hypothesis is that we work in industry or government, as employees or consuhants. Our main responsibility is for product usability. We usually work with product development teams, although we may report to a usability organimtion.We tend to I@ to prior research and suecesslid products for answers to questions rather than relying on cleverness or intuition.We try to articulate the rationale behind our design decisions rather than working from feel or intuition.
Requirements, Models, Prototypes (RMP) is a structured process for HCI design for industrial software development teams. It consists of an organized collection of ten design deliverables, templates for each, and a set of practices. RMP is derived fi-om the authors' ongoing experience and the HCI literature of research and practice. It was devised to aid experienced designers and to help beginners learn. The tutorial is intended for those already familiar with basic HCI design who desire a more systematic approach. KEYWORDSDesign process, structured design, usability requirements model, prototype, formative evaluation., HCI design OVERVIEW Requirements, Models, and Prototypes (RMP) is a semiformal, structured process for designing Human-Computer Interaction (HCI). It was devised to help HCI designers be more cost effective and to promote the fit of HCI design work into industrial software development processes. It is a statement of the current routine practice of the authors.The components of RMP are: q q q A specific minimal set of HCI design deliverables (methods) and their known relationships for each of three groups, Requirements, Models, Prototypes (ten deliverables in all).Templates (tools) for each of these deliverables to promote repeatability, reliability, and efficiency as well as to help beginners.A set of five design practices that help designers work comfortably in contemporary software development environments.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
customersupport@researchsolutions.com
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.