ViaDe_es5a

The different users in the software product we are dealing with are the following:

In addition, we have the following services involved in the system:

The implementation of the system should be done using the React framework that provides the developer the facility to design a usable web page for the user. This will allow to create a path storing milestones, images and videos.

The processing of the files must be done using RDF, a system that SOLID is compatible with. The information will be treated and processed in the client and will be sent to the server where it will be stored. If any information is received, this action will be carried out in the opposite direction.

Solid’s POD server will allow us to store the information in our POD, and access the information in the PODs where the user has permissions.

For the representation of the routes, Google Maps API will be used. It corresponds to the most advanced and used map-related service.

On the other hand, all communication in the application should be through HTTPS using TLS. It is necessary that all TLS requirements that this implies are met, as well as having a valid certificate.

Below is the domain model of the route management application.

Throughout the development of this project, we will build on the architectural pattern based on Layered Arquitecture:

As for design patterns, patterns such as Observer are likely to be used: * It is mainly used to implement distributed event handling systems, in "event driven" software. In those systems, the subject is usually called a "stream of events" or "stream source of events", while the observers are called "sink of events".

More patterns will be used such as the Factories: * It is a creational pattern that uses factory methods to deal with the problem of creating objects without having to specify the exact class of the object that will be created.

For the use of the application, only a series of steps will be necessary:

The team of developers reserves the right to be able to modify the application at any time, always to try to fix or improve existing aspects or to add any other that is considered convenient. Therefore we do not take care of any problem caused by such change.

As for the implementation, we will always try to make the decision that assumes that the code is less coupled, dividing the code by layers. In this way it will be much easier to modify any type of change and in turn fix any existing fault. Any type of pattern that assumes a good balance between the difficulty of understanding and modifying the code and the increase in performance that this entails will be used. Duplication of the code will be avoided.

We will try to make the user have a good experience with the application, providing a friendly interface that will consist of fundamental things such as:

We will not be as dedicated to security as to other aspects, but if we focus on data privacy, this application will be safe, since based on solid, you will get all the route data that the customer will be providing throughout your stay in the application they will be stored in your terminal and not in a centralized data system as other important companies like Facebook and Instagram do. To this we add the "https" protocols that increase security in the browser.

Within the development concepts, the concept of "Build, Test, Deploy" should be highlighted. This concept is what we will rely on to fulfill a good design. The design process looks more or less like this:

There are other concepts such as code generation, migration, configurability that we will not enter but that we will take into account when making our application.

There are numerous operational concepts among which the following stand out:

It should be noted that we will not use the disaster-recovering option due to the lack of resources we currently have at our disposal. Also we will use another technique called backup. In this way we can restore the web application in case of an unexpected error.