A local bank intends to install a new automated teller machine (ATM) to allow. The bank wants you to develop software to perform the financial transactions initi. To capture what a proposed system should do, developers often employ a.
Introduction to Banking Management System Project:
This project makes use of Microsoft Visual Basic for front end and Microsoft Access for back end. The main functions of this project is to store the information about hotel, includes data about room, contains details of customer, and makes entries for updating and deleting the details related to customers. Some of the benefits that can be acquired by installing this system when compare to manual record handling includes reduces errors, removes redundancy, offers better protection, makes work easier, reduces manual labor, etc.
System model is considered as a systematic approach towards software development. For instance, before building any house its very essential to make a layout design of house similar it is in the case of any software. So, even in this case before writing code to any of the software its necessary to make the model of a software. Since the model includes all the steps that need to be followed at the time of developing system. This process makes the task of engineer quite simple and further helps the developer to build software that is less error prone.
The system modeling tasks accomplished includes the processes which serve the requirements of view under consideration. Symbolize the processes behavior of processes and assumptions on which the behavior is based. It explicitly defines both endogenous and exogenous input to model.
Signifies all the linkages which allows engineer better understand the view. This designed software enables the administrations to easily manage the records of all students in university and further makes their work efficient, reduces time, removes inconsistency and removes redundancy.
The other main benefit with this system is that it directly issues the mark sheet to students. Software’s that is required for this system includes Microsoft Visual Basic 6.0, Microsoft Access 2000 and hardware requirements consists of pentium processor, 64MB RAM, 14”monitor, 80 columns by 25 rows text resolution, HP laser jet61, total 104 keys with 12 function keys key board and 220 to 250 Volts.
Download Banking Management System Documentation.
Use Cases for Example ATM System(Click on a use case above to go to the flow of events for that use case)Flows of Events for Individual Use CasesSystem Startup Use Case
The system is started up when the operator turns the operator switchto the 'on' position. The operator will be asked to enter the amount of money currently in the cash dispenser, and a connection to the bank will beestablished. Then the servicing of customers can begin.
System Shutdown Use Case
The system is shut down when the operator makes sure that no customer isusing the machine, and then turns the operator switch to the 'off' position.The connection to the bank will be shut down.Then the operator is free to remove deposited envelopes, replenish cash andpaper, etc.
Session Use Case
A session is started when a customer inserts an ATM card into the cardreader slot of the machine. The ATM pulls the card into the machine andreads it. (If the reader cannot read the card due to improper insertion or a damaged stripe, the card is ejected, an error screen is displayed, and the session is aborted.) The customer is asked to enter his/her PIN, and is then allowed to perform one or more transactions, choosing from a menu of possible typesof transaction in each case. After each transaction, the customer is askedwhether he/she would like to perform another.When the customer is through performing transactions, the card is ejected from themachine and the session ends. If a transaction is aborted due to too many invalidPIN entries, the session is also aborted, with the card being retained in the machine.
The customer may abort the session by pressing the Cancel key when enteringa PIN or choosing a transaction type.
Transaction Use Case
Note: Transaction is an abstract generalization. Each specific concrete type oftransaction implements certain operations in the appropriate way. The flow of eventsgiven here describes the behavior common to all types of transaction. The flows ofevents for the individual types of transaction (withdrawal, deposit, transfer,inquiry) give the features that are specific to that type of transaction.
A transaction use case is started within a session whenthe customer chooses a transaction type from a menu of options. The customer will be asked to furnish appropriate details (e.g. account(s)involved, amount). The transaction will then be sent to the bank, along withinformation from the customer's card and the PIN the customer entered.
If the bank approves the transaction, any steps needed to complete the transaction(e.g. dispensing cash or accepting an envelope) will be performed, and then areceipt will be printed. Then the customer will be asked whether he/she wishesto do another transaction.
If the bank reports that the customer's PIN is invalid,the Invalid PIN extension will be performed and then an attempt will be made tocontinue the transaction. If the customer's card is retained due to too manyinvalid PINs, the transaction will be aborted, and the customer will not beoffered the option of doing another.
If a transaction is cancelled by the customer, orfails for any reason other than repeated entries of an invalid PIN, a screen willbe displayed informing the customer of the reason for the failure of the transaction,and then the customer will be offered the opportunity to do another.
The customer may cancel a transaction by pressing the Cancel key as described foreach individual type of transaction below.
All messages to the bank and responses back arerecorded in the ATM's log.
Withdrawal Transaction Use Case
A withdrawal transaction asks the customer to choose a type of account to withdraw from (e.g. checking) from a menu of possible accounts, and to choosea dollar amount from a menu of possible amounts. The system verifies that ithas sufficient money on hand to satisfy the request before sending thetransaction to the bank. (If not, the customer is informed and asked to entera different amount.) If the transaction is approved by the bank, the appropriate amount of cash is dispensed by the machine before it issues a receipt. (Thedispensing of cash is also recorded in the ATM's log.)
A withdrawal transaction can be cancelled bythe customer pressing the Cancel key any time prior to choosing the dollar amount.
Deposit Transaction Use Case
A deposit transaction asks the customer to choose a type of account to deposit to (e.g. checking) from a menu of possible accounts, and to type in a dollar amounton the keyboard. The transaction is initially sent to the bank to verify that the ATM can accept a deposit from this customer to this account. If the transaction is approved, the machine accepts an envelope from the customer containing cashand/or checks before it issues a receipt. Once the envelope has been received, asecond message is sent to the bank, to confirm that the bank can credit the customer'saccount - contingent on manual verification of thedeposit envelope contents by an operator later. (The receipt of an envelope is also recorded inthe ATM's log.)
A deposit transaction can becancelled by the customer pressing the Cancel key any time prior to inserting theenvelope containing the deposit. The transaction is automatically cancelled if thecustomer fails to insert the envelope containing the deposit within a reasonableperiod of time after being asked to do so.
Transfer Transaction Use Case
A transfer transaction asks the customer to choose a type of account to transfer from (e.g. checking) from a menu of possible accounts, to choose a different account to transferto, and to type in a dollar amount on the keyboard. No further action is required oncethe transaction is approved by the bank before printing the receipt.
A transfer transaction can be cancelled by the customer pressing the Cancel keyany time prior to entering a dollar amount.
Inquiry Transaction Use Case
An inquiry transaction asks the customer to choose a type of account to inquire aboutfrom a menu of possible accounts. No further action is required oncethe transaction is approved by the bank before printing the receipt.
An inquiry transaction can be cancelled by the customer pressing the Cancel keyany time prior to choosing the account to inquire about.
Invalid PIN Extension
An invalid PIN extension is started from within a transaction when the bankreports that the customer's transaction is disapproved due to an invalid PIN.The customer is required to re-enter the PIN and the original request is sent to the bank again. If the bank now approves the transaction, or disapprovesit for some other reason, the original use case is continued; otherwise the process of re-entering the PIN is repeated. Once the PIN is successfullyre-entered, it is used for both the current transaction and all subsequent transactionsin the session. If the customer fails three times to enter the correct PIN, the card ispermanently retained, a screen is displayed informing the customer of this andsuggesting he/she contact the bank, and the entire customer session is aborted.
If the customer presses Cancel instead of re-entering a PIN, the original transactionis cancelled.
Copyright © 1996, 1997, 1998, 2000, 2001, 2002, 2004 - Russell C. Bjork. Permission for non-commercial reproduction for educational use is hereby granted; all other rights are reserved.Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |