Published on

user interface design. Usability is to make customer happy.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. The User Interface Design for LMS
  2. 2. Abstract <ul><li>User- Librarian… </li></ul><ul><li>LMS would be serving for Faculty and Students… </li></ul>
  3. 3. “ Usability” <ul><li>The degree to which a product enables a user to achieve his or her goals, and is an assessment of the user’s willingness to use the product at all. </li></ul>
  4. 4. <ul><li>Make Customer </li></ul>Usability is
  5. 5. in terms of - <ul><li>5 basic principles of Usability </li></ul><ul><li>Ease of learning </li></ul><ul><li>Efficiency of use </li></ul><ul><li>Memorability </li></ul><ul><li>Error frequency and severity </li></ul><ul><li>Subjective satisfaction </li></ul>
  6. 6. Usability - Bad #1
  7. 7. Usability - Good #1
  8. 8. Usability - Bad #2
  9. 9. Usability - Good #2
  10. 10. <ul><li>Development focuses on the machine or system </li></ul><ul><li>Target audiences change and adapt </li></ul><ul><li>Designing usable products is difficult – people thinks it is “EASY” </li></ul><ul><li>Team specialists don’t always work in integrated ways </li></ul><ul><li>Design and implementation don’t always match </li></ul>5 Most reasons makes “Less Usable”
  11. 11. <ul><li>Clarity of Communication </li></ul><ul><ul><li>Does the application convey a clear sense of its intended audience? </li></ul></ul><ul><ul><li>Does it use language in a way that is familiar to and comfortable for its users? </li></ul></ul><ul><ul><li>Is it conversational in its tone? </li></ul></ul>User-friendliness checklist:
  12. 12. <ul><li>Consistency </li></ul><ul><ul><li>Does the application have a consistent, clearly recognizable &quot;look-&-feel&quot;? </li></ul></ul><ul><ul><li>Does it make effective use of repeating visual themes to unify the application? </li></ul></ul><ul><ul><li>Is it visually consistent even without graphics? </li></ul></ul><ul><li>Navigation </li></ul><ul><ul><li>Does the application use (approximately) standard link colors? </li></ul></ul><ul><ul><li>Are the links(button) obvious in their intent and destination? </li></ul></ul><ul><ul><li>Is there a convenient, obvious way to maneuver among related pages, and between different sections? </li></ul></ul>User-friendliness checklist:
  13. 13. <ul><li>Design & maintenance </li></ul><ul><ul><li>Does the application make effective use of icons to tie related items together? </li></ul></ul><ul><ul><li>Are there “not-to-use” buttons bothering users? Functionless forms? </li></ul></ul><ul><li>Visual Presentation </li></ul><ul><ul><li>Is the application moderate in its use of color? </li></ul></ul><ul><ul><li>Does it provide desired button in understandable position? </li></ul></ul>User-friendliness checklist:
  14. 14. E xceptions <ul><li>Exceptions do happen </li></ul><ul><li>The architecture should be smart enough to handle them appropriately </li></ul><ul><li>The “Developer Down Time” should be minimal when an exception occurs </li></ul><ul><li>The architecture should help as much as possible resolving the problem </li></ul>
  15. 15. E xceptions <ul><li>NEVER assume anything </li></ul><ul><ul><li>Don’t assume a certain configuration file exists </li></ul></ul><ul><ul><li>Don’t assume the configuration file is valid </li></ul></ul><ul><ul><li>Don’t assume a specific data exists in the database </li></ul></ul><ul><ul><li>Don’t assume the developer overrode some methods </li></ul></ul><ul><li>The only assumption is: </li></ul><ul><ul><li>“ The developer is not you. You know the architecture the best, he just begins to learn it.” </li></ul></ul><ul><li>Be prepared to handle the most extreme situations </li></ul>Don’t : Display Generic Error Message
  16. 16. The most dreaded error message:
  17. 17. E xceptions <ul><li>When an exception should be thrown, make sure to throw the most accurate one </li></ul><ul><li>Create custom exceptions as many as needed </li></ul><ul><li>Make sure your custom exception and message are specific and informative </li></ul>Don’t : Display Cryptic Error Message
  18. 18. An extremely helpful message:
  19. 19. A real error message caught in one of our log files:
  20. 20. A quite common view in eclipse:
  21. 21. E xceptions <ul><li>Throw the full information about the exception, when needed </li></ul><ul><li>NEVER leave the “catch” clause empty </li></ul><ul><li>If you throw a new exception, make sure to include all the associated information </li></ul><ul><li>Use Exception Handling only when relevant </li></ul>Don’t : Hide Exception Information
  22. 22. Why? What can I do about this?
  23. 23. E xceptions <ul><li>All the exceptions should be written down to a log file </li></ul><ul><li>The log file should give the developer the full understanding of what happened </li></ul><ul><li>The log file is extremely useful in production environments </li></ul><ul><li>Refer the user to the log file, and display him a friendly error message </li></ul>Do : Central Exception Logging
  24. 24. Not too friendly, though…
  25. 26. Splash page
  26. 27. <ul><li>Self Timer </li></ul><ul><li>Progress Bar </li></ul>
  27. 28. Log In
  28. 29. <ul><li>OK – Enter Key </li></ul><ul><li>Alt + o = Short cut Key </li></ul><ul><li>Cancel – Escape button </li></ul><ul><li>Alt + c = Short cut key </li></ul>
  29. 30. Main Page
  30. 31. <ul><li>Date & Time Can be Seen </li></ul><ul><li>Caps lock, Num lock, Insert, Scroll Bar </li></ul>
  31. 32. Change Database Record
  32. 33. To Change Database Password
  33. 34. Issue & Return Book For Student
  34. 36. Issue & Return Book For Staff
  35. 38. Issue & Return Magazine For Student
  36. 40. Issue & Return Magazine For Staff
  37. 42. Issue & Return Newspaper For Student
  38. 45. Issue & Return Newspaper For Staff
  39. 48. THANK YOU USABILITY - DEFINITION Easy to learn Easy to implement Easy to modify Easy to maintain