CC5 - Chapter 2 Notes

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 3

2.

1 Conceptual and Physical Models

Conceptual model
- a model that specifies the needs of a business
- is called an “Entity Relationship Model” (ERD)
- collects and focuses only important data
- Describes the information needs of the business
- facilitates discussion
- prevents mistakes and misunderstandings
- helps in the formation of documenting the system
- makes a sound basis for physical model implementation
- documents the process of the business
- abides and considers the rules and regulations of the industry

Entity Relationship Diagram


Entity
EMPLOY
EE Assigned to
DEPARTM
------------------
Responsible
ENT

--- for

Relationship

Physical Model
- model that describes how a system should be implemented using a DBMS system
- the actual implementation of the database
2.2 Entities, Instance, Attributes, and Identifiers

Entities
- a noun
- a single person, object, or place
- where data is stored

Attributes
- gives more specific information about an entity
- properties
- helps differentiate two entities
- each attribute has only a single value. It can be a number, string, data, image, etc (data
types).
- values can be volatile (constantly changing) or nonvolatile
Mandatory Attributes - attributes that must contain a value
Optional Attributes - attributes may contain a value or be left null

ORDE
R
Product
name Attribu
Price
Data of tes
Purchase

Unique Identifiers
- a mark that is unique and is used to distinguish one entity from another
- either a single or a combination of multiple attributes

E.g.
Nike - for sports equipment
D&D - for musical instruments
Uratex - for bed foams

Instances
- single occurrence of an entity
- are specific examples of an entity
- an entity could only have 1 or more instance

Entities Instances

PERSON Mahatma Gandhi, Michael Jordan

PRODUCT Huawei Nova IT, ASUS G15

JOB Engineer, Lawyer


2.3 Entity Relationship Modeling and ERDs

Entity relationship diagram (ERD)


- tool that can be used to represent data requirements of a business regardless of the type
of database that is used
- a list of all entities and attributes and the relationships between entities
- provides background information regarding entity, data types, and constraints

Note: The model does not require a diagram, but a diagram is a helpful tool

Implementation-Free Model
- not dependent on the physical model
- does not change regardless of the type of database system
- can be used to implement different types of database system

Four goals of ER modeling


● Capture all required information
● Ensure that information appears only once
● Model no information that is deliverable from other information already modeled -
avoid data redundancy
● Location information in a predictable, logical space - organized, accessed, update
easily

You might also like