Read Aloud the Text Content

This audio was created by Woord's Text to Speech service by content creators from all around the world.

Text Content or SSML code:

Chapter 3: In the third chapter; we shall explain the methodology we’ve chosen, which is scrum , identify the actors along with the functional and non-functional requirements, we will also speak about the architectural style chosen and the software and development languages we used in the making of this project. The scrum -Before identifying the actors, we’re going to explain the scrum process, Roles : So we have distributed the roles The product owner is our industrial supervisor MR Mohamed Methneni, the scrum master is our academic supervisor Mme hela malouche and the dev team is me Sprint planning : At this point, after gaining the required knowledge needed, we are ready to start creating our project, since we decided to use the scrum methodology, during the planification phase we split our project into 2 sprints , in each sprint we worked in a changing rythm according to our needs. Actor : In order to answer to the requirements, our product owner has specified 2 actors ; XD Functional requirements the functional requirements our platform should response are: non-Functional requirements Now speaking of the non-functional requirements: to garantee a good product quality we had to respect a couple of constraints which are: Architect pattern -The architectural pattern focuses on how to organize the code created for the platform ,we have chosen MVC (Model-View-Controller) it is for implementing user interfaces with computers. Software envirements : We have used those softwares visual stodio , xampp ,postman in the developing process of our project Framework and Programming language And We have used different frameworks and prog luanguages in order to develop our project , like Php 8,1 , laravel 8 , html 5 , javascript , css 3 , bootstrap Chapter 4 In the 4th chapter; we will explain the implementation of both the sprints by presenting the diagrams Class diagram Here is the global class diagram of our project as we can see we have created 5 data base tables where we can store out our needed data Chapter 5 In this 5th chapter; we will show the resulalt of our work with the interfaces that we have created here w have the connect store to platform where the customer can link his store with our platform and this an example of form of the store that i have workd on ,, here the client should put his store id and secret token in order to link his ecwid store ,, the linking proces changes from store to an other based on the api bases that store is working with -this page represent the product list where the admin put his csv file to list out products and the client can publish products to his import list , -Now we are going to talk abt the import list were our client is able to manage his already published products , -he could send product to store -or delete it -or update its details like the name,price,discription and stock as shown in this form This is a real example of sent products to an ecwid store through the using of our platform and its functionality -This is the page were our client is able to set his margin of profit before sending a product to his store -this final interface is going to represent the dashboard where the client can see some statics of his work on sent product in his varieous stores Chapter 6 In this last chapter we will conclude our presentation by mentionning what we gained during the creation of this project and talk abt amelioration perspectives on how to improve what we have created. X)