ViaDe 1.1 en3b

Nowadays, all the average social platforms for hikers are centralized and not totally secure services. With Viade, we present a proyect that consists of a decentralized routes management system developed following solid specifications.

The main requirements are:

The objective of Viade is to give users a platform where they can share their taste and opinions about the routes they take, in a way that they can be sure all their data will be secure.

Their contributions have make this project posible

Viade´s main goal is to give the ability to store, visualize and be shared to the routes withou storing the actual data, which is kept by the users.

The public target for the applications is all types of users, but especially non-technical users. The application will allow the user to store and visualize their routes in a map.

The users will be able to communicate among them by sharing routes, pictures or videos. The interaction can be between two individuals or multiple, by creating groups of friends. Whenever a user shares content with another one, the target receives a notification.

The application is decentralize, the application and the data storage are separated, being this last one owned and stored by the user. As the application will support interoperability, our users will be able to use the routes and other data in different applications with a similar functionality.

The main idea is to separate the data storage from the rest of the app, so each user will be able to store its data. The communication between the different users and the data sharing will be managed by the application itself.

To achieve this, we follow the SOLID specifications as it ensures that our application is decentralized. Each user will be able to store its data in their own POD and grant the applications access to just certain type of data. With SOLID users can use the data of the routes in other applications that also use that kind of data.

Javascript is going to be used as the programming language, since we are going to make use of the framework React, which makes it easier to develop interactive and attractive graphic interfaces, which is key to obtain a usable interface.

For developing Viade we will be following the next strategy (the necessary reasoning of our decisions is explained in section 9):

Because of the participation in the Inrupt challenge, we will follow the Solid project principles:

Basic usability goals:

We have agreed that the best way for developing Viade is following Scrum.

Functionality will be developed incrementally and at the end of every sprint (three weeks long) we will have working software.

In this first level we take a look on viade’s parts.

These are react components, they show the interface and interact with the user. The components not only encapsulates parts of the interface, but also funcionalities.

They manage the interaction with the pod and translates the data.

Since solid slows down when it needs to retrieve a lot of data we decided to implement a small cache that temporaly stores the routes whithin the session.

Even though they are not reprresented in the diagram, they are clases that represent data. These makes that makes the file format of the routes independent from the rest of the aplication. The interface components and the cache deals with the Route entity and others, instead of dealing with the files directly.

Thie second block is a closer look into the handlers.

It coordinates the interaction between the information retrieved from the pod and its tranlation into entities.

It deals with getting and uploading files into the pod.

They translate the files from the pod.

These would be and example of the diferent parts interacting when uploading a route.

This is the runtime view on how to log in viade.

This is the runtime view on how to create a route in viade.

This is the runtime view on how to visualize a route in viade.

Viade is a browser application, which means that it only requires:

The information stored, and showed in our application will be mostly about routes.

A route is a logic entity, independent from the format in which it is stored and the attributes that it contains, that represent a trajectory formed by different points on the real world.

Routes can be stored and loaded from the Pod of each user independently of which application has created them. That is because, thanks to the ViadeSpec, we have defined an specification that grants interoperability with other route management systems.

Routes are shown to the user through two different interfaces: one where they are listed with the map and the most important data about them, and the other one with more specific data (such as images) that the user can see when accesing the routes details.

We will contemplate two kind of scenarios: * Usage scenarios describe the reaction of Viade to a stimulus. * Change scenarios indicate whether a modification of the system is done.