Draw an ER diagram accordingly to the following user requirements. You can draw the diagram using tools that you prefer, such as Microsoft Viso, which is available in most of the ECS labs Hand-drawn diagram will also be accepted as long as it is clear. (Note: For any other assignments in the future, no hand-written submission will be accepted.) Please submit a PDF file to SacCT. List assumptions for your diagram, if there is any A bank application keeps track of customer information, including SSN, first name, last name, phone number, and address. When a person either owns an account or borrows a loan, the person becomes a customer of the bank. The bank database keeps track of account information, including account balance, type of account (e.g. saving, checking), and when the account is opened by a customer. When a customer opens a new account, the date to open the account is the same as the date the customer owns the account. New customers can be added to an account after the account was opened. We need the date when a customer starts to own an account. A customer can own many accounts. An account must be owned by at least one customer The bank application also keeps track of loan information. A loan has a loan number (unique), total amount of the loan, the loan type (e.g. car). A loan has a number of payments Each payment has a payment number that is unique with respect to a loan. Each payment has an amount, the method for the payment, and a status (paid, not paid), and a due date. A customer can borrow many loans. A loan can be borrowed by many customers, at least onc. The application also keeps track of the information of branches of the bank. Each branch has a branch name (unique) and an address. Each customer has one favorite branch that he/she visits most frequently. If a customer never goes to a branch (for example, only use online banking), he/she does not have a favorite branch. A branch can be the favorite of many customers, at least one