Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Due today
Scenarios Decomposing paper
Next class
Deliverable: Requirements
Introduction to Software Architecture by Garlan and Shaw (read and review only pages 1-16)
Put the user in control Keep the users memory load controlled Consider issues of consistency
What I really would like is a system that reads my mind. It knows what I want to do before I need to do it and makes it very easy for me to get it done. Thats all, just that.
3
Control
Whos in Control?
Does user adapt to computers model of task? Does computer adapt to users model of task?
Consider the novice user Consider the knowledgeable, intermittent user Consider the knowledgeable, frequent user
Consistency
Use the same design standard throughout all screens Use the same input techniques throughout all screens
Iterate through these, with each pass elaborate additional requirements and resulting design
User analysis
Interview the users or representatives of the users Interview sales, marketing, or support staff about user characteristics
Environment analysis
What will be the physical location of the sw? Will user be sitting, standing, walking? Will user be dedicated to this task/multiusers required for this task? Will there be noise, light, or space impairments?
11
Task analysis
What tasks will be done while user is working? What work is performed in special circumstances? What special domains are used during work? What is the sequence of workflow?
12
Using use cases - identify tasks and subtasks Example - computer-aided design for interior design Tasks
Furniture layout Fabric selection Wall/widow coverings sel. Presentation to user Costing Shopping
13
14
15
Format of content
16
17
18
responsiveness
Length of response time
1 sec acceptable More than that - use progress bar and busy icon
Variability
1 sec is better than from 0.2 sec to 3.0 sec
19
20
21
Test the UI
Review material from M. Rettigs paper Prototyping For Tiny Fingers
22
Summary
Weak UI may cause failure of acceptance of system Follow 3 principles of UI design
User in control Reduce memory load Consistency
Development involves
Analysis (user, task, environment) Design (use cases drive sketches) Evaluate and iterate
23
Bjarne Stronstrup
I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone.
24
Threading
User thread services UI
collects events, changes control state, posts events not to be used for game action!
25