|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
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.. |
| 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 |
| Lucy Lockwood, Constantine & Lockwood, Ltd. (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. (Additional presentations to be announced.) |
| Usability and Other Quality Aspects Derived from Use Cases |
| Daniel Kerkow, Kirstin Kohler, Jörg Dörr, Fraunhofer IESE |
| Usability is one of several quality aspects (also referred to as nonfunctional requirements) according to ISO 9126. The elicitation of those during an early phase of the development is crucial in information systems as well as in embedded systems. Despite the practical importance of usability and additional aspects like performance and maintainability, there is rarely any guidance on how to determine and capture these requirements. We present an approach to elicit usability requirements in concert with supplementary requirements based on a use case-based specification of functional behavior. The approach has been proven in a case study with one industrial customer. It is based on a real system dealing with a mobile, interactive application to allow users monitor production activities, manage physical resources and access information. |
| T33 - 1:30p-3:00p |
| Iterative Project Planning with Extreme Programming |
| Chet Hendrickson, Independent Consultant; Ron Jeffries, XProgramming.com |
| What does it take to build software iteratively, in a way that satisfies the customer and supports your company's bottom line? This session will explore how Extreme Programming and Essential Use Cases can be used to build software solutions that meet your organization’s needs. Learn how the planning decisions you make can impact your project and your company. Find out how Essential Use Cases and the practices of Extreme Programming work together to support successful iterative, customer-centered development. |
| 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. |
| 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. |
| 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
Use Cases & Task Cases
Inspection & Review Techniques
Get your registration in before hotel discounts expire. Register...
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.
