Scribd
Upload
13 views3 pages

26 09 24 - Database Basics Cont

The document outlines the three levels of database abstraction: user, conceptual schema, and internal schema, emphasizing that changes at one level should not affect others. It details the roles of database application developers, database administrators, and DBMS developers, along with a six-step database design process. Additionally, it explains entity-relationship diagrams, which model database design by representing entities and their attributes, including the importance of keys for unique identification.

Uploaded by

hrtusyuvitnojtdkga
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
13 views3 pages

26 09 24 - Database Basics Cont

The document outlines the three levels of database abstraction: user, conceptual schema, and internal schema, emphasizing that changes at one level should not affect others. It details the roles of database application developers, database administrators, and DBMS developers, along with a six-step database design process. Additionally, it explains entity-relationship diagrams, which model database design by representing entities and their attributes, including the importance of keys for unique identification.

Uploaded by

hrtusyuvitnojtdkga
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Csc1033 – 26/09

There a 3 levels of database abstraction, which separate users from the physical
database. It goes user, to conceptual schema, internal schema then physical
machine
The user level is the normal community view of the database
The conceptual schema describes what data is stored and their relationships

Logical changes to data shouldn’t require changes to the external schema or


rewriting the application program
Internal schema changes should not require changes to conceptual or external
schema

Roles
Database application developer: builds applications that interface with the
database
Database admin (DBAs): load, store and backup data as well as tweak the
database for performance
DBMS dev: develop more DBMS

Database design
Database design processes can be divided into 6 steps:
Requirement analysis:
what data is to be stored,
what apps must be built,
what ops are most frequently performed and are subject to performance
requirements

conceptual design:
high level of requirement analysis
logical design:
choose the DBMS
convert the conceptual design into a database schema in the BDMS
schema refinement:
analyse any relations
identify problems
refine the schema
physical design:
ensure the design meets performance requirements
build indexes including clustering tables
redesign parts of the schema
application and security design:
write application programs
identify which data can be accessed by which users
take action to ensure that access rules are enforced

E-R diagrams
entity-relationship diagrams are conceptual models of a database design used to
show data that’s stored and data constraint

entities represent sets of stored values called attributes (i.e. student has name,
age, id, phone, address)
entity sets are groups of the same entities all with the same set of attributes
(although they can have different values for the attributes)
the domain of an attribute is the acceptable values for an attribute

in an E-R diagram, entities are represented by a rectangle, with attributes are


represented by ovals
Keys are attributes that can identify a entities uniquely (i.e. a citizen’s key may
be their national insurance number because a name, birthday, etc may repeat
but the NIN wont)

You might also like