Conceptual Data Model Flashcards
Week 2.2 (21 cards)
6 steps of the database system development lifestyle
- planning
- requirements collection and analysis
- database design
- implementation
- testing and validation
- deployment and maintenance
why is the design stage important
- important to ensure data integrity, efficiency and scalability
- emphasise of what data is needed
what 3 database designs are covered in the design stage
- conceptual
- logical
- physical
describe the conceptual data model
- high level data model that outlines the system’s data requirements
- to ensure we get precise understanding of the nature of the data and how it is used
- as a model for communication that is nontechnical and free from ambiguities
what are used to create the conceptual data model
entity-relationship (E-R) diagrams
3 ways of drawing an E-R diagram
- UML
- Chen’s notation
- Crow’s foot
describe UML ER diagrams
- rectangle represents an entity
- top word = name of an entity
- bottom word = attribute
- line and arrow = relationship
- number = possible association of one instance of entity to the other associated entity
describe chen’s notation ERD
- rectangle = entity
- oval = attribute of an entity
- diamond and lines = relationship
- number = possible association of one instance of entity to the other associated entity
describe crow’s foot ERD
- rectangle represents an entity
- top word = name of an entity
- bottom word = attribute
- line = relationship
- crow’s foot = possible association of one instance of entity to the other associated entity
describe entities
- group of objects with same properties, having an independent existence
- each instance of an entity is uniquely identified using the primary key attribute
whats an entity occurence/ object
each uniquely identifiable object of an entity is called an entity occurrence or an object
define strong entity
whose existence is not dependent on another
define weak entity
depends upon another entity
describe attributes
- property of an entity or relationship
- simple or composite
- associated with the domain
how to model attributes
- {PK} = primary key
- {PPK} = partial primary key
- attributes associated with a relationship is shown as a rectangle with a dashed line with the relationship
describe relationships
- set of meaningful associations between one or more participating entities
- number of participants in a relationship = degree
model relationships
what is constraint also known as
multiplicity
what are the 2 forms of multiplicity
- cardinality
- participation
define cardinality
maximum number of possible relationships for an entity participating in a given relationship
define participation
whether all or only some instances of an entity participated in a relationship