Chapter 6 The Process of Interaction Design Presented by: Kinnis Gosha, Michael McGill, Jamey White, and Chiao Huang.

Slides:



Advertisements
Similar presentations
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
Advertisements

Systems Analysis and Design
CS487 Software Engineering Omar Aldawud
Chapter 4 Design Approaches and Methods
Lifecycle models For more info on these models – see text
CSE 470 : Software Engineering The Software Process.
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.
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas The primarily goal of a system is to create value for the organization. Many failed systems were abandoned.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Alternate Software Development Methodologies
THE PROCESS OF INTERACTION DESIGN
Part 1: Introducing User Interface Design Chapter 1: Introduction –Why the User Interface Matters –Computers are Ubiquitous –The Importance of Good User.
COMP 6620 Chapter Presentation Karthik Vemula. Agenda:-  User Centered Approach  Basic Activities of Interaction Design.  In Class Assignment.
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
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
What is Interaction Design?
1 FJK User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo.
Chapter 6 Prototyping, RAD, and Extreme Programming
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Systems.
Fundamentals of Information Systems, Second Edition
What is a good length of string? –Depends on its use How do you design a good length of string? –Can be determined by a process What is a good user interface?
Usability 2004 J T Burns1 Usability & Usability Engineering.
Objectives By the end of today’s class you will be able to… –Describe the major steps in the interaction design process –Explain the importance of iterative.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Principles of Object Technology Module 1: Principles of Modeling.
Chapter 6 The Process of Interaction Design By: Matt Bergstein Matt Bergstein Kevin Clark Kevin Clark Carol Lawson Carol Lawson Angelo Mitsopoulos Angelo.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Chapter 2 The process Process, Methods, and Tools
The process of interaction design. Overview What is involved in Interaction Design? –Importance of involving users –Degrees of user involvement –What.
IT Systems Analysis & Design
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Software Engineering Environment  A quality focus: constant incremental improvement  Process: framework to organize development activities  Methods:
27. august 2007 Lektion 1c 1 Interaktionsdesign- processen Sharp Kapitel 9 Anker Helms Jørgensen Interaktionsdesign Efteråret 2007 Lektion 1c.
Chapter 9 The process of interaction design. Fundamental activities Understanding the requirements Producing a design solution that satisfies those requirements.
 What is involved in Interaction Design? › What is a user-centered approach? › Four basic activities  Some practical issues › Who are the users? › What.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Software Engineering Management Lecture 1 The Software Process.
Comp 15 - Usability & Human Factors Unit 8a - Approaches to Design This material was developed by Columbia University, funded by the Department of Health.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Chapter 9 Prototyping. Objectives  Describe the basic terminology of prototyping  Describe the role and techniques of prototyping  Enable you to produce.
Gary MarsdenSlide 1University of Cape Town Human-Computer Interaction - 4 User Centred Design Gary Marsden ( ) July 2002.
An Introduction to Software Engineering
Fundamentals of Information Systems, Second Edition 1 Systems Development.
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.
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Human Computer Interaction
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Interface Types and Models Dr. Dania Bilal IS 588 Spring 2008.
44222: Information Systems Development
Systems Development Life Cycle
LECTURE 3 Outline What is interaction design about?
Software Engineering Session 12 INFM 603. Software Software represents an aspect of reality –Input and output represent the state of the world –Software.
Software Development Process includes: all major process activities all major process activities resources used, subject to set of constraints (such as.
The Process of Interaction Design
The process of interaction design
User-Centered Design and Development
User-Centered Design and Development
IT Systems Analysis & Design
THE PROCESS OF INTERACTION DESIGN
Presentation transcript:

Chapter 6 The Process of Interaction Design Presented by: Kinnis Gosha, Michael McGill, Jamey White, and Chiao Huang

6.1 - Introduction In previous chapters, we looked at different kinds of interactive products, issues you need to take into account, and some of the theoretical basis for the field. This chapter will explore how we can design and build interactive products.

6.1 - Introduction The main aims of this chapter are to: –Consider what “doing” interaction design involves. –Ask and provide answers for some important questions about the interaction design process. –Introduce the idea of a lifecycle model to represent a set of activities and how they are related –Describe some lifecycle models from software engineering and HCI and discuss how they relate to the process of interaction design. –Present a lifecycle model of interaction design.

6.2 – What is interaction design about? In interaction design, we take a user- centered approach to development. This means that users’ concerns direct the development rather than technical concerns. Design is also about trade-offs, or balancing conflicting requirements. –Generating alternatives is a principle that should be encouraged in interaction design.

6.2.1 – Four Basic Activities of Interaction Design 1. Identifying needs and establishing requirements –In order to design something to support people, we must know who our target users are and what kind of support an interactive product could usefully provide.

6.2.1 – Four Basic Activities of Interaction Design 2. Developing alternative designs –This is the core activity of designing: actually suggesting ideas for meeting the requirements. –Conceptual Design Involves producing the conceptual model for the product, and a conceptual model describes what the product should do, behave, and look like. –Physical Design Considers the detail of the product including the colors, sounds, images, menu design, and icon design.

6.2.1 – Four Basic Activities of Interaction Design 3. Building interactive versions of the designs –The most sensible way for users to evaluate designs is to interact with them. –This does not mean that a software version is required, but rather, a paper-based prototype is quick and cheap to build.

6.2.1 – Four Basic Activities of Interaction Design 4. Evaluating designs –Evaluation is the process of determining the usability and acceptability of the design. –Evaluation is measured in terms of a variety of criteria including: numbers of errors users make using it how appealing it is how well it matches the requirements

6.2.2 – Three Key Characteristics of the Interaction Design Process 1. A User Focus –A process cannot guarantee that a development will involve users, it can encourage focus on such issues and provide opportunities for evaluation and user feedback.

6.2.2 – Three Key Characteristics of the Interaction Design Process 2. Specific Usability Criteria –Specific usability and user experience goals should be identified, clearly documented, and agreed upon and the beginning of the project. –They help designers choose between alternative designs and check on progress.

6.2.2 – Three Key Characteristics of the Interaction Design Process 3. Iteration –Iteration allows designs to be refined based on feedback. –Iteration is important useful if you are trying to innovate. Innovation rarely emerges whole and ready to go. It takes time, evolution, trial and error, and patience.

Section 6.3

Key Questions Who are the users? What do we mean by needs? How do you generate alternative designs? How do you chose among alternatives?

Who are the users? Three types of users –Primary –Secondary –Tertiary Know stakeholders

(OPTIONAL SLIDE) Stakeholders Who do you think are the stakeholders for the check-out system of a large supermarket?

What do we mean by “needs”? Must understand the characteristics and capabilities of the users. Requires consultation from representation of target group. If nothing else, base future behavior on past behavior

(Optional Slide) User Needs SealsAide is designing a new container for it’s fruit flavored sports drink. Who are the users and what would their needs be?

Generating Alternate Designs Creativity Start….Anywhere!

How to choose alternate design? Designs are external or internal External design Two ways to choose alternate design –Test the prototype, let the users choose –Choose what has the best “Quality”

Section 6.4

Lifecycle models Show how the activities are related Lifecycle models are: –Management tools –Simplified version of reality Many lifecycle models exist, for example: –From software engineering: waterfall, spiral, JAD/RAD, Microsoft –From HCI: Star, usability engineering

A simple interaction design model Evaluate (Re)Design Identify needs/ establish requirements Build an interactive version Final product

The waterfall lifecycle model Requirements analysis Design Code Test Maintenance

The spiral lifecycle model Important features: –Risk analysis –Prototyping –Iterative framework allows ideas to be checked and evaluated –Explicitly encourages alternatives to be considered

The spiral lifecycle model From cctr.umkc.edu/~kennethjuwng/spiral.htm

A basic RAD (Rapid Applications Development) lifecycle model JAD workshops Project set-up Iterative design and build Engineer and test final prototype Implementation review

The Star Lifecycle Model Important features: –Derived from some empirical work of interface designers –No particular ordering of activities –Evaluation is central to this model

The Star Model Evaluation Conceptual/ formal design Requirements specification Prototyping task/functional analysis Implementation

The Usability Engineering Lifecycle Model Important features: –Holistic view of usability engineering –Provides links to software engineering approaches, e.g.OOSE –Three essential tasks: requirements analysis, design/testing/development, and installation –Stages of identifying requirements, designing, evaluating, building prototypes –Uses a style guide to capture a set of usability goals –Can be scaled down for small projects

Summary Four basic activities in the design process –Identifying needs and establishing requirements –Developing alternative designs –Building interactive versions of the design –Evaluating designs Three key characteristics of the interaction design process –Focus on users –Specific usability and user experience goals –Iteration Lifecycle models show how these are related

Additional Comments

Microsoft Development Process Attempts to scale up the culture of a loosely-structured, small software team Each small team of developers have freedom to evolve their designs and operate nearly autonomously All teams synchronize their activities daily and periodically stabilize the whole product, “synch and stabilibze”

Planning Phase Begins with a vision statement that defines the goals of the new product and supported user activities Program managers write functional specifications with enough detail to develop schedules and allocate staff

Development Phase Feature list is divided into smaller groups, each with its own small development team Schedule is broken up into milestones Teams work in parallel and synchronize their work on a daily and weekly basis

Stabilization Phase Once a milestone is reached, all errors are found and fixed The next milestone is then pursued

Final Products Excel, Office, Publisher, Windows 95, Windows NT, Word, and Works, among others were developed with this “synch and stabilize” process

Questions???