Draw the Entity Relationship Diagram (ERD) in Crows Foot notation of the database designed for the above application scenario. In the ERD, you need to specify the main components including Entities, Attributes, Relationships, Primary Keys, and Constraints.

Application Description: Suppose there is one bank company ABC that requires to develop a relational database. The daily duty is to serve their customers managing their saving bank accounts, e.g., withdraw, deposit, etc. Additionally, the company ABC also makes business for the home loan marketing, e.g., a customer may have a home loan account.

To set up a home loan account for a customer, there are several information to be collected and recorded:

(1) the customer needs to specify a property address;

(2) a bank staff needs to be assigned to process the home loan application;

(3) the property value should be assessed by using the average of the sold price of the properties located in the same suburb. Note: suppose there are sold properties in every suburbs;

(4) Each customer has their own home loan max limit that is calculated by his/her 10 years annual salary plus 0.65*property value plus customer savings (amount in his accounts): Note: property value is based on avg sold price of that suburb. Note: In general, the bank company used 10 years salary to estimate, e.g., if the customer Kevin has annual income $60,000, then his home loan limit cannot exceed $600,000. For the customers having multiple home loans, their total home load amount cannot exceed the customers home loan limit;

(5) a customer may have more than one home loan because multiple properties can be bought by one customer. Last but not least, your design should reflect the practical requirement as much as possible, i.e., meeting the maximum business rules. For example, some customers may have home loan accounts, but some ones may only have saving accounts. For a customer who need to set up a home loan account, it must create a saving account first. The average sold price for a suburb should be calculated on demand, not saved directly in the database.

(6) A customer may have more than one back account.

(7). A loan may be associated with more than one customer as joint loan

(8) In case of join loan, the database records the loan/joint customer to compute borrowing capacity and total loan of the property.