|
| 1 | +# **Application Support Portfolio — Full‑Stack Banking Operations** |
| 2 | + |
| 3 | +This repository brings together four complementary projects that demonstrate the technical breadth, analytical mindset, and operational discipline expected from a senior Application Support professional in a banking environment. |
| 4 | + |
| 5 | +It showcases end‑to‑end capabilities across **ETL pipelines**, **operational tooling**, **backend diagnostics**, and **frontend support interfaces** — the core pillars of modern support for risk and finance applications. |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +# Repository Structure |
| 10 | + |
| 11 | +``` |
| 12 | +/ |
| 13 | +├── banking_data_pipeline_python/ # Credit Risk ETL (Python) |
| 14 | +├── it_ops_automation_toolkit/ # Shell + Python Ops Tools |
| 15 | +├── support-portal-backend/ # Spring Boot Support API |
| 16 | +└── support-portal-frontend/ # Angular Support Portal UI |
| 17 | +``` |
| 18 | + |
| 19 | +Each module is self‑contained and can run independently. |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +# Project Overview |
| 24 | + |
| 25 | +## **1. Credit Risk ETL Pipeline (Python)** |
| 26 | +A production‑style ETL that computes **Risk‑Weighted Assets (RWA)** using standard credit‑risk parameters (EAD, PD, LGD). |
| 27 | +Includes data‑quality checks, logging, error handling, and SQLite output. |
| 28 | + |
| 29 | +**Run:** |
| 30 | +```bash |
| 31 | +pip install -e banking_data_pipeline_python |
| 32 | +python -m banking_data_pipeline.rwa_calculator |
| 33 | +``` |
| 34 | + |
| 35 | +--- |
| 36 | + |
| 37 | +## **2. IT Ops & Automation Toolkit** |
| 38 | +A set of lightweight tools used for daily operational checks and incident triage. |
| 39 | + |
| 40 | +- `health_check.sh` — process, disk, and file monitoring |
| 41 | +- `log_analyzer.py` — parses logs and summarizes WARN/ERROR/FATAL |
| 42 | + |
| 43 | +These scripts reflect real support workflows: control points, monitoring, and rapid diagnostics. |
| 44 | + |
| 45 | +--- |
| 46 | + |
| 47 | +## **3. Support Portal Backend (Spring Boot, Java 17)** |
| 48 | +A REST API exposing transaction data and surfacing failures with clear error codes. |
| 49 | +Includes health checks, filtering endpoints, and an H2 in‑memory database for fast prototyping. |
| 50 | + |
| 51 | +**Run:** |
| 52 | +```bash |
| 53 | +mvn clean spring-boot:run |
| 54 | +``` |
| 55 | + |
| 56 | +--- |
| 57 | + |
| 58 | +## **4. Support Portal Frontend (Angular)** |
| 59 | +A simple UI for viewing system health and failed transactions. |
| 60 | +Designed to give support teams quick visibility into issues. |
| 61 | + |
| 62 | +**Run:** |
| 63 | +```bash |
| 64 | +ng serve |
| 65 | +``` |
| 66 | + |
| 67 | +--- |
| 68 | + |
| 69 | +# End‑to‑End Flow |
| 70 | + |
| 71 | +The four modules together simulate a realistic support ecosystem: |
| 72 | + |
| 73 | +1. **ETL pipeline** processes credit‑risk data. |
| 74 | +2. **Ops toolkit** monitors the environment and analyzes logs. |
| 75 | +3. **Backend API** exposes diagnostic information. |
| 76 | +4. **Frontend UI** presents it clearly for support teams. |
| 77 | + |
| 78 | +This mirrors the lifecycle of supporting a banking application: |
| 79 | +**data → monitoring → diagnostics → user visibility**. |
| 80 | + |
| 81 | +--- |
| 82 | + |
| 83 | +# Skills Demonstrated |
| 84 | + |
| 85 | +- Python (ETL, data quality, logging) |
| 86 | +- SQL (SQLite, H2) |
| 87 | +- Java (Spring Boot) |
| 88 | +- Angular (TypeScript) |
| 89 | +- UNIX Shell scripting |
| 90 | +- Operational monitoring & log analysis |
| 91 | +- Credit‑risk concepts (RWA, PD, LGD, EAD) |
| 92 | +- Support‑oriented design and troubleshooting mindset |
| 93 | + |
| 94 | +--- |
| 95 | + |
| 96 | +# Purpose |
| 97 | + |
| 98 | +This monorepo serves as a compact, practical demonstration of: |
| 99 | + |
| 100 | +- Technical proficiency across the full support stack |
| 101 | +- Ability to build tools that improve reliability and reduce MTTR |
| 102 | +- Understanding of credit‑risk data flows |
| 103 | +- Experience designing clear, support‑friendly diagnostics |
| 104 | +- A structured, methodical approach to application support |
0 commit comments