FIT2094 Lecture Notes - Lecture 3: Social Security Number, Database, Relational Model
DATABASE DESIGN 1: CONCEPTUAL MODELLING
Requirements Definition:
•Identify and analyse user views!
•A ‘user view’ may be a report to be produced or a particular type of
transaction that should be supported!
•Corresponds to the external level of the ANSI/SPARC architecture!
•Output is a statement of specification which describes the user views’
particular requirements and constraints!
ER Modeling:
•ER (Entity-Relationship) model developed by Peter Chen in 1976 to aid
database design!
•May be used for conceptual (ERD)/logical design!
•ER diagrams give a visual indication of the design!
•Basic components:!
◦Entity!
◦Attribute!
◦Relationship!
Conceptual Design:
•Develop the enterprise data model!
•Corresponds to the conceptual level of the ANSI/SPARC architecture!
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Identify and analyse user views: a user view" may be a report to be produced or a particular type of transaction that should be supported. Corresponds to the external level of the ansi/sparc architecture: output is a statement of speci cation which describes the user views" particular requirements and constraints. Er (entity-relationship) model developed by peter chen in 1976 to aid database design: may be used for conceptual (erd)/logical design. Er diagrams give a visual indication of the design. Conceptual design: develop the enterprise data model. Corresponds to the conceptual level of the ansi/sparc architecture. Independent of all physical implementation: various design methodologies may be employed, including the er (entity- Logical design: develop a strategy for the physical implementation of the logical data model. Choose appropriate storage structures, indexes, le organisations and access methods which will most ef ciently support the user requirements. Physical design phase is dependent on the particular dbms environment in use: ansi/sparc internal level.