Unit3 Data Modeling New PDF

Unit 3 - Data Modeling
Pratian Technologies (India) Pvt. Ltd.

www.pratian.com
Enterprise Model
In Enterprise data modelling
Review current systems Analyze the nature of business areas to be supported Describe the data needed at a very high level of abstraction Plan one or more database development projects
Copyright 2012 Pratian Technologies www.pratian.com
Systems Development Life Cycle

Project Identification and Selection Project Project Initiation Initiation and and Planning Planning
Purpose state business situation and solution Deliverable request for analysis
Analysis
Logical Design Physical Design
Database activity conceptual data modeling
Implementation Maintenance

Project Identification and Selection Project Initiation and Planning
Purpose thorough analysis Deliverable functional system specifications
Analysis Analysis
Database activity conceptual data modeling

Project Identification and Selection Project Initiation and Planning Analysis
Purpose information requirements structure Deliverable detailed design specifications
Logical Logical Design Design Physical Design
Database activity logical database design

Purpose develop technology specs Deliverable program/data structures, technology purchases, organization redesigns
Logical Design Physical Physical Design Design
Database activity physical database design

Purpose programming, testing, training, installation, documenting Deliverable operational programs, documentation, training materials
Database activity database implementation
Implementation Implementation Maintenance

Purpose monitor, repair, enhance Deliverable periodic audits
Database activity database maintenance
Implementation Maintenance Maintenance
In short Database Design
Mini-World View Requirements Collection and Analysis Conceptual Design Data Model Mapping Physical Design
Business rule
A statement that defines or constrains some aspect of the business. It is intended to assert business structure or to control or influence the behavior of the business. Ex: A preferred customer qualifies for a 10% discount, unless he has an overdue account balance.
Entity Relationship Modelling

Entity Relationship (ER) modelling is a design tool is a graphical representation of the database system provides a high-level conceptual data model supports the users perception of the data is DBMS and hardware independent has many variants is composed of entities, attributes, and relationships
The Entity Relationship Model

Customer_name Customer_addr Customer_id accountnumber balance
Customer
Depositor
Account
Rectangles represent entity sets Ellipses represent attributes Diamonds represent sets of relationships among a member from each of several entity sets Lines links attributes to entity sets and entity sets to relationships
Components of an E R Model
Entities Attributes Entity Identifiers Instances of Entities Attribute Domains
Entities
Definition
A person, place, object, event, or concept in the user environment about which the organization wishes to maintain data
Entity Type Vs Entity Instances

An Entity Type is a collection of entities that share common properties or characteristics. Ex of Entity Type
Person EMPLOYEE, STUDENT, PATIENT Place STORE, WAREHOUSE, HOSPITAL Object MACHINE, BUILDING, VEHICLE Event SALE, REGISTRATION, RENEWAL Concept ACCOUNT, COURSE, WORK CENTER
An Entity Instance is a single occurrence of an Entity Type
Types of Attributes
Simple Attribute / Atomic Attribute
Ex: Age, Salary, Sex
Composite Attribute
Ex : Address, Full Name
Types of Attributes contd

Single Valued Attribute
Ex: Gender

Multi Valued Attribute
Ex: Hobby, Educational Qualification, Skill empNum 123 333 679 empPhone 233-9876 233-1231 233-1231 BA, BSc, PhD BSc, MSc empDegree

Derived Attribute
Ex: Age
E R Diagram Conventions
First name Last name
name class date _of_birth
hobby
STUDENT
age
address street state
roll_number
city
pin
Entities Rectangular Box Attribute Ellipse Entity Name Uppercase Attribute Name Lowercase Primary Key - Underlined
Single Line Simple /single valued Dotted Line Derived Double Line Multivalued Components of composite attribute are shown as ellipses emanating from the composite attributes
Key Attributes
Key is an attribute, or a minimal set of attributes, that uniquely identify entities in an entity set.
Composite Identifier
An identifier that consists of a composite attribute Ex: Entity FLIGHT with composite identifier flightID FlightID has component attributes flightno and date
flightNo FLIGHT flightID date
Non-key Attributes
Non-key attributes are attributes that are not part of a key. Generally, most attributes are simply descriptive, and fall into this category. Consider attributes for first name, last name, birth date; usually these attributes are non-key attributes.
Relationships
A Relationship is an association between entities Relationship instance is an association between entity instances where each relationship instance includes exactly one entity from each participating entity type
PUBLISHER
publishes
BOOK
Degree of a relationship
Unary A unary relationship exists when an association is maintained within a single entity
EMPLOYEE
manages
Binary Relationship
A binary relationship exists when two entities are associated
PUBLISHER
publishes
BOOK
Ternary Relationship
A ternary relationship exists when there are 3 entities associated TEACHER
SUBJECT
teaches
STUDENT
Quaternary relationship
A quaternary relationship exists when there are four entities associated. TEACHER
STUDENT
studies
COURSE_ MATERIAL
SUBJECT
CONNECTIVITY
One to One
Ex: Manager manages 1 Department
One to Many
Ex: Department has many Employees
Many to Many
Ex: (No. of )Employee joins many Courses
CARDINALITY
Mapping Cardinality expresses the specific number of entity occurrences associated with one occurrence of the related entity DEPARTMENT 1 has N EMPLOYEE
(0,100) N
(1,1) N
EMPLOYEE
joins
COURSE
(0,2)
(0,10)
A cardinality constraint
Specifies the number of instance of one entity that can (or must) be associated with each instance of another entity
Minimum cardinality
The minimum number of instances of one entity that may be associated with each instance of another entity.
Maximum cardinality
The maximum number of instances of one entity that may be associated with each instance of another entity.
Participation Constraints
There are two ways an entity can participate in a relationship
Totally / Mandatory Partially / Optional
N EMPLOYEE (0,2) Mandatory joins
COURSE
(1,10) Optional
Employee
Assigned to
Project
Associative Entities
Its an Entity it has attributes AND its a Relationship it links entities together When should a relationship with attributes instead be an Associative Entity?
All relationships for the participating entity types are many relationships The associative entity could have meaning independent of the other entities The associative entity preferably has a unique identifier, and should also have other attributes The associative entity may participate in other relationships other than the entities of the associated relationship Ternary relationships should be converted to associative entities
Associative Entities
Associative entity involves a rectangle with a diamond inside. Note that the many-to-many cardinality symbols face toward the associative entity and not toward the other entities
Another situation for Associative entity

Many to Many relationships must be broken down to one to many relationships
AUTHOR
Submits work
PUBLISHER
AUTHORS TABLE AUTHORID A1 NAME SHOBHA DE CITY MUMBAI COUNTRY INDIA
PUBLISHER TABLE PUB_ID P1 NAME MCGRAW HILL CITY NEW YORK COUNTRY U.S.A
WORK TABLE AUTHORID A1 PUB_ID P1 TITLE SISTERS
pub_id authorid title
AUTHOR
N WORK
1 PUBLISHER
authorid
name pub_id city country city country name
A unary relationship with an attribute. This has a manyto-many relationship
Representing a bill-of -materials structure

An associative entity bill of materials structure
A ternary relationship with attributes
Ternary relationship as an associative entity
To summarise : Associative Entity

An entity type that associates the instances of one or more entity types Contains attributes that are peculiar to the relationship between those entity instances.
SUMMARY
Relationship symbols
Entity symbols
Attribute symbols
A special entity that is also a relationship
Relationship cardinalities specify how many of each entity type is allowed

Relationship degrees specify number of entity types involved
A Comparison of ER Modeling Symbols
ER Diagram: Two Most Commonly Used Notations
A quick check of our understanding.
Simple key attribute
The key is underlined
Composite key attribute
The key is composed of two subparts
Entity with a multivalued attribute (Skill) and derived attribute (Years_Employed) Whats wrong with this?
Derived
from date employed and current date
Multivalued:
an employee can have more than one skill
An attribute that is both multivalued and composite
This is an example of time-stamping
Note: a relationship can have attributes of its own

Mandatory cardinalities
Optional cardinalities with unary degree, one-to-one relationship
Entities can be related to one another in more than one way
Here,max cardinality constraint is 4
Question time
Please try to limit the questions to the topics discussed during the session. Thank you.

Unit3 Data Modeling New PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Unit3 Data Modeling New PDF

Caricato da

Copyright:

Formati disponibili

Unit 3 - Data Modeling

Pratian Technologies (India) Pvt. Ltd.

Copyright 2012 Pratian Technologies www.pratian.com

Systems Development Life Cycle

Logical Design Physical Design

Database activity conceptual data modeling

Copyright 2012 Pratian Technologies www.pratian.com

Systems Development Life Cycle

Purpose thorough analysis Deliverable functional system specifications

Logical Design Physical Design

Database activity conceptual data modeling

Copyright 2012 Pratian Technologies www.pratian.com

Systems Development Life Cycle

Purpose information requirements structure Deliverable detailed design specifications

Logical Logical Design Design Physical Design

Database activity logical database design

Copyright 2012 Pratian Technologies www.pratian.com

Systems Development Life Cycle

Logical Design Physical Physical Design Design

Database activity physical database design

Copyright 2012 Pratian Technologies www.pratian.com

Systems Development Life Cycle

Logical Design Physical Design

Database activity database implementation

Implementation Implementation Maintenance

Copyright 2012 Pratian Technologies www.pratian.com

Systems Development Life Cycle

Purpose monitor, repair, enhance Deliverable periodic audits

Logical Design Physical Design

Database activity database maintenance

Implementation Maintenance Maintenance

Copyright 2012 Pratian Technologies www.pratian.com

In short Database Design

Copyright 2012 Pratian Technologies www.pratian.com

Copyright 2012 Pratian Technologies www.pratian.com

Entity Relationship Modelling

Copyright 2012 Pratian Technologies www.pratian.com

The Entity Relationship Model

Copyright 2012 Pratian Technologies www.pratian.com

Copyright 2012 Pratian Technologies www.pratian.com

Entity Type Vs Entity Instances

An Entity Instance is a single occurrence of an Entity Type

Copyright 2012 Pratian Technologies www.pratian.com

Copyright 2012 Pratian Technologies www.pratian.com

Types of Attributes contd

Copyright 2012 Pratian Technologies www.pratian.com

Types of Attributes contd

Copyright 2012 Pratian Technologies www.pratian.com

Types of Attributes contd

Copyright 2012 Pratian Technologies www.pratian.com

name class date _of_birth

address street state

Copyright 2012 Pratian Technologies www.pratian.com

flightNo FLIGHT flightID date

Copyright 2012 Pratian Technologies www.pratian.com

Copyright 2012 Pratian Technologies www.pratian.com

Copyright 2012 Pratian Technologies www.pratian.com

Copyright 2012 Pratian Technologies www.pratian.com

Copyright 2012 Pratian Technologies www.pratian.com

Copyright 2012 Pratian Technologies www.pratian.com

Copyright 2012 Pratian Technologies www.pratian.com

Copyright 2012 Pratian Technologies www.pratian.com

N EMPLOYEE (0,2) Mandatory joins