Conversation
|
This is a good start, but yu are missing a few key top-level classes whcih akes your design incompete. Customer, Manager, and Transaction all need to be modelled as classes, as they have behavior, and properties. this is the way I would do it, but feel free to tweak it +-------------------------------------------------------+ +-------------------------------------------------------+ +-------------------------------------------------------+ +-------------------------------------------------------+ +-------------------------------------------------------+ +-------------------------------------------------------+ +-------------------------------------------------------+ Relationships: Account "1" → "*" OverdraftRequest (Account has many OverdraftRequests) Branch "1" → "*" Account (Branch has many Accounts) Customer "1" → "*" Account (Customer has many Accounts) BankingService "1" → "*" Branch (Manages many Branches) BankingService "1" → "*" Customer (Manages many Customers) BankingService depends on Account, Transaction, and OverdraftRequest for operations Key Design Points: Branch association: Each account links to a branch via branchId Overdraft workflow: Clear separation between request, approval, and processing Messaging: Customer has phone number and receives statements via sendStatement() Service layer: BankingService orchestrates all operations |
No description provided.