-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path1_Introduction_goals.tex
159 lines (133 loc) · 8.79 KB
/
1_Introduction_goals.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
\section{Introduction and Goals}
According to the \acrfull{fao} in 2019, 931 millions tonne of food were wasted [\cite{refart:FAOFW}]. This has
environmental, but especially social consequences. In a world where approximately 9.9\% of the [\cite{refart:AAHWH}]
population suffers from hunger that waste percentage sounds paradoxical.
As reported by the \acrfull{un} 5\% of the global food loss and waste comes from restaurants [\cite{refart:UNSP}].
The solution for this problem must be locally applied so its effects can be seen in a global structure. To do
so we propose to develop a mobile application that connects restaurants, bakeries and or pastries to clients. The
former would offer their remaining products, which are still consumable, prior to the closing time, to a small price
and the latter would browser in the app to find which shops are offering products.
We as ``Clean Up the World \textregistered'' are a rising StartUp whose main concerns is to find environmental solutions to
daily problems. Our portfolio includes projects about management of waste and optimization of household water
usage. This product we want to develop targets small communities, like small cities or regions within a big city,
to reduce the amount of wasted consumable food.
With our project we want to achieve the following goals:
\begin{itemize}
\item Connect \glsplural{provider} with \glsplural{client}, so the former can offer products that the latter
can purchase
\item Collect statistical data about waste reduction within the \glsplural{provider}
\item Promote reduction of food waste that still could be consumed
\item Allow \glsplural{client} to have a different dining experience.
\item Allow \glsplural{provider} to promote their products and gather new clients.
\end{itemize}
To make the easy to read we will use the pronouns ```he''' and ``his'' every time we refer to a single person.
After having an general idea on what the \gls{app} should do, we create the following \gls{sketch} to promote a simple visual
example of our product when in use. This picture was shown to our intended \glsplural{user} and to the boarding committee
so they could have a idea of what to expect.
\begin{figure}[H]
\centering
\includegraphics[width=1\textwidth]{assets/sketch.jpeg}
\caption{Sketch of the first idea}
\label{fig:sketch}
\end{figure}
\subsection{Design Purpose}
The main purpose of this architecture is creating an exploratory prototype of an \gls{app}. We aim to test it with potential
\glsplural{stakeholder} and regions to analyze their general acceptance and wishes [\cite{refbook:DSHC}] and get a fast feedback.
This prototype will also make it feasible to identify unknown needs an wishes of the potential \glsplural{stakeholder}, so we
can eventually increase the scope of functionality. Exploring this domain will also provide us with information regarding
the behavior of our target group when it comes to buying and serving food that would be wasted, but is still consumable.
\newpage
\subsection{Functional Requirements} \label{Requirement_Overview}
The following functionalities describe the basic requirement for the \gls{app}. They were used as main drivers
for the development of this prototype.
\begin{tabularx}{\textwidth}{ccX}
\toprule
Id & Requirement & Description \\
\midrule
F-1 & Register as \gls{client}. & A \gls{client} can register to the app with its e-mail.\\
F-2 & Login & After registration \gls{client} can login into the app. \\
F-3 & Purchase option & A registered \gls{client} can purchase an available offer (see F7).\\
F-4 & Filter/search options & A \gls{client} can perform filter and search actions for products.\\
F-5 & Register as \gls{provider} & A \gls{provider} can register his store and add logos and pictures.\\
F-6 & Create offer & A registered \gls{provider} can publishes what products they are offering with price
and amount. \\
F-7 & Upload offer & A registered \gls{provider} can add, edit or remove offers to his catalog.\\
F-8 & Check orders & A registered \gls{provider} can check all existing orders targeting his shops.\\
\bottomrule
\end{tabularx}
\begin{table}[H]
\setstretch{1.0}
\begin{tabularx}{\textwidth}{lX}
\toprule
ID & Motivation \\
\midrule
F-1 & The entry door of the \gls{app}, where our \gls{client} get an overview of all available offers \\
F-2 & In order to place purchases our client need to be registered. It will also provide
statistical information about consumer behavior \\
F-3 & Since we are dealing with a business relationship we have on one side a client willing to pay
and for a product and on the other side a provider willing to offer a product/service \\
F-4 & Like any other online-shop it is important that our \gls{client} can browse through the available possibilities\\
F-5 & In order to make a product available a \gls{provider} needs to register his shop. This information will
also be used for statistical analyzes about providers, products and consumer behavior \\
F-6 - F-7 & A registered \gls{provider} can make an offer available according to his daily planning.
For future development of this app, this will be helpful to identify tendencies regarding dates, periods
and availabilities. \\
F-8 & Also registered \glsplural{provider} can get an overview about how often their products have been sold. This
may open a different kind of business orientation. \\
\bottomrule
\end{tabularx}
\end{table}
\newpage
The following \gls{use case diagram} should give our \glsplural{stakeholder} an overview of the primary functionality
of the app:
\begin{figure}[H]
\centering
\includegraphics[width=0.5\textwidth]{assets/preliminary_functions.jpg}
\caption{Preliminary functions}
\label{fig:preliminary_use_case}
\end{figure}
\subsection{Quality Goals}
The key qualities of this app are described in the table below:
\begin{table}[H]
\setstretch{1.0}
\begin{tabularx}{\textwidth}{|c|c|c|X|}
\toprule
\multicolumn{1}{c}{ID} & \multicolumn{1}{c}{Quality} & \multicolumn{1}{c}{Priority} & \multicolumn{1}{c}{Motivation} \\
\midrule
QA-1 & \textbf{Usability} & 1 & Since we are working with a prototype it is important the usage is easy as possible,
to attract more \glsplural{user} and to gather information about consumer behavior. \glsplural{client} and \glsplural{provider}
should have a simple interface where they can quickly interact without any burdens. \\
QA-2 & \textbf{Interoperability} & 2 & To reduce programming burdens and accelerate the delivery of a working product the
registration and payment process will rely on third party providers. For that reason the developed features should
work faultless in combination with the external \glsfirst{API} (i.g \gls{mobile payment gateway} and \gls{federated login}). \\
QA-3 & \textbf{Security} & 3 & To guarantee a secure and easy payment process we will handle the \gls{API} of the
\gls{mobile payment gateway} within the development process. The possibility of outsourcing this service would cause
a big damage to the first priority. \\
\bottomrule
\end{tabularx}
\end{table}
\newpage
\subsection{Stakeholders}
The main \glsplural{stakeholder} of this app are described in the table below:
\begin{table}[H]
\setstretch{1.0}
\begin{tabularx}{\textwidth}{cXX}
\toprule
Stakeholder & Description & Motivation \\
\midrule
Providers & Owner of a restaurant, bakery or pastry. & One of the protagonist of this app. They will interact
with clients using the app. From his usage we will gather valuable information about consumer behavior. \\
Clients & Person who wants to purchase last minute product from a provider. & The second protagonist of the app
they will interact with the provider to search and to purchase product. The result of this interaction will
provide us with statistical information to understand how food waste can be reduced. \\
Developers & Team in charge of creating the application using existing tactics and creating new solutions.
& Responsible for guarantee that the main requirements of the app are fulfilled and fully functional.
Since they will be dealing with the background of the product, it is important that they understand it very
good so it can also be implemented in a final version.\\
Boarding Committee of \\ ``Clean Up the Word (R)'' & Members of the management team who wants to delivery
environmental solution do daily problems and at the same time develop a profitable product.
& Group in charge of main decisions regarding what will be developed. Their decision are based on mark tendencies
and on environmental issues. \\
\bottomrule
\end{tabularx}
\end{table}