relational database

CONCEPTUAL DATA MODELING

A data model is used by businesses to help govern the properties of the organization's data. This is important because a business rule represents business policies that should be enforced via the database. During the Requirements Structuring phase a data model captures the conceptual data requirements for a given system. However, in order to implement successful refinements to subsequent models, a commitment must be made to designing an effective conceptual data model.

The Conceptual Data Model represents a view of the overall structure of an organization's data. This view is independent of any other implementation considerations (i.e. database management systems, application software, etc.).

The objective of a conceptual data model is to illustrate the business rules governing the meaning and interrelationships among data. The process begins with creating a conceptual model of the current system being replaced (assuming a system exists). This is necessary for planning the conversion of current data into the new database system.

Data model in ARIS Express 1

Data model in ARIS Express 2

Netzwerkdatenbankmodell

This original model can also serve as a proxy for understanding the data requirements for the new system. After the initial conceptual model is completed, analysts create additional models which include the data requirements for the new system (which should have been uncovered during requirements determination).

Identify the entities and highest-level relationships

A data entity is anything real or abstract about which we want to store data. Entity types fall into five classes: roles, events, locations, tangible things or concepts, example employee, customers, billing etc. The entities that are involved in this data model for JoNasY are the employees, billing, appointment, and the customers.

Employees

JoNasY has four employees, one trainer, and one admins, one juice/snack bar help, and one maintenance /cleaning personal. The data stored on each employee includes employee ID number, name, address, city, state, and phone number. The employee number is uniquely assigned to each employee. Some employees perform multiple duties of

Billing

The table above represents the billing information of the customers that are associated with the company. The table reflect or exhibits their billing information which include the customer ID number which is unique to every customer without any duplications but the but the payment type which is the credit card column shows some duplication of data which can sometimes result in anomalies but can easily be resolved. One bill is assigned to one customer at a time. A bill can be outstanding, having nothing yet paid on it at all. One customer can make many payments, but a single payment is made by only 1 customer.

Customers

The relationship that exhibits between the customers is show in the table above. As you can see, each customer has the information of their address and phone number that separates them from one another. The table shows that a customer lives in this address, state, and zip-code which show a clear understanding that each customer has a relationship with the data that follows.

Appointments

A customer can schedule for many appointments or can schedule for one. Each appointment is scheduled with exactly 1 employee. This schedule are associated with specific time of the day and specific employees according to the table. An appointment must generate exactly 1 bill, a bill is generated by only 1 appointment.