Database Development Lifecycle

Slides:



Advertisements
Similar presentations
1 1 File Systems and Databases. 1 1 Introducing the Database 4Major Database Concepts u Data and information l Data - Raw facts l Information - Processed.
Advertisements

Database Design S511 Session 3, IU-SLIS.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Chapter 6 Database Design
File Systems and Databases
Ch1: File Systems and Databases Hachim Haddouti
File Systems and Databases Hachim Haddouti
Chapter 9 Database Design
6 Chapter 6 Database Design Hachim Haddouti. 6 2 Hachim Haddouti and Rob & Coronel, Ch6 In this chapter, you will learn: That successful database design.
Database Design. Why Database?: From Data … Simple dumping of data on the storage medium provides little value. Database System2 idnameaddresscountrypay.
PHASE 3: SYSTEMS DESIGN Chapter 7 Data Design.
2 1 Chapter 2 Data Model Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Database Technical Session By: Prof. Adarsh Patel.
ITEC 3220M Using and Designing Database Systems
IST 210 Database Design Process IST 210 Todd S. Bacastow January 2005.
Database Systems: Design, Implementation, and Management
1 Database Systems: Design, Implementation, and Management CHAPTER 6 Database Design.
1 Chapter 9 Database Design. 2 2 In this chapter, you will learn: That successful database design must reflect the information system of which the database.
Week 4 Lecture Part 3 of 3 Database Design Samuel ConnSamuel Conn, Faculty Suggestions for using the Lecture Slides.
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
Introduction to Database Systems
Database Organization and Design
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
1/26/2004TCSS545A Isabelle Bichindaritz1 Database Management Systems Design Methodology.
Ch. 1 데이터베이스시스템 (2). Ch.1 Database System 데이터베이스시스템 2 What to Learn Database System Overview Entity-Relationship diagram Relational Data Model  Structure.
Chapter(1) Introduction and conceptual modeling. Basic definitions Data : know facts that can be recorded and have an implicit. Database: a collection.
MIS 673: Database Analysis and Design u Objectives: u Know how to analyze an environment and draw its semantic data model u Understand data analysis and.
8 8 Chapter 8 The University Lab: Conceptual Design Verification, Logical Design, and Implementation Database Systems: Design, Implementation, and Management.
Database Design.
1 DATABASE TECHNOLOGIES (Part 2) BUS Abdou Illia, Fall 2015 (September 9, 2015)
2 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Data Models Why data models are important About the basic data-modeling.
IST 210 Database Design Process IST 210, Section 1 Todd S. Bacastow January 2004.
Introduction: Databases and Database Systems Lecture # 1 June 19,2012 National University of Computer and Emerging Sciences.
Copyright © 2014 Pearson Canada Inc. 5-1 Copyright © 2014 Pearson Canada Inc. Application Extension 5a Database Design Part 2: Using Information Technology.
What is a database? (a supplement, not a substitute for Chapter 1…) some slides copied/modified from text Collection of Data? Data vs. information Example:
Databases and Database User ch1 Define Database? A database is a collection of related data.1 By data, we mean known facts that can be recorded and that.
CS4222 Principles of Database System
Database Development Lifecycle
Methodology Conceptual Databases Design
Database Management.
Database Development Lifecycle
ITEC 3220A Using and Designing Database Systems
Datab ase Systems Week 1 by Zohaib Jan.
Methodology Conceptual Database Design
Information Systems Today: Managing in the Digital World
Fundamentals of Information Systems
Chapter 6 Database Design
Translation of ER-diagram into Relational Schema
Databases and Information Management
Entity-Relationship Model and Diagrams (continued)
What is a Database and Why Use One?
Chapter 2 Database Environment Pearson Education © 2009.
Basic Concepts in Data Management
Chapter 6 Database Design
Database Fundamentals
File Systems and Databases
ERD Exercises.
Chapter 6 Normalization of Database Tables
Database Systems Chapter 1
Databases and Information Management
ITEC 3220A Using and Designing Database Systems
Methodology Conceptual Databases Design
Database Management Systems
MIS2502: Data Analytics Relational Data Modeling
Chapter 3 Database Management
Chapter 2 Database Environment Pearson Education © 2009.
Chapter 2 Database Environment Pearson Education © 2009.
CMPE/SE 131 Software Engineering March 7 Class Meeting
CHAPTER 5 THE DATA RESOURCE
Presentation transcript:

Database Development Lifecycle Database Design Database Development Lifecycle

Database Design: Intro Database System Provides data collection 수집, storage 저장, and retrieval 검색 Composed of people, hardware, software, database(s), procedures, and application programs Database Design Foundation of a successful database system 휼륭한 DB system의 기반 Should promote Data integrity 데이터 무결성 Prevent data redundancies 반복 & anomalies 오류 Must yield a database that is efficient in its provision of data access 효율적인 데이터 접근 meet the objectives of the database system and serves the needs of its users DB시스템의 목적과 이용자의 요구 만족 Database Design

Data Redundancy (데이터의 반복성) Database Systems: Design, Implementation, & Management: Rob & Coronel Database Design

Database Systems: Design, Implementation, & Management: Rob & Coronel Data Anomaly 데이터의 오류 Update anomalies 수정오류 - Data inconsistencies resulting from “islands of information” problem Insertion Anomalies 삽입오류 - Creation of bogus record when adding new data (e.g. new agent) Deletion Anomalies 삭제오류 - Unintended deletion of related data (e.g. agent data when deleting customer) Database Systems: Design, Implementation, & Management: Rob & Coronel Database Design

Database Development Database Construction DB 구축 System Construction 시스템 구축 System Analysis 시스템 분석 Establish the need and extent of an information system System Development 시스템 개발 Design & implement the information system Database Construction DB 구축 Planning & Analysis 기획분석 Analyze data environment & Define database objectives Database Development Design 설계 Construct a data model & establish data management processes Implementation 구현 Create the storage structure (e.g., tables) & user interface for data management Maintenance 유지보수 (corrective & adaptive) modification, backup & recovery Database Design

Database Development Lifecycle Planning & Analysis 기획분석 Design 개념 설계 Implementation 구현 Maintenance 정비  Database Objectives Business Rules Data Model Modification Backup & Recovery Security DBMS Tables User Interface SQL Queries Database Design

Database Lifecycle: Planning & Analysis Database Design Implement Maintain Define Database Objectives DB목적 설정 What will the database (DB) do? What tasks 업무/작업 will the DB support? Data Entry, Update, Search What information will the DB provide? Q & A Study the DB environment How does the business operate? Who are the players? How does the information flow? Examine the data Sample Q&A: Recipe Database Query Result recipe name recipe info (ingredients, steps, …) ingredients recipe names  recipe info main ingredient (meat, fish, …) recipe type (diet, diabetic, …) recipe category (soup, desert, …) budget, time Database Design

Database Lifecycle: Database Design Planning & Analysis Database Design Implement Maintain Create a Database Model DB 모델 제작 that can achieve the database objectives Conceptual Design – ER Modeling Logical Design – Relational Schema & Normalization Physical Design – Schema into DBMS (Table Creation) What is a Database Model? Abstract data structure of the real-world items 실제 항목의 추상적인 data 구조 Need to understand how business works & what role data plays E-R model verification E-R model is verified against proposed system processes. End-user views and required transactions Access paths, security, concurrency control Business-imposed data requirements and constraints Database Design

Database Design: Conceptual Design Planning & Analysis Database Design Implement Maintain Conceptual Design Steps Enumerate the Business Rules How does the business work? Construct the Data Model Identify Entities, Relationship, Attributes & draw an ER Diagram Verify the Data Model Does the data model support the fulfillment of database objectives? E-R model verification E-R model is verified against proposed system processes. End-user views and required transactions Access paths, security, concurrency control Business-imposed data requirements and constraints Database Design

Conceptual Design: Business Rules Planning & Analysis Database Design Implement Maintain What 조직 내 정확한 업무 기술 Brief, precise, and unambiguous descriptions of operations in an organization Based on policies, procedures, or principles within a specific organization Why 정확한 data model 설계를 위하여 Promote creation of an accurate data model Enhance understanding & facilitate communication How (sources) Interviews, Documentation, Observation Examples A painter can draw many paintings. A painting is drawn by a single painter. A teacher can teach 0 to 6 courses per semester. A course is taught by a single teacher. A student must take at least 1 and at most 6 courses. A course can have 10 to 40 students. 1 M PAINTER draws PAINTING 1 M TEACHER teaches COURSE N takes M STUDENT Database Design

Conceptual Design: Data Modeling Planning & Analysis Database Design Implement Maintain What is Data Modeling? A model is a representation of reality that retains only carefully selected essential details. Logical organization of data for optimum information extraction and data manipulation Why Model? 주요한 data 요소들을 이해하고 인식하기 위하여 To understand and identify essential data elements How? Identify Entities 개체, Attributes 속성, & Relationships 관계 ID STUDENT GPA Major Name TEACHER email Office Database Design

Database Design: Relational Schema Planning & Analysis Database Design Implement Maintain Specification of the overall structure/organization of a database Relations Entities w/ Attributes Primary key Unique identifier Foreign key PK of related table Relationship type (connectivity) 1:M, M:N, 1:1 https://www.coursera.org/learn/analytics-mysql/lecture/hDLIS/relational-schemas Database Design

Database Design: Data Dictionary Planning & Analysis Database Design Implement Maintain Detailed description of a data model Lists attribute names and characteristics for each table in the database Blueprint & documentation of a database Database Systems: Design, Implementation, & Management: Rob & Coronel Database Design

Database Design: Lifecycle Define Database Objectives DB 목적 설정 What information will the database provide? Examine the Data Environment data 환경 조사 How does the business work & what data are used? Construct the Data Model data모델 구축 Enumerate the Business Rule. Identify Entities & Relationships between them. Define Attributes (and primary & foreign keys) for each entity Create an initial E-R diagram Normalize the entities 개체 정규화 Process for evaluating & designing good table structures Verify the Data Model data모델 확인 Does the data model support the database objectives? If not, modify the Data Model Database Design

Data Model: University Example Database Design

Exercises

Data Modeling Exercises Draw an E-R Diagram of the data model described by the business rules below. One region can be the location for many stores. Each store is located in only one region. Each store employs one or more employees. Each employee is employed by one store. A job can be assigned to many employees. -- e.g., The "Sales Representative" job can be assigned to more than one employee at a time. Each employee can have only one job assignment. Draw an E-R Diagram of the data model described by the business rules below. One region can be the location for many stores. Each store is located in only one region. Each store employs one or more employees. Each employee is employed by one store. A job can be assigned to many employees. -- e.g., The "Sales Representative" job can be assigned to more than one employee at a time. Each employee can have only one job assignment. Draw an E-R Diagram of the data model described by the business rules below. One region can be the location for many stores. Each store is located in only one region. Each store employs one or more employees. Each employee is employed by one store. A job can be assigned to many employees. -- e.g., The "Sales Representative" job can be assigned to more than one employee at a time. Each employee can have only one job assignment. REGION JOB 1 1 is location for is assigned to M M 1 M STORE employees EMPLOYEE Database Design

Data Modeling Exercises Identify the business rules and draw an E-R diagram of the situation described below. For each professor, there may be multiple advisees. A professor teaches many classes and a class is taught by one professor. Business Rules A professor can advise many students. A student is advised by one professor. A professor can teach many classes. A class is taught by one professor 1 M PROFESSOR teaches CLASS 1 advises M STUDENT Database Design

Data Modeling Exercises Sample DB Create a data model (i.e. ERD) for the school database described below. DB will keep track of advising and class information. DB should provide following information. - The list of students advised for a given year & dates of advising sessions for each students - Course listing for each year & student grades for each class Create a data model (i.e. ERD) for the school database described below. DB will keep track of advising and class information. DB should provide following information. - The list of students advised for a given year & dates of advising sessions for each students - Course listing for each year & student grades for each class Create a data model (i.e. ERD) for the school database described below. DB will keep track of advising and class information. DB should provide following information. - The list of students advised for a given year & dates of advising sessions for each students - Course listing for each year & student grades for each class Create a data model (i.e. ERD) for the school database described below. DB will keep track of advising and class information. DB should provide following information. - The list of students advised for a given year & dates of advising sessions for each students - Course listing for each year & student grades for each class Business Rules A professor can advise many students. A student is advised by one professor. A professor can teach many classes. A class is taught by one professor. A student can take many classes. A class can have many students. A course can generate many classes. A class is generated by one course. A professor can meet many times with an advisee. A student can meet many times with the advisor. 1 M PROFESSOR teaches CLASS 1 1 N M 1 M ADVISING advises generates takes ENROLL M M M M 1 M 1 1 STUDENT COURSE Database Design