Interactive Systems Design: Understanding the Nature

Nature of Interactive Systems Design

• This is about understanding interactive systems design's nature.
• It encompasses four integral processes: understanding, design, representation, and evaluation.
• Evaluation is central to the design process at every design step.
• Design incorporates scenarios, personas and methods based on them.

Overview on Design process

• Design is a creative process focused on producing something new.
• Designer disciplines develop a variety of design process methods and techniques.
• Mature fields define examples of good design for designers.
• These examples, whether fantastic or poor, aid designer learning.
• Designer disciplines encounter design limits
• For example, designed independently or fit into legal/other standards.

Understanding

• Understanding consists of requirements determination, such as
  • System functions
  • Appearance
  • Integration of product, system, or service requirements.
• Designers explore people, activities, and contexts relevant.
• This allows design of a system that meets the demands of its users.

Requirements

• Product requirements: two categories: functional and non-functional.
• Functional requirements explain the system's function and limitations.
• Analysis forms decision-making to determine priorities and timing.
• Functional limitations exist due to technical feasibility that can affect sequencing.
• Legal/organizational constraints might make a design unprofitable.

Conceptual Design

• Design activities focus on conceptual and physical aspects.
• Conceptual design defines the system's abstract components.
• Physical design focuses on tangible elements.
• Conceptual design emphasizes information and functions for success.
• It is important to concentrate on the 'what', not the 'how', forgoing distribution assumptions.
• Conceptual and physical have no clear intersection, with varying 'conceptualness' degrees.

Physical Design

• It specifies how things will function.
• Appearance detailing and product feel.
• Structuring of interactions into a logical order.
• Division and display of functions and knowledge and information between humans and devices.
• Operational, representational and interaction designs are the three physical design components.

Operational and Representational Design

• Operational design outlines system operation and content arrangement.
• Functional activities focus on processes and the flow of activities in the system.
• Representational design involves determining colors, forms, measurements & info layout.
• Representational design focuses on style and aesthetics as they relate to user feelings.
• Some systems aim for engaging interactions, with variability in the level of amusement.

Interaction Design

• The process designates the allocation of functions to users and technology and sequencing of interactions.
• Allocating roles impacts system usability.
• Designers create tasks based on the defined functions.
• Knowledge and action distribution between users/tech alters the experience.
• An example is creating a phone call with functions as: desire, connect, enter number and establish connection.
• With landlines, picking up receiver to dial led to automatic connection upon complete number entry, unlike smartphones.

Representation

• Visualization helps designers clarify ideas and allows evaluation of those ideas.
• Representation relies on suitable media rendering.
• The medium meets process stage, target audience, resources & designer intention.
• Representation techniques enable a creative rendition of abstract ideas.

Evaluation

• Assessment is integral to representation since evaluation methods depend on the representation.
• Assessment parameters are dependent on the representation.
• Any design activity undergoes/follows assessment.
• Examples:
  • Designer confirms design is complete/accurate.
  • Higher-level design descriptions undergo client or abstraction assessments with colleagues.
  • Formal evaluations occur with functional prototypes designed for future users.
• Wide array of assessment methodologies depend on context.
• Techniques should reflect representation, considerations, and stakeholders.

Implementation

• Implementation or production of the design (and planning and management) is often skipped.
• Every product requires created/tested software.
• The databases need designing, populating, and validating.
• Systems must ensure requirements satisfaction before formal release.
• Implementation is a broad topic beyond design, taking a lot of time and finances.

Personas and Scenarios Development

• Designers must consider PACT elements to guide design.
• System users are represented by personas, profiles or archetypes.
• User scenarios describe activities and context.
• Different technologies can reach the system's objective using different scenarios.
• Personas are developed during understanding alongside analysis methods.
• Personas & scenarios develop together with insights in desired user activities.

Personas

• These are specific depiction of system/service users.
• Personas include a name, context, important goals, and aspirations.
• Personas utilize a system that achieves desired goals.
• Designers should comprehend:
  • Design isn't for self.
  • Use personas to represent the user.
  • Walk in another's ,,shoes,,.

Utilizing Personas

• A diverse workforce needs diverse personas.
• For the Robert Louis Stevenson website, personas will cover:
  • German teacher
  • British lecturer
  • African child
  • An American with intrest in Stevenson
• Target groups have various goals, varying by method of web page implementation.

Example Assistants

• Developing an assistant that is: multi-modal, intelligent, personalized and accessable to internet access needed.
• Fitness and wellness assistant offers aid in areas of wellness.
• A two-day workshop designed for different personalities with needs.
• Three personalities were developed to see fitness routines levels with different needs.
• Motivation differs with any personality given unique scenarios.
• Simon needs motivation, limiting television viewing ahead of routines.
• Boyan wanted a social connection.
• Given values will be discussed for unique values.

Persona Simon Sample

• 46 year-old.
• Too much driving, eating but now devorced.
• Is very unhealthy and kids got him a health assistant
• First went to the hospital for angina.
• Kids were concerned for his diet.
• The kids bought him a health trainer to work out and balanced diet.
• He chose a harsh instructor for self discipline named Alf.
• Set biometric paramitres to allow coach to give suggestions.
• Trainers objective is to give owner health.
• Af takes actions based on actions.

Sample Persona Marija

• A 23 Year Old Aerobics Instructor
• Training Hard For A Marathon
• Her training partner moved
• Manily pro-acive
• Anistant will motivate and improve her.
• The assiatnt will be their to set the distance, improve speed and and improve marathon in 4 hours. _ Coach helps when soical life interferes.
• Coach needs to point out inproper things.
• Marthon is now motivated by coach.

Bojan's Personality

• Accountant 32 years old and not kids.
• Dog diew that was exrersized.
• Was thicc until dog died.
• Played sport until unov, has big social life and wants to loose weigth
• Coach makes the procces quick.
• Uses path and makes choices.
• Changes with a tap.
• Does not allow his sleep.

Scenarios

• Narratives that explain activities in context with technology.
• Used in the design for interactivity.
• Scenarious used by computer interaction
• Senarious have become important

Photopal assistants

• Study of assistant with digital photo
• He orainize photos etc
• Talks with uisers to remid past eents.

Photopal example

• A scene was filmed where someone was loooking for photos.
• Feature is to test entry to an assistant.
• Interactions involve touch or voice
• Touching allows the image sclaing is less importamt
• Is possible but 3 by 4 is use

Using Scenarios in Design

• Scenarios and associated personas are key for interactive systems.
• Helpful for understanding, depiction, appraisal, and conceptual/design elements.
• Four scenario types exist:
  • Stories
  • Conceptual scenerios
  • Concete ones
  • Use cases

Categories of Scenarios to Utilize in Design

• Vignettes are typical occurrences to an audience.
• Conceptual scenarios are general descriptions, removing details.
• In concrete scenarios, specific choices and tech expand conceptual scenarios.
• If completed, they become user cases.
• Scenarios aid the understanding of current routines and challenging problems.

Roles of Storys and Scenario

• Location of these in processes are shown.
• Lines will help conncet the types.
• Story will help people be presented.
• Each connevts to many other senarious
  • Designer abstracted into details