Skip to main content

United Community Bank Entity Relationship Diagram | Database Design

By

United Community Bank Database Requirements

The Project The United Community Bank (UCB) is a well established regional bank operating primarily in South England, but with several branches in key cities and towns in the North. The last 5 years saw the bank transform into a fully computerised bank. Keeping in pace with its philosophy of responsive customer service, UCB decided to offer online banking services to its customers. The new online banking service would fully integrate with the core banking solution already implemented at the bank. The online banking service is open to savings account customers and current account holders.

The basic entity for explaining all operations in the bank is the customer. A customer may have one or more accounts in the bank spread across one or more branches. Customers open bank accounts with a specified opening balance and thereafter may either deposit funds into the account or withdraw amounts from them. For each customer the system wants to record name, personal information (e.g. address, phone number), customer id, password, accounts held. For each account, the system should store basic account information (e.g. account number, sort code), the list of transactions and the interest associated with the account and the available overdraft (only for current accounts).

One of the most frequent requests for information by customers is querying on balance and information regarding specific transactions carried out in the bank. In addition to this, the system should be able to perform the following actions: registration of new customers, opening new accounts for customers, deposit transactions, withdrawal transactions, maintaining security password information on customers.

This site will not handle financial transactions but it will pass data on to the core banking solution, so you do not have to worry about handling the cash aspects, but the database must be capable of providing a set of data containing the details of the customer and his/her transactions.

Get Project Solution by contacting us

- via WhatsApp: +92-324-7042178
- via email: codelogixstudio@gmail.com
Labels:

Popular posts from this blog

The Zoo Management System - entity relationship diagram & MS Access Database

By
Zoo Management System - Project Details: You are the employee of a big, worldwide working Zoo Management Company. Your company is responsible for the Zoo management. Your boss thinks it would be a great idea to store all data for each Zoo in a brand new self-developed ZOO Management System. Up to now, the ZOO management company has maps of each ZOO available. Your boss knows that you took a course in introduction on an ERP system, so he asks you if you could help designing such a system. Each ZOO must have the same organizational structure, which should look like this: Each Zoo has a Zoo-Address. Each Zoo has many visitors (Visitor Ticket Process (VTP). Many Zoo-Attractions belong to a Zoo. Module 1: Entity Relationship Diagram Design a ER (entity-relationship) diagram for your ZOO Management System. Use the information provided below with the entities and its attributes. Put the entities in the correct relationship to each other (organizational structure). Module 2: DB Implem...
1 comment
Read more

Human Physiology by Stuart Ira Fox [PDF] (12th edition) free download

By
21 comments
Read more

Student Registration System Web Project using HTML, CSS & PHP

By
Student Registry System In this task, you’re to further develop the student registry you started on lab-task. The solution is based the on the use of HTML5, stylesheets, and PHP, and will use a database for storage of information, MySQL on (school website) is used for this. Information of students is saved in the table student, ID is primary key and is set In addition to this, you need a table named class where id a is the primary key and is set up with AUTOINCREMENT, other columns and data types in accordance with the figure. The property class in the student table needs to be a foreign key that refers to the ID column in the class table. In MySQL you need to use tables of the type INNODB with support for foreign keys, reference integrity shall remain. The task: Write a class with the name StudentRegister (means Student registry), the class should use PDO and only prepared statements/questions. The class shall implement the interface StudentInterface, and use the two classes, Student,...
Post a Comment
Read more