HCI Midterm Set 1
Parallel
In an ideal world, the design engineers and the software engineers would work in _______?
Analysis
UX phase involved with understanding user work and needs. Requirements are extracted from contextual data. Models including how work gets done, how roles interact in the work domain, and the artifacts are presented in this phase.
Work
Set of activities that people undertake to accomplish goals. Some of this includes system usage.
Work Activity Note
Used to document a single point about a single topic, or issue as synthesized from the raw contextual data. Work activity notes are stated as simple and succinct declarative points in the user's perspective.
False
True/False: The UI Often accounts for less than half of the code of the overall system.
Vertical Prototype
Type of prototype that contains as much depth of functionality as possible in the current stage of the project
Horizontal Prototype
Type of prototype that is broad in the features it incorporates but offers less depth in its coverage of functionality
Local Prototype
Type of prototype that represents the small area where horizontal and vertical slices intersect. Depth and breadth both limited is used to evaluate design alternatives for a particular isolated interaction detail.
T Prototype
Type of prototype where much of the design is realized at a shallow level, but a few parts are done in depth. Combines the advantages of horizontal and vertical prototypes, offering a good compromise for system evaluation.
Usability, Usefulness, and Emotional
What three factors contribute to user experience?
Multidisciplinary
What type of team is more likely to capture all necessary data and more likely to make the best sense of data during analysis?
Work and Needs
Wheel Lifecycle Template begins with an understanding of what two things?
Design Ideas, Questions, and Data Holes
During the WAAD Walkthrough, what are three things to be taking notes on?
Contextual Inquiry
Early system or product UX lifecycle activity to gather detailed descriptions of customer or user work practice for the purpose of understanding work activities and underlying rationale. Goal is to improve work practice and construct and/or improve system designs to support it. Includes interviews of customers and users. Tells exactly what users do, need, and think.
Usability
Effectiveness, efficiency, productivity, ease-of-use, learnability and pragmatic aspects of user satisfaction.
Work Domain
Entire context of work and work practices in the target enterprise or other target usage environment
Ethnography
Essential Foundation for Contextual inquiry. Its about studying a group of humans or more intelligent animals in a social setting.
System Concept Statement
A concise descriptive summary of the envisioned system or product stating an initial system vision or mandate; the mission statement for the project. Typically 100 to 150 words in length. Where the project starts even before contextual inquiry. Answers: What is the system name, who are the users, what will the system do, what problems will the system solve, what experience will the system provide to the user?
Flow Model
A diagram giving the big picture or overview of work, emphasizing communication and information flow among work roles and between work roles and system components within the work practice of an organization. "Who does what and how people to communicate to get it done"
Work Activity
Comprised of sensory, cognitive, and physical actions made by users in the course of carrying out the work practice.
Existing
Contextual Inquiry and Analysis is about the existing way or the envisioned way and work practice?
Phenomenological Aspects of Interaction
Cumulative effects of emotional impact considered over the long term, where usage of technology takes on a presence in our lifestyles and is used to make meaning in our life.
User Class
Description of the relevant characteristics of the user population who can take on a particular work role. Includes characteristics such as demographics, skills, knowledge, experience, and special needs.
Concept Model Design
Design that focuses on navigation, but includes high-level design standards that present the architecture visually are generated.
UX practitioners iterate early and frequently.
Differences between UX and SE design models?
Presence
Kind of relationship with users in which the product becomes a personally meaningful part of their lives.
Model-Driven Contextual Approach
Model approach that is guided by your experience in order to make data collection "more efficient"
Data-Driven Model Approach
Model approach that operates without any presuppositions about what data will be observed. There are no predefined data categories to give hints about what kind of data to expect.
Usability Engineering Lifecycle
Phase consisting of a structured top-down iterative approach to software user interface design. Design is driven by requirements data from a requirements analysis phase.
Prototyping
Phase done in parallel with design. Where design alternatives are realized.
True
True/False: Contextual Analysis does not directly yield either requirements or design.
Design
Phase involving the creating of interaction design concepts. Involves creative thinking, brainstorming, and sketching of new design ideas which leads to representation of mental models, conceptual design, and design storyboards. Can include physical mockups of design ideas.
Evaluate
Phase where you verify and refine interaction design. Employ rapid evaluation methods where design meets usability and business goals.
Functionality
Power to do work seated in the non-user-interface computational features and capabilities.
Iteration
Process in which all or part is repeated for the purpose of exploring, fixing, or refining a design or the work product of any other lifecycle activity. "Wash", "Rinse", and "Repeat"
Think Aloud Technique
Qualitative data collection technique in which user participants verbally externalize their thoughts and their interaction experience, including their motives, rationale, and perceptions of UX problems.
Lifecycle
Structured framework consisting of a series of stages and corresponding activities such as analysis, design, implementation, and evaluation that characterize the full evolution of an interaction design or a complete system or product. Suggests a skeleton structure on which you can hang specific process acitivites.
Data Bin
Temporary Repository to Hold Data. Each bin corresponds to a different data category or contextual data topic.
Work Roles
The first thing to start doing as you talk with customers is to identify what?
True
True/False It is better to shadow a single user over a longer time period rather than several users over a short time.
False
True/False You should always interview alone.
Work Practice
The pattern of established actions, approaches, routines, conventions, and procedures followed and observed in the customary performance of a particular job or carry out the operations of an enterprise.
Usefulness
The system of functionality that gives the ability to use the system or product to accomplish the goals of work.
Contextual Analysis
The systematic analysis - identification, sorting, organization, interpretations, consolidation, and communication of the contextual user work activity data gathered in CI, for the purpose of understanding the work context for a new system to be designed.
Work Domain Complexity
The term referring to the degree of intricacy and the technical nature of the corresponding field world.
User Experience
The totality of the effect or effects felt by a user as a result of interaction with, and the usage context of, a system, device, or product including the influence of usability, usefulness, and emotional impact during interaction, and savoring the memory after interaction.
True
True/False: A user experience cannot be designed, only experienced.
Work Activity Affinity Diagram
Used to sort and organize work activity notes in contextual analysis, pulling together notes w/ similarities and common themes to highlight common work patterns and shared strategies across all users.
Limited functionality, many support calls, requests for features that exists, and competitor's selling better products
What are signs of poor user experiences?
Coordination, collaboration/communication, dependency & constraint enforcement, and synchronization
What are the foundations for success in SE-UX development?
Interviewing and Observing
What are two methods used to gather data?
Human user and computer system come together to accomplish something
What is HCI?
Actual work practice, problems, and work context
What should be observed?
Fail to listen to users
Where do organizations with a predominant software engineering culture fall short of?
Virginia Tech
Where was HCI Born?
Usability Analyst
Which of the UX team roles would be associated primarily with the task of verifying and refining interaction design?
Single user in a single role
Work activities within a product design context are centered on?