Если у вас возникли сложности с курсовой, контрольной, дипломной, рефератом, отчетом по практике, научно-исследовательской и любой другой работой - мы готовы помочь.
Предоплата всего
Подписываем
Organizing principles of user interface software
At given price point, total CPU power doubles every 18-24 months
Corollary: at a given performance point
price drops fast
2. history of HCI
3. A/B Testing
4. HCI Methods
UCR
empirical
observational
anecdotal
intuition
Wizard of Oz
A/B testing
Six variations on a text label
N = 100K trials / variation; t = 1 week
Think aloud
5. UCD approach
For example, the user-centered design process can help software designers to fulfill the goal of a product engineered for their users. User requirements are considered right from the beginning and included into the whole product cycle. These requirements are noted and refined through investigative methods including: ethnographic study, contextual inquiry, prototype testing, usability testing and other methods. Generative methods may also be used including: card sorting, affinity diagraming and participatory design sessions. In addition, user requirements can be inferred by careful analysis of usable products similar to the product being designed.
All these approaches follow the ISO standard Human-centred design for interactive systems (ISO 9241-210, 2010).
The ISO standard describes 6 key principles that will ensure a design is user centred:
6. User Interviews
How to interview people
Possibly your most important skill : hear about people’s experiences, learn their meaning & feelings, discover design opportunities
An interview is a method of asking questions and listening
– Uses a planned interview protocol – a set of questions
– Ask what you can’t observe
I know you are a nursing supervisor. If I followed you through a typical day, what would I see you doing?
7. Flow model
8. Breakdown
9. Consent Form
10. Contextual Design
User-Centered Design process
Goal is to find users: Desires, Intents, Drivers
Key Principles: Extend and support work practice
Work practice: Behaviors, Attitudes, Goals, Intents
Challenges for articulation: Users are experts at what they do
But they can’t articulate what they do
Data are hidden in everyday details
Field interviews: Natural context , Tacit aspects of users’ work practice, Consciously not available for users of what they are doing
Good design is systemic: High-level coherent direction, Design, Structural, Layout, Flow across the system
11. Contextual Inquiry
Contextual inquiry (CI) is a user-centered design (UCD) ethnographic research method, part of the Contextual Design methodology. A contextual inquiry interview is usually structured as an approximately two-hour, one-on-one interaction in which the researcher watches the user do their normal activities and discusses what they see with the user.
Contextual inquiry defines four principles to guide the interaction:
If specific tasks are important, the user may be asked to perform those tasks.
A contextual interview generally has three phases, which may not be formally separated in the interview itself:
Before a contextual inquiry, user visits must be set up. The users selected must be doing work of interest currently, must be able to have the researcher come into their workplace (wherever it is), and should represent a wide range of different types of users. A contextual inquiry may gather data from as few as 4 users (for a single, small task) to 30 or more.
12. Work models
Data from each interview is analyzed and key issues and insights are captured. Detailed work models are also created in order to understand the different aspects of the work that matter for design. Contextual design consists of five work models which are used to model the work tasks and details of the working environment. These work models are [2]:
13. Interview question types
The final interview question
What should I have asked you that I didn’t think to ask?
That’s all I wanted to ask you. Anything you want to add?
(or)
How did the interview go for you? Keep the recorder on!
Illustrative questions
Some nurses hate working at night, but others like the flexibility. What’s your experience?
Role-playing questions
Suppose I were a new nurse just coming to this hospital, and I asked you what I should do to succeed. What would you tell me?
Preparatory questions
We’ve been talking about your job. Now I want to ask you about how you got to be where you are today.
14. Behavioral questions
Behavioral questions
“Can you describe a recent occasion when
a patient alert was sounded, and tell me
what you did?”
15. Close ended questions
Closed-ended (“forced choice”)
Closed ended questions are those questions, which can be answered finitely by either “yes” or “no.” Also known as dichotomous or saturated type questions. Closed-ended questions can include presuming, probing, or leading questions. By definition, these questions are restrictive and can be answered in a few words.
16. Interview protocol
Here are our interview protocols we used when we conducted our interviews with lobbyists. The forms below list the questions we asked when we conducted our interviews. Respondents were assured anonymity, so we cannot release their individual responses. Information from the interviews was used, however, to guide our research on the web, through the Library of Congress, and in subsequent interviews
Decide whom you will interview
Plan your interview protocol
Ethical checklist:
Test your protocol and revise
17. Knowledge question
Knowledge questions
“If a patient says she is in pain, what do
you look for?”
18. open-ended question
Open-ended
19. posture in interviewing
The idea is that we don't just think with our minds, we also think with our bodies
• A good posture to empathize with your interviewee is. . . their posture
• Best posture to understand your interviewee is. . their posture
• Mimicry works but NOT if the other is socially incompetent or resistant
20. Rapport
Everything depends on trust and rapport. So what do you do first?
[Rapport occurs when two or more people feel that they are in sync or on the same wavelength because they feel similar or relate well to each other.] by Wikipedia
21. screener
22. users context
23. master apprentice relationship model
24. audience for competitive analysis
25. competitive analysis methods
Understand the marketplace
– Products become successful for a reason
– Provide direction to management
– Exploit strengths and weaknesses
Build domain knowledge
– Learn best practices
– Identify common patterns, language
Research phase
– Study existing products to get the lay of the land
Evaluation phase
– See how your product/prototype compares to existing products
Define goals
Identify competitors
Analyze products
Summarize products
Recommend courses of action
Who is your audience?
– Design team
– Management
– External stakeholders
What is your deliverable?
– Presentation
– Walkthroughs
– Executive summary
Step 0: Define goals
Who is your audience?
– Design team
– Management
– External stakeholders
What is your deliverable?
– Presentation
– Walkthroughs
– Executive summary
Talk to your users
TiVo, Roku, Boxee, Apple TV, Samsung Smart TV…
Chat competitors
Step 2: Evaluate products
Metrics
– Feature checklist
– Walkthrough
– Expert review
– User testing
Dependent on time, budget, access to competing products, and goals
Step 3: Summarize products
Brief summary highlighting strengths, weaknesses, and unique features of each product
Include illuminating quotes, screenshots, and/or videos
Step 4: Recommend courses of action
Executive summary
If your product was analyzed, how did it compare?
Your audience will recall only a couple of recommendations and takeaways; make sure they’re the right ones
26. CA steps
27. Literature review
28. Affinity diagramming
Affinity= Likeness based on relationship or causal connection (from Merriam Webster)
Build from the bottom-up
Labeling Steps
Write blue labels
2. Brainstorm high level themes and write temporary green labels
3. Restructure the wall (if needed)
4. Work on one theme at a time
5. Write pink labels
6. Finalize green labels
Data from individual customer interviews are analyzed in order to reveal patterns and the structure across distinct interviews. Models of the same type can be consolidated together (but not generalized—detail must be maintained). Another method of processing the observations is making an affinity diagram ("wall"), as described by Beyer & Holtzblatt [1]:
Beyer & Holtzblatt propose the following color coding convention for grouping the notes, from lowest to highest level in the hierarchy [1]:
29. blue labels
Blue Labels
2-5 affinity notes per blue label
30. green labels
Green Labels
31. groupping notes
32. pink labels
Pink Labels
Reveal key issues
• Tell you what matters most about blue labels
• Draw people in to read each section
2-5 blue labels for each pink one
34. severity ratings in uars
Essay skatannui s neta
Human Computer Interface (HCI) design is really a subset of User Interface (UI) design. HCI as the name suggests, focuses on how easily or difficult it is to interact with computers to achieve the desired results. Whereas UI is anything which makes a device, equipment, object, etc, behave in such a way that it allows the user to achieve a desired outcome.
Putting it simply, HCI is a subset of UI. Following are 2 are examples of HCI scenarios:
Web designers tend to focus on the way IA is setup for a web site, the positioning of the navigation elements, and how easy or difficult it is for site visitors to get the information they are looking for, or achieve any other results they desire, e.g. purchase a book online.
Computer manufacturers are always trying to make it easy to interact with their devices, e.g. via the use of input/output peripherals such as keyboards, mouse, micophone, screens, speakers, etc. These peripherals which we take for granted are actually UIs which we use to interact with our computers towards a desired outcome, e.g. in my case now, typing this reply to you, Avinash. =)
Let's move on to UI. This covers a wider spectrum than just computers, applications and websites. Let's take something as simple as a door. The door knob is an example of a UI. To open or close the door, we use the door knob. Or in some cases, we use door handles instead.
Another example of UI... There are switches on ovens which allow us to control the temperature of the oven, and whether we want the oven fans to be on or off. These switches are the UI which lets us interact and control the oven. This is similar to light switches, which are interfaces allowing us to control our indoor or outdoor lighting manually.
I would say understanding the UI designs that exist around us, in our everyday lives, is very important towards practicing good HCI design. As a web designer and instructional, I look towards day-to-day familiar metaphors which then become intuitive and/or self-explanatory when seen onscreen.
Hope this helps you.