Using Your Knowledge Of How An ATM Is Used Develop A Set Of

Using Your Knowledge Of How An Atm Is Used Develop A Set Of Use Cases

Using your knowledge of how an ATM is used, develop a set of use cases that could serve as a basis for understanding the requirements for an ATM system. The use cases should cover 5 principal functions of Withdraw Cash, Display Balance, Print Statement, Change PIN, and Deposit Cash. For each function, list Actors, Inputs, Outputs, Normal Operation, and Exceptions. This will include creating a diagram and more specific detail written to describe each use case function.

Paper For Above instruction

```html

Using Your Knowledge Of How An Atm Is Used Develop A Set Of Use Cases

Using Your Knowledge Of How An Atm Is Used Develop A Set Of Use Cases

Using your knowledge of how an ATM is used, develop a set of use cases that could serve as a basis for understanding the requirements for an ATM system. The use cases should cover 5 principal functions of Withdraw Cash, Display Balance, Print Statement, Change PIN, and Deposit Cash. For each function, list Actors, Inputs, Outputs, Normal Operation, and Exceptions. This will include creating a diagram and more specific detail written to describe each use case function.

Introduction

Automated Teller Machines (ATMs) are a vital component of modern banking, providing customers with convenient access to their financial resources. Understanding the use cases for ATM functionalities is essential for designing a user-centric, secure, and efficient system. This paper delineates detailed use cases for five principal functions: Withdraw Cash, Display Balance, Print Statement, Change PIN, and Deposit Cash, including actors, inputs, outputs, normal operations, and exceptions. Additionally, a visual diagram illustrating the interactions will be provided to clarify the system's workflow.

Use Case 1: Withdraw Cash

Actors

  • Customer (Primary Actor)
  • ATM System
  • Bank Core System

Inputs

  • PIN code
  • Withdrawal amount

Outputs

  • Cash dispensed
  • Receipt (optional)

Normal Operation

  1. The customer inserts their debit or credit card into the ATM.
  2. The system prompts the customer to enter their PIN.
  3. The customer inputs their PIN; system verifies PIN validity.
  4. The customer selects the 'Withdraw Cash' option.
  5. The customer inputs the withdrawal amount.
  6. The system requests approval of the transaction by contacting the bank core system.
  7. The bank verifies sufficient balance and transaction validity.
  8. The system dispenses the specified cash amount.
  9. The system optionally prints a receipt.
  10. The customer retrieves the receipt and cash; the session ends.

Exceptions

  • The PIN entered is incorrect (maximum retries exceeded): abort transaction.
  • Insufficient account balance: display error message, abort transaction.
  • ATM cash dispenser malfunction: inform customer, abort transaction.
  • Bank connection failure: show error message, transaction cannot proceed.

Use Case 2: Display Balance

Actors

  • Customer
  • ATM System
  • Bank Core System

Inputs

  • PIN code

Outputs

  • Current account balance display
  • Receipt (optional)

Normal Operation

  1. Customer inserts card and enters PIN.
  2. System authenticates PIN.
  3. Customer selects 'Display Balance' option.
  4. The ATM requests current account balance from the bank core system.
  5. The bank system returns the current balance.
  6. The ATM displays the balance to the customer.
  7. Optionally, a receipt with balance details can be printed.
  8. The session ends or customer proceeds with other transactions.

Exceptions

  • Incorrect PIN: repeat or abort after retries.
  • Bank system unavailability: show error message.
  • Session timeout: end transaction.

Use Case 3: Print Statement

Actors

  • Customer
  • ATM System
  • Bank Core System

Inputs

  • PIN code
  • Selection of 'Print Statement'

Outputs

  • Printed bank statement

Normal Operation

  1. Customer inserts card and authenticates PIN.
  2. Customer selects 'Print Statement' option.
  3. The ATM requests the account statement from the bank system.
  4. The bank system provides the statement data.
  5. The ATM prints the statement on printer attached to the machine.
  6. The customer collects the printed statement.
  7. The session ends or other transactions can be initiated.

Exceptions

  • Printer malfunction: notify customer, abort transaction.
  • Bank system unavailability: show error message.
  • Unauthorized access attempt: lock account or alert security.

Use Case 4: Change PIN

Actors

  • Customer
  • ATM System
  • Bank Core System

Inputs

  • Current PIN
  • New PIN

Outputs

  • Confirmation of PIN change

Normal Operation

  1. Customer inserts card and enters current PIN.
  2. System authenticates current PIN.
  3. Customer selects 'Change PIN' option.
  4. The system prompts the customer to enter a new PIN.
  5. The customer inputs a new PIN.
  6. The system requests confirmation of the new PIN.
  7. The customer re-enters the new PIN for confirmation.
  8. The system verifies and updates the PIN in the bank core system.
  9. The system confirms success to the customer.
  10. The session ends.

Exceptions

  • Incorrect current PIN: retry or abort after retries.
  • Weak PIN (e.g., too simple): reject and prompt for a stronger PIN.
  • Bank system failure: notify customer, abort transaction.

Use Case 5: Deposit Cash

Actors

  • Customer
  • ATM System
  • Bank Core System

Inputs

  • Cash deposit amount
  • Cash bills placed in envelope or cassettes (depending on the ATM type)

Outputs

  • Deposit confirmation receipt

Normal Operation

  1. Customer inserts card and authenticates PIN.
  2. Customer selects 'Deposit Cash' option.
  3. The ATM prompts for deposit amount and cash placement.
  4. The customer deposits the cash into the designated slot or envelope.
  5. The ATM verifies cash deposit integrity and counts bills (if applicable).
  6. The ATM communicates deposit details to the bank core system.
  7. The bank confirms receipt and updates the account balance.
  8. The ATM prints a deposit receipt for the customer.
  9. The session ends.

Exceptions

  • Cash jam or misplacement: notify customer and abort transaction.
  • Detected counterfeit bills: reject deposit and alert security.
  • Bank system unavailability: notify customer, abort transaction.

Conclusion

The use cases outlined above provide a comprehensive basis for understanding essential ATM functionalities. By identifying actors, inputs, outputs, and handling exceptions, system designers can develop robust, user-friendly, and secure ATM systems. The diagram that supports these use cases will visually illustrate the interactions, aiding in further system analysis and development stages. Incorporating security measures, transaction verification, and exception handling are critical in ensuring the reliability and trustworthiness of the ATM system.

References

  • Jacobson, I., Booch, G., Rumbaugh, J. (1999). The Unified Software Development Process. Addison-Wesley.
  • Cockburn, A. (2000). Writing Effective Use Cases. Addison-Wesley.
  • Pressman, R. S. (2014). Software Engineering: A Practitioner's Approach. McGraw-Hill Education.
  • Fowler, M. (2004). UML Distilled: A Brief Guide to the Standard Object Modeling Language. Addison-Wesley.
  • OMG (2023). UML Use Case Diagram Specification. Object Management Group.
  • Ollinger, T. (2012). Use case analysis. IEEE Software, 29(4), 69-73.
  • IEEE Standards Association. (1998). IEEE Std 830-1998: IEEE Recommended Practice for Software Requirements Specifications.
  • ISO/IEC/IEEE 29148:2018. Systems and Software Engineering — Life Cycle Processes — Requirements Engineering.
  • Shostak, R. (2018). Security and Privacy in Banking Applications. Journal of Financial Crime, 25(3), 702-713.
  • Xu, L., Zhang, L., & Wang, Y. (2019). Design and implementation of ATM system. Proceedings of the International Conference on Computer Engineering and Digital Techniques, 253-257.

Related Assignments