Your SlideShare is downloading. ×
Usability Process
Usability Process
Usability Process
Usability Process
Usability Process
Usability Process
Usability Process
Usability Process
Usability Process
Usability Process
Usability Process
Usability Process
Usability Process
Usability Process
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Usability Process


Published on

Usability Process : Usability best practices

Usability Process : Usability best practices

Published in: Design, Technology, Business
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1.  
  • 2. Over View Usability Process Overview User-centered Analysis Wire Frame UI Design HTML Prototype Evaluation/ Usability Testing Implementation
  • 3. What is Usability Engineering?
    • Effectiveness – Can users achieve what they need by using the product?
    • Ease of learning – How fast can a user who has never seen the interface learn to use it?
    • Efficiency of use – How fast can users complete tasks?
    • Memorability – Can users remember enough to reuse the interface effectively?
    • Error prevention – The best way to deal with errors is to design the interface so users do not make errors.
    • Satisfaction – How much does the user like using the system?
    Usability is about:
  • 4.
    • Understand Users
    • Understand user groups
    • Understand their work environment and how they work
    • Understand user’s goals and their problems.
    Purpose of Usability
  • 5. UCD Isn’t Part of the Project Life Cycle
    • Identify business need
    • Establish technical feasibility
    • Design system architecture
    • Implement the system
    • QA testing
    • Launch
    • Maintenance
    Traditional flow:
  • 6. Traditional software development Vs User-centered development Focus on external attributes (look and feel, interaction) Focus on internal architecture Quality defined by user satisfaction and performance (quality in use) Quality measured by product defects and performance (system quality) Solutions are directed by Understanding the context of use (user, task, work environment) Solutions are directed by functional requirements Technology/developer-driven Traditional software development User - driven User-centered development
  • 7. The UCD Lifecycle
  • 8. Answer these questions early Who are my users and how will they perceive the application? What are the users goals with the Application? What areas are critical to overall success?
  • 9. Critical design component
    • Personas
      • Personas are specific, realistic descriptions of a imaginary user
    • Primary Nouns or Things
      • “ Things” users take action or manipulate
      • Primary Nouns connect the tasks with the navigation model.
    • Scenarios
      • Scenarios are detailed, concrete description of an activity
      • They focus on the user’s “story”: what they want to do, why, and what they expect.
    • Task Design
      • Task design creates streamlined task flows within the target system
  • 10. Methodologies to Identify Critical Design Components Understand Users Meeting Card Sort Interview Contextual Inquiry Task Analysis Usability Test Focus Group Design Critique
  • 11. Document the Critical design component Once you have done the User Centered Analysis by any of these methodologies
    • Meeting
    • Interview
    • Card Sort
    • Contextual Inquiry
    • Task Analysis
    • Focus Group
    • Design Critique
    • Usability Test
    Next step is to document the Critical design components……….
  • 12. What type of UI ? Before prototyping identify what type of UI?
    • Task Based
    • Information Based
    • Role Based
    • Pattern Based
    • Free style
  • 13. Way to Usable design
    • Understanding end users’ needs
    • Defining interaction
    • Designing the user interface (UI)
    • - will increase the usability & satisfaction of the user with the application
  • 14. Thank You…… Ramesh.K [email_address]