Skip to content
This repository was archived by the owner on May 10, 2024. It is now read-only.

Commit e8d46fd

Browse files
committed
Merge branch 'develop' of https://github.com/tassiLuca/ChainVote into develop
2 parents 5eaff01 + 3861f88 commit e8d46fd

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/report-asw/report.tex

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -378,7 +378,7 @@ \subsubsection*{Mockups}
378378

379379
Reasoning about usability, has been decided to add another view, Election view, where elections can be displayed, rather categorized or unfiltered. Moreover, vertical display allows a smoother visualization, up to 10 per page even in mobile setting.
380380
%
381-
From both visualization views, users can see the details of an election (\Cref{fig:details-cast-notifications-view}), ask for the code required during voting phase as well as reach the page to cast a new vote.
381+
From both visualization views, users can see the details of an election (\Cref{fig:details-cast-notifications-view}), ask for the code required during voting phase and reach the page to cast a new vote.
382382
%
383383
From the navbar is possible to navigate the notifications view where all recent notifications are displayed along with an indication of whether it has already been read or not.
384384

@@ -448,7 +448,7 @@ \subsection{Backend Architecture}
448448
\item API server: used as middleware between the blockchain network and the clients, it exposes the API to interact with the system
449449
\end{itemize}
450450

451-
Focusing on the API server module, we see, in figure \Cref{fig:system-architecture}, that it provides its functionality through the \texttt{:api-server} and \texttt{:auth-server} submodules: \texttt{:api-server} maintains the logics for interacting with the blockchain network, manage the users data and send the events to the frontend using websockets. \texttt{:auth-server} exposes the login endpoints and generates the JWT tokens used to authenticate the users.
451+
Focusing on the API server module shown in \Cref{fig:system-architecture}, we can see that it provides its functionality through the \texttt{:api-server} and \texttt{:auth-server} submodules: \texttt{:api-server} maintains the logics for interacting with the blockchain network, manage the users data and send the events to the frontend using websockets. \texttt{:auth-server} exposes the login endpoints and generates the JWT tokens used to authenticate the users.
452452

453453
Both modules are based on the same technological stack (Node and Express.js) and share some common functionality distributed through the use of an internal dependency registry (represented as \texttt{:common} in \Cref{fig:system-architecture}). The utility classes and functions are packed as a npm package and imported as dependency.
454454

@@ -474,7 +474,7 @@ \subsection{Backend Architecture}
474474
\subsection{Technologies}
475475
\label{sec:technologies}
476476

477-
As solution stack, we adopted \texttt{MEVN}, in detail:
477+
As solution stack, we've adopted \texttt{MEVN}, in detail
478478
\begin{itemize}
479479
\item \texttt{Node} and \texttt{Express} server side;
480480
\item \texttt{Vue} client side;
@@ -703,11 +703,11 @@ \section{Story board}
703703
\end{figure}
704704
\restoregeometry
705705

706-
An user can register into the system by entering their personal information (which are modifiable once logged in, \Cref{fig:user-area}), a valid email address and a password.
706+
A user can register into the system by entering its personal information (which are modifiable once logged in, \Cref{fig:user-area}), a valid email address and a password.
707707
%
708-
The inputs of the form (like for every form of the website) are checked for correctness, displaying an error message if the input is not valid (\Cref{fig:user-registration}).
708+
The inputs of the form (as every form of the website) are checked for correctness, displaying an error message if the given value is not valid (\Cref{fig:user-registration}).
709709

710-
Moreover, if the user forget the password can request the generation of new one which is sent to the email address provided during the registration (\Cref{fig:password-forgotten}).
710+
Moreover, if the user forgets the password can request the generation of new one which is sent to the email address provided during the registration (\Cref{fig:password-forgotten}).
711711

712712
After registration, the user can authenticate into the system by entering his or her credentials (\Cref{fig:user-login}) and is automatically directed to the dashboard where the most recent elections are displayed based on their status (open, closed, upcoming) (\Cref{fig:dashboard}).
713713
%
@@ -837,7 +837,7 @@ \section{Story board}
837837
\section{Validation}
838838

839839
Due to mobile first principles, validation phase consisted first of all in test all the system functionalities by means of browser's simulator.
840-
This phase has been repeated changing browsers to test portability too. In addition, all the APIs has been tested using either web application and \texttt{Postman}.
840+
This phase has been repeated changing browsers to test portability too. In addition, all the APIs has been tested using either web application, \texttt{Postman} and \texttt{jest}.
841841

842842
\subsection{User experience}
843843

0 commit comments

Comments
 (0)