Critical Issues in User Interface Systems Engineering (Applied Computing)

Benyon, David

ISBN 10: 3540199640 / ISBN 13: 9783540199649

Published by Springer London, 1996

About this Item

LIKE NEW. SHIPS FROM MULTIPLE LOCATIONS.

Seller Inventory # ERICA79735401996406

Bibliographic Details

• Title: Critical Issues in User Interface Systems Engineering (Applied Computing)
• Publisher: Springer London
• Publication Date: 1996
• Language: English
• ISBN 10: 3540199640
• ISBN 13: 9783540199649
• Binding: Paperback
• Condition: Like New
• Book Type: book

About this title

Synopsis

This book developed from an IFIP workshop which brought together methods and architecture researchers in Human Computer Interaction and Software Engineering. To an extent this introduction is a little unfair to the authors, as we have distilled the results of the workshop to give the reader a perspective of the problems within integrated approaches to usability engineering. The papers could not hope to address all ofthe issues; however, we hope that a framework will help the reader gainfurther insights into current research andfuture practice. The initial motivation was to bring together researchers and practitioners to exchange their experiences on Graphical User Interface (Gill) design problems. The two groups represented methodological and architecture/tools interests, so the workshop focused on intersection of how methods can support user interface development and vice versa, how tools, architectures and reusable components can empower the design process. There is, we believe, a constructive tension between these two communities. Methodologists tend to approach the design problem with task/domain/organisational analysis while the tool builders suggest design empowerment/envisioning as a means ofimproving the way users work rather than relying on analysis ofcurrent systems. This debate revolves around the questions of whether users' current work is optimal, or whether designers have the insight to empower users by creating effective solutions to their problems. Tool builders typically want to build something, then get the users to try it, while the methodologists want to specify something, validate it and then build it.