0 = I don't agree that this is a usability problem at all
1 = Cosmetic problem only: need not be fixed unless extra time is available on project
2 = Minor usability problem: fixing this should be given low priority
3 = Major usability problem: important to fix, so should be given high priority
4 = Usability catastrophe: imperative to fix this before product can be released
-
Severity: 0
Problems: None. There is an effort maintain the platform up-to-date in relation to the underlying system, present the status of the various entities and update the platform after each action. A feedback is also performed through a toast message if the action was successful.
-
Severity: 0
Problems: None. The names and acronyms used are those used in the industry and current 5G NFV community.
-
Severity: 0
Problems: None. When performing any relevant action, a menu appears to verify that it was truly intended, enabling to cancel if it was a mistake.
-
Severity: 0
Problems: None. The closing buttons are in the expected locations. The buttons expected to work, such as escape, enter, backspace and others effectively work when expected.
-
Severity: 1
Problems: When a error occurs there is an effort to log and present the error message through, in this case, a toast message. Validation are also performed in some cases, but that functionality should be extended to the entire platform.
-
Severity: 0
Problems: None. The menus and flows are simple and straight-forward enough to recognize the pattern. Additionally, most of the actions are visible or if in a menu, there is a hint to it.
-
Severity: 2
Problems: A concern related to efficiency of use is the listing approach of the various entities. Scrolling and filtering gain unnecessary difficulty. FIltering is also not present. That feature should be added and, if necessary, minor fixes over the entities lists should be performed.
-
Severity: 0
Problems: None. The portal has a minimal design, not to chaotic and clean enough so that the important information is assimilated by the user.
-
Severity: 0
Problems: None. When a error occurs, the message is not the error code, but the message resuming the problem.
-
Severity: 1
Problems: Although the tabs and fields are pretty specific and written in a way to be self explaining, sometimes additional information, possibly through a tooltip-like element would be recommended.
-
Severity: 0
Problems:
-
Severity: 1
Problems:
-
Severity: 0
Problems:
-
Severity: 2
Problems:
-
Severity: 0
Problems:
-
Severity: 2
Problems:
-
Severity: 0
Problems:
-
Severity: 0
Problems:
-
Severity: 2
Problems: não diz onde está o erro especificamente
-
Severity: 1
Problems: