The document describes a proposed centralized electronic materials inventory management system for shops on SP Road in Bengaluru. It aims to address the challenges of tracking inventory across shops due to the dynamic nature of supplies and demand. The proposed system would provide up-to-date information on material availability at different shops to help customers find what they need more easily. Key requirements for the system include tracking inventory, shop and material details, customer information, order management, and reporting capabilities.

1. DATABASE MANAGEMENT
SYSTEM
ASSIGNMENT 1
Name: Abhishek G
UEN : 2022UG000045

2. TITLE: "Tech Treasure: CentralizedManagement for Electronic Material Inventory"
Problem Definition: SP Road in Bengaluru is a bustling marketplace
known for its wide variety of electronic materials. However, finding specific
materials in the numerous shops can be a daunting task due to the lack of a
centralized system that tracks the availability of materials across different
shops. This problem is further compounded by the dynamic nature of the
inventory, which changes frequently based on supply and demand. The
inventory of electronic materials at each shop changes frequently based on
supply (what the shop can source) and demand (what customers are
buying). This dynamic nature of inventory further complicates the task of
finding specific materials.
The goal, then, is to develop a solution that addresses these challenges.
Ideally, this would be a system that provides up-to-date information about
the availability of various electronic materials in different shops on SP Road.
This would save customers time and effort by allowing them to check the
availability of the specific material they need before they visit the shops.

3. Requirements
1. Inventory Tracking: The system should be able to track the inventory of each shop, including
the type and quantity of electronic materials available.
2. Shop Information: The system should store information about each shop, including its
location, contact details, and operating hours.
3. Material Information: The system should store detailed information about each type of
electronic material, including its specifications, manufacturer, and supplier.
4. Customer Information: The system should store information about customers, including their
contact details and purchase history.
5. Order Management: The system should be able to manage orders, including tracking the
status of each order and updating the inventory accordingly.
6. Supplier Information: The system should store information about suppliers, including their
contact details and the materials they supply.
7. Reporting: The system should be able to generate reports, such as sales reports and
inventory reports.
8. User Interface: The system should have an easy-to-use interface that allows users to quickly
find the information they need.
9. Security: The system should ensure the security of the data stored, including customer and
shop information.

4. Entities and attributes

9. Primary key, Candidate Key and Super key
Entity Candidate Keys Primary Key Super Key
Shops ShopID, ShopName ShopID ShopID, ShopName
Materials MaterialID, MaterialName MaterialID MaterialID, MaterialName
Inventory ShopID, MaterialID ShopID, MaterialID ShopID, MaterialID, Quantity
Customers CustomerID, CustomerEmail CustomerID CustomerID, CustomerEmail
Orders OrderID OrderID OrderID, ShopID, CustomerID, MaterialID
Suppliers SupplierID, SupplierContact SupplierID SupplierID, SupplierContact
Employees EmployeeID EmployeeID EmployeeID, ShopID
ProductCategories CategoryID CategoryID CategoryID, CategoryName
Transactions TransactionID TransactionID TransactionID, CustomerID, OrderID
BillingInformation BillingID BillingID BillingID, CustomerID
Manufacturers ManufacturerID ManufacturerID ManufacturerID, ManufacturerContact
PaymentMethods PaymentMethodID PaymentMethodID PaymentMethodID, PaymentMethodName
Discounts DiscountID DiscountID DiscountID, DiscountCode

10. Warranty WarrantyID WarrantyID WarrantyID, WarrantyPeriod
ReturnPolicy PolicyID PolicyID PolicyID, PolicyDetails
SalesReports ReportID ReportID ReportID, ShopID
ShopTimings ShopID ShopID ShopID, OpeningTime, ClosingTime
ShopHolidays ShopID, HolidayDate ShopID, HolidayDate ShopID, HolidayDate, HolidayName
MaterialSpecifications MaterialID, SpecificationName MaterialID, SpecificationName
MaterialID, SpecificationName,
SpecificationValue
ShopContacts ShopID ShopID ShopID, ContactName
MaterialSuppliers SupplierID, MaterialID SupplierID, MaterialID
SupplierID, MaterialID,
SupplyQuantity
Primary key, Candidate Key and Super key

11. Functional Dependencies of attributes
1.Shops
ShopID → ShopName, ShopLocation, ShopSize, ShopType
2.Materials
MaterialID → MaterialName, MaterialCost, MaterialWeight, MaterialColor
3.Customers
CustomerID → CustomerName, CustomerContact, CustomerEmail, CustomerAddress
4.Suppliers
SupplierID → SupplierName, SupplierContact, SupplierAddress, SupplierRating
5.Employees
EmployeeID → EmployeeName, ShopID, EmployeePosition, EmployeeSalary
6.ProductCategories
CategoryID → CategoryName, CategoryDescription
7.Transactions
TransactionID → CustomerID, OrderID, TransactionAmount, TransactionDate, PaymentMethod
8.BillingInformation
BillingID → CustomerID, BillingAddress, PaymentMethod, BillingDate
9.Manufacturers
ManufacturerID → ManufacturerName, ManufacturerContact, ManufacturerAddress, ManufacturerRating

12. 1. Warranty
WarrantyID → WarrantyPeriod, WarrantyDetails, WarrantyCost
2. ReturnPolicy
PolicyID → PolicyDetails, ReturnPeriod
3. SalesReports
ReportID → ShopID, TotalSales, ReportDate, Profit
4. CustomerFeedback
FeedbackID → CustomerID, FeedbackDetails, FeedbackDate, FeedbackResponse
5. ShopTimings
ShopID → OpeningTime, ClosingTime, BreakTime
6. ShopHolidays
ShopID, HolidayDate → HolidayName, HolidayType
7. MaterialSpecifications
MaterialID, SpecificationName → SpecificationValue, SpecificationUnit
8. ShopLocations
ShopID → ShopAddress, ShopCity, ShopState, ShopCountry, ShopZipCode
9. ShopContacts
ShopID → ContactName, ContactPhone, ContactEmail, ContactPosition

13. MaterialSuppliers
SupplierID, MaterialID → SupplyQuantity, SupplyDate, SupplyCost
Discounts
DiscountID → DiscountAmount, StartDate, EndDate, DiscountCode
• And here are the functional dependencies for the weak entities:
1.Inventory
1. ShopID, MaterialID → Quantity, LastUpdated, ReorderLevel
2.Orders
1. OrderID → ShopID, CustomerID, MaterialID, Quantity, OrderDate, DeliveryDate
3.ProductReviews
1. ReviewID → CustomerID, MaterialID, Rating, Review, ReviewDate

14. Entity relationship diagram

15. example
CustomerID CustomerName CustomerContact
1 Yogesh yogesh@gmail.com
2 Chaitanya chaitanya@gmail.com
3. Amar amar@gmail.com
ProductID ProductName ProductCost
1 Resistor 100
2 Capacitor 200
3. laptop 10000
OrderID CustomerID ProductID Quantity
1 1 1 100
2 1 2 50
3 2 3 200
4 3 2 100
In this example, the Orders table is related to both the Customers and Products tables.