Difference between revisions of "Conformity with user expectations"
Juliahamdan (talk | contribs) |
Juliahamdan (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 6: | Line 6: | ||
| − | ''' | + | '''Comparing this criterion to usability observations of BVG Fahrinfo app''' |
Matches: | Matches: | ||
| − | |||
| − | |||
* shows the price | * shows the price | ||
| Line 20: | Line 18: | ||
* shows optimal routes to reach destination | * shows optimal routes to reach destination | ||
| − | + | * shows a list of the history of destinations | |
| Line 28: | Line 26: | ||
* reflecting actual price or tickets at a given time | * reflecting actual price or tickets at a given time | ||
| − | * cannot search names of | + | * cannot search names of destination; can only enter addresses |
* shows too much options (more than expected) | * shows too much options (more than expected) | ||
| − | * | + | * searches are in German Language only |
Latest revision as of 14:30, 14 April 2020
Definition: Conformity to User Expectations means that an application should match the user's expectations on how it should function, be consistent, and be realistic. The application should adhere to specific standards.
Comparing this criterion to usability observations of BVG Fahrinfo app
Matches:
- shows the price
- shows offers and tickets on sale
- shows the time needed to reach destination
- shows optimal routes to reach destination
- shows a list of the history of destinations
Mismatches:
- reflecting actual price or tickets at a given time
- cannot search names of destination; can only enter addresses
- shows too much options (more than expected)
- searches are in German Language only
