How futuregoose/ecommerce_purchase_prediction works
Project Type and Purpose
• Type: Data‑science/ML analysis pipeline with an interpretability dashboard.
• Purpose: Ingest e‑commerce user activity data, clean and transform it, train and compare models (EBM, LightGBM), and expose results via an InterpretML dashboard for stakeholders.
Main Components
A. Data Source
– project_data.csv (raw dataset from UCI repository)
– Uppdragsbeskrivning.pdf (assignment spec – optional annotation)
B. Pre‑Processing Layer
– Data Cleaning Module (handling missing values, outliers)
– Feature Engineering Module (log, sqrt transforms)
– Scripts: goose_helpers.py as a utilities library
C. Sampling & Balancing
– Subsampling / Oversampling
– SMOTE
D. Modeling Layer
– Model Trainer 1: Explainable Boosting Machine (EBM)
– Model Trainer 2: LightGBM
E. Pipeline Orchestration
– Jupyter Notebook (ecommerce_purchase_prediction.ipynb) as the “driver” of the entire workflow
– requirements.txt / Python environment
F. Interpretability & Visualization
– InterpretML Dashboard (web UI component)
G. Stakeholder Interface
– Presentation slide deck (external to repo)
H. Assets & Documentation
– assets/ (any images, charts)
– README.md, LICENSE
Relationships and Data Flows
• The Jupyter Notebook orchestrates calls to goose_helpers.py utilities and each pipeline phase.
• The InterpretML Dashboard reads model outputs (trained artifacts) and feature importances to serve to stakeholders.
Architectural Patterns & Principles
• Pipeline Pattern: Distinct sequential stages (Ingest → Transform → Train → Serve).
• Single‑process Orchestration: Jupyter Notebook as the control plane.
• Modular Utilities: goose_helpers.py separates reusable code.
• Reproducibility: requirements.txt ensures consistent environment.
Technologies & Frameworks
• Python 3.x – pandas, numpy, scikit‑learn
• interpret‑ml for dashboard
• lightgbm
• ebm (Explainable Boosting Machine)
• Jupyter Notebook
Final Checklist
✓ Each component clearly labeled
✓ Technology annotations on or near blocks
✓ Boundary for execution environment (requirements.txt)