Conceptual Design:

From User Requirements to User Interface

Kathy Potosnak

Interface Concepts

28522 State Highway 104 NE

Kingston, WA 98346 USA

+1 360 297 2500

kathyp@interfaceconcepts.com

ABSTRACT

This half-day tutorial introduces a semi-structured conceptual design framework that helps product teams bridge the gulf between user requirements and detailed user interface design. It covers the background, benefits, process, and hands-on application of the framework to a simple example project.

Keywords

Conceptual design, cognitive models, design methods, design process, design techniques, measurable objectives, product design, software design, task analysis, task model, user requirements, usability, user interface design, user-centered design

INTRODUCTION

This half-day tutorial introduces conceptual design and a seven-step framework for creating conceptual designs. It teaches the what, why, and how of conceptual design.

Conceptual design involves explicitly defining the ideas or concepts underlying the user interface of a product. It describes how the designers intend for users to think about the product. Conceptual design covers what a product is, what it does, and how it does it. Once a good conceptual design has been developed, a user interface can be designed which clearly and accurately expresses the underlying concepts.

All products have conceptual designs. If the conceptual model of a product is not designed explicitly, one (or more) will be created implicitly by the people developing the product.

Many usability problems can be traced to poor, inconsistent, incomplete, or competing conceptual designs. Explicitly creating a good conceptual design up front is more cost effective than fixing conceptual problems that are discovered later in the development process.

OBJECTIVES

This tutorial is intended to provide attendees with

· a clear understanding of the purpose and value of the conceptual design of products;

· information about how to create a conceptual design for a product; and

· hands-on experience with a user-centered conceptual design framework.

AUDIENCE

This workshop is recommended for everyone who participates in software design activities, including software engineers, developers, programmers, user interface designers, engineering managers, program managers, usability professionals, and others. The course material is appropriate for beginners as well as seasoned professionals.

CONTENT

Rather than delve directly into creating menus, dialogs, widgets, forms, or other user interface elements, conceptual design focuses the design effort on the underlying concepts, and results in the creation of a model of the user interface for the product. The user interface model clearly and accurately represents the conceptual design to the user and guides the detailed design of the user interface contents.

The conceptual design framework synthesizes many user-centered design principles and practices. It involves the following seven activities:

1. Define a central concept: A concise statement of what the product is and what it is not. Its purpose is to clearly define the boundaries of the product.

2. Describe users and their requirements: A list of what is important to the target users, such as getting work done quickly, being in charge, and feeling successful.

3. Define and prioritize measurable objectives and constraints: Objectives are the goals for the design such as automation of repetitive tasks, user control over the functionality of the product, and appropriate


feedback on results. Operational definitions indicate how the design will be measured against the objectives, for example in usability testing. Constraints define the design space within which these goals may be achieved and tend to be based more on technology and implementation limitations, such as disk space available, display size and resolution, response time requirements, and availability of a pointing device.

4. Design the user's object model: A list of all the objects the user needs to deal with in the product along with their attributes, actions that can be performed on them, and related objects.

5. Design the user's task model: A list of all tasks the users need to be able to perform with procedures on how they will be accomplished in the product.

6. Synthesize a user interface model: Organizes the contents of the user interface around the object and task models, such as menu names are objects and menu contents are actions on objects, or each web page represents a primary object and buttons perform actions on objects.

7. Evaluate results against the objectives: Various evaluation techniques, such as heuristic evaluation and usability testing are applied throughout the design process to measure achievement of objectives.

The benefits of this simple, cost-effective approach include improved consistency, learnability, and ease of use. It has proven effective in the design and redesign of shrink wrap software products, web-based applications, and other software projects.

The material is colorfully illustrated by anecdotes and examples from the instructor's personal experience. Attendees work together as a group as well as in small teams to get hands-on practice applying the framework to a simple, yet realistic example project.

ABOUT THE INSTRUCTOR

Kathy Potosnak is principal consultant and owner of Interface Concepts, a user interface consulting firm she established in 1995. She developed and refined the conceptual design framework based on over 14 years of experience in the field of human-computer interaction at such companies as Adobe, Aldus, and Ashton-Tate.

Kathy received her Ph.D. in engineering psychology from Johns Hopkins University. She has published over 30 articles and taught numerous courses on human-computer interaction. She is an active member of ACM SIGCHI and a cofounder and past chair of the Puget Sound SIGCHI chapter. She is also a member of the Human Factors and Ergonomics

Society, IEEE Computer Society, Usability Professionals' Association, and Washington Software and Digital Media Alliance.

BIBLIOGRAPHY

Akscyn, R., Yoder, E., and McCracken, D. The data model is the heart of interface design. Proceedings of CHI '88 (Washington, D.C., May 1988), ACM Press, 115-120.

Bennett, J.L., and Karat, J. Facilitating effective HCI design meetings. Proceedings of CHI '94 (Boston, MA, April 1994), ACM Press, 198-204.

Coble, J.M., Karat, J., and Kahn, M.G. Maintaining a focus on user requirements throughout the development of clinical workstation software. Proceedings of CHI 97 (Atlanta, GA, March 1997), ACM Press, 170-177.

Gentner, D.R., and Grudin, J. Why good engineers (sometimes) create bad interfaces. Proceedings of CHI '90 (Seattle, WA, April 1990), ACM Press, 277-282.

Gentner, D., and Stevens, A.L. Mental models. Erlbaum, Hillsdale NJ, 1983.

Karat, J., and Dayton, T. Practical education for improving software usability. Proceedings of CHI '95 (Denver, CO, May 1995), ACM Press, 162-169.

Kellogg, W., and Breen, T.J. Evaluating user and system models: Applying scaling techniques to problems in human-computer interaction. Proceedings of CHI+GI 1987 (Toronto, Canada, April 1987), ACM Press, 303-308.

Masson, M.E.J., Hill, W.C., Conner, J., and Guindon, R. Misconceived Misconceptions? Proceedings of CHI '88 (Washington, D.C., May 1988), ACM Press, 151-156.

Norman, D.S., and Draper, S.W. (eds.) User Centered System Design. Erlbaum, Hillsdale NJ, 1986.

Rosson, M.B., and Carroll, J.M. Integrating task and software development for object-oriented applications. Proceedings of CHI'95 (Denver, CO, May 1995), ACM Press, 377-384.

Rosson, M.B., Maass, S., and Kellogg, W.A. Designing for designers: An analysis of design practice in the real world. Proceedings of CHI+GI 1987 (Toronto, Canada, April 1987), ACM Press, 137-142.

Sowa, J.F. Conceptual Structures: Information Processing in Mind and Machine. Addison-Wesley, Reading MA, 1984.

Terwilliger, R.B., and Polson, P.G. Relationships between users' and interfaces' task representations. Proceedings of CHI 97 (Atlanta, GA, March 1997), ACM Press, 99-106.

Winograd, T., Bennett, J., and De Young, L. (eds.). Bringing Design to Software. Addison-Wesley, Reading MA, 1996.