How padalakiran/bank_management_system_for_admin works
The project is a simple command-line Bank Management System designed for an administrator. It allows creating new accounts, displaying customer details, depositing money, withdrawing money, and eventually exiting the application. The system uses Python and leverages external libraries (pandas, phonenumbers, xlrd, openpyxl) to work with Excel files that serve as its database.
Main Components
• Main Application Module: Although the central entry point isn’t explicitly named, the file bank.py likely ties the functionalities together.
• Functional Modules: Each feature is implemented as a separate module:
• .py: Handles account creation.
• .py: Displays customer details.
• deposite.py: Manages depositing funds.
• withdraw.py: Manages money withdrawal.
• Database/Storage Component: The system uses an Excel sheet (with specific columns like Name, AccountNumber, PhoneNo, Amount) to store customer data.
• External Libraries: The project relies on pandas for data manipulation along with phonenumbers, xlrd, and openpyxl for Excel operations.
Interactions and Relationships
• The Main Application (bank.py) orchestrates the call flow between the functional modules.
• When an action is chosen by the admin, bank.py will interact with the corresponding module (for example, invoking add.py for creating a new account).
• Each functional module reads from or writes to the Excel file, employing the external libraries to ensure correct data formatting and validation (e.g., verifying phone numbers).
• There is a direct dependency on the Excel file/database where all account information is stored.
Architecture Patterns and Design Principles
• Modular Design: The separation of concerns across different .py files (add, deposite, withdraw, show) encourages modularity in the code.
• File-Based Data Persistence: The Excel sheet acts as a simple data store, ensuring persistence.
• Command-Line Interface (CLI): The system is designed for CLI use, which means all user interactions and outputs will be text-based.
• Loose Coupling: Each module is built to perform its specific task, allowing easier updates and maintenance.