Scribd
Upload
37 views15 pages

Databases Systems PowerPoint

- Data modeling is the first step in database design and involves creating a representation of real-world data structures and relationships to help understand a problem domain. - A data model is a blueprint that defines entities, attributes, relationships, and constraints based on business rules to build a database meeting user needs. - Business rules are organizational policies that influence database design and ensure consistent interpretation of data.

Uploaded by

codingsteez4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
37 views15 pages

Databases Systems PowerPoint

- Data modeling is the first step in database design and involves creating a representation of real-world data structures and relationships to help understand a problem domain. - A data model is a blueprint that defines entities, attributes, relationships, and constraints based on business rules to build a database meeting user needs. - Business rules are organizational policies that influence database design and ensure consistent interpretation of data.

Uploaded by

codingsteez4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 15

WELCOME TO RICHFIELD

MODULE: DATABASE SYSTEMS 521

Compiled and Presented by NEED M.


Data Models

After studying this topic you should be able to:


• Explain what is data modelling and why data models are
important.
• Describe the basic data-modeling building blocks
• understand what business rules are and how they influence
database design.
• Understand how the major data models evolved.
• Understand how data models can be classified by level of
abstraction.
Data modelling and Data Models

• Data modelling, the first step in designing a database.


• Process of creating a specific data model for a determined problem
domain.
• A data model is a relatively simple representation, usually graphical,
of more complex real-world data structures.
• Help you understand the complexities of the real-world
environment.
• A data model represents data structures and their characteristics,
relations, constraints, transformations, and other constructs.
• Data model is in effect a “blueprint” containing all the instructions
to build a database that will meet all end-user requirements
The Importance of Data Models
• Facilitate interaction among the designer, the applications
programmer, and the end user.
• Foster improved understanding of the organization for which the
database design is developed.
• Data are viewed in different ways by different people.
• When a good database blueprint is available, it does not matter that
an applications programmer’s view of the data is different from that
of the manager and/or the end user.
Data Models Building Blocks
• The basic building blocks of all data models are entities,
attributes, relationships, and constraints.
• An entity is anything (a person, a place, a thing, or an event)
about which data are to be collected and stored.
• entities are “distinguishable”—that is, each entity occurrence is
unique and distinct.
• a CUSTOMER entity : as John Smith, Pedro Dinamita, Tom
Strickland, etc.
Data Models Building Blocks
• An attribute is a characteristic of an entity.
• a CUSTOMER :
• customer last name,
• customer first name,
• customer phone,
• customer address,
• and customer credit limit.
Attributes are the equivalent of fields in file systems.
Data Models Building Blocks Cont.

• A relationship describes an association among entities.


• Customers and agents that can be described as follows:
• an agent can serve many customers, and
• each customer may be served by one agent.
• Data models use three types of relationships:
• one-to-many 1:M
• many-to-many M:M / M:N
• and one-to-one. 1:1
Examples of Relationships

• One-to-many (1:M or 1..*) relationship.


• PAINTER paints PAINTING”
• CUSTOMER generates INVOICE”
• Many-to-many (M:N or *..*) relationship.
• EMPLOYEE learns SKILL.
• STUDENT takes CLASS.
• One-to-one (1:1 or 1..1) relationship
• EMPLOYEE manages STORE
• EMPLOYEE supervises DEPARTMENT
Business Rules
• A business rule is a brief, precise, and unambiguous description
of a policy, procedure, or principle within a specific organization.
• Help to create and enforce actions within that organization’s
environment.
• Business rules are used to define entities, attributes,
relationships, and constraints.
• “an agent can serve many customers, and each customer can be
served by only one agent,”
• Business rules must be easy to understand and widely
disseminated, to ensure that every person in the organization
shares a common interpretation of the rules.
Examples of Business Rules

 Examples of business rules are as follows:


1. A customer may generate many invoices.
2. An invoice is generated by only one customer.
3. A training session cannot be scheduled for fewer than 10
employees or for more than 30 employees.
• Note that those business rules establish entities,
relationships, and constraints.
Discovering Business Rules

• The main sources of business rules are company managers,


policy makers, department managers, and written
documentation such as a company’s procedures,
standards, and operations manuals.
• Direct interviews with end users.
Discovering Business Rules

• The main sources of business rules are company managers,


policy makers, department managers, and written
documentation such as a company’s procedures,
standards, and operations manuals.
• Direct interviews with end users.
Importance of Discovering Business Rules

 They help to standardize the company’s view of data.


 They can be a communications tool between users and
designers.
 They allow the designer to understand the nature, role, and
scope of the data.
 They allow the designer to understand business processes.
 They allow the designer to develop appropriate relationship
participation rules and constraints and to create an accurate
data model.
Naming Conventions

• During the translation of business rules to data model


components, you identify entities, attributes, relationships,
and constraints.
• This identification process includes naming the object in a
way that makes the object unique and distinguishable from
other objects in the problem domain.
• Entity names should be descriptive of the objects in the
business environment, and use terminology that is familiar
to the users.
Naming Conventions Cont.

• An attribute name should also be descriptive of the data represented


by that attribute.
• It is also a good practice

• to prefix the name of an attribute with the name of the entity (or an
abbreviation of the entity name) in which it occurs.
• For example, in the CUSTOMER entity, the customer’s credit limit may
be called CUS_CREDIT_LIMIT.
• The CUS indicates that the attribute is descriptive of the CUSTOMER
entity, while CREDIT_LIMIT makes it easy to recognize the data that
will be contained in the attribute.

You might also like