Scribd
Upload
48 views4 pages

Team 2 - Project Specifications

inf

Uploaded by

Altaa Tungaa
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
48 views4 pages

Team 2 - Project Specifications

inf

Uploaded by

Altaa Tungaa
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/ 4

The topic of the project: Sportswear shop database system

Name of the shop: Skea Fitness Depo

Team number: 2
Team members: Dobromir Dobrev, Binderiya Usukhbayar,
Vladimir Chanov, Sofia Kurochkina, Dimitar Dimitrov
03/10/2020

Project idea:

We are planning to make a sportswear shop database management system that will be
used to manage employees and their responsibilities. The main goal is to track orders
from the manufacturer to the final cashier and streamline inventory management
processes.

Selected DBMS: Maria DB (XAMPP)

Tables and relationships:


1. Supply_chain
2. Manufacturer
3. Vendor
4. Employee
5. SportsWear_Shops
6. Consultant
7. Customer_Support
8. Sales-Manager/Supervisor
9. Cashier
10. Category
11. Sub-Tasks
12. Task
13. Order_details
14. Items
15. sells
Outline of the DBMS:

The supply chain will consist of information about the manufacturer and the vendor,
which will be our sportswear shop branches.

The database system will be designed to manage the employees in each store.
Employee details such as first name, last name, SSN, and address will be registered in
each table of employee type (Consultant, Customer_Support, Sales-
Manager/Supervisor, and Cashier).

Sub-tasks for each employee include their usual working hours and general work
responsibilities, such as hours worked, etc. Tasks for each employee will be assigned
and managed through the DBMS, supervised by the Sales-Manager/Supervisor.
Cashiers (cash_ID) will execute the orders in accordance with the item (s) (item_ID),
which may be different products from different categories.

This DBMS will have different relations between tables, as follows:

The table Supply_chain is connected to the Manufacturer via a foreign key. This is to identify
each manufacturer, with their own personal attributes. Table supply_chain has two composite
keys.

Table Supply_chain is also connected to the Vendor and sells via the v_DUNS composite key.
This is to ensure that every vendor and sell is unique for itself.

Table sells is connected to the SportsWear_Shops table with a foreign key SW_address. This is
to ensure that for every sale made in the shop, the address is uniquely identified for the specific
shop.

From table SportsWear_Shops, the staff Number is connected to Employee SSN, via a foreign
key. This is to ensure that every employee is divided into the correct shop and they are
identified by their SSN. While, from table Employee, SportShop_address is a foreign key to
SW_address, to ensure the employee’s address is correctly connected to the shop.

From table Employee, we have several connections with tables, Consultant, Customer_Support,
Supervisor, and Cashier. All of the tables, who are connected to the employee, have one unique
identifier or primary key and this is the employee_NR. We put the primary key on the number, to
ensure that each employee is correctly identified for the specific position. All of table fields with
SSN are connected to the Employee table via a foreign key.
Since the cashier sells the items, from Order_details, we have connected cash_ID to the table
Cashier via a foreign key. This is to see, which cashier has sold a specific product.

For the supervisor or manager, there are two tables that contain the description of their tasks.
The Sub_tasks table is connected to the Task table with a foreign key of task_id. The Sub_tasks
table contains information about the supervisor’s or manager’s daily shift.

And lastly, we have different categories of items, for instance, t-shirts, shoes, etc, which are in
table Category. It contains the item_ID, as a foreign key to the serial_number. This is to ensure
that every ordered item belongs to the specific category. In table Items, we have the information
regarding the specific item.

Table constraints:

Some specific table fields have certain constraints. For example, SSN and phone
number can take only up to 10 characters. For other table fields like names and
addresses, we have put a default constraint of 255 characters.

Schema:

You might also like