Data Models

Chapter 6-information management

What is Data Modeling? | IBM

Learning Objectives
▪ Data Modeling, Why models are important.
▪ Basic data-modeling building blocks.
▪ What business rules are and how they influence database design.
▪ How the major data models evolved.
▪ Emerging alternative data models and the need they fulfill.
▪ How data models can be classified by their level of abstraction.
 Data
Modeling and
Data Models
Chapter 6-information management

What is Data Modeling? | IBM

Data Modeling and
Data Models
Data Modeling and Data Models
▪ Data Modeling: Interactive and progressive process of creating
specific data model for a determined problem domain/field.
▪ Data Models: Simple representations of complex real-world data
structures
• -useful for supporting a specific problem domain
• Model: Abstraction of a real-world object or event.
Data Modeling and Data Models
▪Data Modeling: Interactive and progressive process of
creating specific data model for a determined problem
domain.
✓Data modeling is the process of creating a visual representation of
either a whole information system or parts of it to communicate
connections between data points and structures. The goal is to
illustrate the types of data used and stored within the system, the
relationships among these data types, the ways the data can be
grouped and organized and its formats and attributes.
Data Modeling and Data Models
▪ Data Models: Simple representations of complex real-world data
structures
✓-useful for supporting a specific problem domain
✓Data models are built around business needs. Rules and requirements are
defined upfront/frank, honest through feedback from business stakeholders
so they can be incorporated into the design of a new system or adapted in
the iteration of an existing one.
The Important of Data Models.
• Model: Abstraction of a real-world object or event.
✓A model can come in many shapes, sizes, and styles. It
is important to emphasize that a model is not the real
world but merely a human construct to help us better
understand real world systems. In general all models
have an information input, an information processor, and
an output of expected results.
 Types of
data models
Chapter 6-information management

What is Data Modeling? | IBM

Types of data models
▪ Like any design process, database and information system
design begins at a high level of abstraction and becomes
increasingly more concrete and specific.
▪ Data models can generally be divided into three categories,
which vary according to their degree of abstraction. The
process will start with a conceptual model, progress to a
logical model and conclude with a physical model.
Types of data models
▪ Conceptual data models. They are also referred to as domain models
and offer a big-picture view of what the system will contain, how it
will be organized, and which business rules are involved.
▪ Conceptual models are usually created as part of the process of
gathering initial project requirements. Typically, they include entity
classes (defining the types of things that are important for the
business to represent in the data model), their characteristics and
constraints, the relationships between them and relevant security and
data integrity requirements. Any notation is typically simple.
Conceptual Model
Types of data models
• Logical data models. They are less abstract and provide greater
detail about the concepts and relationships in the domain under
consideration. One of several formal data modeling notation
systems is followed.
• These indicate data attributes, such as data types and their
corresponding lengths, and show the relationships among
entities.
• Logical data models don’t specify any technical system
requirements.
Logical Model
Logical Model

Logical ERD is a detailed version of a Conceptual ERD. A

logical ER model is developed to enrich a conceptual
model by defining explicitly the columns in each entity
and introducing operational and transactional entities.
Although a logical data model is still independent of the
actual database system in which the database will be
created, you can still consider that if it affects the
design.
Types of data models
• Physical data models. They provide a schema for how the data
will be physically stored within a database. As such, they’re the
least abstract of all. They offer a finalized design that can be
implemented as a relational database, including associative tables
that illustrate the relationships among entities as well as the
primary keys and foreign keys that will be used to maintain those
relationships. Physical data models can include database
management system (DBMS)-specific properties, including
performance tuning.
Physical Model
 Importance
And Benefits
of Data
Modeling
Chapter 6-Data Model-Information
Management

What is Data Modeling and Why Do You Need It? (dasca.org)

#1 Higher Quality Applications
• Data modeling is an important stage in any software
project. Without it, it's impossible to get a clear
picture of how your database should look and how it
will be used.
• It is a way to determine the relationships between
various pieces of information. This will help you
decide what kind of queries can be run against this
data.
#1 Higher Quality Applications

• Data modeling has the obvious advantage of

producing higher-quality applications that are low
maintenance and are less susceptible to crashes.
#2 Reduced Cost and Time in
Application Development
• Data modeling can significantly impact how much and how quickly
you can build an application. You will have to gather requirements
from your users and code the database structure manually if you
don't have a data model.
• It is easier to add tables and views to a data model if you already
have one. If you build an app and need to add or modify a table, you
can add it to the data model and update your existing application.
• Your team will need to update the database and code if you don't
have data models. If you have to make multiple changes to the
entire application, this can be time-consuming and costly.
#3 Early Detection of Data Issues &
Errors
• Often, errors and data issues are not detected until the
process progresses. A user may go to make a purchase but
get an error message stating "bad data". This is a sign that the
data was not good from the start. It is possible to test it in a
laboratory or test server. However, errors are not discovered
until production runs.
• You have more time to fix a problem before it affects your
users.
#3 Early Detection of Data Issues &
Errors

• Many companies use data modeling because it provides a

detailed view of your users' interactions with your business,
down to the details such as which fields they access and how
frequently they use them. This level of detail provides crucial
information that can help you identify problems and make
the right corrections. Regular Data Model Audits will ensure
that your data model is optimized for users and their goals.
#4 Faster Application Performance
• Data modeling is more than just about making or saving
money. While that's certainly important, the true value of data
modeling lies in making your application run more efficiently
and faster.
• Data modeling is crucial to an application's performance
because it gives a high-level plan of how the application
should deal with data. Developers know what data they can
expect, how they will use it, and where each piece of
information will be kept in their memory. They can therefore
write simple functions that retrieve data quickly.
#4 Faster Application Performance
• This is a very different approach to using tables to
store data in an unorganized way. Developers would
need to write complex SQL queries to find the
information they are looking for if unstructured
tables were used. Structured tables will allow the
database engine to locate the information, and
developers won't worry about it.
• What is the result? Applications can handle large
data volumes more efficiently without slowing down.
#5 Better Documentation for Long-
Term Maintenance

• Data models are used to describe business processes

and their interrelationships. It is easier to understand
and maintain long-term business processes if all data
related to them are in one place.
#5 Better Documentation for Long-
Term Maintenance
• Data modeling is also useful in documenting
business requirements and designing the
application. A single source can help communicate
the requirements and design better. Identifying and
implementing changes is easy due to new
requirements, enhancements, or bug fixes.
• Data modeling is an essential part of software
development. It requires expertise and effort, but the
rewards are well worth it.
 Data Model
Basic
Building
Blocks
Chapter 6-Data Model-Information
Management

What is Data Modeling and Why Do You Need It? (dasca.org)

Data Model Basic Building Blocks
• The building blocks in the data model are as follows:
• Entity − Unique and distinct object used to collect and
store data
• Entityis anything such as person, place, thing, or event about
which data to be collected and stored.
• Entity maybe physical object such as costumer or products
• Entity may also be an abstraction such flight route or musical
concerts.
Data Model Basic Building Blocks

• Attribute: Characteristics of an entity.

• Example:
• Last Name, First Name, Costumer Phone Number,
Address, and Costumer Credit Limit.
• The attributes is the equivalent of fields in file system.
Data Model Basic Building Blocks
• Relationship − A relationship describes an association among
entities.
• One-to-Many (1:M)
• Many-to-Many (M:M or M:N)
• One-to-One (1:1)
• Example:
There is a relationship between costumer and agent, that may be describe as
an agent can serve many costumer and each costumer may be served by one
agent.
Data Model Basic Building Blocks

• Constraints − A constraint is a restriction placed on

the data. It is helpful to ensure data integrity
Example:
The student can take a maximum of two books
from the library.
 Business
Rules
Chapter 6-Data Model-Information
Management

What is Data Modeling and Why Do You Need It? (dasca.org)

What is a Business Rules
• A business rules is a statement that imposes some form
of constraints on a specific aspects of the database such
as the elements within the fields specification for a
particular field or the characteristics of a give
relationship. You base a business rule on the weight
organization perceives the uses of each data which you
determine from the manner in which the organization
functions or conducts its business
Business Rules

• Brief,precise, and unambiguous description of a

policy, procedures, or principle.
• Enable defining the basic building blocks
• Describe main and distinguishing characteristics of
the data.
Business Rules
• Example:
• A students can take a maximum of two books from the library, is an
example of business rule and is apply the constraints on the students
database.
• Students cannot have more than two instruments checked-out at the
same time
• A ship date cannot be prior to an order date to any given order
• Department offer courses
• Courses generates class
• Professor teaches a class
 Discovering
Business
Rules
Chapter 6-Data Model-Information
Management

What is Data Modeling and Why Do You Need It? (dasca.org)

Sources of business rules

• Company Managers
• Policy Makers
• Department Managers
• Written Documentation
• Direct Interview with the users
Reasons for identifying and
documenting business rules
• Help standardize company’s view of data
• Communications tool between users and designers
• Allow designer to;
• Understand the nature, role, scope of data, and business
processes
• Develop appropriate relationship rules and constraints
• Create an accurate data model
 Translating
Business
Rules into
Data Models
Components
Chapter 6-Data Model-Information
Management

What is Data Modeling and Why Do You Need It? (dasca.org)

Translating Business Rules into Data
Models Components
• Nouns translate into Entities
• Verbs translate into relationships among entities
• Relationship are Directional
• Questions to identify the relationship type
• How many instances of B are related to one instance A?
• How many instances A related to once instances of B?
Translating Business Rules into Data
Models Components
• Naming Conventions/rules
• Entity Names- Required to:
• Be descriptive of the objects in the business environment
• Use terminology that is familiar to the users
• Attribute name- Required to be descriptive of the data represented by the
attribute
• Proper naming:
• Facilitates communication between parties
• Promotes Self-documentation
Standard
Database
Concepts
Chapter 6-Data Model-Information
Management
Database Schema
Standard Database Concepts
• Schema:
• Conceptual organization of the entire database as
viewed by the database administration.
• database schema defines how data is organized within a
relational database; this is inclusive of logical constraints
such as, table names, fields, data types, and the
relationships between these entities.
Standard Database Concepts
• Schema:
• Schemas commonly use visual representations to
communicate the architecture of the database, becoming
the foundation for an organization’s data management
discipline. This process of database schema design is also
known as data modeling.
• A database schema is considered the “blueprint” of a
database which describes how the data may relate to other
tables or other data models. However, the schema does
not actually contain data.
Standard Database Concepts

• Data Manipulation Language(DML)

• Environment in which data can be managed
and is use to work with the data in the
database.
Standard Database Concepts
• Data Manipulation Language(DML)
• Example:
• Insert, update, and delete statement from
the sql.
• Its
usage DML statement is use to insert,
update or delete the record.
Standard Database Concepts
• Data Definition Language (DDL)
• Enables the database administrator to
define the schema components.
• DDL statement are used to create a
database schema constraints, user, tables
etc.
Standard Database Concepts

• Data Definition Language (DDL)

• Examples:
• Create, drop, rename, and alter
Relational
Model
Chapter 6-Data Model-Information
Management
Relational Model
Relational Model
• Produced an automatic transmission database that
replaced standard transmission databases.
• Base on a relation
• Relation or Table: Matrix composed of intersecting tuple and attribute
• Tuple: Rows
• Attribute: Columns
• Describes a precise set of data manipulations
constructs
Relational Model

• In this model, data is organized in two-

dimensional tables and the relationship is
maintained by strong a common field.
Relational Model
Relational Model
Relational
Database
Management
System
Chapter 6-Data Model-Information
Management
Relational Database Management
System
• Performs basic functions provide by the
hierarchical and network DBMS systems
• Makes the relational data model easier to
understand and implement
• Hides the complexities of the relational model
from the user
Relational Database Management
System

• Example Diagram
SQL-Based
Relational
Database
Application
Chapter 6-Data Model-Information
Management
SQL-Based Relational Database
Application
• End-used interface
• Allows end user to interact with the data
• Collection of tables stored in the database
• Each table is independent from another
• Rows in different tables are related based on common values in
common attributes
• SQL Engine
• Executes all queries
Entity
Relationship
Model
Chapter 6-Data Model-Information
Management
Entity Relationship Model
• Graphical representation of entities and their
relationship in a database structure
• Entity Relationship Diagram (ERD)
• Uses graphic representations to model database components
• Entity Instance or Entity Occurrence
• Rows in the relational table
• Connectivity
• Term used to label the relationship types
Entity Relationship Model
• In this database model, relationships are
created by dividing object of interest into
entity and its characteristics into attributes.
• Different entities are related using
relationships.
• E-R model are defined to represent the relationship
into pictorial form to make it easier for different
stakeholder to understand.
Entity Relationship Model
• Example
Entity Relationship Model
• Example
Entity Relationship Model
Entity Relationship Model
• The ER Model Notation/representation
Emerging
Data Models
Chapter 6-Data Model-Information
Management
Big Data
• By helping companies uncover hidden patterns and
trends, big data is now used in nearly every industry to plan
future products, services and more. As of 2022, in fact,
approximately 97 percent of businesses are investing in big
data’s growing power.
• At its best, though, big data grounds and enhances human
intuition.
• These 3 companies are using big data to shape industries
from marketing to cybersecurity and much more.

23 Big Data Examples & Applications | Built In

Big Data Example:

Location: San Francisco, California

As a rideshare company, Uber monitors its data in order

to predict spikes in demand and variations in driver
availability. That information allows the company to set
the proper pricing of rides and provide incentives to
drivers so the necessary number of vehicles are available
to keep up with demand. Data analysis also forms the
basis of Uber’s estimated times of arrival predictions,
which goes a long way toward fulfilling customer
satisfaction.
23 Big Data Examples & Applications | Built In
Big Data Example:
Location: Los Gatos, California
The premise of Netflix’s first original TV show — the David Fincher-directed
political thriller House of Cards — had its roots in big data. Netflix
invested $100 million in the first two seasons of the show, which premiered
in 2013, because consumers who watched House of Cards also watched
movies directed by David Fincher and starring Kevin Spacey. Executives
correctly predicted that a series combining all three would be a hit.

Today, big data impacts not only which series Netflix invests in, but how
those series are presented to subscribers. Viewing histories, including the
points at which users hit pause in any given show, reportedly influence
everything from the thumbnails that appear on their homepages to the
contents of the “Popular on Netflix” section
23 Big Data Examples & Applications | Built In
Big Data Example:

Location: Seattle, Washington

Like Facebook and Google, Amazon got sucked into
the adtech business by the sheer amount of consumer data at
its disposal. Since its founding in 1994, the company has
collected reams of information on what millions of people buy,
where those purchases are delivered and which credit cards
they use. In recent years, Amazon has begun offering more and
more companies — including marketing companies — access to
its self-service ad portal, where they can buy ad campaigns and
target them to ultra-specific demographics, including past
purchasers.
23 Big Data Examples & Applications | Built In
Big Data Challenges

• Volume does not allow the usage of

conventional structure
• Expensive
Big Data Challenges
• OLAP tools proved inconsistent dealing
with unstructured data.
• Easy OLAP Definition
• OLAP (Online Analytical Processing) is the technology behind
many Business Intelligence (BI) applications. OLAP is a powerful
technology for data discovery, including capabilities for limitless
report viewing, complex analytical calculations, and predictive
“what if” scenario (budget, forecast) planning.
Thank you!
EMMANUEL S. MOLINA-Instructor