Login
Communauté Vinci
Extérieur
Si votre nom d'utilisateur ne se termine pas par @vinci.be ou @student.vinci.be, utilisez le formulaire ci-dessous pour accéder à votre compte de lecteur.
Titre : | Working as a full stack developer for Febiac Data Service |
Auteurs : | Abisha Mochamad Abisha Valbie, Auteur |
Type de document : | Travail de fin d'études |
Editeur : | Woluwe-Saint-Lambert : Haute École Léonard de Vinci, 2023 |
Langues: | Français |
Index. décimale : | TFE - Informatique de gestion (IPL) |
Mots-clés: | Web interface ; REST API ; Full stack developer |
Résumé : |
During my internship at Febiac, I worked on 4 different projects.
The first project that I worked on is an IVI parser. IVI is an abbreviation for International vehicle identification. The goal of this project was to develop an application that is able to parse data from an IVI which is an XML file and saves the extracted data inside a database. Throughout the development of the application I was able to learn the python programming language and a couple of python libraries such as SQLalchemy, pydantic, pyodbc and multiprocessor. The second project I worked on is TAXO lite calculator. Its a website that provides tax calculation for all taxes applicable for a vehicle. For this project, I used Next.js framework because it was the framework that the developers who are working for Febiac used to develop a website. For the backend of the TAXO lite calculator, I was using FastAPI. Its a python REST API framework. The reason they chose FastAPI is because it covers what they need and its fast and simple to create an API using FastAPI. During the development of the TAXO lite calculator I was working mostly on the website interface of the TAXO lite calculator. The backend (TAXO API) is already built and the only thing I developed is a new endpoint that will be used by the TAXO lite calculator. It was fairly straightforward since the logic to calculate the taxes already exists and I just need to implement that logic inside my endpoint. The third project was more complicated than the previous one. This project consists of creating a frontend and a backend (a full stack project). This project was called the BEV-PHEV data management interface. The goal of this project is to replace an Excel file that the Data Service department uses to save the additional information for an electric or a plug-in vehicle. The need to build this interface comes from the limitation of our system called Technicar. Technicar was created before the invention of an electric vehicle and thus cannot save the additional data required for an electric or a plug-in vehicle. To solve these issues the Data Service department has been using an Excel file to keep those additional data but this was not a perfect solution because it was hard to use and to synchronise the data from the Excel file. The new interface will allow the Data Service department to save the additional data using a web interface inside a database. This interface will work in tandem with Technicar. The web interface will manage the data that the user put for an electric or plug-in vehicle and the backend will be incharge of inserting or updating the data inside the database. The fourth project was a backend project. It was not as complicated as before but during the development of this project I was able to improve and not make the same mistake I did during the development of BEV-PHEV data management (backend). The name of this project is Temporary Migration interface. For this project I was only responsible for the backend. This project was built for the migration of the old system to the new one. In the old system, it was possible for a car brand to have multiple names. This problem also applies to the car model, car submodel and car model version. This makes it hard for the Data Service department to work with the data that is saved inside the old system. To solve this, they created a mapping mechanism that maps all the names that define a brand/model/model version/submodel to one brand/model/model version/submodel name. This mechanism was built inside 4 Excel files(brand, model, model version and submodel). In the new system, this issue will not exist but to prepare the migration from the old to the new system, the department needs an interface that is easy to use like Excel and a database that will store the mapping data. Storing the mapping data inside a database will make it easier for the data to be migrated to the new database that will be used by the new system.The backend that I developed will be incharge of adding or updating the mapping data that comes from the new temporary migration interface |
Accès : | Identifiez-vous avant d'accéder au document électronique |
Disponible en ligne : | Oui |
Lieu du stage : | Febiac |
Département : | Informatique de gestion |
Documents numériques (1)
Ce document n'est visible qu'après identification
TFE - Informatique de gestion Adobe Acrobat PDF |