S. Wilson and P. Johnson 1 CADUI'96 - 5 June 1996 - FUNDP Namur Bridging the Generation Gap: From Task Models to User Interface Designs Stephanie Wilson.

Slides:



Advertisements
Similar presentations
Structured Design The Structured Design Approach (also called Layered Approach) focuses on the conceptual and physical level. As discussed earlier: Conceptual.
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
1. Experiential Typology Planners should first consider “the ‘wants’ of the learner, ie what the learner perceives to be his or her need; and the ‘needs’
Bologna Process in terms of EU aims and objectives
Human-Computer Interaction Design Principles & Task Analysis.
Part 1: Introducing User Interface Design Chapter 1: Introduction –Why the User Interface Matters –Computers are Ubiquitous –The Importance of Good User.
User and Task Analysis Howell Istance Department of Computer Science De Montfort University.
Design Activities in Usability Engineering laura leventhal and julie barnes.
Identifying Needs and Establishing Requirements John Thiesfeld Jeff Morton Josh Edwards.
Design and Evaluation of Iterative Systems n For most interactive systems, the ‘design it right first’ approach is not useful. n The 3 basic steps in the.
© De Montfort University, Design Process Howell Istance Department of Computer Science De Montfort University.
Principles and Methods
CSCI 102 Intro to IT B Autumn 2002 Introduction to HCI Lecturer Gene Awyzio (02)
© Copyright Eliyahu Brutman Programming Techniques Course.
Chapter 7 design rules.
1 System: Teallach Presenters: Baolinh Le, [Bryce Carder] Course: Knowledge-based User Interfaces Date: April 29, 2003 Teallach: A Model-Based User Interface.
Task analysis 1 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Preece et al Chapter 7.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
User interface design. Recap User Interface GUI Characteristics (Windows, Icons, Menus, Pointing, Graphics) User Centered Design User Interface Design.
Domain-Specific Software Engineering Alex Adamec.
2 1 Chapter 2 Data Model Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
FH Augsburg - FB Informatik 1 CADUI' June FUNDP Namur Software Life Cycle Automation for Interactive Applications: The AME Design Environment.
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
Requirements Analysis
Southern Cross University 1 CADUI' June FUNDP Namur Investigating Layout Complexity Tim Comber Dr. John Maltby Centre of Computing Southern.
An Approach to Task Modelling for User Interface Design Costin Pribeanu National Institute for Research and Development in Informatics, Bucureşti, Romania.
Artificial Intelligence CIS 479/579 Bruce R. Maxim UM-Dearborn.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
1 ICAS’2008 – Gosier, March 16-21, 2008 A Transformational Approach for Pattern-based Design of User Interfaces Costin Pribeanu Jean Vanderdonckt National.
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
Gary MarsdenSlide 1University of Cape Town Human-Computer Interaction - 7 Design Guidelines & Standards Gary Marsden ( ) July 2002.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Guidelines for Designing Inquiry-Based Learning Environments on the Web: Professional Development of Educators Byung-Ro Lim IST, Indiana Univ. July 20,
Intent Specification Intent Specification is used in SpecTRM
CSE 240 Lecture 10. © Lethbridge/Laganière 2001 Chapter 7: Focusing on Users and Their Tasks2 For Next time Finish Reading Chapter 6 Read Chapter 7.
Basic Concepts Software Architecture. What is Software Architecture? Definition: – A software architecture is the set of principal design decisions about.
Design Rules-Part B Standards and Guidelines
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Methodologies of the SDLC Traditional Approach to SDLC Object-Oriented Approach to SDLC CASE Tools.
Université Toulouse I 1 CADUI' June FUNDP Namur Automatic Ergonomic Evaluation : What are the Limits ? Christelle FARENC *, Véronique LIBERATI.
Interaction Design Notes from Nathan Pearson and Sommerville 9 th edition.
Univ. Autónoma de Madrid 1 CADUI' June FUNDP Namur A Framework for the Automatic Generation of Software Tutoring Javier Contreras Francisco.
Software Engineering User Interface Design Slide 1 User Interface Design.
Towards a Pattern Language for User Interface Design
1 CADUI' June FUNDP Namur Defense Science & Tech. Org. Declarative interaction through interactive planners Conn V Copas Defence Science.
Human Factors In Visualization Research Melanie Tory and Torsten Moller Ajith Radhakrishnan Nandu C Nair.
Chapter 6 Determining System Requirements. Objectives:  Describe interviewing options and develop interview plan.  Explain advantages and pitfalls of.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Introduction: definition of a lesson plan It can be simple as a mental checklist or as a complex as a detailed two-page typed lesson plan.
Stanford University 1 CADUI' June FUNDP Namur The Mecano Project Angel R. Puerta Knowledge Systems Laboratory Stanford University Stanford.
TRIGONE Laboratory LIS Laboratory 1 CADUI' June FUNDP Namur The DIANE+ Method Jean-Claude TARBY TRIGONE Laboratory University Lille 1 LILLE.
The Structure of the User Interface Lecture # 8 1 Gabriel Spitz.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
The Structure of the User Interface Lecture # 2 Gabriel Spitz.
Introducing Design and Technologies. Victorian Curriculum F–10 Released in September 2015 as a central component of the Education State Provides a stable.
Petter Nielsen Information Systems/IFI/UiO 1 Systems development Methodologies IN364.
Welcome to the HA499 Seminar!
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
Université Toulouse I 1 CADUI' June FUNDP Namur Implementation Techniques for Petri Net Based Specifications of Human-Computer Dialogues.
Investigate Plan Design Create Evaluate (Test it to objective evaluation at each stage of the design cycle) state – describe - explain the problem some.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
The purposes of nursing theory?
What Do We Mean by Usability?
Design rules.
HCI – DESIGN RATIONALE 20 November 2018.
Chapter 0 : Introduction to Object Oriented Design
Fundamentals of Human Computer Interaction (HCI)
Requirements I Peter Dolog dolog [at] cs [dot] aau [dot] dk
Dept. of Computation, UMIST
Presentation transcript:

S. Wilson and P. Johnson 1 CADUI' June FUNDP Namur Bridging the Generation Gap: From Task Models to User Interface Designs Stephanie Wilson and Peter Johnson Department of Computer Science Queen and Westfield College University of London

S. Wilson and P. Johnson 2 CADUI' June FUNDP Namur Or... Design Guidelines and Task-Based Design

S. Wilson and P. Johnson 3 CADUI' June FUNDP Namur Guidelines  Directing principles to be followed to achieve a particular effect in some situation  Expressed in different forms  Flexibility...

S. Wilson and P. Johnson 4 CADUI' June FUNDP Namur Flexibility in Guidelines Anybody out there?

S. Wilson and P. Johnson 5 CADUI' June FUNDP Namur Guidelines in User Interface Design  Directing principles to be followed during design or evaluation of a system to increase its usability  General, abstract and broad in application or Specific, concrete and narrow in application  Constructive or evaluative  Emerge from theory or practice  Largely concerned with later stages of design

S. Wilson and P. Johnson 6 CADUI' June FUNDP Namur Overview  Guidelines and user interface design  Task-based design  Guidelines in task-based design:  Analysing work tasks  Envisioning work tasks  Designing interaction  Conclusions

S. Wilson and P. Johnson 7 CADUI' June FUNDP Namur Task-Based Design Existing task description(s) Envisioned task description Interface design Analysis of work Design of work Design of interaction Method Models Processes Tools

S. Wilson and P. Johnson 8 CADUI' June FUNDP Namur Guidelines in Task-Based Design  Focus on processes  Developing practical guidance  Motivated by experience Task analysis guidelines Abstract UI model (A) Existing work tasks Envisioned work tasks (B) Envisioned work tasks (A) Interface design (A) Abstract UI model (B) Interface design (B) Guidelines for envisioning work Guidelines for designing interaction Style guides, colour guides, typography etc

S. Wilson and P. Johnson 9 CADUI' June FUNDP Namur Analysing Work Tasks  Analysing and modelling Specific Tasks  Modelling Composite Tasks

S. Wilson and P. Johnson 10 CADUI' June FUNDP Namur Specific Tasks  Identify characteristics of specific tasks first  Use more than one data collection technique  Analyse many different users performing each task  Identify all variations and individual differences in tasks

S. Wilson and P. Johnson 11 CADUI' June FUNDP Namur Composite Task Models  Produce a composite task model from each task description for the same goal  Resolve conflicting descriptions  Identify optional aspects of a task  Identify compulsory aspects of a task  Identify commonalities of behaviour and objects  Identify constraints and dependencies  Identify different objects and typical objects

S. Wilson and P. Johnson 12 CADUI' June FUNDP Namur Envisioning Future Work Tasks  Influences: existing task descriptions, problem statement, requirements, design ideas, design constraints  Scoping the design  Improving the work

S. Wilson and P. Johnson 13 CADUI' June FUNDP Namur Scoping the Design  Identify tasks that can be avoided or are unnecessary  Identify tasks that can be carried out by system  Identify tasks that can only be carried out by user  Identify where user will interact with system to perform a task  Introduce any new tasks

S. Wilson and P. Johnson 14 CADUI' June FUNDP Namur Improving the Work  Identify where sequences of activities can be made easier to perform  Create more powerful objects by combining individual objects  Restructure the task to bring together information required at the same point in the task  Ensure that safety and security procedures are supported

S. Wilson and P. Johnson 15 CADUI' June FUNDP Namur Creating an Interface Design  Influences: task descriptions, requirements, design ideas, design constraints, design guidelines  Task influences:  Task decomposition information  Action and object information  Sequencing information

S. Wilson and P. Johnson 16 CADUI' June FUNDP Namur Task Decomposition Information  Reflect the goal, sub-goal and action decomposition in the interface structure  Group interface components that support closely related parts of the task  Group components either spatially or temporally  Let the lowest level of task decomposition (actions) be the strongest determinant of interface structure

S. Wilson and P. Johnson 17 CADUI' June FUNDP Namur Task Actions and Objects  Use task objects to identify information to be displayed and/or manipulated  Use task actions to identify commands  Use action-object groupings to determine the ways in which information can be manipulated  Support simple objects, and the actions applied to them, by standard widgets  Support complex task objects by a group of standard widgets or by specialised widgets

S. Wilson and P. Johnson 18 CADUI' June FUNDP Namur Task Sequence Information Task Sequence Information  Reflect task sequencing in the dialogue structure  Do not violate task sequencing in the interface design ...But constraints can be relaxed in situations where safety conditions will not be contravened

S. Wilson and P. Johnson 19 CADUI' June FUNDP Namur Conclusions  Importance of design processes in task-based and model-based approaches to design  Practical guidance for designers  Implications for tools and future work