1 Human-Computer Interaction Lab, University of Konstanz, Germany Thomas Memmel 1, Harald Reiterer 1 INSPECTOR Interdisciplinary UI Specification Tool.

Slides:



Advertisements
Similar presentations
Chapter 11 Design, prototyping and construction 1.
Advertisements

Tool-Support for Interdisciplinary and Collaborative User Interface Specification IADIS 2008 Amsterdam – Workgroup HCI University of Konstanz – Thomas.
Design, prototyping and construction
Chapter 11 Designing the User Interface
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Rapid Prototyping Dimensions and terminology Non-computer methods
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
User Interface Specification in Complex Web-based Information Spaces INSPECTOR: Method and Tool for Visual UI Specification 1 Human-Computer Interaction.
Human Computer Interaction
The Software Quality Star: A conceptual model for the software quality curriculum Ronan Fitzpatrick School of Computing, Dublin Institute of Technology,
1 Why prototype? “…the value of prototypes resides less in the models themselves than in the interactions they invite.” Michael Schrage – Serious Play.
The Process of Interaction Design. Overview What is Interaction Design? —Four basic activities —Three key characteristics Some practical issues —Who are.
The Process of Interaction Design
What is Interaction Design?
Multi-Fidelity User Interface Specifications Thomas Memmel 1, Jean Vanderdonckt 2, Harald Reiterer 1 1 Human-Computer Interaction Group, University of.
SIMS 202 Information Organization and Retrieval Prof. Marti Hearst and Prof. Ray Larson UC Berkeley SIMS Tues/Thurs 9:30-11:00am Fall 2000.
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
Design Process …and the project.
Usability 2004 J T Burns1 Usability & Usability Engineering.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Using Use Case Scenarios and Operational Variables for Generating Test Objectives Javier J. Gutiérrez María José Escalona Manuel Mejías Arturo H. Torres.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Chapter 13: Designing the User Interface
User Interface Design Chapter 11. Objectives  Understand several fundamental user interface (UI) design principles.  Understand the process of UI design.
Web Design Process CMPT 281. Outline How do we know good sites from bad sites? Web design process Class design exercise.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
User Interface Theory & Design
1 Conceptual Modeling of User Interfaces to Workflow Information Systems Conceptual Modeling of User Interfaces to Workflow Information Systems By: Josefina.
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
1 DENIM: An Informal Web Site Design Tool Inspired by Observations of Practice CS 376 – Research Topics in HCI 11/01/2005 Tony Tulathimutte.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 12.
Overview Prototyping and construction Conceptual design
HCI Prototyping Chapter 6 Prototyping. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “prototyping” –Explain the.
Design, prototyping and construction CSSE371 Steve Chenoweth and Chandan Rupakheti (Chapter 11- Interaction Design Text)
UML & Prototyping. What is a prototype? A prototype is a small-scale model. It can be (among other things): a series of screen sketches a storyboard,
Interaction Design Process COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 5 Chapter 3 (Heim)
HCI – Prototyping. Why Prototype?  Prototyping is a well understood and used technique in design engineering where products are tested via a model prototype.
More on “The Huddersfield Method” A lightweight, pattern-driven method based on SSM, Domain Driven Design and Naked Objects.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
Object-Oriented Analysis and Design An Introduction.
Comp 15 - Usability & Human Factors Unit 8a - Approaches to Design This material was developed by Columbia University, funded by the Department of Health.
1 Workshop on Business-Driven Enterprise Application Design & Implementation Cristal City, Washington D.C., USA, July 21, 2008 How to Describe Workflow.
Design Options for Multimodal Web Applications Adrian Stanciulescu and Jean Vanderdonckt {stanciulescu, UCL/IAG/BCHI.
Prototyping. What is a prototype? In other design fields a prototype is a small- scale model: a miniature car a miniature building or town.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
Chapter 9 Prototyping. Objectives  Describe the basic terminology of prototyping  Describe the role and techniques of prototyping  Enable you to produce.
Task Analysis CSCI 4800/6800 Feb 27, Goals of task analysis Elicit descriptions of what people do Represent those descriptions Predict difficulties,
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Design and Implementation of a Rationale-Based Analysis Tool (RAT) Diploma thesis from Timo Wolf Design and Realization of a Tool for Linking Source Code.
Begin Class with More Studio. Introduction to Prototyping.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Human-Computer Interaction University of Konstanz hci.uni-konstanz.de Agile Human-Centered Software Engineering Thomas Memmel, Fredrik Gundelsweiler, Harald.
Overview Prototyping Construction Conceptual design Physical design Generating prototypes Tool support.
Design, prototyping and construction(Chapter 11).
Prototyping Creation of concrete but partial implementations of a system design to explore usability issues.
5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
Lecture 2 Supplement - Prototyping
Task Analysis CSCI 4800/6800 Feb 27, 2003.
Prototyping.
Informatics 121 Software Design I
Design, prototyping and construction
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Informatics 121 Software Design I
Chapter 11 Design, prototyping and construction 1.
DESIGN, PROTOTYPING and CONSTRUCTION
Design, prototyping and construction
Presentation transcript:

1 Human-Computer Interaction Lab, University of Konstanz, Germany Thomas Memmel 1, Harald Reiterer 1 INSPECTOR Interdisciplinary UI Specification Tool

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Common Denominator ? Software Engineering Usability Engineering Business Process Modeling How do we build interactive systems with high UI quality and usability in complex organizations? 2 Usability Expert: - Must bridge the disciplines - Needs to extend his expertise Usability-driven question: Bridge the gaps

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Responsibility Assignment in Corporate Projects 3 Client Avoids CASE-Tools Office dominates Informal notations preferred Gulf between academic methods and industrial practice IT Supplier Structured approaches Formal Notations (e.g. UML) Professional tools (GUI-Builder) Programming languages

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Current Situation Media disruptions Text-based artifacts Document-based requirements management Difficult to translate into UI Intransparent Ambiguous Corporate UI Development Process IT Supplier Client 4 User Needs General Requirements Specific UI Requirements UI SpecificationUI PrototypingImplementationFeedback Required Change Usability strategic factor UE must not be outsourced Early prototyping Rapid feedback Corporate Design Specification incl. Design IT Supplier Client Prototyping-Driven UI Specification (Schrage 1999)

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Trade-Off : Ceiling and Threshold 5 Capabilities Resources (time, experience,…) 100% 50% Ceiling Threshold First generation Second generation Third generation Integrated Development Environments UI types Walls

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Tool Requirements 6 Purpose/Added ValueTool Requirement Traceability of design rationale; transparency of translation of models into UI design Switching back and forth between different (levels of) models Smooth transition from problem- space concepts to solution space Smooth progression between abstract and detailed representations HCI experts can build abstract and detailed prototypes rapidly Designing different versions of a UI is easy and quick, as is making changes to it Provide support for design assistance and creative thinking for everybody; all kinds of actors can proactively take part in the UI specification Concentration on a specific subset of modelling artefacts, which can be a UML-like notation or one that best leverages collaboration The early detection of usability issues prevents costly late-cycle changes Allowing an up-front usability evaluation of look and feel; providing feedback easily

Mayhew, Rosson & Caroll, Constantine Constantine, Ambler, Beck Holt, Ambler 1. Usability Engineering High-Fi Prototype Low-Fi Prototype, Conceptual Model UI Storyboard, Navigation Map Flow Chart, Process Model Task Map Task Case Personas, User Scenario, User Role Activity, Information, Interaction Scenario 2. Software Engineering Pilot SystemEssential UI Prototype Use Case Storyboard, UI Flow Diagram Activity, Robustness & Sequence Diagram Use Case Diagram (Essential) Use Case User Story, User Role, Personas Usage Scenario 3. Business Process Modelling Power Point PrototypeMockups UI Slide Show, UI Storyboard Activity, Sequence, & Data Flow Diagram Use Case Diagram Business Use Case Personas, Business Roles Business Vision 4. Common Denominator Detailed PrototypeAbstract Prototype UI Storyboard Flow Chart, Activity & Data Flow Diagram Use Case Diagram, Task Map (Essential) Use Case Personas, User Role, Role Map Scenario Map Level of abstraction: Text to UI design Define a common denominator for interdisciplinary UI modelling (Bridge the gaps) New Research

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Interactive UI Specification Explained 8 Interactive UI PrototypesInteractive UI Specifications Vehicle for requirements analysis Vehicle for requirements specification Exclusively models the UI layer; may be inconsistent with specification and graphical notations Allows drill down from UI to models; relates UI to requirements and vice versa Either low-fidelity or high-fidelitySeveral levels of detail Supplements text-based specification Alternative to text-based UI specification Design rationale saved in other documents Incorporates design knowledge and rationale

User Model Task Model Interaction Model Vanderdonckt: CAMELEON Reference Framework

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Levels of Abstraction 10 Drawing is based on Garrett, Jesse J. (2002). The Elements of User Experience: User-Centered Design for theWeb. New Riders Press.

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Mapping Artefacts to the Zoom-Canvas 11

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Video 12

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. UI Design: Inspector – Expression Blend 13

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Evaluation: Questionnaire (Daimler AG) 14 Questionnaire topicAvg. Ability to integrate documents and logic with INSPECTOR3.66 Chance to capture conceptual and schematic ideas3.83 Support for user, task and interaction modelling4.00 Possibility to link models and to thereby increase the traceability and transparency3.66 Text-based and graphical requirements modelling (aggregated)3.79 Accessibility of the prototyping features3.16 Provided functionality at the UI design layer3.40 Applicability of the UI designs for usability evaluations3.33 Possibility to link UI designs in order to create a simulation3.25 Overall UI prototyping capabilities (aggregated)3.28 Chance to get both overview and detail on the zoom-based specification space3.33 Helpfulness of the zoom-interaction style during prototyping and modelling3.00 Support for switching between created artefacts3.50 Accessibility of all necessary information on the zoom-canvas3.50 Overall rating of the interaction with INSPECTOR (aggregated)3.33 The overall contribution of INSPECTOR to existing UI specification practice3.83 The improvement of work style through a combination of different models with multi- fidelity UI design 4.83

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Dimensions of Future Work Collaboration –Provide an interaction framework for joint UI modelling, design and specifcation e.g. Gigapixel displays and multi-modal interaction Common denominator –Consider to in-/decrease the amount of models Creativity –Support different grades of formality Simulation –Link disciplines by simulation –Drive the UI process by externalization of vision –Prototyping-driven UI specification 15

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Summary & Conclusion Model-driven and model-based approach for UI specification New research towards a common denominator for UI- related modelling Idea of interactive UI specifications First empirical studies prove: the idea to interconnect a thoughtful selection models with different levels of UI design very much contributes to UI specification processes in client organisations 16

CADUI 2008, Albacete (Spain), Inspector – Interdisciplinary Specification Tool Thomas Memmel and Harald Reiterer. Additional Information Thanks to Jean Vanderdonckt for inviting INSPECTOR to become a member of the usiXML supply chain Please visit for more information about the projecthttp://hci.uni-konstanz.de/inspector Please visit our YouTube channel to get in touch with HCI at lake Constance We are happy to invite you as a guest speaker! 17

Thank you very much Please do not hesitate to ask questions 18