Online_Banking_Management_System

A multithreaded client-server architecture that replicates the behaviour of an online banking system.

I. Database :

The database is in the form of ".txt" files. It comprises of the following 3 files :

1. LoginInformation.txt :

   • Contains the authorization details of the users.
   • Details are in the form -> || Username || Password || User Type || Unique Account Number ||

2. AccountsInformation.txt

   • Contains information regarding the accounts of customers.
   • Information is in the form -> || Unique Account Number || First Name || Last Name || Account Type || Balance ||

3. AdminRequests.txt

   • Contains queries to be processed by admin.
   • Each query has a different format. The 3 queries are :- adding an account, deleting an account and modifying an account (which has been limited to just password change).

II. Features implemented in the project :

1. A login system with 3 types of login - Normal User, Joint Account User, Admin

2. If a User is not registered at Login Prompt, he/she is given an option to create a normal/joint account. An add query is generated to be approved by Admin.

3. After a Normal/Joint User logs in, they are provided with the following menu :

• Deposit : Deposit certain amount to your account.
• Withdraw : Withdraw certain amount from your account.
• Balance Enquiry : Provides current balance in the account.
• Password Change : Generates a query for password change to be approved by Admin.
• View Details : View details of user's account number specified by him/her.
• Delete Account : Generates a query for deletion of account to be approved by Admin.
• Exit : Exit the menu.

4. After an Admin logs in , the following menu is provided :

• Execute pending Add queries
• Execute pending Delete queries.
• Execute pending Modify queries.
• Search for a specifc account details.
• Execute All Queries
• Exit

5. The concepts applied throughout the project include Socket Programming , Process Management, File Management, Mutex Locking, Multithreading , Signal Handling and Inter Process Communication Mechanisms.

6. All functional interactions are displayed on the client side. The server side only displays messages whenever there is a new client connection. Along with this, the server side will display the total number of visitors for the day with each new connection. The server allows a total of 25 clients per session. This can always be changed manually in the code.

7. Extras :

• The code allows re-prompting/re-entering of choices wherever possible.
• Sufficient checks and error messages to take care of ambiguities and incorrect information such as incorrect password and confirmation passwords.
• Ambiguities while handling of joint accounts (adding, viewing details) are taken care of.
• All interactions with the database are solely handled by an Admin.
• SIGINT handler to take care of abrupt disconnections. (via Ctrl-C)
• Takes care of the message boundary problem. (Refer to this for an understanding of the problem : https://www.codeproject.com/Articles/11922/Solution-for-TCP-IP-client-socket-message-boundary)

III. Running the code

1. To compile the server code, run the command : gcc -o server online_banking_server.c -lpthread
2. To execute, run the command : ./server <port_number> (For eg : ./server 8000)
3. To compile the client code, run the command : gcc -o client online_banking_client.c -lpthread
4. To execute, run the command : ./client <port_number> (For eg : ./client 8000)