Bookstore DB Requirements

Slides:



Advertisements
Similar presentations
SQL Database for a Book Store Clinton McKay. Explanation The database contains information about the books held in stock, their authors, publishers, customers,
Advertisements

Table design screen Field name Data type Field size Other properties.
Database Design University of California, Berkeley
Table design screen Field name Data type Field size Other properties.
8/28/97Information Organization and Retrieval Database Design University of California, Berkeley School of Information Management and Systems SIMS 202:
Case study Lisa’s Bookstore IST210.
Seminar #1 – Refreshing databases concepts and SQL CM036: Advanced Databases1 Seminar 1: Revisiting Databases and SQL Purpose To refresh basic concepts.
A Beauty Salon Management Key Features of The Product:  Masters  Employee salary management  Product stock management  Services and package management.
CSE 441: Systems Analysis & Design
Practice of ER modeling
Entity Relationship Diagrams (ERDs). Entity Relationship Diagram (ERD) documentation technique to represent relationship between entities in system. Think.
By: Devi Sumadi The Administration information system design and construction of UD. Usaha Jaya Engineering Equipment Company.
Database Fundamentals Lecture 4 Useful website for MySQL download language.com/workshops/Default.asp ?workshop=21.
MS Access. Access is a DBMS/RDMS DBMS = Database Management System RDMS = Relational Database Management System.
Normalization Exercise. First Normal Form Second Normal Form.
Ch6. Introduction to Database. What is a Database? Database is a collection of related information. It is organized so that it can easily be accessed,
Quiz questions. 1 A data structure that is made up of fields and records? Table.
Week 2 Lab2 ER Diagram Dina A. Said
Database Design – Lecture 6 Moving to a Logical Model.
Database Design – Lecture 7
Entity Relationship Diagrams (ERDs)
OBJECTIVE Understanding process and timelines for Vodafone customer orders.
IST 220 – Intro to Databases Database Design I. DB Design – Sports League The league needs to keep track of Teams Players Coaches Sponsors How many tables.
Yum Juices Database. Background Organic juice company producing fruit and vegetable juices to own recipes. Supply juices by the litre to range of organic.
Our Business Requirements Grandmother’s Books - II.
G057 - Lecture 05 From Scenario To Design Mr C Johnston ICT Teacher
DATA MODELING AND ENTITY-RELATIONSHIP MODEL II IST 210: Organization of Data IST210 1.
Year 12 > 13 Applied GCE ICT Unit 7 Using Database Software.
Enterprise Processes and Systems MIS 2000 Instructor: Bob Travica Updated 2016 Class 16.
Database Relationships
DATA MODELING AND DATABASE DESIGN
Week 03 – ER Diagram INFOSYS 222.
Data Modeling Using the ERD
Let try to identify the conectivity of these entity relationship
DFD Examples.
The Entity-Relationship Model
DFD Examples.
Database Management Systems II
DFD Examples.
Enterprise Processes and Systems
E-R Diagram (Cont.) Draw ER Diagram for the following scenario:
The Jonesburgh County Basketball Conference (JCBC) is an amateur basketball  association. Each city in the county has one team that represents it.  Each.
Database Relationships
ER MODEL Lecture 3.
ER Modeling Case Studies
The Entity-Relationship Model
Hospital DB Requirements
Practice of ER modeling
Company Requirements.
ERD Exercises.
Amazom.com “Product/Book Information Management Business Process”
TEXAS SUPPLEMENT WAREHOUSE
Technical Module A Data Modeling Definitions
Entity – Relationship Model
Process Diagram for Sally’s Bookstore (as written)
Instruction Assignment #1 (due May 16, 2018)
ERD (Entity Relationship Diagrams)
Database Relationships
Flat Files & Relational Databases
Databases.
ER Modeling Case Studies
Mapping an ERD to a Relational Database
DFD Examples.
Database Management system
Entity Relationship Model
IS6125 Database Analysis and Design Lecture 8: Practice with ERDs
Some examples of simple business rules:
DATA MODELING AND DATABASE DESIGN
IS6145 Database Analysis and Design Lecture 6: Practice with ERDs
Recursive Relationship and Weak Entity Examples
Presentation transcript:

Bookstore DB Requirements

Entity Sets Customers open an account by providing their national number, name, address, phone, and book type preferences. For each employee, the following information is recorded: an employee identification number, national number, name, address, phone, a birth date, and the position within the bookstore.

Entity Sets For each book writer, the following information is recorded: national number, name, address, and phone. Any ideas?

Entity Sets The database records the following information about each book: a book identification number, name, publication year, the publisher's name, the book category, and the number of books in stock.

Entity Sets The database also keeps the following information about book supplying companies: an identification number, name, phone, address, and the name of the contact person.

Relationships A book may be bought by one or more customers, and one customer may buy one or more books.

Relationships A book may be written by one or more writers, and one writer may write one or more books. Additionally, an employee may monitor the sales of one or more books; however, a book is monitored by exactly one employee. Suppliers may provide one or more books; however, a book is supplied by exactly one supplier.

ERD

Mapping ERD into tables

Relational Model Person (NN, Name, Address, Phone) Customer (NN, Pref) Emp (NN, Bdate, Pos) Writer (NN) Buy (Cust_NN, Book_ID) Writes (Writer_NN, Book_ID) Book (ID, Name, Publisher, Stock, Year, Category, Sup_ID, Monit_E_NN) Supplier (ID, Name, Address, Phone, Contact)