D7.2 Necessary hardware and software package for the student pilot deploymen
By Kasper Damgaard, Hamza Ghani, Norbert Goetze, Anja Lehmann, Vasiliki Liagkou, Jesus Luna, Gert Læssøe Mikkelsen, Apostolos Pyrgelis, Yannis Stamatiou
Download: PDF, Review Status: Not yet externally reviewed
In this document we provide the details of the implementation of the Patras pilot system components as well as their API mapping with the first version of the ABC4Trust reference implementation. We explain how these components interact among them as well as with the pilot users. We provide the details of their set-up, initialization, and proper operation within the ICT infrastructure of CTI and the users’ personal computers. We also provide the results of a preliminary risk analysis of the pilot system and we give in the Appendix the user manual for the pilot participation of the students, the user consent form as well as the course evaluation questionnaire that will be used during the course evaluation period.
In this deliverable we provide the details of the implementation, set-up and operation of the system that will be employed in the Patras pilot of the ABC4Trust project: remote evaluation of courses by University students. The design, implementation, and testing of the pilot system was based on the use cases and pilot requirements documented in deliverables D5.1, D5.2, and D7.1 as well as the first version of the ABC4Trust reference implementation of Privacy-ABCs provided by WP4.
The architecture of the pilot system, as explained in the deliverable, is comprised of five main components: (i) the Identity Management System, which is responsible for issuing credentials to the students, (ii) the Course Evaluation System, which supports the remote evaluation of university courses by eligible students, (iii) the User Client System, which allows students to view and manage their credentials, (iv) the Class Attendance System, which registers the number of times that students attend a course, and (vi) the Smart Cards and Smart Card Readers, which are distributed to the students in order to prove their eligibility for evaluating a course based on Privacy-ABCs technology.
In the sections that follow, our objective is to provide the details of the implementation for each of these components as well as their interaction towards the realization of the pilot’s use cases. Emphasis is placed in providing practical implementation requirements and describing in detail the necessary hardware, software, and network environment in which these components can operate efficiently.
We also provide the API mapping of the software components to the ABC4Trust reference implementation libraries as well as the interfacing and interactions protocols employed between the various modules.
Moreover, a preliminary risk analysis is provided that was applied to the current configuration of the pilot system in order to identify and rank the potential risks. We also show how we handled the risks through the security measures provided within CTI’s premises and network configuration.
Finally in the Appendix, although it does not concern the integral parts of the pilot system, we give the following information that is nevertheless necessary for the appropriate set-up and run or the pilot and its use cases: the user manual, which the students will be consulting during the operation of the pilot, the course evaluation questionnaire, and the user consent form that they have to sign in order to give their consent to participate in the pilot.
Results pertaining to the evaluation of the pilot, the reference implementation as well as the Privacy-ABCs technologies, in general, based on pilot participants’ feedback will be documented in deliverable D7.3 by the end of Month 36 of the project.