The interaction 1.1

THE INTERACTION AND ITS DESIGN Module 5

Course Intended Learning Outcome

  • Construct an interface design in line with the interaction principle.

Topics

a.
b.
Interaction
Models of Interaction
Interaction Designt

Interaction

Topic 1

The Interaction

  • Interaction Models: Help understand what occurs during interactions and identify potential difficulties.

  • Ergonomics: Analyzes physical characteristics of interactions to determine their effectiveness.

  • Interaction Styles: Affect the communication and dialog between the user and system.

  • Context: The social and organizational context affects both users and systems during the interaction.

What is Interaction?

  • Definition: The communication between two or more participants:

    • User: Individual utilizing the system.

    • System: The interactive technology being used.

Models of Interaction

Topic 2

Terms of Interaction

  • The primary aim of an interactive system is to assist the user in achieving objectives within a specified application domain.

  • Domain: Refers to the area of focus; for example, graphic design.

  • Goal: What the user aims to achieve; e.g., creating a solid red triangle.

  • Task: The methodology for accomplishing the goal, broken down into operations/actions; e.g., selecting the fill tool and clicking over the triangle.

  • Task Analysis: Involves identifying the problem space concerning the user of the interactive system, articulated through the domain, goals, intentions, and specific tasks.

  • The system and user use languages that express concepts relevant to the domain.

  • Core Language: The system's language detailing computational aspects of the domain relevant to its state.

  • Task Language: The user's language describing the psychological attributes relevant to the user state.

Donald Norman’s Model

  • Execution and Evaluation: Known for being influential in Human-Computer Interaction due to its intuitive grasp of user-computer interactions.

  • Focuses primarily on the user's perspective of the interface.

  • The interactive cycle consists of two phases: execution and evaluation.

    • Execution: Involves the user performing actions.

    • Evaluation: Involves the user assessing the outcome of those actions in relation to their goals.

Seven Stages in Norman's Model of Interaction

  1. User establishes a goal.

  2. User formulates intention.

  3. User specifies actions at the interface.

  4. User executes action.

  5. User perceives system state.

  6. User interprets system state.

  7. User evaluates the system state concerning the initial goal.

Execution/Evaluation Loop in Norman's Model

  • The process can be visualized as an ongoing loop where:

    • User establishes the goal,

    • Formulates intention,

    • Specifies actions at interface,

    • Executes action,

    • Perceives system state,

    • Interprets system state,

    • Evaluates system state concerning the goal.

Using Norman’s Model

  • Some systems have varying levels of usability, which can be described by:

    • Gulf of Execution: The discrepancy between the user's intended actions to achieve a goal versus the actions the system permits.

    • Effective interface minimizes this gulf by ensuring that system actions align with user intentions.

    • Gulf of Evaluation: The disparity between the actual state presented by the system and the user's expectations.

    • A small gulf signifies ease of assessment by the user, while a large gulf suggests difficulty in understanding system feedback.

Human Error

  • Slips: Understanding of system/goal is correct, but actions taken are not (e.g., accidental actions).

  • Mistakes: User may not even have the correct goal in mind.

  • Solutions:

    • Slips: Addressed through better interface design.

    • Mistakes: Mitigated through improved understanding of the system.

Abowd and Beale Framework

  • An evolved framework building upon Norman's model, consisting of four components:

    1. User

    2. Input

    3. System

    4. Output

  • Each component has its unique language; interaction depends on translations between these languages.

  • Problems in interaction stem from issues in translation between components.

General Interaction Framework Steps

  1. User formulates goal and task to achieve it.

  2. User interacts with the system via input, translated into operations in the system's core language.

  3. System adapits according to operations; execution phase concludes, leading to new output representing the system's state.

  4. User observes output to evaluate success relative to the initial goal, thus completing the interactive cycle.

Abowd & Beale’s Model Summary

  • User intentions translate into interface actions, which lead to alterations in the system state, reflected in the output display, and interpreted back by the user.

  • This framework facilitates understanding interaction broadly, transcending electronic systems, and allows for comparative system assessments.

  • Abstraction for defining interactive elements beyond contexts.

Interaction Design

Topic 3

Interaction Design Overview

  • Interaction design focuses on developing interactive products and services, encompassing considerations beyond the mere development of items to how users will engage with them.

  • Emphasizes close examination of users’ needs, limitations, and contexts, thereby optimizing design to cater to specific requirements.

Dimensions of Interaction Design

  • Words: Text elements such as button labels provide users with essential information.

  • Behavior: Defines how products respond to user inputs and provide feedback.

  • Visual Representation: Encompasses graphical elements such as images, typography, and icons that facilitate user interaction.

  • Time: Refers to media that changes over intervals, such as animations, videos, and sounds.

  • Physical Objects/Space: Involves the mediums through which user interaction occurs, e.g., a laptop using a mouse, or a mobile phone using touch.

Important Questions Interaction Designers Ask

  • What interactive mechanisms do users have?: Determines possible user actions with the interface.

  • What visual cues exist regarding appearance and function?: Ensures functional intuitiveness and simplicity.

  • Do error messages assist users?: Aids in preemptively addressing issues through corrections or explanations.

  • What feedback mechanisms follow user actions?: Critical for prompts that confirm tasks carried out.

  • Are interface elements adequately sized?: Ensures user-friendliness and accessibility.

  • Are standard formats applied?: Utilizes familiar designs to enhance product learnability and user experience.