1. Usability Engineering Process flow Model Presented by: Sivaprasath Selvaraj

3. Business case for Usability

4. Lack of Usability

5. ROI Measures

6. Approach to Design

7. Interface Design Occurs Late in Engineering

8. Less User-Centered Design – More Hidden Costs

10. Real Example: Design Strategy

11. Basic Parameters of User Profiles

12. User Profile Example

13. Task Profile Example

14. Task Prioritization

15. Environmental Profile

16. Task Analysis – Before & After

17. The Purpose of Task Analysis

18. Navigation Structure

19. Information Architecture

20. Wireframes

21. Prototypes

22. Peer Review

23. Expert Review

25. What is Usability? Several formal and informal definitions of usability exist. The most widely recognized is probably the ISO definition: The usability of an interface is a measure of the effectiveness, efficiency and satisfaction with which specified users can achieve specified goals in a particular environment with that interface. Usability is the ease of use and learnability of a human-made object.

27. Improve ease of use and ease of learning

28. Increase user productivity and user satisfaction

29. Increase user trust in the system

30. Reduce support costs and training costs

31. Reduce development costs and time

32. Reduce maintenance costs

33. Increase product sales, revenue and market share

34. Increase site traffic and transactions/purchases

36. Lack of Usability Although the definition of usability may be the subject of some discussion, lack of usability is readily recognizable. Systems that lack usability are characterized by: Existence of workarounds - because the interface is difficult or does not match workflow in the real world, users develop workarounds to compensate for the inadequacies of the system Low usage levels - Users use the system as little as possible. Dissatisfaction - Users, and particularly novices, will find the system difficult or frustrating to use Rework or double-handling - Inefficient design often means that the same data may need to be entered or read more often than is necessary. Because incorporating usability is a quality activity, it often occurs that systems with poor usability are also deficient in other areas. For example, they are likely to be crash-prone, poorly documented and difficult to maintain.

37. ROI Measures

39. (Real-world) Scenario driven

40. Task success view of quality

42. Less User-Centered Design – More Hidden Costs

43. More User-Centered Design – Less Hidden Costs

44. Flow Diagram of Usability Engineering in SDLC Design Strategy Personas & Profiles Scenarios Requirement Gathering Task flow Analysis NavigationStructure Information Architecture Wireframes Final Product OrApplication Prototypes(Low-Fidelity & Hi-Fidelity) Usability Testing on Hi-Fidelity prototypes

47. Requirement Gathering1. Interviews 2. Survey 3. Contextuel Observation 4. Focus Groups 5. JAD Sessions In Planning stage, documents are created in detail, 1. Refined Design Strategy, 2. Personas & Profiles, 3. scenarios and 4. Requirement gathering.

48. Value of a Design Strategy

49. Real Example: Design Strategy

51. Navigation Structure

52. Information Architecture

53. Wireframes

54. Low Fidelity Prototypes

55. High Fidelity PrototypesOnce Design Strategy is completed, Execution stage take place with following methods, 1. Task flow Analysis 2. Navigation Structure 3. Information Architecture 4. Wireframes and 5. Low Fidelity & High Fidelity Prototypes

56. The Purpose of Task Analysis

57. Task Analysis – Before & After

58. Navigation Structure

59. Information Architecture

60. Wireframes

61. Prototypes

63. Expert Review

65. Expert Review (Subject Matter Experts)

66. Heuristic Evaluation Heuristic evaluation is the most popular of the usability inspection methods. Heuristic evaluation is done as a systematic inspection of a user interface design for usability. The goal of heuristic evaluation is to find the usability problems in the design so that they can be attended to as part of an iterative design process. Heuristic evaluation involves having a small set of evaluators examine the interface and judge its compliance with recognized usability principles (the "heuristics"). By Jakob Nielsen 1. Visibility of system status 2. Match between system and the real world 3. User control and freedom 4. Consistency and standards 5. Error prevention . 6. Recognition rather than recall 7. Flexibility and efficiency of use 8. Aesthetic and minimalist design 9. Help users recognize, diagnose, and recover from errors 10. Help and documentation

67. Thank you Presented by: Sivaprasath Selvaraj