Database system

1

The Relational Database Model

Eman Khalifeh

Institutional Affiliation

Course Title

9/9/2020

2

Description of the steps that you took to ensure that your design was normalized to the

desired level

The entity relationship diagram shown in the file attached is a conceptual representation

of the information captured in the databases and how different entities relates to each other. The

diagram helps the database designers to describe the overall design of the database concisely and

accurately. The database designer can easily transform the diagram into relation schema which

hasten the design process.

The diagram has entities which as attributes thus writing queries to deal with the

information in the databases will be an easy process. The entity relationship diagram was

designed to prevent anomalies associated with the database systems. These anomalies can affect

the data integrity as well as the security. The database design in our case has removed the

anomalies through the following ways. First, all records will be containing data; there will be no

null entry. Secondly, the database also has implemented accuracy regarding to the data by

ensuring consistency; the approach prevents the perceived data integrity issues. Thirdly, the

database will not allow the existence of the similar data in the entire database, which will avoid

the data redundancy in the database.

The database will be therefore free from any kind of anomalies that might arise when it

has been deployed to a working environment. The team will conduct vigorous test to ensure that

the anomalies are resolved in the database system. The entity-relationship diagram shows the

high-level interactions of entities and how they can work to achieve the goals. Dante’s aim of

implementing the system is to ensure that all its operations are smooth and secure. For instance,

the billing ought to record the amount paid by the customer, the employee who recorded the

information, and the service that the customer wants.

3

Therefore, the solution to the problem discussed is to design the most effective

conceptual diagram. The entity-relationship diagram simulates the entire system to identify

issues and see if it handles the case presented. Firstly, the billing issues associated with the

current systems emanate from deprived record keeping. It is not clear no what information that

the client wants to save from the client related to the bills. The conceptual diagram shows the

attributes that the user needs to store to process the billing effectively. Also, the relationship

between the billing helps the customer to link some given bills to individual customers.

Second, the issue of scheduling appointments is a problem to the organization, currents

the organization can schedule the appointment but cannot ensure that those appointments are

adhered to as the number of customers can change any time. This might render some of the

appointments ineffective. The conceptual diagram solves the issue by showing how the

customer, appointment, employee-related. Therefore, on the implementation of the actual

system, the customer will have known already the employee that will serve them.

Last, employees in the organization are a bit of a problem with handling the task with

Dante. Sometimes some employees do not find work while at the same time, some employees

have a huge amount of work. This problem is brought about by the inconsistencies present in the

system. With the diagram it possible to conceptualize how the incoming beauty task is

distributed across the employee of the organization. Also, the organization can plan to contract

the employees considering the available tasks.

4

ER-diagram.eddx