WELL-DESIGNED DATABASES Process faster Easy to develop and maintain Easy to read and write code.

Slides:



Advertisements
Similar presentations
Information Systems Technology Ross Malaga B Copyright © 2005 Prentice Hall, Inc. B-1 WORKING WITH DATABASES.
Advertisements

Chapter 5 Normalization of Database Tables
WHAT D IS RAW, UNPROCESSED FACTS AND FIGURES COLLECTED, STORED AND PROCESSED BY COMPUTERS.
McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. Extended Learning Module C Designing Databases and Entity-Relationship.
Extended Learning Module C
© McGraw-Hill Companies, Inc., McGraw-Hill/Irwin Extended Learning Module C Designing Databases and Entity-Relationship Diagramming.
Database Basics Alan B. Marr, M.D., F.A.C.S. Associate Professor of Clinical Surgery.
Systems Development Life Cycle
Database Design (Data Modeling) DCO11310 Database Systems and Design By Rose Chang.
© 2002 by Prentice Hall 1 David M. Kroenke Database Processing Eighth Edition Chapter 2 Introduction to Database Development.
Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
Entity-Relationship Model and Diagrams (continued)
Extended Learning Module C Designing Databases and Entity-Relationship Diagramming McGraw-Hill/Irwin Copyright © 2010 by the McGraw-Hill Companies, Inc.
Chapter 5 Normalization of Database Tables
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 5 Normalization of Database Tables.
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Chapter 14 & 15 Conceptual & Logical Database Design Methodology
Page 1 ISMT E-120 Introduction to Microsoft Access & Relational Databases The Influence of Software and Hardware Technologies on Business Productivity.
Entity-Relationship Design
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Chapter 5 Normalization of Database Tables
Data Modeling ERM ERD.
MICROSOFT ACCESS 2007 BTA – Spring What is Access?  Microsoft Access is a database management system…this means that it contains database information.
1 Chapter 1 Overview of Database Concepts. 2 Chapter Objectives Identify the purpose of a database management system (DBMS) Distinguish a field from a.
Chapter 9 Designing Databases Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Management Information Systems By Effy Oz & Andy Jones
Information Systems: Databases Define the role of general information systems Describe the elements of a database management system (DBMS) Describe the.
Concepts and Terminology Introduction to Database.
2005 SPRING CSMUIntroduction to Information Management1 Organizing Data John Sum Institute of Technology Management National Chung Hsing University.
5 1 Chapter 5 Normalization of Database Tables Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
BIS Database Systems School of Management, Business Information Systems, Assumption University A.Thanop Somprasong Chapter # 5 Normalization of Database.
I Information Systems Technology Ross Malaga 4 "Part I Understanding Information Systems Technology" Copyright © 2005 Prentice Hall, Inc. 4-1 DATABASE.
Information Systems & Databases 2.2) Organisation methods.
1.  An introduction to data modelling  The purpose of data modelling  Modelling data relationships 2.
Next Back A-1 Management Information Systems for the Information Age Second Canadian Edition Copyright 2004 The McGraw-Hill Companies, Inc. All rights.
C-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Extended Learning Module.
Fanny Widadie, S.P, M.Agr 1 Database Management Systems.
Prepared By Prepared By : VINAY ALEXANDER ( विनय अलेक्सजेंड़र ) PGT(CS),KV JHAGRAKHAND.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Access Review. Access Access is a database application A database is a collection of records and files organized for a particular purpose Access supports.
Entity-Relationship (E-R) Diagrams
+ Information Systems and Databases 2.2 Organisation.
Relational Theory and Design
Normalization of Database Tables
Lesson 2: Designing a Database and Creating Tables.
Database Basics BCIS 3680 Enterprise Programming.
INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.
Information Access Mgt09/12/971 Entity-Relationship Design Information Level Design.
1 DATABASE TECHNOLOGIES (Part 2) BUS Abdou Illia, Fall 2015 (September 9, 2015)
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
Done By : Gillian Swaby. Objectives: 1. What is an Entity-Relationship Diagram? 2.What are the symbols used in ERD? Explain each. 3. What is a one- to-
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 9 Designing Databases 9.1.
Entity Relationship Diagram (ERD). Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship.
INFORMATION TECHNOLOGY DATABASE MANAGEMENT. A database is a collection of information organized to provide efficient retrieval. The collected information.
Hoi Le. Why database? Spreadsheet is not good to: Store very large information Efficiently update data Use in multi-user mode Hoi Le2.
5 1 Chapter 5 Normalization of Database Tables Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Database Planning Database Design Normalization.
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.
NORMALISATION OF DATABASES. WHAT IS NORMALISATION? Normalisation is used because Databases need to avoid have redundant data, which makes it inefficient.
Microsoft Office Access 2010 Lab 1
Fundamentals of Information Systems, Sixth Edition
Functional Dependencies
CSCI-100 Introduction to Computing
Entity-Relationship Model and Diagrams (continued)
Databases and Information Management
MIS2502: Data Analytics Relational Data Modeling
Entity-Relationship Diagram (ERD)
Presentation transcript:

WELL-DESIGNED DATABASES Process faster Easy to develop and maintain Easy to read and write code

DATABASE DESIGN PROCESS DETERMINE THE PURPOSE OF THE DATABASE CREATE A MODEL DETERMINE THE TABLES AND FIELDS YOU NEED DETERMINE THE RELATIONSHIPS REFINE YOUR DESIGN

DETERMINE THE PURPOSE OF THE DATABASE Start with the output and work backward. What output does the client want to see? What input will be required to produce that output? Describe the screens, the reports, the results that will be produced. Study the existing system. Determine what must be kept, what must be changed and what must be scrapped. Keep this in mind: Any system you deliver must perform at least as well as the system the client is using now.

CREATE A MODEL Create a model (drawing, graphic representation, schema) of the data. The model is created with the help of the client. The client knows what needs to be done although he may not know how it will be done - that's your job. Always keep the client involved at the design stage.

DEFINITIONS Entity: an object, a thing in the system about which data is kept - equivalent to a file - it will be implemented as a table in the database. (Ex: Student, Professor, Class) Attribute: an item of data refering to an entity - equivalent to a field - it will be implemented as a column in a table in the database. (Ex: Student_Id, Student_Name)

DATA MODELING Primary key: the attribute (or combination of attributes) that uniquely identifies every occurence of an entity. (Ex: Student_Id for "Student" entity) Relationship: the way entities link to one another (Ex: Professor teaches Class, Student registered in Class)

DATA MODELING The main tool in the modeling process is called an Entity-Relationship diagram or E-R diagram for short. It shows all the components we have been discussing: Entities, Attributes of Entities, Key attributes of Entities and Relationships between Entities.

DATA MODELING

DEFINING ATTRIBUTES (COLUMNS) Relate each field directly to the subject of the table Don't include derived or calculated data Include all the information you need Store information in its smallest logical parts

DEFINING RELATIONSHIPS Normalization: The process of coding relationships in database modeling. Every table must have a primary key The primary key can never contain an empty or Null value. Every attribute of every occurence in the table can contain only one value.

REFINE YOUR DESIGN Do you have one table with a large number of fields that don't all relate to the same subject? Do you have fields that are intentionally left blank in many records because they aren't applicable to those records? Do you have a large number of tables, many of which contain the same fields? Are you repeatedly entering duplicate information in one of your tables?