Scribd
Upload
14 views

Database

The document discusses designing an information system for a bank. It describes an entity-relationship diagram with accounts, branches, customers, and loans as entities. It provides the equivalent relational model and steps to create a database with tables for the entities and relationships and insert sample data.

Uploaded by

chomohzidane
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
14 views

Database

The document discusses designing an information system for a bank. It describes an entity-relationship diagram with accounts, branches, customers, and loans as entities. It provides the equivalent relational model and steps to create a database with tables for the entities and relationships and insert sample data.

Uploaded by

chomohzidane
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Powered by AI

Copilot

Certainly! Let’s address each question related to designing an information system for a bank:

1. What is this representing? Describe it with all its components.

The provided image appears to be an Entity-Relationship (ER) diagram for a bank information
system. ER diagrams visually represent the structure of a database by illustrating entities, their
attributes, and the relationships between them.
Here are the components depicted in the diagram:
Entities:
Account: Represents bank accounts held by customers.
Branch: Represents bank branches.
Customer: Represents individual bank customers.
Loan: Represents loans provided by the bank.
Attributes:
Each entity has specific attributes associated with it. For example:
Account: Attributes include A/C_no, Balance, and Assets.
Customer: Attributes include c_name (customer name) and c_street (customer
address).
Loan: Attributes include l_id (loan ID) and amt (loan amount).
Relationships:
The diagram shows relationships between entities:
Branch has a one-to-many relationship with Account (one branch can have
multiple accounts).
Customer has a one-to-many relationship with Account (one customer can have
multiple accounts).
Customer has a one-to-many relationship with Loan (one customer can have
multiple loans).

2. Give the equivalent relational model of this figure.

To create the equivalent relational model, we’ll map the entities and their relationships to tables in a
relational database:
Account:
Table name: Account
Attributes: A/C_no, Balance, Assets, Branch_name
Branch:
Table name: Branch
Attributes: Branch_name, Branch_city, Assets
Customer:
Table name: Customer
Attributes: c_name, c_street
Loan:
Table name: Loan
Attributes: l_id, amt
Relationships:
Create foreign keys in the tables to represent the relationships (e.g., Branch_name in
Account refers to Branch_name in Branch).

3. Using appropriate software, create a database entitled “BANK” with three accounts, each having
borrowed 150,000 FCFA at your customer service. Name the database “HNDSEW2022” and place it
in a folder named “HND2023.” Write a query to select all customers.

To achieve this, follow these steps:


1. Create a database named “BANK” using a database management system (DBMS) like MySQL,
PostgreSQL, or SQL Server.
2. Within the “BANK” database, create the necessary tables (Account, Branch, Customer, and
Loan) based on the relational model.
3. Insert three sample accounts with loan amounts of 150,000 FCFA each.
4. Name the database “HNDSEW2022” and place it in a folder named “HND2023.”
5. Write a SQL query to select all customers:
SELECT c_name, c_street
FROM Customer;

6. Execute the query to retrieve the customer information.

Remember that this is a simplified explanation, and in a real-world scenario, additional considerations (such as
security, scalability, and performance) would be essential for designing a robust bank information system.

You might also like