CS5714 Usability Engineering An Iterative, Evaluation- Centered Life Cycle For Interaction Development Copyright © 2003 H. Rex Hartson and Deborah Hix.

Slides:



Advertisements
Similar presentations
Systems Development Environment
Advertisements

PROGRAM AND PROJECT MANAGEMENT
Lecture # 2 : Process Models
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Software Project Management
CS5714 Usability Engineering Wrap Up and Making It All Work Copyright © 2003 H. Rex Hartson and Deborah Hix.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Part 1: Introducing User Interface Design Chapter 1: Introduction –Why the User Interface Matters –Computers are Ubiquitous –The Importance of Good User.
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?
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Introduction to Software Engineering Dr. Basem Alkazemi
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
Chapter 8 Prototyping and Rapid Application Development
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
User Engineering | Sept 2004 | Dave Roberts © 2004 IBM Corporation Coping With Complexity Creating a solution with User Engineering.
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
CHAPTER 19 Building Software.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
Satzinger Chp. 2 Part Part 4 of 4 2 Object-Oriented Analysis and Design with the Unified Process Testing Testing is critical discipline Testing activities.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Introduction to Interactive Media The Interactive Media Development Process.
Copyright © 2015 Pearson Education, Inc. Chapter 7: Software Engineering.
Software Engineering Management Lecture 1 The Software Process.
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
Chapter 3: Managing Design Processes
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Chapter 6 Prototyping, RAD, and Extreme Programming Systems Analysis and Design Kendall & Kendall Sixth Edition.
HCI Design Process CS774 Human-Computer Interaction Spring 2004.
Chapter 3 Managing Design Processes. 3.1 Introduction Design should be based on: –User observation Analysis of task frequency and sequences –Prototypes,
McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 12 Implementing Business/IT Solutions.
Project & Risk Management For next class -- Pressman: 3, , 5.8, , 6.6 Introductions Software Development Processes Software Maturity Models.
Dr. H. Rex Hartson Fall 2003 Introduction to the Course Copyright © 2003 H. Rex Hartson and Deborah Hix. CS5714 Usability Engineering.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Chapter 7: Software Engineering
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CS223: Software Engineering Lecture 16: The Agile Methodology.
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
4.2 SOFTWARE DEVELOPMENT METHODOLOGGY PRESENTED BY : AZURA IBRAHIM SYARIFAH SYAZA BTE SEYD ZULKAFLY CS230(5A)
Software Development Process includes: all major process activities all major process activities resources used, subject to set of constraints (such as.
Advanced Software Engineering Dr. Cheng
Introduction to Systems Analysis and Design
Building Information Systems
Use Cases Discuss the what and how of use cases: Basics Benefits
CASE Tools and Joint and Rapid Application Development
CIS 376 Bruce R. Maxim UM-Dearborn
Chapter 1 The Systems Development Environment
Web Development A Visual-Spatial Approach
The V Model The V Model Damian Gordon Damian Gordon.
Chapter 1 The Systems Development Environment
Chapter 2 Software Processes
Christina Gu Jason Lee Stephen Smith
Software Development Process
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Presentation transcript:

CS5714 Usability Engineering An Iterative, Evaluation- Centered Life Cycle For Interaction Development Copyright © 2003 H. Rex Hartson and Deborah Hix.

LC 2 Topics Connections of user interaction development to software engineering Development activities in the usability engineering life cycle Usability management User interface development team System developmentMobius

LC 3 Typical Software Engineering LC The Waterfall Model

LC 4 The Process of User Interaction Development Connections of user interaction development to software engineering All these figures depict communication paths, not temporal ordering of activities Distinction between design and implementation Start with basic software engineering concept:

LC 5 The Process of User Interaction Development Adding systems analysis, testing, and problem (application) domain

LC 6 The Process of User Interaction Development Analogous activities for user interface development

LC 7 The Process of User Interaction Development Connecting the processes together and adding rapid prototyping

LC 8

9 The Process of User Interaction Development The rest of this course is about just this part:

LC 10 The Wheel – Usability Engineering Life Cycle Process Model Iterative, evaluation-centered process model for interaction development New life cycle concept comes from: – The waterfall model – movement toward completion – Star (Hartson & Hix, 1989) – evaluation centered – LUCID (Cognetics, Inc.) – development activities – Boehm’s Spiral Model – iteration – New work by Helms & Hartson (2001) – put it together

LC 11 The Wheel – Usability Engineering Life Cycle Process Model – Star (Hartson & Hix, 1989) Evaluation centered

LC 12 The Wheel – Usability Engineering Life Cycle Process Model – Boehm’s spiral model-evolution through iteration

LC 13 The Wheel – Usability Engineering Life Cycle Process Model – Boehm’s spiral model abstracted Devt methodology

LC 14 The Wheel – Usability Engineering Life Cycle Process Model – Spiral model adapted

LC 15 The Wheel – Usability Engineering Life Cycle Process Model – Spiral unwound

LC 16 The Wheel – Usability Engineering Life Cycle Process Model – Spiral unwound and stretched out

LC 17 The Wheel – Usability Engineering Life Cycle Process Model – Waterfall with whirlpools

LC 18 Wheel Connect- ing into Wheel, for inter- cycle iteration

LC 19 The Wheel – Usability Engineering Life Cycle Process Model Life cycle=iterative configuration of cycles (each associated with a stage/form of the product) – Example: System analysis model, scenarios and screen designs, lo-fi prototype, hi-fi prototype, software production & integration Cycle is a sequence of four development activity types: – Analyze – Design – Build – Evaluate

LC 20 The Wheel – Usability Engineering Life Cycle Process Model Cycle as sequence of four types of development activities

LC 21 The Wheel – Usability Engineering Life Cycle Process Model Zoom in on details of a generic cycle activity

LC 22 The Wheel – Usability Engineering Life Cycle Process Model Choose a technique for each activity type in each cycle

LC 23 The Wheel – Usability Engineering Life Cycle Process Model – Shows how each activity type is assigned a technique, the role of the person doing the activity, support tools, and documentation Example: In scenario and screen design cycles, design walk- through is used as evaluation technique Basic Principles – Process is product oriented – Products evolve through cycles (cycles named for product forms)

LC 24 The Wheel – Usability Engineering Life Cycle Process Model – Each cycle is iterative – Each cycle contains same activity types – Each cycle is evaluation-centered – Work products (documentation) evolve over cycles – Process can be viewed at different levels Process, cycle, activity, documentation

LC 25 The Wheel – Usability Engineering Life Cycle Process Model Any part of the process is an instance of what is possible – Pick and choose cycles, activities, iterations to meet schedule, budget, management style Integrate with software engineering development process Validated by Helms & Hartson (2001) in e- commerce start-up company

LC 26 The Wheel – Usability Engineering Life Cycle Process Model Any part of process is instance of what is possible – Developers include their favorite UE methods and techniques – Omit activities, cycles, iterations indicated by management, budget, schedule, project scope, team composition – Can be different every time

LC 27 Usability Management The control mechanism for the iteration Control involves: – Establishing usability specifications – Evaluating against usability specifications – Performing impact and cost/benefit analyses

LC 28 Usability Management – Deciding on changes to make to interaction design – Deciding when to stop iterating Same process can be applied to develop user documentation or training course

LC 29 Roles on user interface development team Note: Different roles, but not necessarily different people – User interaction designer (or usability engineer or usability specialist) – Evaluator (or facilitator) – User (and/or user representative) – Software engineer and/or programmer – Technical writer – Graphic designer – Application domain expert (also called subject matter expert) Meet the User Interface Development Team Engineers