How lakhia13/cmpsc430-project works
Project Type and Purpose
• This is a Python‐based desktop loan management system with a Tkinter GUI.
• It provides administrative and customer views for managing customers and multiple loan types.
• It persists data in an Oracle XE database running in Docker.
File‐Structure Analysis
• Top‐level scripts:
• main.py – application entry point and GUI launcher
• db.py – data‐access layer, connection management, schema initialization
• views/ directory – UI components (customer login, customer admin, loan management)
• requirements.txt – declares Python dependencies (e.g., cx_Oracle, python‐dotenv, Tkinter)
• .gitignore, .idea – IDE and VCS metadata
README Insights
• Python 3.x + Tkinter for GUI
• Oracle XE in Docker, environment variables for credentials/DSN
• Automatic table creation/sample data on first run
• Two user roles: Admin and Customer
Main Components
a. Desktop Application
• Presentation Layer: Tkinter windows (login, admin, customer, loan forms)
• Application Logic: validation, view controllers (embedded in view modules)
• Data‐Access Layer: db.py, uses cx_Oracle and environment variables (.env)
b. External Service
• Oracle XE Database (Docker container gvenzl/oracle-xe)
c. Dev/Ops & Runtime
• Docker host (ports 1521, 5500)
• Python runtime & venv
• Environment config (.env)
Relationships & Interactions
• User → Tkinter UI (views/*.py)
• UI invokes application logic (in same view modules or via helper classes)
• Logic calls Data‐Access Layer (db.py)
• db.py uses connection parameters from .env to connect over TCP to Oracle XE
• Oracle responds with query results/ACKs → db.py → UI update
Architectural Patterns & Principles
• Layered architecture:
• UI Layer (Views)
• Business Logic Layer (Controllers in views)
• Data Layer (db.py)
• Separation of concerns: each module has a clear responsibility
• Externalize configuration (env vars)