CC5 - Chapter 2 Notes
CC5 - Chapter 2 Notes
CC5 - Chapter 2 Notes
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
--- 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
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