Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.

Slides:



Advertisements
Similar presentations
A Framework for Agile Instructional Development Sharon E. Bratt, PhD. Grant Macewan University.
Advertisements

References Prof. Saul Greenberg, University of Calgary, notes and articles INUSE 6.2 and RESPECT 5.3 Handbook Prof. , University of , Notes and articles.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Software Development Life-Cycle Models
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
Agile Usability Testing Methods
Alternate Software Development Methodologies
THE PROCESS OF INTERACTION DESIGN
CS 5150 Software Engineering
The Process of Interaction Design. Overview What is Interaction Design? —Four basic activities —Three key characteristics Some practical issues —Who are.
The Process of Interaction Design
A Prototyping Lifecycle. The Waterefall Model and Prototyping 4 As early as the 1980’s the classic “Waterfall model” of software development was criticised.
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Software Engineering Incorporating Interface Design Into Software Engineering.
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
COMP 350: Object Oriented Analysis and Design Lecture 2
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
An Agile View of Process
Software engineering Process models Pavel Agejkin.
AgileCamp Presents: Agile Software Development. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Chapter 2 The process Process, Methods, and Tools
1 Agile Methodology & Programming Ric Holt July 2009.
Chapter 4 Agile Development
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Business Analysis and Essential Competencies
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
Interaction Design Process COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 5 Chapter 3 (Heim)
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
©2011 1www.id-book.com The process of interaction design Chapter 9.
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
Software Engineering Saeed Akhtar The University of Lahore Lecture 5 Originally shared for: mashhoood.webs.com.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
1 Human Computer Interaction Week 7 Prototyping. 2 Introduction Prototyping is a design technique where users can be involved in testing design ideas.
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
IXD activities. What is Interaction Design? — a goal-directed problem solving activity informed by intended use, target domain, materials, cost, and feasibility.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
Module 2: What is Agile? Why use it? TLO: Given a DoD program involved in software development, the student will recognize situations where applying agile.
Interface Types and Models Dr. Dania Bilal IS 588 Spring 2008.
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
44222: Information Systems Development
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
User-Centered Design Services for MSU Web Teams Sarah J. Swierenga, Director Usability & Accessibility Center MSU Webmasters 402 Computer Center February.
Chapter 5 Agile Development Moonzoo Kim KAIST
Workshop 4: Developing a one page business case
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Design.
SNS College of Engineering Coimbatore
Software Life Cycle Models
Introduction to Software Engineering
Project Lifecycle and IT Product Life Cycle
User CENTERED DESIGN IB TOPIC 7.
Presentation transcript:

Interaction Design CMU

Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design

The process of interaction design Video: Tim Mott - watching users Paul Bradley - model building, user testing for the mouse

Four threads of technical development 1) Prototyping and Iterative Development 3) Software Psychology and Human Factors 2) New User Interface Software 4) Models, Theories, and Frameworks Software crisis in the 60’s…

Requirement Definition System & Software Design Implementation Unit Testing Integration & System Testing Operation & Maintenance Waterfall Life Cycle Model User involvement Sequential phases Each phase complete before the next

Iterative design process User Testing Design Prototyping Involve users throughout the process Process is highly iterative From linear to iterative processes

Approaches to IxD

General Approaches in IxD 1. Focus on users 2. Find alternatives 3. Use ideation and prototyping 4. Collaborate and address constraints 5. Create appropriate solutions 6. Draw on a wide range of influences 7. Incorporate emotion

Four main approaches to working on interaction design projects User-centered design (UCD) Activity-centered design Systems design Genius design

User-Centered Design Process 1.Identifying needs 2.Establish requirements 3.Develop alternative designs to meet needs 4.Build prototypes that can be communicated and assessed 5.Evaluate - throughout process evaluate what is being built and user experience it offers

UCD : Designer Roles Involve users in every stage of project. Consult users at start to see if project addresses needs. Conduct extensive research to determine user goals. Ideation, users brought in to help generate concepts - known as Participatory design. Evaluate and test prototypes with users.

User-Centered Design Premise of UCD:  Users know best.  Users of product or service know what their needs, goals, and preferences are.  Designers must find those things and design for them.

UCD : Designer Roles Designers facilitate achievement of users' goals. Participation from users at every stage process, ideally. Designers try to fit products to people, not people to products.

People must adapt to or accommodate the design. Source:

Wait to see where people walked – paths formed Fit products to people instead people to products.

Wait to see where people walked – paths formed Fit products to people instead people to products.

UCD : Designer Roles UCD is best at getting designers to move away from their own preferences  … and to focus on user preferences.

IBM

IBM | User-Centered Design principles 1. Set business goals Determine market, users, and competition. 2. Understand users 3. Assess competitiveness Ongoing awareness of competition. 4. Design total user experience (UX) Everything a user sees and touches 5. Evaluate designs 6. Manage by continual user observation Source:

IBM | User-Centered Design process 1. Market definition  Define the target audience… 2. Task analysis  Understand the users' goals and tasks… 3. Competitive evaluation  Determine strengths and weaknesses of competition. 4. Design and walk-through  Create alternative proposed solutions, solicit feedback… 5. Evaluation and validation  User feedback on the evolving design and iterate design… 6. Benchmark assessment  Benchmark assessment against competition… Source:

Activity Centered Design

Activity-Centered Design Roots in Activity theory - when people interact with environment, production of tools results. Tools are "exteriorized" forms of mental processes.

Activity-Centered Design Decision-making and internal mental state of user de-emphasized. What people do and tools they create are most important – not user. I want to be able to…

Activity-Centered Design ACD allows designers to focus on the work at hand and create support for activity itself.

Activity-Centered Design Suited for:  complicated actions  products with many diverse users.

Activity-Centered Design Focused not necessarily on user’s goals but on actions and decisions, known as tasks. Here, task is most important, not user goals. Looking for most efficient and effective way to complete task. Many different people may be in this job.

Activity-Centered Design Like UCD, ACD relies on research as the basis for its insights. Observe and interview users for insight about behavior. Catalog users activities and tasks, and design solutions to help users accomplish tasks.

An Agile Approach to User Experience and Design

Agile Manifesto Uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:  Individuals and interactions over processes and tools  Working software over comprehensive documentation  Customer collaboration over contract negotiation  Responding to change over following a plan

IBM

1. Incorporating continuous user feedback All stakeholders (principals, users, partners/deployers, and developers) should be an integral part of the design and development team.

2) Working across multiple iterations User research and high-level design before code development, even though design will change over iterations. User research and design for a specific iteration should precede the actual code development for that release. Usability evaluations with live code after the milestone is made available to users.

3) Understanding your stakeholders User research should include  a definition of the roles,  personas,  goals,  tasks,  environment of use, and  limitations and constraints. Use cases and user stories should be used to describe the overall value of the product.

4) Designing the user experience Use high-fidelity prototyping for user interactions that are difficult to code (to eliminate waste). Get iterative user feedback on designs prior to code development to ensure development time is well spent. Product builds can also be used for early user feedback and evaluation. Design must be communicated to the development team. Design changes should be communicated through daily meetings.