1 / 9

Jumping for Joy’s: Database Design Project

This project aims to design a database for Joy's Embroidery, a retailer specializing in UC Berkeley apparel, to optimize inventory management, sales tracking, and overall store operations.

fpike
Download Presentation

Jumping for Joy’s: Database Design Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Group 3: Deborah Chang, Ying Chen, Jessica Liang, Angella Liu, Timothy Manglicmot, Kathy Phan, Scott Tung Jumping for Joy’s: Database Design Project

  2. Agenda • Our client – Joy’s Embroidery • Database requirements • EER diagram • Project attributes • Proposed benefits • Project timeline Joy’s Embroidery on Channing and Telegraph Ave.

  3. Our Client - JOY’S EMBROIDERY • Retailer located near campus • Specializes in UC Berkeley apparel • Provides custom embroidery • Five employees (two warehouse, three retail) • Receives finished products from warehouses • Receives raw materials from suppliers • No existing database or information retrieval system A look at the products inside the retail store

  4. Database Requirements • Joy’s Embroidery, the retailer, carries inventory. Store inventory consists of finished products replenished by warehouses. Products are manufactured goods of raw materials and design. • Warehouses receive store orders placed by retailer employees to fill store inventory. • Warehouses store raw materials and operating equipment, which are delivered from suppliers. • Retailer employees take sales orders from customers. Sales orders can be for regular or customized products.

  5. EER Diagram

  6. Attributes of Generalized Entities • Sales Orders (SOID, Item, Quantity, Discount, PayType, VerifN) • Store • Custom (CustomerID2) • Customer (CustomerID, Fname, MI, Lname, Address, City, Zip, Phone) • Employees (SSN, Fname, MI, Lname, Address, City, Zip, Phone, StartDate, Location, Dept) • WHEmployee (Manager, Wage) • WHManager (Salary)

  7. Proposed Benefits • Well-organized inventory • Optimal reorder quantities and points • More efficient store operation • Well-managed sales • Increased outreach • Decreased holding costs • Tracked orders • Recognizing “hot” products • Tracked cash flows

  8. Project Timeline

  9. Any Questions?

More Related