Model based design.

Slides:



Advertisements
Similar presentations
Requirements gathering
Advertisements

Task-Centered User Interface Design who are the users? what are the tasks? plagiarize! iterative design –rough descriptions, mock-ups, prototypes test.
Identifying, Modifying, Creating, and Removing Monitor Rules for SOC Ricardo Contreras Andrea Zisman
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
Chapter 4 Design Approaches and Methods
Agile Usability Testing Methods
USABILITY AND EVALUATION Motivations and Methods.
Methodology Overview Dr. Saul Greenberg John Kelleher.
What is Interaction Design?
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Empirical Methods in Human- Computer Interaction.
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
Evaluation Through Expert Analysis U U U
Design Process …and the project.
Evaluation Methods April 20, 2005 Tara Matthews CS 160.
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
Usability and Evaluation Dov Te’eni. Figure ‎ 7-2: Attitudes, use, performance and satisfaction AttitudesUsePerformance Satisfaction Perceived usability.
©2011 1www.id-book.com Analytical evaluation Chapter 15.
Predictive Evaluation
SWE 316: Software Design and Architecture – Dr. Khalid Aljasser Objectives Lecture 11 : Frameworks SWE 316: Software Design and Architecture  To understand.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Multimedia Specification Design and Production 2013 / Semester 1 / week 9 Lecturer: Dr. Nikos Gazepidis
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
Chapter 11 Analysis Concepts and Principles
Comp 15 - Usability & Human Factors Unit 8a - Approaches to Design This material was developed by Columbia University, funded by the Department of Health.
User-Centered System Design. - a philosophy of user interface design introduced by Don Norman & Steve Draper in 1986.
Human – Computer Interaction
Lecture 7: Requirements Engineering
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Software Engineering User Interface Design Slide 1 User Interface Design.
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.
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
Evaluation Methods - Summary. How to chose a method? Stage of study – formative, iterative, summative Pros & cons Metrics – depends on what you want to.
Cognitive Walkthrough More evaluating with experts.
Chapter 15: Analytical evaluation. Aims: Describe inspection methods. Show how heuristic evaluation can be adapted to evaluate different products. Explain.
Introduction to Evaluation “Informal” approaches.
Fall 2002CS/PSY Predictive Evaluation (Evaluation Without Users) Gathering data about usability of a design by a specified group of users for a particular.
User Interface Evaluation Introduction Lecture #15.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Searching and Using Electronic Literature III. Research Design.
 System Requirement Specification and System Planning.
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.
Cognitive Informatics for Biomedicine – Chapter 5
User Interface Evaluation
Methodology Overview basics in user studies Lecture /slide deck produced by Saul Greenberg, University of Calgary, Canada Notice: some material in this.
SIE 515 Design Evaluation Lecture 7.
Chapter 1: Introduction to Systems Analysis and Design
Chapter 5 – Cognitive Engineering
3 Research Design Formulation
Topic for Presentaion-2
CS701 SOFTWARE ENGINEERING
HCI in the software process
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
Introduction to Software Engineering
Informatics 121 Software Design I
Informatics 121 Software Design I
Lecture Software Process Definition and Management Chapter 3: Descriptive Process Models Dr. Jürgen Münch Fall
SBD: Analyzing Requirements
Desirable “-abilities” in HCI
Usability Techniques Lecture 13.
The interaction.
HCI in the software process
Interaction design basics
Chapter 1: Introduction to Systems Analysis and Design
Comp 15 - Usability & Human Factors
Measurement What is it and why do it? 2/23/2019
Evaluation.
Human Computer Interaction Lecture 14 HCI in Software Process
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

Model based design

Objective The interactive system design consisting of several stages such as Requirement Specification Design Prototyping Evaluation The interactive system design is highly iterative

The process of design (recall from L15) interviews ethnography what is there vs. what is wanted guidelines principles standards dialogue notations precise specification architectures documentation help evaluation heuristics scenarios task analysis what is wanted analysis design implement and deploy prototype

Objective The iterative life cycle is Time consuming and Also requires cost (for coding and testing) It is always good if we have an alternative method that reduces Time, effort and cost required for the design life cycle Model-based design provides one such alternative

Motivation Suppose you are trying to design an interactive system First, you should identify such as Requirements (“Know the user”) Contextual Inquiry Which are time and cost consuming and tedious process Instead of going through the process, it would have been better if we have a “model of the user” Which is known as model based design

Idea of a model A ‘model’ in HCI refers to “A representation of the user’s interaction behavior under certain assumptions” The representation is typically obtained form extensive empirical studies Collecting and analyzing data from end users The model represents behavior of average users, not individuals It saves lots of time, cost and effort

Types of model 1. Descriptive/ prescriptive models It describe user behavior during interaction in qualitative terms. An example is the Norman’s model of interaction These models help in formulating (prescribing) guidelines for interface design

Types of model 2. Predictive engineering models: These models can “predict” behavior of a user in quantitative terms. An example is the GOMS model (to be discussed later in this module) GOMS model can predict the task completion time of an average user for a given system.

Predictive engineering models The predictive engineering models used in HCI are of three types Formal (system) model Cognitive (user) model Syndetic (hybrid) model

Predictive engineering models Formal (system) models The interactive system is represented using ‘formal specification’ techniques For ex: ‘state transition networks’/’system state space’ Cognitive (user) models These models capture the user’s thought (cognitive) process during interaction For ex: A GOMS model tells us the series of cognitive steps involved in typing a word Syndetic (hybrid) model Complex and rarely used

Model based design limitations The models can not capture individual user characteristics It only models average user behavior

Summary Model-based design reduce the need for real users in interactive system However, they can not completely eliminate the role played by real users It can be employed in the initial design stages

Descriptive/ prescriptive models: Donald Norman’s model Seven stages user establishes the goal formulates intention specifies actions at interface executes action perceives system state interprets system state evaluates system state with respect to goal Norman’s model concentrates on user’s view of the interface