Goal Directed Design -I

Human Machine Interaction

•User Interface is necessary for almost all Types
of Systems
•Systems may be
•100% Hardware
•Software
•Supporting Equipments
• Above Systems can be
called as Digital Systems
 Use Usage and Usability
•NINE Basic Questions
• Who are the Users of the systems
• What are the tasks that will be carried out by the user
• What are user’s Expectations about documents
• What functions should be incorporated
• What information user want to process
• How users think the system should work (Story type)
• What are the extreme Environments
• Is there any parallel processing required (reconciliation)
• Are there any special input devices need to be configured
 What Mistakes we Normally do
•We expect users to think like Computer
•W e ask to perform Difficult operations
•( May Not be difficult for Developers)
•Resultant System may not be as put in
requirements
•User is Ignored
 Design

“Design is the process that consist of user

oriented approach where all meaningful
activities are systematically framed together
and utmost importance is given to person who
is going to use the system”
Activities Involved
( Software Engineering approach)
•Understanding User’s
Requirement
•Understanding Purpose of the
user to use the system
•Understand Work Environments
 Program
Build
Users
and Test

Delivered

Programmer

Software Evolution Process Phase 1

 Phase II
Program
Manager as
Specified Refinement Users

Delivered

Initiation Phase Programmer

 Phase III
Manager
Refinement

Look and Feel

AAL is
WELL
Delivered
Initiation
Phase Programmer

Test Plan

Test Engineer
Test Tool
Manager Phase IV Users

Test & QA
Initiation
Phase
Design Test Engineer
Specs

Programmer

DESIGNER
 Desire Viability and Capability
Desire
l

Designer
What people need
l

Viable
l

How Business can be sustained

l

Capability
l

What we can Build

l

Manager

Technical Expert
 Recognize the Goals

What are the Goals

l

How to Identify them

l

How we can confirm the sure Goals

l

Are Goals common to all

l

Can They be different Each Time

l
 Design Prototype

It is User Friendly
l

It Provides Feasibility
l

User is Able to effectively operate the system

l

User level satisfaction is guaranteed

l
 Real Life Scenarios

Automated Customer Care Interafce using the Telepho

l

Information Kiosk for Bank Customers and ease of us

l

Self Checkout Counter for Departmental Store

l
 GOAL Directed Design process
Customer

Systematic Research and Review Report

Interface Designs and Prototyp

System Development
 Goal Directed Design process

Requirements
Research Modelling Refine
Framework
Support
 Goal Directed design
l
Research:
l
Bridge the Gap : User and Developer
l
Field Survey
l
Contextual interview and Observations
l
Who are potential Users
l
Competitive Products
l
persona in modeling and Constraint
 Modeling Phase
l
Information Flow and Work Flow
l
Attitude Aptitude and Goals
l
Motivations to do the Best
 Requirement Gathering

l
Required Connectivity between user and other m
l
Most Important tasks to be carried out

Framework Phase
l
System behavior.
l
Visual Design as well as Physical form of Desig
l
Interaction design.
 Refinement and Support

l
Design Details and Implementations
l
Storyboard in high detail
l
Alteration of shortcomings in earlier stages
l
Provide a Goal oriented design
l
Support will have continuous improvement ti
l
level acceptance
Implemenation model and Mental Model
Implementation Model V/s mental Model
 User Levels
l
Beginner
l
Expectations
l
Intermediate
l
Expectations
l
Expert
l
Expectations
 Typewriter Example using QWERTY

LH Practice
l
RH Practice
l
ASDF JKL;
l

l
DO THIS 100 LINES AND TEST SPEED AT 101ST LINE
l
Or practice Aroh and Awaroh for Raga in words and in a
l
Or play bits for 90 seconds on drums
Bell Curve
Experts
Experts
Qualitative v/s Quantitative
 Qualitative

More Refined or superior than Quantitative



More Informative and communication oriented Product



Data Analytics may benefit


Examples
SME Interview
 Persona and Goal

Personas help us to determine, communicate,

build consequences, measure, and
contribute the design quality of the product.

It also helps to fit the product as per the

experience level of the user.
 Steps in constructing Personas

Identify Behavioaral Variables



Map Interview


Identify behavior pattern



Synthesize characteristics


Check Redundancy and completeness



Designate persona Types


Case Study and Questions