Requirements

Functional Requirements:

• Deposit adds funds to an account.
• Withdraw removes funds, rejecting if the balance is insufficient.
• Transfer atomically debits one account and credits another.
• Maintain an accurate account balance and prevent overdrafts.
• Record transaction history with timestamp, type, amount, and resulting balance.
• Support multiple account types, such as checking and savings accounts.

Non-Functional Requirements:

• List the key non-functional requirements (eg thread safety, extensibility, maintainability, etc.)...
• we must include thread safety in case of 2 users trying to access the same account or same resource in that case we can apply synchronized block or method will be helpful.
• We must provide extensibility like if user try to withdraw via cash, netbanking, or mobile banking or UPI. and also we can provide extensibility to choose what kind of account he want to use like current account or saving account.

Core Objects & Relationships

Based on the requirements and use cases, identify the main objects of the system and analyze how they interact and relate to each other...

User{

id primary key,

name,

email,

address

}

Account{

accountId primary key,

account_type, (current account/ saving account)

branch_name,

IFSC_code,

balance,

user_id foreign key reference (user(id))

}

Transcation{

transactionId primary key,

transactionType, (cash / UPI / netbanking)

transactionDetails,

transaction_account_id foreign key reference (account(account_id))

}

APIs & Class Members

For each class, define the attributes (data) it will hold and the methods (functions) that operate on the attributes. Ensure they align with the object's responsibilities and adhere to the principle of encapsulation. Write your code in the code editor below.

Deep Dive

Explain design tradeoffs you considered. Check and explain whether your design adheres to SOLID principles. Explain how your design can handle changes in scale and whether it would be easy to extend with new functionalities. Identify areas for future improvement...

My design follow SOLID principles

Single Responsiblities - all classes serve single responsiblities no other things are there