How mhdmirzan/pizza-insights works
Project Type and Purpose
• This is a Business Intelligence (BI) dashboard project built in Power BI to analyze pizza sales data.
File-Structure Analysis
• Top-level assets:
• order_details.csv, orders.csv, pizza_types.csv, pizzas.csv → raw data sources
• “pizza SQL codes/” → a collection of SQL scripts (“ETL layer”) transforming and aggregating those CSVs
• pizza_dashboard.pbix → Power BI Desktop file containing data model and reports
• Power BI & SQL pizza insights.pdf and Questions.txt → documentation and analysis questions
• No application code or microservices—this is a data pipeline + BI reporting solution.
README Insights
• Confirms a published Power BI report with a screenshot.
a. Main Components
1. Data Sources (CSV files)
2. ETL Layer (SQL scripts folder)
3. Staging & Data Model (fact and dimension tables)
4. Power BI Desktop (.pbix)
5. Power BI Service (cloud hosting and sharing)
6. Documentation Artifacts (PDF, Questions.txt)
b. Relationships & Data Flow
• Documentation feeding into analysis best practices or stakeholder review
c. Architectural Patterns & Principles
• ETL pipeline: extract raw data, transform via SQL, load into BI-ready schema
• Star schema in data model: facts (order_details) linked to dimensions (orders, pizzas, pizza_types)
• Self-service BI: one monolithic .pbix file with data model and visuals
d. Key Technologies & Frameworks
• Data storage: flat CSV files (source)
• Processing: SQL engine (could be local SQLite, SQL Server, or Power Query M if imported directly)
• Visualization: Power BI Desktop & Power BI Service