2. Methods
The design of ecological training tasks for executive functions necessitates a coordinated multidisciplinary research effort. On one hand, complex technical solutions are required, such as adapting to the difficulty of performing exercises or exploiting automated planning techniques for the exercises. On the other hand, the supervision of cognitive psychologists is of paramount importance. Testing with subjects is essential for tuning tasks before delivery. It is also essential to consider issues such as personalisation and adaptability when working with older adults [
14]. Indeed, the reduced plasticity in ageing necessitates a higher level of customisation and adaptability.
The cyclic development process is depicted in
Figure 1. The development of tasks is divided into six macro phases based on a cyclic structure. The sequence of the phases is not fixed; movement between them is possible in both directions. The outcome of each phase determines which phase has to be performed next. A working version of the software is produced during the first step, so experimentation can start early in the software life cycle. Each subsequent release of the task incorporates new functions or rectifies any deficiencies present in the previous release.
The identification of the task commenced with an initial prototype of a cognitive training task, named Weekend in Rome referred to as Version 0.0 (V0.0), which required users to plan a two-day vacation in Rome [
12]. This prototype was subsequently enhanced (V1.0) through the involvement of older adults in focus groups [
13], with the objective of addressing fundamental requirements. Subsequent to this, two pilot studies were conducted, with the objective of fine-tuning the task and its difficulty levels. A usability study (A) was conducted to assess user satisfaction, which enabled the prototype to be refined (V2.0). An evaluation study (B) was then carried out to assess the system’s effectiveness and gather preliminary results. The following sections present the details of the training task and the two pilot studies.
2.1. The Weekend in Rome Task
In the Weekend in Rome task, users have to organise virtual train and hotel reservations and to complete various activities, such as visiting specific locations and attending particular events. To execute these tasks, users have to navigate a map where the goals are those typically encountered in real-life planning of trips (e.g., making reservations, checking bus schedules, and noting opening hours of specific locations). This scenario is encoded as a planning problem using PDDL (Planning Domain Definition Language) [
15]. This approach enables the generation of numerous instances of the problem, each featuring different goals and constraints. This is possible because the planer can be used to assess the feasibility of each instance.
The system proposes three main stages of difficulty, designated as easy, medium, and difficult. Each stage comprises at least three distinct instances of the problem, each of which must be solved twice in order to advance to the subsequent level. The easy stage is characterised by a map in which each point can only be reached on foot, there are eight Points Of Interest (henceforth referred to as POIs) placed on the map, and the user is required to solve from a minimum of three goals to a maximum of five. In the medium stage, a map is presented where some connections are possibles only with the use of buses. Buses operate on a scheduled basis, with specific times of operation indicated on the map. Additionally, the map includes a second railway station, from which users can embark or disembark. An illustrative example of this stage is presented in
Figure 2. In the medium stage, users are required to achieve a number of goals, ranging from a minimum of six to a maximum of eight. In the difficult stage, a new POI is added to the map, and users are asked to achieve a minimum of seven and a maximum of ten goals. For each stage, three instances of the task are provided with increasing difficulty levels. In order to complete their training, users must finish all difficulty stages, consisting of nine tasks, planning their journey by achieving at least 80% of the goals in each task.
Three types of goals can be achieved: a simple passage from a POI (e.g. visited Pantheon); a visit at a POI, which must take place within the opening hours of the attraction (e.g. done-activity Colosseum); a visit at a POI at a given time, for doing a specific activity (e.g. done-activity-timed Olympic Stadium at 18). Although, the developed exercise is specific to Rome, the structure can be implemented for any European city.
2.2. Exploiting Automated Planning
Versions 0.0 and 1.0 of the Weekend in Rome prototype were based on an automatic planner, PDDL4J (Planning Domain Description Library for Java) [
16]. The planning domain is described using PDDL 1.2, which also allows the specification of several problems to be solved dynamically.
The planning domain encodes a set of PDDL rules, which encompasses all possible actions and interactions with the user. These include travel (e.g., walking, bus, and train), activities to be carried out at a POI (e.g., visiting, visiting at a certain time), sleeping and having breakfast in a booked hotel, and exercising. A planning problem, in accordance with the specified difficulty stage, incorporates the specific activities, bus and train timetables, connections between the various points on the map, and the goals to be achieved.
The planner is employed in different phases of the training process, namely for the generation of new solvable exercises and for the evaluation of solutions. The interaction between the user and the planner is depicted in
Figure 3. The Trip Generator is activated when the user is required to undertake a new instance of the task (1). It takes as input the user profile and the level of difficulty of the new task (2), and generates a new problem instance by extracting the goals to be achieved by the user from a set of possible goals randomly (3a). Successively, the Trip Generator calls the Planner to find a plan that solves the new instance of the problem (4). If the Planner fails, steps (3a) and (4) are repeated, and other goals are selected until a solvable scenario is created (3b). Once a solvable scenario is generated, the user can start to execute the task (4). At the conclusion of the exercise, upon the user’s completion of their visits by taking the return train (5), another component is initiated, the Trip Evaluator (6). The Trip Evaluator quantifies the number of goals attained, assigning a percentage rating to the user, ranging from 0 to 100. A difficulty level is deemed to have been successfully completed when the obtained percentage is at least 80%. Consequently, it is possible to pass the instance of the problem even if the plan has not been fully executed. Furthermore, the Trip Evaluator provides feedback to the user on the plan implemented (7). For example, "Congratulations! You completed this exercise without any errors" when a difficult exercise is passed, or "This exercise was much more difficult than the previous one. Try to keep track of bus schedules" in case of failure.
2.3. Pilot Study A: Testing Usability and Satisfation
A pilot study (A) was conducted with a group of healthy young and older adults to assess the usability of the Weekend in Rome (V1.0) task. The aims of the pilot study were the following:
to provide a preliminary validation of the usability of the training task on healthy older adults;
to identify the specific requests and needs of the older adults when performing the task;
to identify processing characteristics specific to older adults by examining differences in performance between older and younger adults;
to test the difficulty stages proposed by the system;
to collect all the relevant suggestions proposed by the participants.
A total of 22 participants were recruited for the study, comprising 11 young adults (aged 18-26 years) and 11 older adults (aged 62-83 years). The young adult group, comprising three males and eight females, had an average age of 23.64 (SD=1.12) and an average of 17.27 years of education (SD=1.01). The older adult group, comprising six males and five females, had an average age of 68.73 (SD=7.55) and an average of 11.45 years of education (SD=1.96).
All participants completed a series of 40-minute training sessions until they had experienced all the difficulty levels. Prior to the commencement of the study, all participants signed the Research Informed Consent Form and received written instructions for accessing and utilising the training tool. The young adults completed the online sessions independently, while the older adults were supervised until they demonstrated satisfactory compliance with the tool. All participants were instructed to contact the experimenter should they require further information or clarification. The sessions were monitored using the remote-control facilities provided by the system. At the conclusion of the sessions, all participants completed a usability questionnaire.
2.3.1. Results of the Pilot Study A
The results of the usability questionnaire indicated that all the older participants were able to easily access the online system. Furthermore, the majority of them (9/11) reported no difficulties in understanding and performing the task. The responses were based on a Likert scale (1= not at all; 4= a lot). The majority of the older participants indicated that good planning abilities (M=3.64; SD=0.50) and computer experience (M=3; SD=0.63) were crucial for completing the task. With regard the gradual increase in difficulty, the responses indicated a limited satisfaction (M= 2.45; SD=0.93). Furthermore, the item related to the ecological quality of the task indicated a need for improvement (M= 2.73; SD=0.90). Older adults identified the high involvement, the possibility to improve their problem-solving and planning abilities, the engaging and challenging task format, and the new technological approach as the main strengths of the task. Older participants offered a number of suggestions for improvement. These included making the task goals visible on the map at all times, streamlining the train booking process, adding new places to visit, changing the colour of the streets in the map to enhance visibility, adding new actions related to a real journey (i.e., the introduction of a budget for the trip to cover expenses of hotels, trains and buses). All participants successfully completed the task.
A t-test was conducted on the critical dependent variables with Group as the between-subject factor (young vs older). The following performance variables were evaluated: number of not achieved goals, execution time (minutes), number of clicks on reservations, number of clicks on goals. See Table 1 for the results. A significant difference (p <0.05) was found between the two groups in the number of not achieved goals, execution time, and number of clicks on reservations. The older adults showed a higher number of not achieved goals, a longer execution time, and a higher number of clicks on reservation, indicating that they check the train and hotel reservations more often.
To test the difficulty stage proposed by the Trip Generator, a repeated measures ANOVA was carried out on execution time. The between-subject factor was Group (young and older adults), while the within-subject factor was difficulty stage (easy, medium, and difficult). The simple effects of group [F (1, 20) = 20, p < .001] and difficulty stage [F (2, 40) = 17.43, p < .001] were significant. It is noteworthy that the interaction between group and difficulty stage was significant [F (2, 40) = 5, p = .012] (see
Figure 4). Older adults were slower than younger adults for all the difficulty stages. Furthermore, older adults were slower in the medium and difficult stages relative to the easy stage. Interestingly, no significant difference emerged between the medium and the difficult stages for both young and older participants.
Table 1.
Means and Standard Deviations for the critical variables of the task.
Table 1.
Means and Standard Deviations for the critical variables of the task.
| Variables |
Young Group M(SD) |
Older Adults M(SD) |
p |
| Number of sessions |
2.09 (0.53) |
4.27 (1.10) |
< .001 |
| Not achieved goals |
8.73 (5.85) |
13.82 (6.08) |
.05 |
| Execution time |
79.95 (31.94) |
176.52 (66.66) |
< .001 |
| Clicks on reservations |
18.73 (11.81) |
32.55 (14.67) |
.02 |
| Clicks on goals |
86.91(22.88) |
110.7(40.3) |
0.12 |
2.4. The revised version of the Weekend in Rome task
The results of the pilot study A permitted the identification of several areas for improvement in the training task, particularly in relation to the utilisation of automated planning.
With regard to the user interface, the pilot study A confirmed that it was well designed and not confusing for older participants. Nevertheless, in response to the suggestions of the participants, several modifications were implemented. These included improvements to the map visibility, the display of task goals, and the train reservation procedures. In addition to conventional trains, the latter now include high-speed trains. To this end, a new panel was added in the interface to the right of the map presented in
Figure 2, which eliminates the need for repeated clicks on the reservations and goals buttons. Another suggestion was to make the task more similar to a real journey. To this end, new locations to visit were incorporated, short videos were created for specific POIs to present general information and their history, and new actions to accomplish were added.
However, several comments were not related to simple updates of the user interface, but rather had a strong implication on the system architecture. For example, the introduction of a limited budget for the trip to cover expenses of hotels, trains and buses. This new feature affected both the planner and the user interface, the latter with the introduction of a spreadsheet for expenses and simulation of credit card payments.
Considering the planner, a key objective was to enhance the progression of difficulty stages, implementing nine increasing difficulty levels (three for each stage).
In Version 1.0 of Weekend in Rome, the progression of difficulty levels was based on increasing the number of goals tied to specific times and introducing, from easy to intermediate levels, the presence of buses that allowed travel between points on the map only at certain times. These constraints led to a reduction in the number of possible plans for solving the problem and an increase in the number of steps required to solve the plan. The planning problem was encoded in PDDL 1.2, where time and movements were managed by predicates, and the actions that the user could perform on the map were described by actions in the domain.
While the introduction of buses from easy to medium stages allowed for an adequate increase in difficulty, we did not observe the same effectiveness in simply introducing a greater number of goals during pilot study A. Upon analysis of the results, it became evident that an increase in the difficulty stage did not always correspond to an increase in user difficulty. More precisely, it was observed that moving from the medium to the difficult stage, merely increasing the difficulty of the activities with more stringent time constraints and/or adding new goals did not necessarily result in an increase in the real and perceived difficulty: participants completed the training for the medium and the difficult stages in the same execution time. It became evident that the progression of difficulty stages in the final part of the exercise was not as steep as it could have been. In essence, the time required to solve these tasks and the number of attempts to pass them decreased on average, whereas an increase in both was expected and more appropriate for cognitive training. It was determined that this effect was caused by the rule used for passing to the next difficulty level, which applies when an 80% performance is obtained. The issue was that the minimum number of goals required to achieve the threshold was not changing in accordance with the progression of difficulty stages.
To address this issue, the rule for advancing to the next level was updated, requiring participants to achieve all the proposed goals and execute the plan without any errors. Moreover, additional goals and constraints were introduced to further reduce the number of possible plans to reach the correct solution. These included requirements to minimise the expense of the trip or the time spent in the city at the difficult stage. The introduction of the budget variable was intended not only to enhance the ecological value of the game but also to increase the difficulty of the exercises. At the difficult stage, three minimisation objectives were identified: one on time, one on costs, and one encompassing both time and travel costs.
Since these features were not supported by the planner used in the versions 0.0 and 0.1 (PDDL4J), which only supports PDDL 1.2, it became necessary to rewrite the domain using PDDL 2.1, introducing functions for the representation of time and budget. Consequently, an upgrade was implemented with the Expressive Numeric Heuristic Search Planner (ENHSP) [
17], which supports fluents and plan metrics as required by PDDL 2.1.
Figure 5 provides an illustration of the transition from PDDL 1.2 to 2.1. It presents the encoding of the action "travel-by-train," which implements the train trip to Rome, utilising budget and time as fluents. The definition of the planning domain was improved by employing a more expressive language. Indeed, several predicates were required to implement the progression of time in PDDL 1.2. These were used to represent that two time instants are consecutive and to state that they are not in the future anymore when the action is executed. In contrast in PDDL 2.1, increasing the time variable was sufficient.
2.5. Pilot Study B: Testing Difficulty Stages, Usability and Effectiveness
A new version of the Weekend in Rome task (V2.0), including all the illustrated changes, was delivered. Subsequently, a pilot study B was designed to test the progression of the updated difficulty stages, the usability of the improved version, and to gather preliminary effectiveness results. The specific objectives of the study were as follows:
This second pilot study (B) involved a cohort of healthy older adults only.
The objectives of this pilot study were as follows:
To assess the actual rise in difficulty compared to the previous version.
To validate the usability of the system, including the collection of suggestions and the assessment of participant satisfaction.
To assess the improvement in ecological appearance.
To test whether there are improvements in the trained cognitive ability, specifically planning and problem-solving skills.
To assess the trained cognitive abilities three months after the training.
The study comprised a sample of 22 participants (aged 67-81 years), divided into an experimental group and a control group. The selection criteria for participants in both groups were as follows: individuals aged 65 and above, with no cognitive and/or psychiatric disorders. The experimental group, comprising seven males and four females, had an average age of 72.72 years (SD=4.90) and an average of 12.36 years of education (SD=5.20). The control group, comprising six males and five females, had an average age of 70.18 (SD=4.35) and an average of 13.65 years of education (SD=3.75). Prior to the commencement of the study, all participants signed the Research Informed Consent Form. The experimental group received written instruction for accessing and utilising the training tool. The training phase was delivered exclusively to the experimental group and comprised eight training sessions (two per week), each lasting 40 minutes, using the Weekend in Rome task (V2.0). The training sessions were monitored, with 10 out of 11 participants being observed in person and one remotely using the facilities provided by the SWIFT platform.
The participants were assessed at three distinct time points: T1, the test phase, at the beginning of the study, to establish baseline performance; T2, the re-test phase, soon after the training, five weeks afterwards the test phase; and T3, the follow-up phase, three months after the re-test phase, exclusively among the experimental group. The assessments were administered to all participants at the Department of General Psychology (Padova). The following tests were administered: the Behavioural Assessment of the Dysexecutive Syndrome (BADS) [
18,
19] and the Everyday Problem Test (EPT) [
20,
21].
The BADS is a battery for the assessment of executive functions, comprising six subtests. The Rule Shift Cards Test assesses the ability to inhibit a previously learned response mode. This test is designed to assess cognitive flexibility. The Action Program Test assesses the ability to develop an action plan to solve a problem. The Key Search Test assesses the ability to plan actions and monitor one’s performance. The Temporal Judgment Test assesses the ability to predict and estimate time. The Zoo Map Test assesses the subject’s ability to plan and minimise errors through self-monitoring. The Modified Six Elements Test assesses the subject’s organisational ability, shifting ability and behavioural control. Each test is associated with a specific scoring method and is calibrated to establish cut-offs based on the age of the participant and the execution time. The EPT is a test of everyday problem-solving, with a focus on performance accuracy. It presents real-world problems covering all seven instrumental activities of daily living domains (household management, transportation, meal preparation and nutrition, financial management, health, shopping, and telephone skills). The abbreviated (14-item) and parallel (14-item) versions of the Italian adaptation of the test were employed. One point is awarded for a correct answer, while zero points are given for an incorrect response. Subsequently, the scores are adjusted according to age and educational level cut-offs.
Furthermore, usability and satisfaction questionnaires were administered at the conclusion of each training sessions, as was the case in Study A. Additionally, participants were invited to provide suggestions regarding potential modifications to enhance the training task and the SWIFT platform user interface through interviews.