We are three students of the MSc of Engineering in Computer Science of Sapienza University of Rome and this project has been developed as part of the Internet of Things 19-20 course. Visit our LinkedIn profiles to learn more about us.
ARte (Augmented Reality to educate) is a smartphone application for the Sapienza University of Rome's Arte Classica Museum that aims to improve the interaction between visitors and artworks and social distancing (COVID-19 era), providing useful information to the museum’s managers at the same time.
By accessing the mobile app website, visitors will be able to perform various functionalities on their device based on the Augmented Reality technology powered by IoT data. Such data are provided by several STM32 Nucleo boards installed throughout the museum.
At the same time, after the explicit agreement of the user, data about the usage of the web app is anonymously collected to preserve privacy via crowdsensing.
All data is then displayed on a dashboard website to allow museum managers to analyze it for statistical purposes.
- Design: a document that shows some details on the product/service from the user point of view.
- Architecture: a document that includes details on the technical aspects of the product/service, including a high-level presentation of the conceptual architecture of the software and hardware components that make up the product/service, a description of the main software/hardware components, how these components interact and a network architecture.
- Evaluation: a document that provides details on how to evaluate the product/service, from a user experience point of view and from a technical point of view. The document describes the evaluation methodology for both the overall system as well as each individual component for the technical/user dimensions.
- 2nd delivery: a document that briefly explains:
- the comments that we received during the 1st delivery and how we have addressed them,
- changes made to our design, architecture and evaluation plan since the 1st delivery,
- a brief presentation of the technical work done since the 1st delivery,
- a brief list of the functionalities that is still missing and will be done till the 3rd and final delivery,
- a brief presentation of the evaluation conducted since the 1st delivery,
- a brief list of what we expect to evaluate till the 3rd and final delivery.
- 3rd delivery: a document that briefly explains:
- the comments that we received during the 2nd delivery and how we have addressed them,
- changes made to our design, architecture and evaluation plan since the 2nd delivery,
- a brief presentation of the technical work done since the 2nd delivery,
- a brief presentation of the evaluation conducted since the 2nd delivery,
- a brief list of the functionality that is still missing.
- Presentation of the product/idea and the evaluation plan.
- Presentation of the technical approach and architecture.
- Presentation lecture slides.
- Results of the first survey about the idea
- Presentation of the project from a technical point of view, including a demo.
- Presentation of the evaluation of the project that has already been done.
- Presentation of the future plans for technical development and evaluation until the 3rd and final delivery.
- Presentation lecture slides.
- Results of the second survey about the UX, UI and the idea.
- Demo of the project.
- Hackster article presenting the project.
- Presentation slides.
- Results of the third survey about the UX, UI and the idea.
This project is licensed under the MIT License.