Tag Info

New answers tagged

0

Ideally the bank application should worry more about the account than the customer. For example, the bank should have methods like addAccount() : which will add account and create a customer implicitly if it is the first account of the customer and deleteAccount() : which will delete the account and delete the customer implicitly if it is the last ...


-2

Object Oriented Modeling, its used to represent the real world in a Software Application. In other times, a single account, had only, and only one customer, assigned. These days, several customers, can be assigned and removed from an account. There are many ways to model an application, so there is not really a "100% bad" or "100% good" way. Your example ...


3

This seems like a classical Has Many/Belongs To relationship type. What we usually do is kind of a merge between your 2 options, where: A Customer has a list of the many Accounts he has. An Account has a reference to the Customer it belongs to. That being said, @James Anderson is accurate as he states the importance of customers rather than the account ...


6

Oh Dear. Your design is how bank applications were designed in the 1970s. Myself and several thousand professionals have spent decades undoing this design error to get systems looking more like option 1. Banks deal with customers the account is just a mechanism for dealing with some of the customers money. More importantly the stack of regulators who ...


1

YMMV, but in our environment, we prefer any test code automatically to be rebuild after a change to library on which the test code depends was made. Having to switch between configurations first makes it easier to forget the rebuild. And don't you run into trouble when you try to debug through the test applications, and step from the test application's code ...



Top 50 recent answers are included