Conference Program
| Proposals |
| Overview |
| Details |
| Events |
| Schedule |
| Program |
| Speakers |
| Organizers |
| Registration |
Second International Conference on Usage-Centered Design
TOPIC - Modeling & Methods
| PRE-CONFERENCE TUTORIALS SATURDAY - 18 October |
| A1 - 8:30a-5:30p |
| Usage-Centered Design: A Crash Course in Designing for Use |
| Larry Constantine and Lucy Lockwood, Constantine & Lockwood, Ltd. |
| This intensive, hands-on tutorial provides a practical introduction to usage-centered design, a proven, industrial-strength process with an established track record on varied development projects from modest XP applications to very large-scale systems. Participants will gain experience in using simplified, agile techniques to quickly organize information about users and user tasks into concise models for driving the visual and interaction design. They will learn how abstract models of user roles, task cases, and abstract user interface prototypes can lead to better designs and dramatic improvements in user performance and ease of learning. The major focus will be on task modeling with essential use cases, which serve as a common thread throughout an integrated usage-centered software development process. Work on a case study problem will provide practice in applying the models and methods of usage-centered design. |
SUNDAY - 19 October |
| B1 - 9:00a-5:00p |
| From Usage-Centered Design to Object-Oriented Design |
| Robert Biddle, Victoria University of Wellington, New Zealand |
| Usage-Centered Design has introduced new principles for beginning the design of user interfaces. This tutorial teaches you how these same ideas can be used to link to Object-Oriented Design of systems. In particular, you will learn how task cases can work together with responsibility-driven design to increase guidance during design and increase traceability between requirements and design. This also turns out to be a good way to learn object-oriented design, and for user interface designers and system developers to learn more about each others’ world. The tutorial also shows how these techniques relate to ideas in agile methods and to object-oriented design patterns. |
| B3 - 9:00a-5:00p |
| Representing Work for the Purpose of Design |
| Karen Holtzblatt, inContext Enterprises |
| What do you do with field data to see the big picture of the users? How do you see opportunities for increasing productivity or and defining new products? Who are the people you are designing for? How can technology enhance their work practice? How do you drive high-level use cases with user data? This tutorial introduces key Contextual Design work models and shows how to use them to vision product solutions and drive use cases. Learn to use modeling techniques such as the affinity diagram, flow model, and sequence models to represent your user population, its issues, and tasks. Understand how to use this data to identify solutions that really meet user need and increase business value. Learn about using the visioning process and storyboards to show how field data is used to define requirements and work out high-level use cases. The tutorial combines lecture, example, practice, and discussion. |
| B4 - 9:00a-5:00p |
| Agile Usage-Centered Modeling for Setting Scope, Goals, and Priorities |
| Jeff Patton, Tomax Corporation |
| Agile development methodologies advocate deferring design decisions as long as possible. This is commonly misinterpreted to mean “don’t design.” While leaving options open is valued, agile methodologies also place strong emphasis on understanding what goals the software should meet to provide value to its users. The methods and models found in Usage-Centered Design are ideally suited to help users and developers collaborate to discover those goals and their priorities. This tutorial will provide you with hands on experience using collaborative card-based techniques to explore a real-world business problem and successfully identify and model user roles, tasks and interaction contexts. You’ll see how you can easily involve developers and end-users to provide valuable shared understanding of the project goals. We’ll engage in this process with the explicit goal of arriving at a prioritized list of features and a project schedule that can feed easily into your favorite agile methodology. You’ll walk away with a clear understanding of how to use Usage-Centered Design to jump-start an agile project with the strong set of goals and priorities that are key to any projects success. |
MONDAY |
| M21 - 11:00a-12:30p |
| Designing for Breakthroughs in User Performance |
| Jeannine Strope, McKesson |
| Supporting users who have hundreds of mission-critical tasks—performed outside of the actual software yet recorded in the software application—requires a task-driven design with a streamlined, efficient, almost anticipatory workflow. McKesson Clinicals took the opportunity to revamp and rewrite legacy applications using usage-centered design to create a world class clinical system. Along the way we reached great heights in design and encountered great pitfalls in technology and temperament, all the while trying to balance market demand with design priorities. This session presents our hands-on design and lessons learned in employing usage centered design with an agile development process to create task-critical applications.. |
| M31 - 1:30p-3:00p |
| Usage-Centered Design in Extreme Programming and Agile Software Development Environments |
| Jeff Patton, Tomax Corporation |
| Agile development methodologies, and Extreme Programming in particular, advocate deferring design decisions till the last possible minute. How in this type of environment can you successfully practice Usage-Centered Design or other sound user interface and interaction design practices? This presentation will give an overview of Agile development concepts and Extreme Programming as a specific and most popular Agile methodology. In fact, Usage-Centered Design modeling techniques work well to generate the broad scope and priorities necessary to make agile development methodologies work well. The session discusses using Usage-Centered Design as a quick collaborative approach for gathering requirements and building functional design. Learn how to use Usage-Centered Design artifacts such as role and task models to drive project planning and keep development focused on the most important thing: producing software actually usable by people. |
| M42 - 3:30p-5:00p |
| Persona-Based Expert Review: A Technique for Usefulness and Usability Evaluation |
| Joshua Seiden, 36 Partners |
| Personas are traditionally associated with the process of creating system design. But personas offer valuable advantages to usage-centered design teams during the evaluation of software systems. Persona-based expert reviews are more robust than typical expert reviews, because they combine principles-based reviewing techniques with the use of explicit user models. Persona-based reviews are particularly good at ensuring coverage during the review process. The method also excels at uncovering bad matches between system functionality and user expectations. This session will explore persona-based expert review in depth, discussing techniques to ensure your personas are well-suited for evaluation purposes, describing how personas are used during the evaluation process, and stepping through a typical software evaluation. |
| M43 - 3:30p-5:00p |
| Use Case Storyboards: Integrating Usability with RUP and UML |
| Jim Heumann, IBM Software Group |
| Use cases are a way to capture the functional requirements of a software system. To keep them simple and easy-to-read they purposely don't address either usability requirements or the user interface with which users will interact. However, both of these are vitally important to the success of any software that has significant user interaction. This session will introduce a technique, based on the Rational Unified Process (RUP) and Unified Modeling Language (UML), that uses use cases as input to produce a conceptual design of the UI and to specify the usability requirements. The main outputs of this technique are Use Case Storyboards, which define the system's conceptual screens, screen content and navigation paths. Attendees will get a comprehensive introduction to how GUI's fit with use cases, including conceptual user interface design and the specification of usability requirements. |
TUESDAY - 21 October |
| T21 - 10:30a-12:00n |
| Forum: Usability Processes and Practices |
| Robert Biddle, Victoria University of Wellington, New Zealand (Moderator) |
| This session of short presentations explores new ways to integrate and refine usability and software engineering approaches to improve the quality of software design and development. |
| Usage-Centered Design and the OPEN Process Framework |
| Brian Henderson-Sellers, James Hutchison, University of Technology, Sydney |
| Usage-Centered Design supplies a unique and comprehensive approach for the presentation and interaction design of user interfaces. Since it does not address either detailed software design (e.g. internals of objects) or larger scale project management issues, it needs to be complemented and supplemented. This paper describes the OPEN Process Framework (OPF), which offers that larger scale integrative approach. Based on a meta-model, the OPF supports method engineering but is deficient in its support of the HCI issues for which usage-centered design provides excellent support. Therefore we examine the ways in which the OPEN Process Framework and usage-centered design can co-exist in a mutually supportive environment.. |
| T23 - 10:30a-12:00n |
| Designing for Performance Using Usage-Centered Design |
| Helmut Windl, Siemens AG |
| New software applications like Windows XP, Office 2003, and Windows Movie Maker 2 show that user interfaces are turning radically from being object-oriented to task and performance support. At first sight, usage-centered design seems to be the perfect approach to design such systems, but a closer inspection reveals that usage-centered design has to be slightly refined to do the performance support job. This session shows how to use usage-centered design to create systems that follow the electronic performance support system (EPSS) philosophy. It covers the necessary extensions and refinements to the usage-centered design models and process. |
| T41 - 3:30p-5:00p |
| Agile Customer-Side Practices |
| Tom Poppendieck, Poppendieck LLC |
| Extreme Programming and other agile methods are quite specific about developer side practices and how the developer side and customer side interact, but they are silent on how to create an effective user interface. This presentation advocates usage centered design as the core of customer side practices. Incremental development of essential use cases and essential UI models can fit naturally into the iteration cycles of an agile project. Essential use cases are then extended to full-dress form so that functional customer tests can be directly specified from the essential use cases. These tests tell the developer side when they are done with a collection of stories. This presentation also discusses the practice of evolving and using a ubiquitous domain language for the project to ensure that business rules and domain concepts are accurately implemented and validated. The domain language is used in the use cases, the essential user interface model, the code, and the tests. |
WEDNESDAY - 22 October |
| W21 - 10:30a-12:00n |
| Forum: Putting Usage-Centered Design to Work |
| Lucy Lockwood, Constantine & Lockwood, Ltd. (Moderator) |
| This session of experience reports explores the perils, pains, and payoffs of usage-centered design in practice. It draws on the experiences of people who have been applying usage-centered design in a variety of settings to a range of problems. |
| Integrating Usage-Centered Design into the Centers for Disease Control Development Process |
| Ralph Lord, Northrup Grumman Mission Systems |
| Since October 2001 when letters containing aerosolized Anthrax were discovered in the US Postal system, the Centers for Disease Control and Prevention and their contractors have been developing new software systems to improve the agency’s ability to prepare for and respond to bio-terror events. The agency has also been working to standardize on a CDC version of the Rational Unified Process (RUP) for its software development activities. As a member of the Software Process Engineering Group formed to customize the Unified Process, Ralph Lord led an effort to integrate usage-centered roles, activities and artifacts into both the CDC-UP and ongoing development projects. This report discusses the proposed role of “User Experience Analyst” in the CDC-UP and highlights some of the bio-terror software projects which have been positively impacted by usage-centered design activities. |
| Case Study: From Use Cases to User Interface Using UML |
| Chris Armstrong, ATC Enterprises, Inc. |
| This case study shows how to successfully apply Highsmith’s Adaptive Team Collaborative Process to the rapid definition of a user interface model from software requirements expressed as use cases. Over several weeks, a state organization was assisted in launching a project to build a web-based portal for the state’s supreme, appellate, and local jurisdiction judiciary. The externally viewed portal services were captured in a use case model. From the use case model, a user interface content and navigation model was developed in the Unified Modeling Language (UML). This report will also review how these models were captured in Rational Rose and Rational RequisitePro and how the project’s consumables were generated automatically from the tool repository. |
| W22 - 10:30a-12:00n |
| Lean Feature-Driven Development of Interaction Designs |
| David Anderson, uidesign.net; Brian O’Byrne, JStateMachine Project |
| Lean Feature-Driven Development using Statechart modeling and Mediator Pattern can reduce variation in UI development with precise, right-the-first-time implementation of the interaction designer’s intent. In this approach, content models are elaborated into Statecharts that can be directly mapped to an MVC Type-II architecture and Mediator Pattern. With minor extensions, Statecharts can model complex application behavior and be mapped into UI features for tracking in Feature Driven Development. Statecharts drawn using UML modeling tools can be exported in XMI and imported into the JStateMachine engine implementing table driven Mediator and Command patterns in either a Web Servlet or JFC (Swing) environment. |
| W33 - 1:30p-3:00p |
| User Interface Architecture Patterns with UML |
| Bobbi Underbakke, ATC Enterprises, Inc. |
| Software architecture is an abstract concept yet it has very concrete effects on a software application’s design and how the software evolves over time. Just as the underlying software has an architecture, the user interface also has its own architecture. There are several well-known patterns for the user interface architecture that allow UI designers to set the direction for doing detailed UI design. This session will review the principles of user interface architecture with common UI patterns and then discuss how to represent those patterns with the Unified Modeling Language (UML). In addition it will also provide an overview of how the user interface architecture affects detailed UI design activities. |
Be sure to be a part of the excitement. Register now and save!
TOPIC THREADS -
User Performance & Performance Support
Modeling &
Methods
Inspection & Review Techniques
Register Before 19 September and Save
Get your registration in before hotel discounts expire. Register...
forUSE 2002 Proceedings Available
Get your copy of the Complete forUSE 2002 Package (Proceedings, CD-ROM, and Handouts). Click for more details...
Conference Home
|
Call for Participation |
Conference Overview
Registration Details |
Special Events |
Schedule-at-a-Glance
Program |
Speakers
|
Organizers & Sponsors |
Registration
Form
Constantine & Lockwood, Ltd.
Home | Contact Us
© 2002-3, Constantine & Lockwood, Ltd. forUSE is a trademark/servicemark of Constantine & Lockwood, Ltd.
