UX Final

Emotional Impact +Heuristic Evaluation Report

 

Name of system being evaluated: M-Bus E-ticket System

 

Prepared By:

Name : 박지현, 송영웅

 

Evaluation of:

Problem #1 : Clarity of Ads

Do you think that the contents of Ads were clear to understand? 1 (1~5)

Reason for reporting as negative or positive: The second Ad about Solution & Lenovo thinkpad was unclear to target users. They recognized the Ad as separate two Ads. (This was applied later in the prototype.)

Scope of problem: Solution & Lenovo thinkpad Ad page

Severity of problem (high/medium/low): high

Justification for severity rating: no justification. Change is needed in the Ad.

Suggestions to fix: put additional description in the Ad (such as “~과 함께하는”, “with”). Change the background to the same color.

Possible trade-offs (why fix might not work): additional description might be also unclear. They can be

 

 

Problem #2 : Aesthetic view

Does the application have good design in Aesthetic view? 2

Reason for reporting as negative or positive: Weird Design, too many colors are used there. Aesthetic view was so  terrible that I think the inventor gave up the outlook of the application.

Scope of problem: Log in page

Severity of problem (high/medium/low): high

Justification for severity rating: Design is not that bad. If color is changed, I think it will greatly improve.

Possible trade-offs (why fix might not work): reduce the number of colors in the design

 

 

Problem #3 : Recognition of Ads

Can you remember the Ads in the application? 2

Reason for reporting as negative or positive: Ads did not have great impact on users.

Scope of problem: All the Ads in the Application

Severity of problem (high/medium/low): medium

Justification for severity rating: Ads do not have great impact because they are just banners.

Suggestions to fix: Remove the Ads.

Possible trade-offs (why fix might not work): Banners are part of the system; just removing it against the system.

Can you remember the Ads in the application? Not at all

 

 

Heuristic : Plain language

Does the prototype use the natural language that is familiar to the target user? 4

Reason for reporting as positive: All the phrases and sentences in the prototype were understood at once.

 

 

Heuristic : Time spended to do the task.

How much time did you spend on getting M-Bus E-ticket? 5

Reason for reporting as positive: It got less than a minute to get the ticket. This is really efficient because students do not have to go other places to get the M-Bus ticket.

 

 

Heuristic : Consistency

Are the locations of icons appropriate, efficient and consistent? 4

Reason for reporting as positive: It took less than a minute to get the ticket. It means the design is efficient. However, there were no logout button in the prototype. (This was applied later in the prototype.)

Prototype

Benchmarking