What is Data Modelling?

Data modeling is the process of creating a data model for the data to be stored in a Database. This data model is a
conceptual representation of

 Data objects
 The associations between different data objects
 The rules.

Data modeling helps in the visual representation of data and enforces business rules, regulatory compliances, and
government policies on the data. Data Models ensure consistency in naming conventions, default values,
semantics, security while ensuring quality of the data.

There are many kinds of data models. Some of the most common ones include:

 Record Based Logical Model

◦ Relational model
◦ Hierarchical database model
◦ Network model
 Object Based Logical Model
◦ Entity-relationship model
◦ Object-oriented database model
 The object-relational model (which combines the two that make up its name)

Record Based Logical Models

1: Relational model

The most common model, the relational model sorts data into tables, also known as relations, each of which
consists of columns and rows. Each column lists an attribute of the entity in question, such as price, zip code, or
birth date. Together, the attributes in a relation are called a domain. A particular attribute or combination of
attributes is chosen as a primary key that can be referred to in other tables, when it’s called a foreign key.

Each row, also called a tuple, includes data about a specific instance of the entity in question, such as a particular
employee.The model also accounts for the types of relationships between those tables, including one-to-one, one-
to-many, and many-to-many relationships. Here’s an example:
2: Hierarchical model

The hierarchical model organizes data into a tree-like structure, where each record has a single parent or root.
Sibling records are sorted in a particular order. That order is used as the physical order for storing the database.
This model is good for describing many real-world relationships.

This model was primarily used by IBM’s Information Management Systems in the 60s and 70s, but they are rarely
seen today due to certain operational inefficiencies.

3: Network model

The network model builds on the hierarchical model by allowing many-to-many relationships between linked
records, implying multiple parent records. Based on mathematical set theory, the model is constructed with sets of
related records. Each set consists of one owner or parent record and one or more member or child records. A
record can be a member or child in multiple sets, allowing this model to convey complex relationships. It was most
popular in the 70s

Object Based Logical Model

1: Entity-relationship model

This model captures the relationships between real-world entities much like the network model, but it isn’t as
directly tied to the physical structure of the database. Instead, it’s often used for designing a database
conceptually.
Here, the people, places, and things about which data points are stored are referred to as entities, each of which
has certain attributes that together make up their domain. The cardinality, or relationships between entities, are
mapped as well.

A common form of the ER diagram is the star schema, in which a central fact table connects to multiple
dimensional tables.

2: Object-oriented database model

This model defines a database as a collection of objects, or reusable software elements, with associated features
and methods. There are several kinds of object-oriented databases:

A multimedia database incorporates media, such as images, that could not be stored in a relational database.

A hypertext database allows any object to link to any other object. It’s useful for organizing lots of disparate data,
but it’s not ideal for numerical analysis.

The object-oriented database model is the best known post-relational database model, since it incorporates tables,
but isn’t limited to tables. Such models are also known as hybrid database models.
Object-relational model

This hybrid database model combines the simplicity of the relational model with some of the advanced
functionality of the object-oriented database model. In essence, it allows designers to incorporate objects into the
familiar table structure.

Why use Data Model?

The primary goal of using data model are:

 Ensures that all data objects required by the database are accurately represented. Omission of data will
lead to creation of faulty reports and produce incorrect results.
 A data model helps design the database at the conceptual, physical and logical levels.
 Data Model structure helps to define the relational tables, primary and foreign keys and stored
procedures.
 It provides a clear picture of the base data and can be used by database developers to create a physical
database.
 It is also helpful to identify missing and redundant data.
 Though the initial creation of data model is labor and time consuming, in the long run, it makes your IT
infrastructure upgrade and maintenance cheaper and faster.

Types of Data Models

There are mainly three different types of data models:

1. Conceptual: This Data Model defines WHAT the system contains. This model is typically created by
Business stakeholders and Data Architects. The purpose is to organize, scope and define business
concepts and rules.
2. Logical: Defines HOW the system should be implemented regardless of the DBMS. This model is typically
created by Data Architects and Business Analysts. The purpose is to developed technical map of rules and
data structures.
3. Physical: This Data Model describes HOW the system will be implemented using a specific DBMS system.
This model is typically created by DBA and developers. The purpose is actual implementation of the
database.
Conceptual Model

The main aim of this model is to establish the entities, their attributes, and their relationships. In this Data
modeling level, there is hardly any detail available of the actual Database structure.

The 3 basic tenants of Data Model are

Entity: A real-world thing

Attribute: Characteristics or properties of an entity

Relationship: Dependency or association between two entities

For example:

 Customer and Product are two entities. Customer number and name are attributes of the Customer entity
 Product name and price are attributes of product entity
 Sale is the relationship between the customer and product
Characteristics of a conceptual data model

 Offers Organization-wide coverage of the business concepts.

 This type of Data Models are designed and developed for a business audience.
 The conceptual model is developed independently of hardware specifications like data storage capacity,
location or software specifications like DBMS vendor and technology. The focus is to represent data as a
user will see it in the "real world."

Conceptual data models known as Domain models create a common vocabulary for all stakeholders by establishing
basic concepts and scope.

Logical Data Model

Logical data models add further information to the conceptual model elements. It defines the structure of the data
elements and set the relationships between them.

The advantage of the Logical data model is to provide a foundation to form the base for the Physical model.
However, the modeling structure remains generic.

At this Data Modeling level, no primary or secondary key is defined. At this Data modeling level, you need to verify
and adjust the connector details that were set earlier for relationships.

Characteristics of a Logical data model

 Describes data needs for a single project but could integrate with other logical data models based on the
scope of the project.
 Designed and developed independently from the DBMS.
 Data attributes will have datatypes with exact precisions and length.
 Normalization processes to the model is applied typically till 3NF.
Physical Data Model

A Physical Data Model describes the database specific implementation of the data model. It offers an abstraction
of the database and helps generate schema. This is because of the richness of meta-data offered by a Physical Data
Model.

This type of Data model also helps to visualize database structure. It helps to model database columns keys,
constraints, indexes, triggers, and other RDBMS features.

Characteristics of a physical data model:

 The physical data model describes data need for a single project or application though it maybe
integrated with other physical data models based on project scope.
 Data Model contains relationships between tables that which addresses cardinality and nullability of the
relationships.
 Developed for a specific version of a DBMS, location, data storage or technology to be used in the project.
 Columns should have exact datatypes, lengths assigned and default values.
 Primary and Foreign keys, views, indexes, access profiles, and authorizations, etc. are defined.

Advantages and Disadvantages of Data Model:

Advantages of Data model:

 The main goal of a designing data model is to make certain that data objects offered by the functional
team are represented accurately.
 The data model should be detailed enough to be used for building the physical database.
 The information in the data model can be used for defining the relationship between tables, primary and
foreign keys, and stored procedures.
 Data Model helps business to communicate the within and across organizations.
 Data model helps to documents data mappings in ETL process
 Help to recognize correct sources of data to populate the model

Disadvantages of Data model:

 To developer Data model one should know physical data stored characteristics.
 This is a navigational system produces complex application development, management. Thus, it requires a
knowledge of the biographical truth.
 Even smaller change made in structure require modification in the entire application.
 There is no set data manipulation language in DBMS.
Conclusion

 Data modeling is the process of developing data model for the data to be stored in a Database.
 Data Models ensure consistency in naming conventions, default values, semantics, security while ensuring
quality of the data.
 Data Model structure helps to define the relational tables, primary and foreign keys and stored
procedures.
 There are three types of conceptual, logical, and physical.
 The main aim of conceptual model is to establish the entities, their attributes, and their relationships.
 Logical data model defines the structure of the data elements and set the relationships between them.
 A Physical Data Model describes the database specific implementation of the data model.
 The main goal of a designing data model is to make certain that data objects offered by the functional
team are represented accurately.
 The biggest drawback is that even smaller change made in structure require modification in the entire
application.

Types of Database Design

Conceptual database design This design is implemented using a semantic data model, for example for creating
a design for an organization database we can use and we do use the ER-Data model.

Logical Database design This design is performed using a data model for which we have a DBMS available and
we are planning to run our database system that DBMS.

Physical Database Design: The Logical design created using a specific data model and created after the
analysis of the organization, it needs to be implemented in a physical DBMS software so the Physical database
design is performed and the design created so far in the logical form are implemented on that very DBMS.

By separating the three design levels we get the benefit of abstraction on one hand whereas on the other
hand we can create our logical and conceptual designs using better design tools, which would have not been
possible if we are using the same design-tool for al the three levels. Moreover if in future there is a need to
make a change in the physical implementation of the data we will have to make no changes in the logical or
conceptual level of the database design , rather the change can be achieved by only using the existin