How juned7952-stack/global-sales-dashboard works
1. Repository shape
- This repo is essentially a single Power BI report artifact: Dashboard.pbix.
- README.md describes the report’s purpose; there is no separate application code, backend service, or source-data folder in the repo.
2. Primary subsystem: the BI report
- The .pbix file is the whole product boundary.
- It contains the report pages, the semantic model, Power Query transformations, and the visual layer used to present the dashboard.
3. Business purpose
- The dashboard is focused on global orders and sales analytics.
- Its intended outputs are KPI views and trend/segmentation analysis for revenue, profit, regions, products, and customer segments.
4. Data ingestion boundary
- The README indicates the report relies on sales data that is cleaned and transformed in Power Query.
- The actual source systems/files are not included in the repository, so any architecture diagram should show an external data source feeding the PBIX.
5. Transformation layer
- Power Query Editor is the main ETL boundary inside the report.
- This is where raw sales data is shaped before it enters the model, likely handling cleaning, filtering, type conversion, and table preparation.
6. Data model layer
- The report uses relationships between multiple tables, so the semantic model is a core part of the architecture.
- This model is what enables cross-filtering and consistent aggregation across regions, products, dates, and customer segments.
7. Analytics layer
- The dashboard exposes measures such as total revenue and profit, sales distribution, top-selling products, and time-based trends.
- These metrics are likely computed in the model and then reused across multiple visuals, rather than being hardcoded in each chart.
8. Presentation layer
- The report uses standard Power BI visual types: line charts, bar charts, maps, cards, and slicers.
- These visuals are the user interaction boundary for exploring performance by geography, time, category, and segment.
9. User interaction flow
- Users typically start with high-level KPI cards, then filter via slicers and drill into regional, product, or temporal trends.
- The map and charts work together to support both overview and comparison workflows.
10. Operational/tooling boundary
- The only runtime/tooling explicitly referenced is Power BI Desktop.
- That means the repository is meant for authoring and viewing the report in Power BI, not for deployment of a standalone service.
11. Important repo note
- The README mentions Task_1.pbix, but the file tree contains Dashboard.pbix.
- An architecture diagram should treat this as the same report artifact, but the filename mismatch is worth noting for documentation accuracy.
12. What is not present
- There is no visible codebase, test suite, CI pipeline, or external infrastructure described in the repo.
- So the architecture is best drawn as a self-contained BI dashboard with an external data source feeding Power BI’s transformation and modeling pipeline.
Main entry points: Dashboard.pbix Dashboard.pbix · README.md README
Components 18
Repository
Files tracked in the repo
- README · Describes the dashboard purpose and usage
README.md - Dashboard.pbix · Main Power BI report artifact
Dashboard.pbix
Power BI report
The report artifact and its internal layers
- Power Query · Cleans, filters, and shapes incoming data
- Prep steps · Type conversion, filtering, and table shaping
- Data model · Relationships and shared aggregation layer
- Sales fact · Core transactional sales table
- Date dim · Supports time intelligence and trend analysis
- Product dim · Supports product and category analysis
- Region dim · Supports geography and map analysis
- Segment dim · Supports customer segment analysis
- Measures · Reusable analytics such as revenue, profit, and sales trends
- Report pages · Dashboard canvases containing the visuals
- KPI cards · Headline metrics for revenue and profit
- Trend charts · Line and bar charts for time and category comparison
- Map view · Geographic distribution and regional performance
- Slicers · User filters for time, region, product, and segment
Other components
- Power BI Desktop · Tool used to open, edit, and view the report
- Sales data · Upstream data source not included in the repository
Connections 26
- README → Dashboard.pbix: documents · README describes the report artifact
- Power BI Desktop → Dashboard.pbix: opens · Report is authored and viewed in Power BI Desktop
- Sales data → Power Query: feeds · Raw sales data enters the report through Power Query
- Power Query → Prep steps: uses · Power Query performs cleaning and shaping steps
- Prep steps → Sales fact: loads · Prepared transactional data is loaded into the model
- Prep steps → Date dim: loads · Date table is prepared for time analysis
- Prep steps → Product dim: loads · Product table is prepared for category analysis
- Prep steps → Region dim: loads · Region table is prepared for geography analysis
- Prep steps → Segment dim: loads · Segment table is prepared for customer analysis
- Sales fact → Data model: central table · Core facts sit inside the semantic model
- Date dim → Data model: relates to · Date dimension participates in model relationships
- Product dim → Data model: relates to · Product dimension participates in model relationships
- Region dim → Data model: relates to · Region dimension participates in model relationships
- Segment dim → Data model: relates to · Segment dimension participates in model relationships
- Data model → Measures: powers · Shared DAX measures are defined on top of the model
- Measures → KPI cards: drives · Headline metrics are rendered from model measures
- Measures → Trend charts: drives · Charts reuse the same analytics calculations
- Measures → Map view: drives · Geographic visuals are computed from model measures
- Slicers → Data model: filters · User selections cross-filter the model
- Report pages → KPI cards: contains · Dashboard pages host KPI cards
- Report pages → Trend charts: contains · Dashboard pages host trend and comparison charts
- Report pages → Map view: contains · Dashboard pages host geographic visuals
- Report pages → Slicers: contains · Dashboard pages expose interactive filters
- Dashboard.pbix → Power Query: includes · The PBIX bundles transformation logic
- Dashboard.pbix → Data model: includes · The PBIX bundles the semantic model
- Dashboard.pbix → Report pages: includes · The PBIX bundles the report pages and visuals