You are on page 1of 2

FAUFILE

Tools:

I. Front party:
*Flutter :
Flutter is a Framework based on the dart language. It is a framework very similar to React Native, but
more suited to the development of mobile applications, thanks mainly to its large library of Widgets
UI, which allows a better customization of graphical interfaces.

Framework: A coherent set of structural software components used to create the foundation of a
software, following a very precise architecture.

*Dart :
Dart is a web programming language developed by Google in 2011. The initial purpose of this
language is to replace Javascript by solving problems and providing better performance and security.
It allows to make transitions and animations very fast making it a language very suitable for mobile
applications.

I. Back party :
*Node.js :
Node. JS is a Javascript-based framework. As part of the development of our application, we used
Node. js to expose Web services containing data from our database in order to use them in the Front
part.

Web Service: A computer interface protocol for communicating and exchanging data between
heterogeneous applications and systems in different environments.

Course of work (problems and steps):

After designing the data tables required for our application, we created an SQL database (BD)
containing the entities of our ecosystem (users, tickets, regions, Services, domains). We opted for a
relational database because it is sufficient and more practical than a non-relational database such as
MongoDB, for a project of this scale. Then we started to develop the back part of our project, which
will allow us to its conclusion to communicate the data of our BD with our interfaces of the front
part. Following some tests with the Symfony framework, which is a web development-oriented PHP
framework on the front and back side, we decided to choose the Node. JS Framework Since we only
need the exposure of our web services, and therefore the Back part of the work, and also because
the frameworks "dart" such as Flutter are better adapted to communicate with frameworks in
Javascript such as Node. js. Our web services being exposed and our relationship with the comics
established, we started the Front part, starting with the Login part of the users, then displaying the
lists of regions, areas of services and services, and finally the management of the tickets. We
estimated the duration of each service to estimate the user's wait time until the order of his ticket
arrives. We also gave a certain amount of time as a result of which the ticket cancels if the user does
not show up to take advantage of his service.

You might also like