To complete the assignment, follow these steps:$1.$ Define Your Database Design $($Normalized$)$A$.$ Data Elements and Definitions$1.$Customer: Information about RBC customers.CustomerID: Unique identifier for each customer. $($Primary Key$)$FirstName: Customers first name.LastName: Customers last name.DateOfBirth: Customers date of birth.Email: Customers email address.PhoneNumber: Customers phone number.AddressID: Foreign key linking to the Address table$\mathrm{.}2.$Account: Information about customer accounts.AccountID: Unique identifier for each account. $($Primary Key$)$CustomerID: Foreign key linking to the Customer table.AccountType: Type of account $($e$.$g$.,$ Checking, Savings$).$Balance: Current balance of the account.DateOpened: Date the account was opened$\mathrm{.}3.$Transaction: Information about account transactions.TransactionID: Unique identifier for each transaction. $($Primary Key$)$AccountID: Foreign key linking to the Account table.TransactionType: Type of transaction $($e$.$g$.,$ Deposit, Withdrawal$).$Amount: Amount of the transaction.TransactionDate: Date the transaction occurred$\mathrm{.}4.$Address: Information about customer addresses.AddressID: Unique identifier for each address. $($Primary Key$)$StreetAddress: Street address of the customer.City: City of the customer.State: State of the customer.PostalCode: Postal code of the customer.Country: Country of the customer.B$.$ VISIO DiagramCreate a VISIO diagram illustrating the tables $($Customer$,$ Account, Transaction, Address$)$ and the relationships between them. Ensure that foreign key constraints are clearly depicted$\mathrm{.}2.$ Answer Questions in the Word DocumentA. Purpose of Each ElementCustomer: Stores personal information of customers.Account: Stores information about customer accounts.Transaction: Stores transaction details for each account.Address: Stores address information for customers.B$.$ Range of Values for Each Data ElementCustomerID, AccountID, TransactionID, AddressID: Unique integers, auto$-$incremented.FirstName, LastName, Email, StreetAddress, City, State, Country: String values.DateOfBirth, DateOpened, TransactionDate: Date values.PhoneNumber: String $($with format constraints$).$AccountType, TransactionType: Enumerated string values $($e$.$g$.,$ Checking, Savings for AccountType; Deposit, Withdrawal for TransactionType$).$Balance, Amount: Decimal values.C$.$ Primary KeysCustomer: CustomerIDAccount: AccountIDTransaction: TransactionIDAddress: AddressIDD. Normalization Rules AppliedFirst Normal Form $(1$NF$)$: Each table has a primary key and all columns contain atomic values.Second Normal Form $(2$NF$)$: All non$-$key attributes are fully functionally dependent on the primary key.Third Normal Form $(3$NF$)$: All attributes are functionally dependent only on the primary key, removing transitive dependencies.E$.$ Data Element InterrelationsCustomer table relates to Account through CustomerID.Account table relates to Transaction through AccountID.Customer table relates to Address through AddressID$\mathrm{.}3.$ List of Tables and Data Elements in RBCBranch: Information about RBC branches.BranchID: Unique identifier for each branch.BranchName: Name of the branch.Location: Location of the branch.Employee: Information about RBC employees.EmployeeID: Unique identifier for each employee.FirstName: Employees first name.LastName: Employees last name.Position: Job title of the employee.BranchID: Foreign key linking to the Branch table.Loan: Information about loans issued to customers.LoanID: Unique identifier for each loan.CustomerID: Foreign key linking to the Customer table.LoanAmount: Amount of the loan.LoanType: Type of loan $($e$.$g$.,$ Personal, Mortgage$).$InterestRate: Interest rate of the loan.StartDate: Date the loan was issued.EndDate: Date the loan is due.Supporting Database Design RequirementsData Security: Ensure encryption and access controls are in place to protect sensitive customer information.Scalability: Design should support future growth in data volume and user base.Data Integrity: Implement constraints and validation rules to maintain data accuracy and consistency.Performance: Optimize queries and indexing to ensure efficient data retrieval and manipulation.By following this outline, youll ensure a well$-$structured, normalized database design with clear documentation and visualization of tables and relationships, meeting the requirements for your IT$-$driven solution project.