
Chapter 16. ATM Application Business Model and Controller 291
Figure 187. Relationship Tailoring (Before and After)
We tailored the relationships in two ways: assigning user-friendly names and
specifying the required attribute. (Thesetting of the required attribute is lost
in the generation process; custid is a NOT NULL column in the card table.)
The tailored relationships are:
❑ Card CustomerCard Customer: owningCustomer (1, required),
ownedCards (m)
❑ Cardaccount CardAccounts Card: atmCard (1, required), toAccounts (m)
❑ Account BankAccount Bank: owningBank (1), ownedAccounts (m)
❑ Customer BankCustomer Bank: theBank (1, required), hasCustomers ...