Génie logiciel
209 documents à télécharger gratuitement
Cours, examens, TD, TP et exercices de génie logiciel. Thèmes couverts : UML, MERISE, conception, architecture logicielle, Scrum, agile.
This thesis details the development of a custom CRM system for call centers using Symfony4. It begins with an analysis of existing solutions, identifying their limitations, and proposes a more efficient, tailored system. The design incorporates a three-tier architecture, focusing on functional and non-functional specifications to ensure scalability and usability. The implementation demonstrates the use of Symfony4 and associated technologies, showcasing enhanced features and favorable test outcomes for practical deployment.
This thesis presents the design and implementation of a CRM dedicated to a call center using Symfony4. It is a professional master's thesis submitted at the University of Carthage for the degree of Mastère Professionnel. The work is dedicated to those who provided support and encouragement throughout the author's academic journey.
Ce mémoire présente la conception et la mise en place d'un système de gestion de la relation client (CRM) pour un centre d'appel. Le projet explore les besoins spécifiques de l'organisme d'accueil, Ophony, et propose des solutions adaptées. La recherche s'appuie sur une analyse approfondie des exigences fonctionnelles et non fonctionnelles, ainsi qu'une méthodologie de conception rigoureuse.
This document discusses the design and implementation of a Customer Relationship Management (CRM) system tailored for call centers using Symfony4. It identifies issues in existing solutions, outlines functional and non-functional requirements, and proposes a modular architecture comprising presentation, business logic, and data layers. The developed system features user authentication, campaign management, and comprehensive administrative functionality, validated through test scenarios. Future improvements focus on enhancing the application's interface and scalability.
This document describes the development of a CRM system, Vicidial, tailored for call centers using Symfony 4. It begins with a study of existing applications, analyzing issues such as inefficiency, poor security, and lack of ergonomic functionality. The author proposes a solution with features like MVC architecture, enhanced statistics dashboards, and role-based functionalities. Using the SCRUM methodology, the project is detailed from initial conception to development phases, concluding with future perspectives such as notification systems and messaging spaces for administrators.
This document outlines the development of the back-office module for MOBIPOS, a point-of-sale terminal system aimed at managing multi-store operations. Conducted at Eurequat Algérie, the project involved implementing features like user management, stock control, sales reporting, and cash register configuration, using the Scrum methodology. Advanced features of the module include the integration of a functional architecture, robust testing (unit, integration, and acceptance), and managing anomalies during implementation. The final system was completed and tested successfully, with client app...
Ce mémoire présente la réalisation d'un module back office pour le système terminal de point de vente MOBIPOS. Le stage a été effectué chez Eurequat Algérie, où l'objectif principal était d'approfondir les connaissances théoriques en les mettant en pratique. Le document couvre également les spécifications des besoins, la conception et la méthodologie employée dans ce projet.
This document outlines the design and development of a CRM system tailored for call centers, utilizing the Vicidial framework with added reporting features implemented in Symfony 4. It describes the analysis of existing systems, proposes solutions, and follows SCRUM methodology for project management. The thesis includes the development of user management, campaign organization, and reporting tools integrated into a scalable architecture. The work concludes with recommendations for improving call center operations through enhanced software design.
This document provides an in-depth exploration of UML diagrams, specifically focusing on component and deployment diagrams. Component diagrams detail the implementation and interaction of software components and define dependencies, interfaces, and representations. Deployment diagrams outline the physical architecture of software systems, describing nodes, their associations, components, and deployment configurations across varied architectures, including centralized, client-server, and three-tier systems. Exercises and solutions demonstrate real-world examples, progressively redesigning a...
This document discusses the functionality and representation of UML diagrams, particularly focusing on component and deployment diagrams. It covers basic concepts, relationships between components, and how interfaces are depicted in UML. The document aims to assist developers in understanding the relationships and dependencies vital for software design.
The document discusses foundational concepts related to software architecture and design patterns, emphasizing their importance in simplifying complex systems by using components and structured frameworks. It explores various software architectures, including 1-tier, 2-tier, and 3-tier architectures, detailing their purposes, limits, and benefits like ease of maintenance, reliability, and scalability. It highlights the transition from basic monolithic systems to client-server models and later multi-tier architectures, stressing their role in improving software quality, adaptability, and sec...
This document outlines the competencies that students should achieve in the software architecture module. It discusses various software quality criteria and the importance of software design patterns. It emphasizes the correlation between software architecture and the software development lifecycle.
Ce chapitre traite de la conception architecturale et physique d'un logiciel, en se concentrant sur l'adhérence aux exigences et la qualité. Il aborde la définition de la conception logicielle, ainsi que l'importance de la réutilisabilité et de la maintenabilité dans le développement logiciel. Les différents types d'architectures, comme l'architecture logique et physique, sont également discutés.
Ce document traite de l'importance de construire des logiciels de qualité dans le domaine du génie logiciel. Il souligne les défis du développement logiciel, tels que le coût et le temps, et l'importance de méthodes et d'outils pour surmonter ces difficultés. Le texte mentionne également la crise de la qualité des logiciels et l'art de la construction logicielle.
Ce document présente les concepts fondamentaux du génie logiciel, tels que les enjeux et l'importance de cette discipline, ainsi que les cycles de vie et les méthodologies de développement logiciel. Il aborde également des thèmes cruciaux, tels que la gestion de configuration et le test logiciel. En outre, il propose d'appliquer ces connaissances à travers un projet utilisant la méthode agile SCRUM.
This thesis presents the development of a reporting tool based on the Symfony 4 framework. The document explores the needs analysis, conceptual design, and implementation of a 3-tier architecture for the tool. The methodology involves using modern web development practices and frameworks such as Symfony, VICIdial, and Nuxeo to address functional and non-functional requirements. Findings indicate that the proposed solution improves reporting efficiency and seamlessly integrates with call center operations, showcasing the tool's potential for broader enterprise applications.
Les descriptions des diff rentes parties du rapport : Il s agit d exposer le plan de votre rapport, c est dire les diff rentes parties cit es ci-dessus avec la page correspondante de chacune.
Ce chapitre traite de l'analyse des besoins dans le développement de systèmes interactifs. Il met l'accent sur les différences d'approche entre l'Interaction Homme Machine et le Génie logiciel. L'importance de comprendre le système existant ainsi que les utilisateurs pour assurer la réussite d'un nouveau système est également soulignée.
Ce document présente un exercice de modélisation structurelle UML pour le développement d'une application de calcul d'itinéraires pour un robot dans une zone géographique. Il décrit les classes nécessaires, les associations entre elles et propose des modifications et décorations à apporter au modèle existant. Les étudiants sont invités à comprendre, compléter et améliorer cette modélisation.
This document contains exercises related to UML modeling and object-oriented design principles. It includes tasks for creating sequence diagrams for various scenarios including a person management system and a traffic light control system. Additionally, it involves modeling the order and delivery system of a pizza restaurant chain, focusing on functionalities and interactions.
This document provides a detailed lab exercise on locale manipulation in software development. It covers various programming languages including C++, Java, JavaScript, and PHP for displaying dates based on user locale. The tasks focus on understanding the cultural aspects of programming through practical applications.
This document outlines a lab exercise focused on character encoding in software development. It includes tasks for encoding characters into bytes, creating C++ and Java programs to handle various encodings, and understanding HTML and PHP encoding practices. The goal is to provide hands-on experience with character sets and their implementations in different programming environments.
This document outlines the requirements for a software engineering project where students must create an application to manage data from a given H2 database. The application should follow the MVVM architecture pattern and include unit tests. It consists of multiple Eclipse projects, including infrastructure, views, controllers, and models.
This document explores several use case scenarios related to software management for a car repair business and an archaeological support system. The use cases highlight the functional requirements and interactions between different actors within the systems. Specific examples illustrate the implementation of extended and included use cases in a structured manner.
















