Your report must include: Listing of new program files (or modified files) with appropriate comments, Description of the algorithms used, Expected input format with source, Expected output format with source, A capture of the interaction with your program (test cases to demonstrate it works as specified). Modify the existing echoing client/server pair to act as an electronic bank. The client handles the user interaction while the server acts as the bank. There is only one client accessing the bank at a time. The user, via the client, may open new account, deposit money into an existing account, check the account balance, close the account, or withdraw money from an existing account. When creating a new account the user must supply a name and initial deposit in whole dollars. The server will return an account number for future interactions. To deposit money the user must supply the account number and an amount of money to deposit in whole dollars. The server will return the balance in the account. To check the balance in the account the user need only supply the account number. The server returns the account balance or an error if the account number does not exist. To close an account the user asks for the entire balance to be withdrawn. Doing this invalidates the account number. To withdraw money from an existing account the user must supply the account number and the amount of money to withdraw in whole dollars. On deposit, balance checking, or closing, the account number must exist otherwise the server returns an error.
## Deliverables
Your report must include: Listing of new program files (or modified files) with appropriate comments, Description of the algorithms used, Expected input format with source, Expected output format with source, A capture of the interaction with your program (test cases to demonstrate it works as specified). Modify the existing echoing client/server pair to act as an electronic bank. The client handles the user interaction while the server acts as the bank. There is only one client accessing the bank at a time. The user, via the client, may open new account, deposit money into an existing account, check the account balance, close the account, or withdraw money from an existing account. When creating a new account the user must supply a name and initial deposit in whole dollars. The server will return an account number for future interactions. To deposit money the user must supply the account number and an amount of money to deposit in whole dollars. The server will return the balance in the account. To check the balance in the account the user need only supply the account number. The server returns the account balance or an error if the account number does not exist. To close an account the user asks for the entire balance to be withdrawn. Doing this invalidates the account number. To withdraw money from an existing account the user must supply the account number and the amount of money to withdraw in whole dollars. On deposit, balance checking, or closing, the account number must exist otherwise the server returns an error. On withdrawal, the account must exist and have sufficient funds to cover the withdrawal otherwise the server returns an error. The bank must be persistent. It must maintain the account information from one invocation of the server to the next. (the afs version needs the iostream included.) Afs-UNIX Linux Microsoft Visual Studio v6 Readme Readme Example write up .doc: [login to view URL] Example write up .pdf [login to view URL]
## Platform
Afs-UNIX Linux Microsoft Visual Studio v6 Readme Readme Example write up .doc: [login to view URL] Example write up .pdf [login to view URL]