1 / 16

Multi-Fidelity User Interface Specifications

Multi-Fidelity User Interface Specifications. Thomas Memmel 1 , Jean Vanderdonckt 2 , Harald Reiterer 1 1 Human-Computer Interaction Group, University of Konstanz, Universitätsstrasse 10, 78457 Konstanz, Germany http://hci.uni-konstanz.de 2 Université catholique de Louvain (UCL)

lael
Télécharger la présentation

Multi-Fidelity User Interface Specifications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Multi-Fidelity User Interface Specifications Thomas Memmel1, Jean Vanderdonckt2, Harald Reiterer1 1Human-Computer Interaction Group, University of Konstanz, Universitätsstrasse 10, 78457 Konstanz, Germanyhttp://hci.uni-konstanz.de 2Université catholique de Louvain (UCL) Louvain School of Management (LSM) - Information Systems Unit (ISYS) Belgian Laboratory of Computer-Human Interaction (BCHI) http://www.isys.ucl.ac.be/bchi

  2. Challanges of UI Specification Zetie 2005 • Different disciplines, speaking different languages • Separation of concerns (client & supplier) • Media disruptions, loss of precision, ambiguity • Lots of systems lack UI quality (usability, user experience) failure

  3. UI Specification Is Not A Linear Proces • Creating innovative interactive products requires • Leaping between abstract and detail • Designing design alternatives • Keeping the design space open as long as possible From: Löwgren & Stolterman 2004, Thoughtful Interaction Design

  4. Responsibility Assignment in Corporate Projects

  5. Corporate UI Development Process • Current Situation • Media disruptions • Text-basedartifacts • Document-basedrequirementsmanagement • Lack oftraceability • Difficulttotranslateinto UI • Intransparent • Ambiguous Client Client IT Supplier IT Supplier • Required Change • Usability strategicfactor • UE must not beoutsourced • Early prototyping • Rapid feedback • Corporate Design • Specification incl. Design • Save rationale & artifactselectr. Prototyping-Driven UI Specification

  6. Prototyping for everybody: Comm. Tools iRise Axure

  7. Related Work Canon & Task Sketch Denim/Damsk

  8. Bringing it all together • Provide shared means of communication to support collaboration of different disciplines • Identify a common denominator • Overcome limitations of text-based work-style • Provide something tangible and interactive • Determine ingredients of UI specification • Support switching between abstract and detail (multi-fidelity) • Provide traceability and transparency • Save design rationale

  9. Interactive UI Specification Explained

  10. Model-driven vs. Model-based • Model-driven UI specification • Uses formal, predefined models • Allows code generation directly from models • Very suitable for straight forward design solutions or when design space is constrained • Model-based UI specification • Is based on models, but no need to code generation • Models visualize requirements • More appropriate when innovation is required and disciplines must be bridged

  11. Level of abstraction: Text to UI design Define a common denominator for interdisciplinary UI modelling (Bridge the gaps) Mayhew, Rosson & Caroll, Constantine Constantine, Ambler, Beck Holt, Ambler New Research

  12. Zooming through Levels of Abstraction Drawing is based on Garrett, Jesse J. (2002). The Elements of User Experience: User-Centered Design for the Web. New Riders Press.

  13. Evaluation • Interviews (n=7): Very positive feedback; experts expect improvement of work style through multi-fidelity approach • Long-term diary study (4 weeks; n=8) • Rapid enhancement of tool usability (1.75 to 4.25) • Incorporated „contextual layer“ • Support masters/templates, creation of patterns • Versioning of specification objects (design rationale) • Annotation support, defect management console • Ongoing expert interviews (e.g. SIEMENS AG)

  14. Future Work: Collaboration

  15. Summary Towards a common denominator for UI-related modeling in non-IT organizations Include business process modeling in research on bridging in the gaps Idea of interactive UI specifications Situation-dependant alternative to model-driven UI specification methods Experimental tool-support to encourage collaboration and creativity

  16. Thank you very much for your attention http://hci.uni-konstanz.de/INSPECTOR Website of INSPECTOR method & tool http://www.irise.com The iRiseprototyping and specificationtool http://www.axure.com The Axure Pro prototyping and specificationtool http://www.usixml.org User Interface eXtensibleMarkupLanguage

More Related