Scribd
Upload
10 views

A Database

Uploaded by

honganhp0903
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
10 views

A Database

Uploaded by

honganhp0903
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

PROJECT NAME: BIKESTORES INFORMATION MANAGEMENT

SYSTEM: A COMPREHENSIVE OVERVIEW


Group members Student ID
Nguyễn Thị Mai Anh 23070612
Phạm Thị Linh 22070519
Phạm Hồng Anh 23070678
Phạm Tiến Phú 19071623

STEP 1: CREATE A DOCUMENT (.DOCX OR .PDF FILE), WRITE A


DETAILED DESCRIPTION OF THE SYSTEM THAT NEEDS TO BE
BUILT.
I. Requirements:
A comprehensive Bike Store Management System must ensure efficient
management of key aspects such as product information, customer details,
supplier data, sales transactions, inventory, and financial reporting. Below are
the detailed requirements for the system:
1. Product Information Management:
 Product Details:
o Store detailed information for each product, including product code,
name, type (e.g., mountain bikes, road bikes, electric bikes),
specifications, color, price, and inventory quantity.
o Support categorization of products by type or features for easier
management.
2. Customer Information Management:
 Customer Data:
o Maintain customer information such as customer ID, full name,
address, phone number, email, and purchase history.
o Manage loyalty program details and apply discounts or rewards for
loyal customers.
3. Supplier Management:
 Supplier Records:
o Store information about suppliers, including supplier ID, company
name, address, contact details, and transaction history.
o Track products sourced from each supplier and monitor contract
status.
4. Sales Transaction Management:
 Transaction Details:
o Record all sales transactions, including transaction ID, date, sold
products, quantities, total value, and payment methods (cash, credit
card, bank transfer, etc.).
o Generate invoices automatically and update inventory immediately
after each transaction.
5. Inventory Management:
 Stock Tracking:
o Monitor inventory levels for each product type, detect low stock
levels, and alert staff to reorder.
o Manage stock entries and withdrawals, including date, product code,
quantity, and associated suppliers.
6. Warranty and After-Sales Service Management:
 Warranty Details:
o Record warranty information for each sold product, including
warranty period, conditions, and service history.
o Track warranty claims and provide after-sales services effectively.
7. Reporting and Analytics:
 Business Reports:
o Generate detailed reports on revenue, profit, sold quantities, inventory
levels, and supplier performance.
o Provide analytics on loyal customers, best-selling products, and
purchasing trends.
8. User Management:
 User Roles and Permissions:
o Support role-based access control for staff such as sales personnel,
inventory managers, store managers, and accountants.
o Log user activities to ensure data security and transparency.
9. Integration and Connectivity:
 System Integration:
o Integrate with online payment systems device.
o Connect with logistics or delivery management systems if required.
10. Additional Features:
 Search and Filter Functions: Provide quick search and filtering options
based on criteria like product name, customer name, or supplier name.
 User Interface: Design a user-friendly interface that is easy to navigate
and supports multiple languages if needed.
=> This system ensures efficient management of store operations,
minimizes errors, and enhances the overall operational performance of the
bikestores.
II. Analyze the requirement:
To design a database for the Bike Store Information Management System based
on the requirements, we need to break down the requirements into the core
entities, relationships, attributes, and constraints. Here’s a step-by-step analysis
that leads to identifying key elements for the database design:
1. Identify Core Entities
Entities are the main objects or components that we need to manage in the
library system. Based on the requirements, the primary entities are:
 Customer: Represents individuals who purchase bikes or accessories.
 Product: Includes bikes, accessories, and related items.
 Store: Locations where products are sold.
 Staff: Employees managing sales.
 Order: Tracks customer purchases, details of items within an order.
 Supplier: Entities supplying products to the store.
 Inventory: Tracks product stock levels
2. Identify Attributes
Each entity will have a set of attributes that store the details related to that entity.
 Customers Table:
o CustomerID (Primary Key): Unique identifier for each customer.
o FirstName: First name of the customer.
o LastName: Customer's last name.
o DateOfBirth: Date of birth of the customer.
o Email: Email address of customer.
o Phone: Contact number of the customer.
o Address: Residential address of customer.
 Products Table:
o ProductID (Primary Key): Unique identifier for each product.
o ProductName: Name of the product.
o Brand: Represents manufacturers of the products.
o CategoryName: Groups of products (e.g., Mountain Bikes, Road
Bikes, Helmets).
o Price: Price of the product.
 Stores Table:
o StoreID (Primary Key): Unique store identifier.
o StoreName: Name of the store.
o Address: Store address.
 Staff Table:
o StaffID (Primary Key): Unique Staff identifier.
o StoreID (Foreign Key): Refers to the store where the staff works
o FirstName: Staff’s first name
o LastName: Last name of the staff.
o DateOfBirth: Date of birth of the staff.
o Email: Staff’s email.
o Phone: Contact number of the staff.
 Orders Table:
o OrderID (Primary Key): Unique identifier for each order.
o CustomerID (Foreign Key): Refers to the customer who placed the
order.
o StoreID (Foreign Key): Referring to the store where the customer
placed the order.
o StaffID (Foreign Key): Refers to the employee who performs the
transaction.
o ProductID (Foreign Key): Refers to the product that is ordered.
o OrderDate: Date of the order.
o Quantity: Quantity of product ordered.
o UnitPrice: Price per unit product.
 Suppliers Table:
o SupplierID (Primary Key): Unique identifier for each supplier.
o SupplierName: Name of the supplier.
o Phone: Contact number of the supplier.
o Email: Email address of the supplier.
 Inventory Table:
o StoreID (Foreign Key): Refers to the store where the product is
stored.
o ProductID (Foreign Key): Refers to the product that is available in
the store.
o Quantity: Quantity available.

You might also like