alessiomason / se2022-11-hiketracker

Main project for the Software Engineering II course (group 11)

SE2022-11-HikeTracker

This repository contains the main project developed (by group 11) throughout the Software Engineering II course @ Politecnico di Torino. It consists of a web application to browse hikes and huts and to track personal hikes.

🌐 Qui in italiano

Features

• Browse hikes, huts and parkings using a series of filters
• See an hike condition and weather reports for the area
• Track an ongoing hike and mark reached reference points
• Visualize general performance statistics, summarizing all registered hikes
• As a local guide or a hut worker, manage hikes and huts information
• As a manager of the system, approve local guides and hut workers

Technology

The application is developed in JavaScript and uses a two-server architecture: it uses Express as a framework for the backend and React for the frontend.

Screenshots

Home page	Explore hikes
Hike page	Tracked hike

Hard-coded users

Email	Password	Access right
[email protected]	password	Platform manager
[email protected]	password	Hiker
[email protected]	password	Local guide
[email protected]	password	Hut worker

Running the software

The software can be executed by running the services' Docker containers.

Docker commands for client

To use the Docker service for client:

• git pull origin main
• docker pull erengul/se2022-11-hiketracker-client:latest
• docker run -it -p 3000:3000 erengul/se2022-11-hiketracker-client:latest

It will run over the 3000 port.

Docker commands for server

To use the Docker for server:

• git pull origin main
• docker pull erengul/se2022-11-hiketracker-server:latest
• cd /server/
• sudo docker run -v $PWD/db:/db -p 3001:3001 erengul/se2022-11-hiketracker-server:latest

It will run over the 3001 port.

Run both services

In the root folder, run docker-compose build && docker-compose up.

• https://hub.docker.com/repository/docker/erengul/se2022-11-hiketracker

Commands for testing

cd ./server

npm run test (Unit Tests)

npm run apiTest (Integration Tests)

Tests status

se2022-11-hiketracker's Issues

[DEMO 4 - Visitor] Website colors

You have done a really well job on the site interfaces. However, I have noticed that there are many different colours used on the various pages, and this can become annoying. The variety of colours can distract attention and make it more difficult to navigate the site. In addition, too many colours can tire the eyes and psyche of users. I would suggest limiting the number of colours used on the site and using more uniform shades to increase the usability and user-friendliness of the interfaces.

Responsive Display

As a visitor, I want to use the website on my smartphone: the application in general is responsive but I only found a small bug regarding the image on the homepage when I made the screen smaller

[DEMO 4 - Local Guide] Not always clear where to find operations

I have noticed that sometimes it is not always clear where to look for the actions I need. For example, to manage changes in huts, parking lots and hikes, I need to go to my personal profile, but I do not find much correlation in this. This can make it difficult for us local guides to find what we need and can also increase the time needed to complete an action. I would suggest that you consider how to better organise the layout of the site so that it is more intuitive for us local guides to find what we need.

Closed and completed hikes

As an hiker I find strange the possibility of suspend a hike in progress without being able to resume its execution later on. Moreover, stopped hikes must not be in the list of completed hikes to avoid being misleading. A solution could be just a change of title (from "completed hikes" to "history", for example) or provide stopped ones in a separate list.

Reference Point Hiker Description

As a local guide, I would to add one or more reference points when I upload a new track file and edit the fields of the hike description

Use plural for lists links in the navbar