Download User-Centered Information Design for Improved Software Usability

• Billing
• Forecasting
• Budgeting
The problem with hierarchical decomposition is that it can be hard both for analysts to analyze and for
designers to use. To minimize the complexity, the trend is to seek contextualized, user-centered
representations of tasks via, for example, scenarios of typical work. Scenarios make task analysis data
usable. Write scenarios that illustrate typical sequences of actions with real data. Include user exceptions
that typically disrupt real-life tasks. Examples of exceptions are typing errors or interruptions like
switching to another, higher priority task [4].
Scenarios are real and detailed examples of things users actually need to do. Lewis and Rieman [5],
while talking about task analysis for a traYc modeling system, mention the following as one of the tasks
they developed: “Change the speed limit on Canyon Boulevard Eastbound between Arapahoe and 9th.
Calculate projected traYc flows on Arapahoe West of 6th assuming Canyon speeds between 25 and 55
in increments of 5 mph.” This example describes what the user wants to do, but not how. It is very
specific, even specifying street names. It is also complete, as it covers both changing the speed limit and
calculating the projections for Arapahoe. Such a description should also specify who will perform the
tasks.
Scenarios also nicely complement the requirements produced by traditional software engineering. For a
document development software package, for example, a scenario might be to produce the book, UserCentered Information Design for Improved Software Usability by Pradeep Henry. This scenario
supplements the detailed partial tasks collected in traditional requirements analysis, which might include
things such as “key in text,” “check spelling,” and “print the document.” The traditional approach helps
to ensure that all important functions of the system are recognized, while the representative tasks in the
task-centered approach provide an integrated picture of those functions working together.
Joint analysis in UCID In UCID, both the HCI view and the technical writing view are important. The
HCI view is jointly executed early during the UCID analysis phase by usability engineers and technical
writers. Later, technical writers carry out the technical writing view for designing the information
architecture.
Previous Table of Contents Next
[an error occurred while processing this directive]