Changes for page Graphical User Interface

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,4 +1,5 @@
1	1	= Motivation =
	2	+
2	2	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:
3	3	1. Voice
4	4	1. Tablet
...	...	@@ -28,21 +28,21 @@
28	28
29	29	The pages below can be seen as an example, and they could be adapted to each patient's needs. The activities can be tuned for the patient's needs as well.
30	30
31		-= Landing Page =
32		-This landing page has for objective to be shown when Pepper is waking up. Once the user see that page, Pepper should ask the identity of the person interacting with her and the visuals should propose different answer proposition. The visual below are generic role, however, they could be tuned to first names so that Pepper seem more friendly and human.
	32	+== Landing Page ==
	33	+There is first a connection page. When opening the app, the user is required to pick their role, as shown in the picture below. Then, they log in with their credentials (log in page not shown).
33	33	[[image:homepage.png||width="1000" height="560"]]
34	34
35		-= Patient Page =
36		-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.
37		-We defined the first row as potential activities for the PwD to do, and the second row as potential use cases where the PwD needs Pepper help.
	36	+== Patient Page ==
	37	+This page has for objective to display every potential interaction that the PwD could make use of when communicating with Pepper. In case the PwD wants to directly start an activity with Pepper, they can also see them from the app. This also allows for checking which activities are currently implemented on Pepper for the specific PwD.
	38	+We defined the first row as potential activities for the PwD to do, and the second row as potential use cases where the PwD may need Pepper's help.
38	38	[[image:patientux.png||width="1000" height="560"]]
39	39
40		-= Patient's relative Page =
41		-This page has for objective to display every potential interaction that the patient's relative could make use of when communicating with Pepper.
	41	+== Patient's relative Page ==
	42	+This page has for objective to display every potential interaction that the patient's relative could make use of regarding Pepper.
42	42	[[image:patientrelativeux.png||width="1000" height="560"]]
43	43
44		-= Health care professional Page =
45		-This page has for objective to display every potential interaction that the patient's relative could make use of when communicating with Pepper. Most interactions of the HCP are about editing the patient's information or preferences. As the health care professional might not be trained to make some changes in the code of Pepper, if a separate website/online platform is not provided to the HCP, we believe that making use of Pepper for helping the HCP to modify some information could be useful.
	45	+== Healthcare professional Page ==
	46	+This page has for objective to display every potential interaction that the patient's relatives could make use of regarding Pepper. Most interactions of the HCP are about editing the patient's information or preferences.
46	46	[[image:hcpux.png||width="1000" height="560"]]
47	47
48	48	[1]: Molich, R., & Nielsen, J. (1990). Improving a human-computer dialogue. Communications of the ACM, 33(3), 338-348.