Evaluation of UISB The User Interface Specification Browser

Transcription

1 Evaluation of UISB The User Interface Specification Browser Marko Nieminen, Mikael Johnson, Jarmo Parkkinen, Toni Koskinen Helsinki University of Technology Information Ergonomics Research Group / /ierg User Interfaces and Usability /usability

2 UISB Support for Distributed/Multi- Disciplinary UI Specification and Design User interfaces (UI) are effective tools for communicating the functionality and structure of a product or an application (software, service) to the intended customers and especially end users The development of user interfaces (UI) requires multidisciplinary expertise A multi-disciplinary design/development group needs tools to communicate the UI specifications and intermediate UI designs to each other UISB The User Interface Specification Browser is an attempt to support this distributed/ decentralised UI design activity

3 Our Previous Work Requirements for UISB: The results of our previous study (presented in HCII2001) pointed out several problems related to user interface definition and specification work: 1) problems related to the user interface (UI) documents themselves and 2) problems related to the organisational processes of controlling the UI specifications The UISB application: The resulting UISB application has been presented in HCII2003 Results from the previous papers are not presented in this presentation

4 The UISB Tool User Interface Specification Browser

5 Aim of the Study To evaluate: How does UISB support the development and early evaluation of interactive UI s? How does UISB support the creation of dynamically working UI s from the development standpoint (visual designer, interaction/ software designer)? How do the interactive UI s created with UISB serve usability testing/evaluation in the early stages of development project?

6 Research Settings Evaluation was carried out in co-operation with a real development organisation (developing a mobile handheld device) Evaluation 1: Developer workshop Evaluation 2: A UISB model applied in an earlyphase usability test

7 Evaluation 1: Developer Workshop Arrangements Developer users Workshop (N=7) with several stakeholders (roles: visual designer, code writer, manual writer, project manager) Usability walkthrough & business process simulation combined (testing the application and walking through the development activities with all development representatives) Design task: The UI features that allow users to read, reply to, and delete a short message with a mobile device

8 Evaluation 1: Results Stages in the Development Process 1) Visual designer (visual layout; files) -> 2) Technical designer (menu structure; file import) -> 3) Writer of the user s manual (desktop publishing) Good in UISB menu structure creation was considered easy Challenges LOTS of detailed UI improvement suggestions, e.g. ability to continue from previous design state/situation, autosave functionality, behaviour of the properties window adjustments/personalisation: UISB desktop layout and visible user interface components should be possible to define according to the individual needs (the support for session/workspace memory ), also different views according to the development role of the person external applications: ability to cope with existing tools & file formats (linking vs. importing) modelling semi-interaction: not just static screenshots and not complete interactive applications

9 Evaluation 2: Usability Test Experiment End-users testing a UI model running in UISB a usability test (N=16) with a UI model in the specification phase a laptop with touch-screen ( direct UI interaction ) comparison of two competing interaction structures: gathering support for development decision making test task: change a phone number in the phone book (with two different paths in the menu structure)

10 Evaluation 2: Results all users were able to use the semi-interactive UI specification model UISB enabled realistic interaction with the on-screen mock-up users were keen on commenting the mock-up interaction and visual design (the model was not considered as a finalised product) the development of the two competing interactive and testable designs was easy to do it was possible to arrange the usability test with an interactive prototype earlier than usually in the development process

11 Conclusions Basic functionality of UISB did work; Many improvements are, however, required in the UISB UI level and in the development activities Experimenting with different design solutions not feasible enough with current UISB functionality An UISB like tool requires consideration/changes in the UI development process (modelling of interaction, co-operation, division of design work): The idea/concept of semi-interactive modeling in UI design specification work is not easily comprehensible and applicable UI design process (work) & tool match how to do simultaneous design about UI design processes and activities alongside tool development work The utility of such a tool needs to be evaluated from the standpoint of the whole process (e.g. design work usability test) The complete utility of UISB did not get completely clear in a short workshop meeting; this would require a longitudinal study