Elements of Database System

Slides:



Advertisements
Similar presentations
BUSINESS DRIVEN TECHNOLOGY Plug-In T4 Designing Database Applications.
Advertisements

Entity-Relationship Model and Diagrams (continued)
Lesson-19 Data Modeling and Analysis
Concepts of Database Management Seventh Edition
July 14, 2015ICS 424: recap1 Relational Database Design: Recap of ICS 324.
Normalized bubble chart for Data in the Instructor’s View Instructor Organization Title Standard fee Text book Course + Date Participant Grade.
Chapter 14 & 15 Conceptual & Logical Database Design Methodology
Relational databases and third normal form As always click on speaker notes under view when executing to get more information!
Copyright 2008 McGraw-Hill Ryerson 1 TECHNOLOGY PLUG-IN T5 DESIGNING DATABASE APPLICATIONS.
Conceptual Database Design
Chapters 15 &16 Conceptual and Logical Database Design Methodology.
CS370 Spring 2007 CS 370 Database Systems Lecture 4 Introduction to Database Design.
Overview of Database Development Data Modeling and Relational Database Design.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
+ Information Systems and Databases 2.2 Organisation.
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
1 6 Concepts of Database Management, 5 th Edition, Pratt & Adamski Chapter 6 Database Design 2: Design Methodology Spring 2006.
IT 5433 LM3 Relational Data Model. Learning Objectives: List the 5 properties of relations List the properties of a candidate key, primary key and foreign.
DATA MODELING AND DATABASE DESIGN
Normalized bubble chart for Data in the Instructor’s View
Software Design.
Entity- Relationship (ER) Model
Chapter 5 Database Design
Business System Development
Chapter 4: Logical Database Design and the Relational Model
Basic Concepts in Software Design
IS 130 Information systems 1
Databases Chapter 16.
SEEM3430: Information Systems Analysis and Design
(Winter 2017) Instructor: Craig Duckett
Database Systems Chapter 3 1.
© 2014 by McGraw-Hill Education. This is proprietary material solely for authorized instructor use. Not authorized for sale or distribution in any manner.
© The McGraw-Hill Companies, All Rights Reserved APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
Information Systems Today: Managing in the Digital World
Software Specification Tools
DESIGNING DATABASE APPLICATIONS
Chapter 7: Entity-Relationship Model
Basic Concepts in Software Design
Introduction to Database Systems
Lecture on Data Modeling and Analysis
Lecture # 13 (After 1st Exam)
Constraints AND Examples
بسم الله الرحمن الرحيم.
Software Development Life cycle
Databases and Information Management
Entity-Relationship Model and Diagrams (continued)
From ER to Relational Model
Data Base System Lecture 6: Relational Model
Chapter 3 The Relational Model.
(Winter 2017) Instructor: Craig Duckett
IST 318 Database Administration
Microsoft Applications
CHAPTER 4: LOGICAL DATABASE DESIGN AND THE RELATIONAL MODEL
Database solutions Chosen aspects of the relational model Marzena Nowakowska Faculty of Management and Computer Modelling Kielce University of Technology.
Analysis models and design models
Databases and Information Management
COMP 208/214/215/216 – Lecture 7 Documenting Design.
Computer Science Projects Database Theory / Prototypes
Database Design Hacettepe University
logical design for relational database
MIS2502: Data Analytics Relational Data Modeling
INSTRUCTOR: MRS T.G. ZHOU
IT 244 Database Management System
Summary Data Modeling SDLC What is Data Modeling
Constraints AND Examples
Shelly Cashman: Microsoft Access 2016
Lecture 23 CS 507.
DATA MODELING AND DATABASE DESIGN
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Chapter 3 The Relational Model
Presentation transcript:

Elements of Database System LECTURE 3 BBA 8TH (M) Elements of Database System Database Design Technique process of database design consist of three major phases an information requirement analysis phase a logical design phase physical design phase O\/\/@!$ $}{@f!Qu3

Elements of Database Systems An information requirement analysis phase involves: 1st & most Imp phase Working with users to define their information needs in detail Information as users see it Information is viewed in terms of the way it appears in documents. On terminal screens Even images in users mind

Elements of Database System Logical design Various views have been defined and specification developed, they must be coordinated and organized into an integrated cohesive system. Process referred to as logical design Developing a data model for each user view Integrating the entities, attributes, and relationship into a composite logical schema that describes the database for that module in terms unrelated to the sw package being used

Elements of database 3. Transforming the logical schema into a software schema expressed in the language of the chosen database management package.

Elements of database A Primary Key Concatenated keys Uniquely identifies each data item in a group of related items. A primary key is a data item with only single headed arrow. Concatenated keys Are formed by joining two or more data items to produce a primary key A one to many relationship exists between one of the other elements of the group and the key

Un-normalized bubble chart Instructor High degree university year Course Text book fee date Organization Prospect Title street City zip

Un-normalized bubble chart The last figure is said to be un-normalized; becz it has many-to-many relationships between data items in the same group and one-to-many relationship between non-key items in the same group. We need to normalize it; means keys have only single headed arrows to items within their data group, although they can have one-to-many relationships with keys of other data groups.

Normalized bubble chart Instructor High degree university year Course + Date Standard fee Text book Prospect Title zip Organization street City

Rules to normalize the bubble chart If a bubble has single headed arrows entering it from other items in its group and leaving it to other items in its group, it is a potential primary key and should be moved into a new group with the items it identifies. If an items or a group of items has no key, a concatenated key should be formed to serve as an identifier. Names (of people, courses, products), identification numbers (social security number, account number), and dates are likely candidates for concatenated keys)

Rules to normalize The concatenated key should be formed from the fewest number of data items possible to identify the data items in its group

Thanks very much!! Any Questions????????