0% found this document useful (0 votes)
20 views1 page

Final Requirement in OOP

Uploaded by

marcmercado2004
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views1 page

Final Requirement in OOP

Uploaded by

marcmercado2004
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Republic of the Philippines

ISABELA STATE UNIERSITY – ANGADANAN CAMPUS


Centro 03, Angadanan, Isabela

Bachelor of Science in Information Technology


FINAL REQUIREMENT IN OBJECT-ORIENTED PROGRAMMING
DIRECTION: Build a Java Program, to represent ATM Transaction, where a User has to choose input
from the options displayed on the Screen. The available options on the Screen include operations
such as Withdraw, deposit, balance. The Java program should have at least 5 stored accounts where
the user can perform the different transactions listed below:

Following are the basic operations available in the ATM


1. Withdraw
2. Deposit
3. Check Balance
4. Exit

Approach to each Option

A. Withdraw:
1. Take the amount user desires to withdraw as input.
2. If the balance amount greater than or equal to the withdrawal amount then
Perform the transaction and give the user the desired amount.
3. Else print Insufficient Funds message.
B. Deposit:

1. Take the amount user desires to deposit as input.


2. Add the received input from the user to balance and update its value.
3. balance = balance + deposit.
4. Print a message on screen stating deposit transaction has been successful.
C. Check Balance:
• Print a message on screen showing the value of balance amount.
D. Exit:
• Exit the current Transaction mode and return the user to the home page or
initial screen.

• Utilize Object-Oriented Programming (OOP) principles:


• Encapsulation: Wrap the account details and transactions in a class.
• Inheritance: Create a subclass for user-specific accounts.
• Polymorphism: Implement polymorphic behavior for transaction methods.
• Abstraction: Abstract away the details of account operations within the ATM class.
• Ensure user-friendly interactions and handle invalid inputs gracefully.
• Implement a loop to allow users to perform multiple transactions until choosing the exit
option.
• Keep the code modular and well-documented for clarity and maintainability.

You might also like