2DAMi 30/05/2023

Mikel Bermejo, Haizea Franco, Julen Barainca y Sendoa Badiola

MyHealthyDiet
1. Introduction 3
2. Analysis 3
2.1. System definition 3
2.1.1. Functional description 3
2.1.2. User identification 4
2.2. Specification of use cases 4
2.2.1. Diet management use cases 4
2.2.1. Plate management use cases 5
2.2.3. Ingredient management case uses 5
2.2.4. Tip management case uses 6
2.2.5. User management case uses 6
2.3. Conceptual Data Model 7
2.4. Solution software architecture 10
2.4.1. Server side software architecture 10
2.4.2. Client side software architecture 11

2
1. Introduction
In this section we determine the technical parts of our project. We
specify the main elements of our application. On the one hand the
analysis and on the other hand all the functionalities necessary to deploy
the application.

2. Analysis

2.1. System definition

2.1.1. Functional description

It is an application aimed at all users who want to live in a healthy way

but cannot or do not want to go in person to a specialist. It will be
available in play store, app store and the respective web page of the
application.

Software:
The desktop and tablet software will be installed on play store, app store
and the respective application website.

Hardware:
Using the existing database in the company and its own network we will
develop a solution with a desktop and cell application that users can get
on the internet and play store. To perform it we will manage a server with
different protocols. You can have a continuous flow of 5000 users
simultaneously.

3
2.1.2. User identification

There are two types of users: client and administrator.

The administrator will have full access to view, create, delete or modify
the inventory. He/she will be in charge of receiving incidents and
completing the necessary actions. He/she will also register the users.

The client will have a more limited access, being able to interact only by
choosing diets, sending incidents and will be able to see all the visible
functionalities, statistics, tips and progress.

2.2. Specification of use cases

2.2.1. Diet management use cases

4
2.2.1. Plate management use cases

2.2.3. Ingredient management case uses

5
2.2.4. Tip management case uses

2.2.5. User management case uses

6
2.3. Conceptual Data Model

7
8
9
2.4. Solution software architecture
2.4.1. Server side software architecture

10
2.4.2. Client side software architecture

11
12