Database Design and Physical Architecture
Database Design and Physical Architecture
Description
A customer data management database is a centralized system that stores and manages customer
data, including contact information, purchase history, and interactions.
This system has made to lessen the hardship of the seller while using, editing and updating the
existing data. Moreover, this system is designed for the particular need of the seller to carry out
an update of information in a smooth and effective manner. This system reduce as much as
possible any errors while entering any data to this system.
Features
Easy in updating data
Organized Information
Effective at storing Data
Ensure Data Accuracy
Entities
Staff: is the person responsible for a majority of the interactions with the system and is
responsible for registering a customer after the initial purchase of the system, editing the profile
information of registered customers, adds a customer order, changes the status of the order
(which can be “pending”, “delayed” or “delivered”), searches for the customers profile, and edits
customer information stores in the database. In the database, Staff has a full name and a unique
login ID.
Order: is an entity that is altered when a customer’s order has changed and In a customer data
management system, order data is typically recorded and associated with customer profiles. This
data includes details such as order ID, Order date, products or services purchased, quantities,
pricing, and payment information. Orders are an integral part of customer data management as
they help track customer activities and purchase history.
Customers: are individuals or entities who interact with a business or clerk and provide their
personal information, preferences, and purchase history The system stores and manages
customer data to facilitate personalized experiences, targeted marketing, and customer data
management.
The constraints:
The staff is the only one who can register a new customer.
The staff is the only one who can add an order and change the order.
A customer can be registered by one and only one staff member.
Physical Database
User/Login
- Username: Varchar
- Password: Varchar
+ Verify Login()
Is
Clerk
- ID: Varchar
- Name: String
1..1 + Register() 1..1
+ Update()
+ Search()
+ Delete()
Registers Adds
1..n 1..n
Customer Order
-CustomerID: Int - OrderID: Int
-CustomerName: String - OrderType: String
- CustomerPhone:String - OrderQuantity: Int
- CustomerAddress: - OrderDate: Date
String + Add()
-CustomerEmail: String + Update()
+ Register() + View()
+ Update()
Web Server
Application Server
web Application