Design process.

Slides:



Advertisements
Similar presentations
HCI SEMESTER PROJECT PROJECTS  Project #2 (due 2/20)  Find an interface that can be improved  Interview potential clients  Identify an HCI concept.
Advertisements

Software Process Models
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
Lifecycle models For more info on these models – see text
Agile Usability Testing Methods
SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
CS305: HCI in SW Development Evaluation (Return to…)
1 Human-Centered Design I Presented by: Craig Titus EPICS High Workshop – Summer 2010 Lecture: Human-Centered Design Presented By: Craig Titus.
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
What is Interaction Design?
Chapter 6 The Process of Interaction Design Presented by: Kinnis Gosha, Michael McGill, Jamey White, and Chiao Huang.
Administrivia  Review Deliverable 2 –Overview (audience) –Excellent additions  User Goals  Usability Goals  User Group (who are you designing for?)
Design process User centered design. Poster session – next Thursday Buy a poster board Or tape your stuff to the wall Brief description of topic, key.
Midterm Exam Review IS 485, Professor Matt Thatcher.
Project Sharing  Team discussions –Share results of heuristic evaluations –Discuss your choice of methods and results  Class-level discussion –Each spokesperson.
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
Design and Evaluation of Iterative Systems n For most interactive systems, the ‘design it right first’ approach is not useful. n The 3 basic steps in the.
Design Process …and the project.
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?
SE 555 Software Requirements & Specification 1 SE 555 Software Requirements & Specification Prototyping.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Requirements Gathering
Mid-Term Exam Review IS 485, Professor Matt Thatcher.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Interface Guidelines & Principles Focus on Users & Tasks Not Technology.
CS 235: User Interface Design August 27 Class Meeting Department of Computer Science San Jose State University Spring 2015 Instructor: Ron Mak
CS 235: User Interface Design August 27 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
Requirements, cont. …and a word on Ethics. Project Part 1: Requirements Gather data using one or more techniques Learn about environment, users, tasks,
Empirical Evaluation Assessing usability (with users)
Ibrahim A. Atoum Portable-02, Room-03 University of Hail, KSA
The process of interaction design. Overview What is involved in Interaction Design? –Importance of involving users –Degrees of user involvement –What.
Ciarán O’Leary Wednesday, 23 rd September Ciarán O’Leary School of Computing, Dublin Institute of Technology, Kevin St Research Interests Distributed.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
27. august 2007 Lektion 1c 1 Interaktionsdesign- processen Sharp Kapitel 9 Anker Helms Jørgensen Interaktionsdesign Efteråret 2007 Lektion 1c.
 What is involved in Interaction Design? › What is a user-centered approach? › Four basic activities  Some practical issues › Who are the users? › What.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
ITIS 6010/8010 Principles of Human Computer Interaction Dr. Heather Richter
Comp 15 - Usability & Human Factors Unit 8a - Approaches to Design This material was developed by Columbia University, funded by the Department of Health.
Requirements, cont. …along with Ethics. Agenda Questions? Data gathering techniques Requirements expressing Ethics.
CS 5150 Software Engineering Lecture 3 Software Processes 2.
Gary MarsdenSlide 1University of Cape Town Human-Computer Interaction - 4 User Centred Design Gary Marsden ( ) July 2002.
Design Process …and understanding users. Agenda Finish history Design process Understanding users.
Task Analysis …and we’ll really get to Ethics this time.
User Interfaces 4 BTECH: IT WIKI PAGE:
SBD: Analyzing Requirements Chris North CS 3724: HCI.
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 ITM 734 Introduction to Human Factors in Information Systems Cindy Corritore This material has been developed by Georgia Tech HCI faculty,
Today Next time  Interaction Reading: ID – Ch 2 Interaction  Introduction to HCI & Interaction Design Reading: ID – Ch. 1 CS 321 Human-Computer Interaction.
Working with People & Project Overview “Doing right by your participants”
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
Administrivia  Feedback from the mid-term evaluation  Insights from project proposal.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It specifies what functions the user will need.
Computer/Human Interaction Spring 2013 Northeastern University1 Name of Interface Tagline if you have one (80 chars max, including spaces) Team member.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Prototyping Creation of concrete but partial implementations of a system design to explore usability issues.
Evaluation / Usability. ImplementDesignAnalysisEvaluateDevelop ADDIE.
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.
The Project. A little video inspiration IDEO – an industrial design company.
SIE 515 Design and Usability
User-centred system design process
Topic for Presentaion-2
HCI in the software process
HCI in the software process
Interaction design basics
HCI in the software process
Evaluation.
Human Computer Interaction Lecture 14 HCI in Software Process
Presentation transcript:

Design process

Design How do we come up with new (good) designs for interactive systems? Why is it so difficult?

What is design? achieving goals within constraints goals - purpose who is it for, why do they want it constraints materials, platforms trade-offs

Interactions and Interventions design interactions not just interfaces not just the immediate interaction E.g. email in the office designing interventions not just artefacts not just the system, but also … documentation, manuals, tutorials what we say and do as well as what we make

The Tao of UCD DESIGN IMPLEMENT USE & EVALUATE

User-Centered Design Process 1. Understand constraints/context 2. User analysis 2. Task analysis 4. Function allocation 5. Define usability criteria All of the above included in requirements definition and task analysis.

User-Centered Design (cont’d) 6. Design UI - including help and documentation Consider alternatives! Apply formative evaluation techniques & iterate 7. Build & test prototypes Apply formative / summative evaluation techniques & iterate 8. Build & test the real application Apply summative evaluation techniques & iterate 9. Release, update and maintain

Lifecycle models Show how activities are related to each other Lifecycle models are: management tools simplified versions of reality Many lifecycle models exist, for example: from software engineering: waterfall, spiral, JAD/RAD, Microsoft, agile from HCI: Star, usability engineering

A simple interaction design model Exemplifies a user-centered design approach

The process of design scenarios task analysis what is wanted guidelines principles analysis interviews ethnography what is there vs. what is wanted precise specification design dialogue notations implement and deploy evaluation heuristics prototype architectures documentation help

ISO 13407

Discussion What do methods have in common? Where do they differ? How would you choose or adapt a method?

Other HCI design “methods” Usability engineering Focus on usability metrics and evaluation Participatory design User as participant in the design process Contextual design Based around contextual inquiry, focusing on the customer

SE traditional ‘waterfall’ lifecycle Requirements analysis Design Code Test Maintenance

Spiral Lifecycle model Important features: Risk analysis Prototyping Iterative framework so ideas can be checked and evaluated Explicitly encourages considering alternatives Good for large and complex projects but not simple ones From cctr.umkc.edu/~kennethjuwng/spiral.htm

Discussion How would you incorporate HCI design into larger SE design frameworks?

Summary Four basic activities in the design process Identify needs and establish requirements Design potential solutions ((re)-design) Choose between alternatives (evaluate) Build the artefact User-centered design rests on three principles Early focus on users and tasks Empirical measurement using quantifiable & measurable usability criteria Iterative design Lifecycle models show how these are related

Design rationale Recall: design is achieving goals within constraints How do you document the Constraints? Alternatives? Decisions?

Why is HCI Design Difficult? Difficult to deeply analyze human behavior May be too close to the domain Cost/features may be considered over good human factors Creativity is challenging!

How to be creative? How do we create and develop new interface ideas and designs? Ideas come from Imagination Analogy Observation of current practice Observation of current systems Borrow from other fields Animation Theatre Information displays Architecture ..… metaphor

Project Structure Group project – 3-4 people Worth 50% of grade Design and evaluate an interface 1 - Understand the problem, users, tasks, environment (15%) 2 – Design and prototype (20%) 3 – Evaluation (15%)

Project Groups 3-4 people You decide Diverse is best! Consider schedules, email habits, etc. Form and choose topic by next Wednesday – cool name

Previous Projects Suggested Project Theme: System for organizing and showcasing art Friend Finder on a cell phone System for assisting anesthesiologists Money tracker in your wallet Mobile photo album Chef’s display in a kitchen Suggested Project Theme: Design a service to promote, encourage or support sustainability of the environment.

Coming up with project ideas Think of someone else Avoid being biased by your intuitions Think off the desktop too! Mobile, handheld, environmental Think everyday Think about people first, then technology

Project Topics Real “client” Domain family and friends? Organization you belong to, volunteer with? Hobbies or other activities? Domain Office, home, school

Project Details Part 0 – Team and topic formation – Due Jan. 23 Create team page on Swiki Choose a project topic Complete IRB certification if not already done Part 1 - Understanding the problem – Due Feb. 13 Describe tasks, users, environment, social context Any existing systems in place Helps form basis for your requirements Describe the problem, not the solution

Project Details Part 2a - Design Alternatives poster – Due March 12 Storyboards, mock-ups for multiple different designs Get feedback on ideas during poster session Part 2b – System Design and Evaluation Plan – Due April 2 Description of the system requirements and design Rationale for design decisions Plan for conducting evaluation Part 2c – System Prototype – Due April 2 Prototype that implements all or part of the design Allows for interactive experience

Project Details Part 3 – Evaluation – Due April 23 Conduct evaluation with example users Characterize pros and cons of the UI Discuss what you would do to fix problems Part 3b – Presentation – April 23 In class presentation of the entire project, 15 minutes

Your turn Pair or triple up… Brainstorm ideas/problems Choose a couple and elaborate Think of examples of other people having the problem Try to determine 5 Ws for the problem Pause to share ideas with everyone…

Exercise Interview each other about applications on your cell phone: What is your favorite feature of your cell phone? What is your least favorite feature? What do you do with your phone besides make phone calls? Is there anything else you would like to do with you cell phone? Switch cell phones and Observe each other call back the last person who called Add your name and number of the contact list

Impressions? What was surprising? What did you observe? How would this be different in real world? How did you feel about being observed?

Working with People Issues of rights, respect, ethics YOU will be observing and talking to people to: Gather requirements Get initial design feedback Perform evaluations of your design Important to be professional with any interaction with potential users

Why an issue? Usability testing can be arduous; privacy is important Each person should know and understand what they are participating in: what to expect, time commitments what the potential risks are how their information will be used Must be able to stop without danger or penalty All participants to be treated with respect

Recruiting Participants Who you are recruiting Must fit user population (validity) How you are recruiting Must adequately disclose purpose and tasks Compensation Does compensation fit task? Reasonable expectations? Note: Maintaining proper ethics applies to all participants, even friends and family

Consent Why important? People can be sensitive about this process and issues Errors will likely be made, participant may feel inadequate May be mentally or physically strenuous What are the potential risks (there are always risks)? Examples? “Vulnerable” populations need special care & consideration Children; disabled; pregnant; students (why?)

Attribution Theory Studies why people believe that they succeeded or failed--themselves or outside factors (gender, age differences) Make sure participants do not feel that they did something wrong, that the errors are their problem

IRB, Participants, & Ethics Institutional Review Board (IRB) Federal law governs procedures Reviews all research involving human (or animal) participants Safeguarding the participants, and thereby the researcher and university Not a science review (i.e., not to asess your research ideas); only safety & ethics

IRB @ UNCC http://www.research.uncc.edu/comp/chuman.cfm On-line tutorial Guidelines Consent procedures and template forms Protocol application forms IRB Protocol 101 Training http://www.research.uncc.edu/comp/human_trng.cfm 1/31: 10am, 2/1: 5pm, 2/2: 10am & 5pm

Ethics Certification Ethics is not just common sense Training being standardized to ensure even and equal understanding of issues Go get your certification: http://www.research.uncc.edu/tutorial/index3.cfm -use your UNCC ID to do the test -email me the confirmation, or email me when you took the test previously