Paris, France

ICADE

Client

Nunances
Date

2021
Project link

Visit Icade's website

For this project our client, Nuances, wanted to develop a tool to manage signage for ICADE, centralizing information about all its signage elements. This tool would allow users to locate each sign, select its nature and type, and thus obtain its definition and complete description. Icade will then have a comprehensive overview of all its signage elements across all of its business parks and can determine whether or not updates are necessary.

Web Design

For the web design of this project, we wanted to create a clean and simple design that would allow users to easily navigate through the different pages and find the information they are looking for. We used a color palette that is consistent with Icade's branding, and we also used icons and images to make the design more visually appealing.

Graphic Elements

Maquette

In the image above you can find the first version of the maquette. Visit Eureka's first maquette

In the image above you can find the third version of the maquette Visit Eureka's third maquette

Web Development

For this project we used PHP language which allowed us to access Laravel's Framework. The information system, will be developed as an application, web platform, and tablet. Users will register/log in to get an overview of Icade business parks and can select the element that interests them.

This application should allow users to:

Have an overview of signage elements
A complete description of all Icade signage ranges and products
Facilitate the integration of new elements as well as the modification of existing ones (updates)
Accurate dating of elements to allow for updates when necessary
Easily generate quotes via a form (PDF export) and keep the client (supplier) informed

A map of each park

All signage elements are marked on a map, and once you click on them, you can see a photo, the type of signage, the installation date, and the option to edit it if you have administrator rights. You can see above the Home page (administrator version).

Model catalog

All products belong to a model type. Once this model is created, a form is completed to create a copy. This copy contains all the detailed information about the signal: model type, legal specifics, copy description, copy condition, and maintenance.

The export tab

Using the export tab, you can select the wind farms and the model of interest. Once exported, you will receive a .zip file containing all the images and an Excel file of all the selected information in .csv format.

Above, you can see the export tab and in figure and the documents that are exported.

The ‘Helpers’ users

To be able to grant access to a specific type of user to enter all the information on the signage available in the parks, we created a specific type of user called 'Helpers'. Users known as 'Helpers' only have access to certain information assigned to them by the management group. These users complete the form by visiting ICADE parks, taking the necessary photos, and filling out the requested information on the form.

You can see above a helper's dashboard, mentioned previously, is the first thing a Helper sees when they log in.

Conceptual Data Model (CDM)

The conceptual data model (CDM) is a representation of the computer system used, along with the necessary data. In the image below, we can see that almost all the tables are associated with the record in different ways. The record is the main form where information is created and saved in the database.

Logical Data Model (LDM)

For the logical data model (LDM), I used the reverse engineering feature of MySQL Workbench, which provided me with all the tables available in my database. Once I connected them using the cardinalities specified in the conceptual data model (CDM), I obtained the result shown in the image below.

Conclusion

Creating this application was a very interesting project, as it was the first one I completed entirely using the Laravel framework. For this project, we integrated the required features into the first version of the application.

Another interesting aspect of this project is its evolution. For two to three months, I was able to manage the project using an Agile methodology, which involved sprints on some days and assessments on others to identify potential problems. Throughout, the application was developed collaboratively by three developers, who sometimes worked together and sometimes independently, but always kept track of each other's progress.