Use cases ... Apa format... No Plagarism Pls....
q.frantlbn
CIS210007VA016.docx
CIS210007VA016-1178-001 - Systems Analysis And Developme
Week 6 Assignment 2 Submission
on Mon, Nov 13 2017, 12:26 PM
100% highest match
Submission ID: ff071882-18e2-4fc7-b40f-57693f2e8138
· Assignment 2.docx
Word Count: 1,393
Attachment ID: 187774396
100%
Citations (5/5)
1. 1 Another student's paper
???orig.citation.highlight.msg???
2. 2 Another student's paper
???orig.citation.highlight.msg???
3. 3 Another student's paper
???orig.citation.highlight.msg???
4. 4 Another student's paper
???orig.citation.highlight.msg???
5. 5 Another student's paper
???orig.citation.highlight.msg???
Use cases to support an ATM service November 13, 2017
1 Introduction A withdrawal, deposit, transfer or an inquiry transaction provide the specific features for the given type of transaction. However, the flow of events is common for these transactions.
A use case begins within a session when a customer selects a transaction type from a list of options. ATM machine asks the user to provide the necessary details such as the account and amount. These details are relayed to the bank system for verification. Upon verification and approval, the transaction is conducted, and receipt printed. The customer is prompted to select whether to make another transaction (Hay, 2011).
Withdrawal Transaction Use Case Withdrawal operation requires the client to choose the type of account to withdraw from (eg saving, checking) from a list of possible accounts, and to pick an amount from a list of withdrawal amounts. The system ensures that the money is to be withdrawn before the transactions take effect from the bank. Should the transactions be approved from the bank, the bank will dispense the exact amount and then a receipt is issued latter. The TM then keeps the record of transactions, which occur during the transaction period. During withdrawal, the customer is given an option of cancelling the cancelling key to reverse the transactions.
1 This use case gives a description of how a user uses a bank ATM machine to withdraw cash from ATM.
· The ATM must have adequate internet connection.
1 · The ATM machine Must have money to dispense to customers.
· The cash withdrawal option must be present.
Post-conditions: 1 The customer gets the amount that he wanted to withdraw as well as a receipt showing the details of the transaction. In addition, the systems update the customer’s account after the transaction Specifications:
Primary Actor: Customer Stakeholders:
- Customer: 1 Wants a precise withdrawal transaction (quick and accurate operation).
- Bank: 1 Wants to provide high quality service to the customer that is fast, accurate and reliable.
- Bank owning the ATM machine: (In case, the customer withdraws from another bank): Wants to charge the customer the appropriate amount of charge for the withdrawal.
- ATM machine Administrator: Wants to make sure that the ATM has enough cash to dispense for an estimated number of withdrawal transactions per day.
1. 1 The customer inserts ATM card into the ATM machine and keys in PIN.
2. 2 The system validates the ATM card and PIN number 3. 1 The customer chooses the ‘Cash Withdrawal’ option from the Options list items.
4. 1 The system prompts the customer to key in a certain amount of cash to withdraw.
5. 1 The customer keys in a cash amount and chooses the ‘Submit’ option on the Cash Withdrawal window.
6. 1 The system validates the amount keyed in; verifies the customer account balance and checks that the machine has sufficient cash for the withdrawal transaction, and prompts the customer to select an option to get a receipt for the transaction.
7. 1 The customer chooses the ‘OK’ option on the Receipts Screen.
1. 1 The customer keys in invalid PIN. The system prompts the customer to key in a valid PIN.
2. 1 The customer inserts an incompatible ATM card. The ATM machine ejects the card and gives an error message on the Home screen.
3. 1 The customer keys in an amount that exceeds the withdrawal limit.
4. 1 The system denies the execution of the withdrawal operation and gives an error message.
A deposit transaction prompts the customer to select a given type of bank account to make a deposit, such as saving, checking, or ordinary account from a list of accounts. This operation asks the customer to key in the amount to deposit. First, the ATM machine checks the eligibility of the customer to deposit cash. A confirmation from the bank system on this transaction allows the ATM machine to accept the customer’s envelope and issues a receipt. The ATM machine sends an acknowledgement of envelope receivership to the bank system. The bank credits the amount to the customer bank account pending a verification procedure to be done to examine the contents of the envelope. The ATM machine keeps a transaction log as a record of the transaction (Halpin, Krogstie & Proper, 2009).
A customer can cancel a deposit transaction by selecting and pressing the Cancel key only before inserting the envelope holding the deposit. Once the envelope is accepted, the operation cannot roll back and dispense the envelope. The system cancels the transaction automatically in case the customer delays or fails to insert the envelope (Bajaj & Wrycza, 2009).
1 · The ATM machine must have an active network connection with the Bank System.
Post-conditions: 1 The customer gets the acknowledgement on the cash amount or cheque amount deposited as well as a receipt showing the details of the transaction. 3 In addition, the systems update the customer’s account after the transaction
Specifications:
Primary Actor: Customer Stakeholders:
- Customer: 1 Wants a precise deposit transaction (quick and accurate operation).
- Bank: 1 Wants to provide high quality service to the customer that is fast, accurate and reliable.
- ATM machine Administrator: Wants to make sure, that the ATM can accept envelopes for an estimated number of deposit transactions per day.
A deposit transaction prompts the customer to select a particular of bank account to make a cash transfer. It can be a saving, current or ordinary account from a list of accounts. This operation further asks the customer to select a different account to make transfer to and key in the amount to transfer. The bank system confirms that the customer account has enough money for the transfer request before approving the transaction. (If it cannot satisfy the request, an alert message of insufficient amount informs the customer and asks to key in a different amount.) If this transaction gets an approval from the bank, the system transfers the exact amount of cash before issuing a receipt. (The ATM machine records and keeps a log of the transaction. The customer can also cancel the operation by pressing the Cancel key before selecting the amount to transfer option.
Invalid PIN Extension A wrong PIN extension originates from a transaction when the bank systems validates the customer's transaction and disapproves it due to a wrong PIN. The ATM machine prompts the customer to re-enter the PIN and the machine sends an authentication request to the bank. In case of transaction approval or disapproval, the former use case progresses; otherwise this step of re-entering the PIN is repeated. A successful validation of the PIN permits the execution of both the current transaction and all subsequent transactions in the session. 4 A three successive unsuccessful login attempts cause the card to be retained. 1 A screen gives a message advising the customer to contact the bank for manual retrieval of the card, and the customer session terminated. The customer can press the Cancel key to haul the entire transaction back to the beginning.
The customer authentication is one of the many ethical issues, the use case exposes about the development or use of the ATM system. The ATM machine authenticates the customer partially without ascertaining fully the person making the transactions is the real cardholder.
Running head: 5 ATM USE CASE 1
2 References Bajaj, A., & Wrycza, S. (2009). 1 Systems analysis and design for advanced modeling methods. Hershey, PA: 1 Information Science Reference.
Bajec, M., & Eder, J. (2012). 1 Advanced information systems engineering workshops. Berlin: Springer.
Gomaa, H. (2000). 1 Designing concurrent, distributed, and real-time applications with UML. Reading, MA: Addison-Wesley.
1 Halpin, T., Krogstie, J., & Proper, E. (2009). 1 Innovations in information systems modeling. Hershey, PA: 1 Information Science Reference.
Hay, D. (2011). 1 UML & data modeling. Westfield, NJ: Technics Publications.
Sein, M. (2001). 1 Contemporary trends in systems development. New York: Springer Science.
