Prompt Detail:
Sure, I can create an Entity-Relationship (ER) diagram based on the provided information. Here's the ER diagram:
sql +---------------+
| Customer |
+---------------+
| CustomerID(PK)|
| Name |
| Address |
| PhoneNumber |
| EmailAddress |
+---------------+
|
| 1
|
+---------------+
| Account |
+---------------+
1 | AccountNumber (PK)|
+---------------+ AccountType |
| | Balance |
| | InterestRate |
| | OpeningDate |
| | CustomerID (FK)|
| | BranchID (FK) |
+---------------+---------------+
| 1 |
| |
| 1 N |
| +---------------+
| | Branch |
| +---------------+
| | BranchID (PK)|
| | BranchName |
| | Address |
| | City |
| | State |
| +---------------+
| |
| 1 |
+--------------------------------------+
| |
+---------------+ |
| Loan | |
+---------------+ |
| LoanID (PK) | |
| LoanAmount | |
| InterestRate | |
| RepaymentPeriod| |
| StartDate | |
| CustomerID (FK)| |
+---------------+ |
| |
| |
| 1 |
+---------------------------+
| |
+---------------+ |
| Transaction | |
+---------------+ |
| TransactionID | |
| TransactionType| |
| Amount | |
| Date | |
| Time | |
| AccountNumber (FK)|
+---------------+
This diagram follows the laws of Entity-Relationship diagrams, depicting entities as rectangles, attributes within ellipses, and relationships as lines connecting entities with appropriate cardinality indicators (e.g., 1 or N). Each entity is labeled with its name and its primary key attribute(s) are underlined. ForeignKey attributes are also indicated where appropriate.