XWiki - Foundation.Technology.Graphical User Interface

= Motivation =

As explained in the section [[Humanoid Robot>>https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/view/Foundation/Technology/Humanoid%20Robot/]], Pepper can interact with the PwD, its relatives and the Healthcare professional using 3 communication channels:

1. Voice

1. Tablet

1. Gesture

For both redundancy of information (i.e. audio impaired patient) and for ease of interaction between Pepper and any human we believe that making use of the tablet could be useful.

8

9

This section describe a first iteration of a graphical user interface that could be used on the tablet of Pepper.

10

11

Please note that this section has not been implemented in the prototype and is simply here to reflect the amount of thinking that went into the graphical user interface. Moreover, we believe that it would be great future work to both think of new design and implement them on Pepper.

12

13

= High level description =

14

In an ideal setup Pepper's tablet would be tactile and humans could either talk to Pepper or use the tablet to interactive with it. However, as the tablet of Pepper is not tactile in its current version, we made some design choices thinking that the tablet is mainly a visual support for the person interacting with Pepper to be aware of the possible actions to do.

15

16

Our design choices are based on Nielsen's heuristics [1]. Below is the list of design choices we performed:

17

* The design of the visual is extremely simplistic as it needs to be used by users that are unfamiliar with technology. This is based on the 8th principle: Aesthetic and minimalist design.

18

* Moreover, we tried to use rather large font so that again it would be easier to read for any type of patient that might have a need for glasses. This is based on the 2nd principle: Match between system and the real world.

19

* Every page is consistent with the others and have some specific standards. This is based on the 4th principle: Consistency and standards.

20

21

This is the list of feature that has a page:

22

1. Neutral colour background

23

1. A title page, that provides confirmation to the user that they are on the correct page. This is based on the 1st principle: Visibility of system status.

24

1. Multiple coloured boxes that refers to either activities or setting up.

25

1. An emergency button, in case an external help is needed.

26

27

Of course, the pages below can be seen as example, but they could be adapted to each patient's need. The activities can be tuned for the patient's need.

28

= Landing Page =

29

This landing page has for objective to be shown when Pepper is waking up. Once the user see that page, we believe that Pepper could that The current user would have

30

[[image:homepage.png||width="1000" height="560"]]

31

32

= Patient Page =

33

This page has for objective to display every potential interaction that the PwD could make use of when communicating with Pepper. As discussed in the [[Humanoid Robot>>https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/view/Foundation/Technology/Humanoid%20Robot/]] section, Pepper vocal system works using keywords. Therefore, we believe that by displaying the keyword for which Pepper has been precoded to respond to, it will encourage the user to employ the appropriate keyword that has been predefined.

34

[[image:patientux.png||width="1000" height="560"]]

35

36

= Patient's relative Page =

37

[[image:patientrelativeux.png||width="1000" height="560"]]

38

39

= Health care professional Page =

40

[[image:hcpux.png||width="1000" height="560"]]

41

42

[1]: Molich, R., & Nielsen, J. (1990). Improving a human-computer dialogue. Communications of the ACM, 33(3), 338-348.

Wiki source code of Graphical User Interface