1. By, Robert Larmore Lisa Paul Palathingal 02/20/2014

2.  Iterative, evaluation-centered, UX lifecycle template  Iterative Process: All or part is repeated for the purpose of exploring, fixing or refining a design  Lifecycle: Structured framework consisting of a series of stages and corresponding activities 2

3. 3

4. 4

5. 1) Analyze 2) Design 3) Implement 4) Evaluate 5

6. 1) Analyze 2) Design 3) Implement 4) Evaluate 6

7. Analyze: Understanding the business domain, user work and user needs Sub-activities:  Contextual Inquiry  Contextual analysis  Extracting requirements  Synthesizing design-informing models 7

8. 1) Analyze 2) Design 3) Implement 4) Evaluate 8

9. Design: Creating conceptual design, interaction behavior, and look and feel Sub-activities:  Design ideation and sketching  Mental models and conceptual design  Design production 9

10. 1) Analyze 2) Design 3) Implement 4) Evaluate 10

11. Implement: Prototyping Types:  Vertical  Horizontal  T  Local 11

12. 1) Analyze 2) Design 3) Implement 4) Evaluate 12

13. Evaluate: Verifying and refining interaction design Methods:  Rapid evaluation  Fully rigorous 13

14. 14

15.  Activities can overlap Objective:  Move forward to production 15

16. Team must be able to decide:  When to leave an activity  Where to go after any given activity  When to revisit a previous process activity  When to stop making transitions and proceed to production 16

17. Answers depend on transition criterion:  Whether designers have met the goals and objectives  Whether there are adequate resources (time and budget) remaining to continue 17

18. Factors:  Risk tolerance  Project goals  Project resources  Type of system being designed  Stage of progress within project 18

19. Risk:  Things going wrong  Features or requirements being missing  Not meeting needs of users The less tolerance for risks, the more need for rigor and completeness in the process 19

20. Resources:  Budget  Schedule  Person Power 20

21.  Practitioners with extensive experience need less rigorous process 21

22.  Type of system being designed: Example: mp3 player vs. air traffic control system  Stage of progress within project: Early stage: Analysis Later stage: Evaluation 22

23. 23

24. 24

25.  About elaborateness of user actions to accomplish tasks in the system 25

26. Low interaction complexity: smaller, easier tasks Example: ordering flowers from a Website High interaction complexity: larger, more difficult tasks requires special skills or training Example: manipulating a color image with Adobe Photoshop 26