This repository serves as the single source of truth for the Insurance Analytics MockProject (Rookie Data DN 2026 / CarPro Insurance Analytics). It contains all project documentation, SQL DDL scripts, test assets, and Microsoft Fabric-related configurations and notebooks.
Important
Project Handover & Client Delivery: For a quick index mapping all consolidated project deliverables (Source Code, Technical Documentation, Performance Reports, Deployment Guides, and Test Assets) as shown in the presentation slides, please refer to the Knowledge Transfer & Project Handover Guide.
The objective of this project is to implement a medallion data architecture (Bronze → Silver → Gold) to ingest, clean, model, and serve insurance analytics data. The data platform leverages Microsoft Fabric as the primary integration engine, Power BI for reporting, and GitHub for source control management and collaboration.
flowchart LR
subgraph "Medallion Architecture"
Source["Source DB / JSON"] -->|Ingestion| Bronze[("Bronze Layer<br/>(Delta Landing)")]
Bronze -->|Cleansing| Silver[("Silver Layer<br/>(Deduplicated / Clean)")]
Silver -->|Transformation| Gold[("Gold Layer<br/>(Star Schema)")]
end
Gold -->|Direct Lake| Semantic["Power BI Semantic Model"]
Semantic -->|Embedded| WebApp["Next.js Web Application"]
This repository is structured around the five core pillars of our client handover:
- Source Code: PySpark notebooks and data pipelines for Bronze ingestion, Silver cleansing, and Gold SCD Type 2 dimension loading. Includes sql/ schemas and the web-app/ Power BI embedded Next.js application.
- Technical Documentation: Complete system architecture designs, BPMN process workflows, star schema data models, and column-level Source-to-Target Mappings (STTM).
- Performance Reports: Stress-test benchmarks showing pipeline execution logs at scale (1M, 5M, 10M, 100M, and 4 Billion rows), alongside detailed refactoring and optimization reports.
- Deployment Guide: Continuous Integration and Continuous Deployment (CI/CD) pipelines, setup prerequisites, orchestration strategies, and environment promotion runbooks.
- Test Assets: Automated row-level data quality constraints, temporal integrity checkers, KPI revalidation logs, and sample database validation datasets.
For a detailed walkthrough of each asset, please check the Project Handover Guide.
Below is the physical folder organization of the repository:
rookies-data-dn-2026/
├── .github/ # GitHub actions automation workflows
├── architecture/ # System architecture design & diagrams
│ ├── data-quality/ # Data quality specs
│ ├── diagrams/ # Mermaid diagram source files
│ └── exports/ # Exported diagram images (PNG)
├── cicd/ # CI/CD workflows and deployment guides
├── config/ # Environment configuration templates
├── docs/ # Project documentation and designs
│ ├── business-process/ # Business workflow analysis
│ ├── data-modeling/ # Star schema designs & table definitions
│ ├── final-deliverables/ # Handover guides and client deliverables
│ ├── presentation/ # Presentation slides
│ ├── refactor-optimize-pipeline/ # Pipeline performance optimizations
│ ├── source-to-target-mapping/ # Column mappings (STTM)
│ └── standards/ # Global team development guidelines
├── fabric/ # Microsoft Fabric Git integration artifacts
├── json-source/ # Mock transaction source data files
├── sql/ # Raw SQL scripts and DDLs
│ ├── etl-control/ # Control flow schemas
│ ├── lakehouse/ # Silver/Gold Delta table DDLs
│ └── source/ # Source system simulator SQLs
└── tests/ # Quality assurance and testing suite
├── data-quality/ # PySpark constraints & KPI validations
├── performance/ # Scalability stress-test benchmarks
└── pipeline-tests/ # Integration pipeline validations
To keep collaboration clean and trackable, all team members must follow our Git branching, naming, and commit conventions:
- Repository Structure & Naming Guide – Directory usage rules and general file naming.
- Branching & Commit Conventions – Kebab-case branch templates and conventional commit structures.
- Pull Request Process – PR size limits, template, reviewer checklists, and merge policies.
-
Promotion Workflow – Environment progression (Feature
$\rightarrow$ dev$\rightarrow$ release$\rightarrow$ main). - Conflict Resolution Guide – Resolving conflicts in source code and Jupyter Notebooks.
- For Python variables, classes, SQL tables, and database schemas, follow the Python & SQL Naming Convention Guide.
- For Fabric-specific item structures, consult the Fabric Workspace Structure Guide.
- Start Task: Create a feature branch off
devfollowing Branching Conventions. - Implement Changes: Write code using Code Naming Standards.
- Commit Code: Commit changes frequently with Conventional Commits.
- Push & Create PR: Push feature branch and create a PR using the PR Template.
- Review & Merge: Review with checklist, resolve any Conflicts, merge to
dev, and delete the branch.