• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Si622 Evaluations Of Systems And Services
 

Si622 Evaluations Of Systems And Services

on

  • 283 views

 

Statistics

Views

Total Views
283
Views on SlideShare
264
Embed Views
19

Actions

Likes
0
Downloads
0
Comments
0

4 Embeds 19

http://ricardoyi.com 14
http://www-personal.umich.edu 3
http://www.ricardoyi.com 1
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Si622 Evaluations Of Systems And Services Si622 Evaluations Of Systems And Services Presentation Transcript

    • SI622 Evaluations of Systems and Services Project: PublicDrum.org Team Stick: Ricardo Yi, Dawn Barton, Lisa Quist, Edwin Teng
    • Findings & Introduction Methods Recommend Summary ations Presentation Outline • Overview of Public Drum • Methods • Findings & Recommendations • Summary
    • Findings & Introduction Methods Recommend Summary ations About PublicDrum.org • Overview of Public Drum – Aggregation Service – Event Distribution • Types of Users – Aggregators – Creators
    • Findings & Introduction Methods Recommend Summary ations User Demographics Bryan Shaw • Occupation: Concert promoter in Chicago • Age: 35 • Education: Bachelor's degree (liberal arts) Elizabeth Bennett • Works part time at Home Depot. • Age: 27 • Education: BA in music performance
    • Findings & Introduction Methods Recommend Summary ations Methods Summary  Comparative Evaluation • 5 competitors: Zvents, Yahoo Upcoming, ArborWeb, ArborWiki , ArtsEverywhere  Heuristic Evaluation • 4 Evaluators, 14 findings  Survey • Response Rate: 22.8%  User Testing • 1 pilots tests, 5 actual tests; 7 findings
    • Findings & Introduction Methods Recommend Summary ations Comparative Evaluation
    • Findings & Introduction Methods Recommend Summary ations Heuristic Evaluation # Issue Severity Heuristic Category 1 Design 0 Aesthetic and minimalist design 2 Event entry form 1.5 Consistency and standards/Recognition rather than recall/ Visibility of system status 3 User Registration 2 User control and freedom/ Error prevention 4 Difficult to see who is using 2 Aesthetic and minimalist design/ Public Drum Consistency and standards/ Match between system and the real world 5 Global and Footer navs use 2 Consistency and standards/ unexpected vocabulary Match between system and the real world 6 Event Recommendations 3 Recognition rather than recall/ Flexibility and efficiency of use 7 No way to tell if aggregators 3 Visibility of system status have subscribed to an event 8 Search Vocabulary 3 Match between system and the real world/ Consistency and standards 9 Hard to enter events 3 Flexibility and efficiency of use/ Consistency and standards/ Error prevention 10 Global and Footer navs are 3 Flexibility and efficiency of use/ difficult to navigate Aesthetic and minimalist design/ Consistency and standards 11 Status of Event Submission 3.5 Visibility of system status 12 Difficult to navigate website 3.5 Consistency and standards/ Flexibility and efficiency of use/ Error prevention 13 Event Correction Process 4 Error prevention 14 Hard to find search 4 Consistency and standards/ Visibility of system status
    • Findings & Introduction Methods Recommend Summary ations Survey
    • Findings & Introduction Methods Recommend Summary ations User Testing # Usability Issue Priority Category 1 Unclear navigation terminology 4 Task 2, Task 3 2 Buttons are unclear and out-of- 4 Task 2, Task 4 place 3 Lack of Feedback 3 Task 1, Task 2, Task 4 4 Extra and/or out-of-place elements 2.5 Task 2 on the form 5 Unclear terminology and 2 Task 1,Task 2, requirements within forms Task 3 6 Time entry is confusing/annoying 1.5 Task 2 7 Calendar configuration is 1 Task 2 confusing/annoying
    • Findings & Introduction Methods Recommend Summary ations Finding #1 • Users have difficulty logging in – lack of system feedback – unclear what they're supposed to do • Recommendations – Big font saying you must check your email to complete registration – Do not say you have successfully completed it because people do not check email after seeing that – Have the least amount of text as possible, because people do not read big blocks of text
    • Findings & Introduction Methods Recommend Summary ations Finding #2 • Navigation is unclear and disorienting to the user. • Recommendations – Consistent navigation throughout the site – ONE global nav – buttons should look like buttons, users accidentally – clicked the help part
    • Findings & Introduction Methods Recommend Summary ations Finding #3 • Form elements do not conform to web standards which confuses the user. • Recommendations – asterisk the required fields – collapse the information that does not pertain to every user (ticket details, sound, images) – buttons should be at the bottom of the form
    • Findings & Introduction Methods Recommend Summary ations Finding #4 • Vocabulary does not meet web standards and confuses users • Recommendations – use standard web vocabulary. for example, search vs. find vs. track vs. use – be consistent. enter events does not also mean edit events
    • Findings & Introduction Methods Recommend Summary ations Finding #5 • Buttons do not conform to web standards and confuse users – buttons generally happen at the bottom of the form – buttons usually look alike (as in not have red font) – buttons do not change functions (publish/unpublish) • Recommendations – publish/unpublish/save for later could be accomplished with radio buttons and "save" button--this way there is no confusion – remove unnecessary buttons/clarify function (clear form vs. clear) – separate functions
    • Findings & Introduction Methods Recommend Summary ations Expected benefits • System feedback in these areas will allow users to feel more comfortable, by giving them more information about the system status • Reducing user frustration by increasing system visibility will increase use of site by creators, which will increase use of site by aggregators.
    • Findings & Introduction Methods Recommend Summary ations Summary • Areas for future investigation? – Search, perhaps, or Aggregation section – "Tools" section has code, code is scary etc.
    • Thank you! Q&A
    • Findings & Introduction Methods Recommend Summary ations