Chapter 12 INTERACTION DESIGN IN PRACTICE. Overview AgileUX Design Patterns Open Source Resources Tools for Interaction Design www.id-book.com2.

Slides:



Advertisements
Similar presentations
User Experience Krista Van Laan. Agenda What is User Experience? How does a User Experience team support the rest of the organization? What processes.
Advertisements

Design, prototyping and construction
QuEdge Testing Process Delivering Global Solutions.
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
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
CS487 Software Engineering Omar Aldawud
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
Agile Usability Testing Methods
DiscoverDefineDesignDevelopDeliver PROCESS TM. Intelligaia Technology confidential & proprietary Discover Overview: Gather information, brainstorm, competitive.
Alternate Software Development Methodologies
For a Good User Experience UX Design Goals, Methods, Tools & Tales William Washington | Washington Kevin Makice| Indiana Kuali Student UX.
THE PROCESS OF INTERACTION DESIGN
Chapter Extension 19 Alternative Development Techniques © 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke.
Chapter 6 Prototyping, RAD, and Extreme Programming
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
COMP 350: Object Oriented Analysis and Design Lecture 2
Software Development Overview CPSC 315 – Programming Studio Spring 2008.
Creator: ACSession No: 19 Slide No: 1Reviewer: - CSE300Advanced Software EngineeringMarch 2007 ‘Agile Methods’ (part 2) CSE300 Advanced Software Engineering.
CHAPTER 19 Building Software.
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
Software engineering Process models Pavel Agejkin.
Project Proposal: Academic Job Market and Application Tracker Website Project designed by: Cengiz Gunay Client: Cengiz Gunay Audience: PhD candidates and.
PROJECT LM-01 Presentation 16 Oct 2006 University of Wollongong, Australia.
CIS 321—IS Analysis & Design
Lecture # 04 & 05 CS314 Introduction To Software Development Software Development Process (SDP) Instructor :Muhammad Janas khan
Current Trends in Systems Develpment
SE-280 Dr. Mark L. Hornick 1 Process Adaptations.
The UX Connection Driving Innovation on an Agile Project Hugh Beyer Cohealo.
Embracing change with Extreme Programming Method Engineering Erik ten Brinke
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 12.
Interaction Design Process COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 5 Chapter 3 (Heim)
Merja & Pauli Rapid prototyping & other stuff.
Globalizing Content for Online Security Stephan Cocron Global Content Manager VeriSign, Inc.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Content The system development life cycle
CS2003 Usability Engineering Human-Centred Design Dr Steve Love.
ITM 407: Human and Technology Interaction Management Chapter 9. Design Production Dr. Evren Eryilmaz.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
© 2010 Bennett, McRobb and Farmer1 Development Process Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using.
Rational Unified Process Mr Hisham AlKhawar. Iterative versus Waterfall  We need to use a life cycle model in order to approach developing a system easily,
Agile: Lessons Learned (a retrospective) Tony
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
UI Panel: Agile User Interface Design Colin Clark.
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
Software Development Overview CPSC 315 – Programming Studio Spring 2013.
UX meets XP. Overview of core approaches to creating interactive software Waterfall, iterative design, Agile Hybrid methods of evaluation H&P Chapter.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Lecture 4 – XP and Agile 17/9/15. Plan-driven and agile development Plan-driven development A plan-driven approach to software engineering is based around.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Extreme Programming. Extreme Programming (XP) Formulated in 1999 by Kent Beck, Ward Cunningham and Ron Jeffries Agile software development methodology.
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Design, prototyping and construction(Chapter 11).
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
CS 4500: Software Development Software Process. Materials Sommmerville Chapters 1, 2 and 3 Software Cycle and Models:
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Project Management Software development models & methodologies
Development Process Based on Chapter 5 Bennett, McRobb and Farmer
Software Development.
Shifting to Agile: Are University Libraries Ready?
The Project Infrastructure
Fundamentals of Information Systems, Sixth Edition
Ernest Cachia Department of Computer Information Systems
Information Technology Project Management – Fifth Edition
INTERACTION DESIGN IN PRACTICE
Presentation transcript:

Chapter 12 INTERACTION DESIGN IN PRACTICE

Overview AgileUX Design Patterns Open Source Resources Tools for Interaction Design

Agile development Short (one to three week) timeboxes of iterative development (sprint, iteration, cycle) Early and repeated customer/user feedback Re-prioritisation of work based on customer/user so that emergent requirements can be handled Many approaches, e.g. eXtreme Programming (XP), Scrum, DSDM

AgileUX Integrates techniques from interaction design and Agile software development AgileUX requires a change of mindset In Agile, as implementation proceeds: –requirements are elaborated –requirements are re-prioritised All techniques in UX are still relevant but when and how much needs re-thinking –focus on product, not design, as deliverable –cross-functional teams Three practical areas: user research, aligning work practices, documentation

User research Aims to characterise users through data collection and analysis Agile’s timeboxing approach does not support long periods of user research User evaluations and some detailed work can be fitted within a timebox Some user research can be performed in iteration 0 (zero), before implementation starts Ongoing programme of user research

Aligning work practices Designing a complete product upfront causes problems because of re-prioritisation Some upfront work is needed (technical and UX) Use a parallel tracks approach: –create product vision before development starts –do design work one iteration ahead of development –some teams work two iterations ahead

Parallel tracks approach to AgileUX

Aligning work practices Advantages of parallel tracks approach: –no design time wasted on features not implemented –usability testing and contextual inquiry could be done on the same customer visit, saving time –timely feedback on the designs was received from developers and customers –Agile flexibility supports schedule changes if a problem is found Parallel tracks is commonly used

Documentation Most common communication approach for UX designers Agile discourages this kind of communication, in favour of discussion Only use documentation where needed. Ask: –Who will read it? –Who will use it? –What is the minimum needed? –Is there duplication anywhere? –How polished does it need to be?

Documentation: how polished?

Documentation: how polished?

Design Patterns Capture design experience: –a solution to a problem in a context –can be instantiated in many ways: generative Patterns may be individual, in languages, in catalogues, galleries or libraries Patterns often are associated with software components, e.g. Github or platform websites Carousel pattern as example:

Design Patterns Insert Figure 12.5 (a)

Design Patterns Capture design experience, but that doesn’t necessarily mean good design: –anti-patterns: don’t do it this way! –dark patterns: deliberate tricks

Open Source Resources Components, frameworks, systems available free of charge Community-driven Available for interaction design: –design pattern libraries –Bootstrap framework

Open Source Resources

Tools for Interaction Design Tools support all aspects of the design process: –creativity, sketching, simulation, brainstorming, library search, mindmapping, video capture Tools integrate together to speed up prototyping Interactive wireframes or mockups can be produced using, e.g. –Balsamiq© –Axure© Higher fidelity prototype can be produced by linking interactive wireframe to design pattern library with software components

Summary AgileUX refers to approaches that integrate UX design and agile development –it requires a change in mindset by designers and developers –requirements are repeatedly re-prioritised, which aims to avoid wasted effort –UX design activities need rethinking: when, how much, and how to take forward Design patterns present a solution to a problem in a context Open source resources, e.g. on Github, make development of standard applications easier and quicker A range of automated tools to support interaction design in practice is available