How ahmadayman28/optimization-of-the-tourism-industry works
Project Type and Purpose
• This is a hybrid full-stack desktop application plus data-science pipeline.
• It combines:
– A relational database (SQL Server) for persistent storage of packages, budgets, resources, and results
– An ETL layer (Python/Jupyter notebooks) for data preprocessing, integration, and mathematical modeling
– Optimization engines (exact MILP via PuLP, Genetic Algorithm, Ant Colony) implemented in Python
– An AI forecasting component (seven ML models exposed via a Tkinter GUI)
– A C# Windows-Forms user interface for admin operations (role-based access for SuperAdmin, Manager, etc.)
Main Components
A. Data Sources
– Excel files (Budget.xlsx, PackageSeason.xlsx, Resource.xlsx, TourPackage.xlsx)
– External raw data (historical booking records, market research, social media)
B. ETL & Preprocessing
– “Ui/Code for First Normal Form on data” notebooks
– “Ui/Code For Import Data from Excel into Database” notebooks
C. Database Layer
– Tables: Packages, Seasons, Resources, Budgets, Predictions, OptimizationResults
D. Business Logic & Modeling
– Mathematical model notebooks (“Exact Solution.ipynb”)
– Meta-heuristic algorithm notebooks (GA, AC)
– Data‐analysis notebooks for trend analysis and visualization
E. AI Prediction Model
– Jupyter notebooks in “AI Prediction Model & GUI”
– Tkinter-based GUI for forecasting demand with multiple regressors
F. User Interface (Desktop App)
– C# Windows Forms solution (“GP Optimization of Tourism Industry.sln”)
– Forms: LoginForm, AdminDashboardForm, SuperAdminDashboardForm
– Role-based access control, CRUD operations on Packages, Budgets, Resources
G. Documentation & Reporting
– PDF/PPTX documents, Excel dashboards for descriptive statistics, trend charts
Relationships & Data Flows
1. Excel → ETL notebooks → SQL Server (initial load & normalization)
2. SQL Server ↔ C# UI (CRUD operations by admins)
3. SQL Server → Optimization notebooks (Exact/GA/AC) → Results → SQL Server or output files
4. SQL Server & cleaned datasets → AI notebooks → Predictions → Tkinter GUI → end‐users
5. Reporting outputs (graphs, charts) generated by Jupyter and by Excel dashboards
Architectural Patterns & Design Principles
• Layered Architecture:
– Data Layer (SQL Server)
– Service/Processing Layer (Python ETL, optimization, AI models)
– Presentation Layer (C# WinForms, Tkinter GUI)
• Separation of Concerns: ETL, modeling, UI are distinct modules
• Extensibility Points: New optimization algorithms or ML models plug into the Jupyter workflow
• Role-Based Access: Enforced in the C# app, decoupled from data storage