Scribd
Upload
66 views6 pages

Mini Project Guideline and Sample Project

This document describes the development of a Furniture Inventory Management System database. It includes: 1) Requirements collection which outlines suppliers, products, orders, and customers need to be tracked with unique IDs and attributes for each. 2) The conceptual ER diagram modeling the entities and relationships. 3) Logical and physical schema design sections which are not filled in. 4) Example SQL queries to create tables for the Supplier, Product, Order, and Customer entities along with primary and foreign keys.

Uploaded by

Bb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
66 views6 pages

Mini Project Guideline and Sample Project

This document describes the development of a Furniture Inventory Management System database. It includes: 1) Requirements collection which outlines suppliers, products, orders, and customers need to be tracked with unique IDs and attributes for each. 2) The conceptual ER diagram modeling the entities and relationships. 3) Logical and physical schema design sections which are not filled in. 4) Example SQL queries to create tables for the Supplier, Product, Order, and Customer entities along with primary and foreign keys.

Uploaded by

Bb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

KINGDOM OF SAUDI ARABIA

MINISTRY OF HIGHER EDUCATION


JAZAN UNIVERSITY
COLLEGE OF COMPUTER SCIENCE & INFORMATION SYSTEMS

MINI PROJECT
DATABASE CONCEPTS AND DESIGN
ITEC-211

TITLE: Furniture Inventory management system

Submitted To:
Teacher Name:

Dept. of IT AND Security

Submitted by: Submission date:

Marks
Group Name ID Email Id
obtained
Rahaf Thabet 202208842
A Al sulimani 202208842@stu.jazan.edu.sa

Inventory management system (SAMPLE)

Page 1
In this section we describe a sample database application, called INVENTORY
MANAGMENT SYSTEM, which serves to illustrate the basic ER model
concepts and their use in schema design. We list the data requirements for
the database here, and then create its conceptual schema step-by-step as
we introduce the modeling concepts of the ER model. The INVENTORY
MANAGMENT SYSTEM database keeps track of inventory suppliers,
products, orders and customers

Phase I: Requirements collection and Analysis (3 marks)

Guidelines: After consultation, the following requirements for a company


database have been determined:

1. The inventory is supplied by different suppliers. Each supplier has a


unique name, a unique number (ID), contacts (phone number , email)
and address
2. A supplier supplies different product, each product has a unique number
(ID), unique name, available quantity, the and price relation keeps track
quantity of the supplement and the total price of supplement
3. A product has unique code unique name, and available quantity and
price. A product may be included in many orders
4. An order include one or many products, an order is recognized by a
unique number and total price date and time of purchase

5. A customer place one or many orders, a customer has unique


number(ID), name, and a phone number

Phase II: Conceptual design: E-R Diagram (3 marks)

Concepetual

Page 2
Logical Scheme Design

Page 3
Physical scheme Design

Page 4
QUERY FOR CREATING COMPANY DATABSE (10 MARKS FOR LAB)

CREATE TABLE "Supplier" (


"Sup_ID" Number(4),
"Sup_Name" VARCHAR(30),
"phone_no" Number(12),
"email" VARCHAR(60),
"Address" VARCHAR(60),
PRIMARY KEY ("Sup_ID")
);

CREATE TABLE "Order" (


"Ord_ID" Number(9),
"date_time" DATETIME,
"Cus_ID" Number(7),
"total_price" Number(6),
PRIMARY KEY ("Ord_ID")
);

CREATE TABLE "Product" (


"Pro_ID" Number(5),
" Sup_ID" Number(4),
"Pro_name" VARCHAR(30),
"qnautity" Number(8),
"price" Number(8),
"Ord_ID" Number(9),
CONSTRAINT "FK_Supplier.Sup_ID"
FOREIGN KEY ("Sup_ID")

Page 5
REFERENCES "Supplier"("Sup_ID")
);

Alter TABLE Product


Add constraint "FK_product_ord"
Foreign key(Ord_ID) REFERENCES Order(Ord_ID)

CREATE TABLE "Customer" (


"Cus_ID" Number(6),
"F_name" VARCHAR(30),
"phone_number" Number(12),
"L_name" VARCHAR(30),
PRIMARY KEY ("Cus_ID")
);
Alter TABLE Order
Add constraint "FK_Cus _ord"
Foreign key(Cus_ID) REFERENCES Customer (Cus_ID)

Page 6

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy