Database design documentation
Entity Relationship diagrams
Case Study: Vicki's Vinyl - Order LPs online
Any database system can be represented as a collection of one or more 'objects', 'things' or A concept in which data can be collected e.g. Customer, employee, appointments.
For example, Vicki’s Vinyl record shop will have customers, who have orders that relate to albums they have purchased.
Attributes can be used to describe individual properties of an entity.
Diagrams are used in the design stage to help plan how data will be organised and provide an overview of a system and how it might work. They are called A visual/graphical representation of the relationships that exist between different entities in a database management system..
An ER diagram for an ordering system could be modelled as follows:
This can be read as 'ONE customer can place MANY orders, and each order can have MANY products'.
