iHelp: User Centric Design II

This deliverable is the second output of T2.4 – “User Centred Design”, targeting to provide a user centred design process and design thinking methodology that guides the design and development of the iHelp platform, as also to align the iHelp architecture and components with user centred design principles. Indeed, the software produced by iHelp will only be effective if users and patients continue to use the system for long enough to have an impact on their long-term behaviour and hence on their long-term risk of developing pancreatic cancer.
The nature of the user centred design process motivates a major difference between the outputs of T2.4 – “User Centred Design” compared to the other tasks in WP2 – “Requirements, State of the Art Analysis and User Scenarios in iHelp”. Moreover, it is worth to mention that D2.8 – “User Centric Design I” and D2.9 – “User Centric Design II” are separate deliverables covering results from different parts of the user centred design process and complementing each other in a whole, whilst the deliverables of the other tasks, for example D2.6 – “Functional and Non-Functional Specifications I” and D2.7 – “Functional and Non-Functional Specifications II” are two versions of the same deliverable, covering more detailed specifications as their task progresses. Thus, whilst an observer at the end of the project can read only D2.7 and skip D2.6, they will need to read both D2.8 and D2.9 to understand the results of T2.4.
The areas of focus of the current deliverable are:
▪ User involvement in formulating system functionality and interfaces is one of the main requirements of the regulations governing the development of medical-related software like iHelp. To ensure this user involvement, we conducted a series of workshops, where our pilot users were able to reflect on the proposed software functionality and to feed back their wishes in terms of improvement of this functionality. The results of the first round of workshops were reported in the preceding deliverable, i.e., D2.8 – “User Centric Design I” (M., N., C., + 21), whilst the results of the second round are reported in this deliverable (D2.9 – “User Centric Design II”).
▪ The finalised versions of the wireframes illustrating the agreed functionality of iHelp as seen by its users are presented here. These are based on the functional requirements produced by T2.1 – “Requirements, State of the Art Analysis and User Scenarios in iHelp” and represent the results of several iterations of user-driven development, including two workshops with our pilots, and earlier iterations with project partners and pilots.
▪ The Usability Engineering Guidelines are one of the main outputs of this deliverable, and they have been derived after carefully considering the characteristics of the different types of users, and the circumstances in which they will use the system, such as brightness, noise, etc.
▪ The Usability Evaluation Criteria described in this deliverable are the major contribution to the evaluation of the user interfaces that will be done later on in iHelp. These Key Performance Indicators (KPIs) are developed after working closely with end-users to ensure the long-term use of the iHelp software.