VIETNAM NATIONAL UNIVERSITY HO CHI MINH CITY

UNIVERSITY OF INFORMATION TECHNOLOGY

REPORT

DATABASE SYSTEM DESIGN,

MANAGEMENT AND ADMINISTRATION

Student name: Dang Quoc Khoa

ID: 18520911

Ho Chi Minh City, 6/2021.

THANK YOU
 Teacher's comments

……………………………………………………………………………………………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………
………………………………………………………………………………….………………………………………

………,Day…..Month…..Year…..
Confirm
 MENU
Part I. INTRODUCTION............................................................................................1
1. Abtract................................................................................................................... 1
1.1. Problem............................................................................................................1
1.2. Solution............................................................................................................1
2. Project purpose.....................................................................................................1
Part II. REQUIREMENT SPECIFICATION............................................................2
1. Funtional requirement..........................................................................................2
1.1. Manage employee.............................................................................................2
1.2. Add employee...................................................................................................2
1.3. Edit employee...................................................................................................2
1.4. Delete employee...............................................................................................2
1.5. Manage customer.............................................................................................3
1.6. Add customer....................................................................................................3
1.7. Edit customer....................................................................................................3
1.8. Delete customer................................................................................................3
1.9. Manage product...............................................................................................3
1.10. Add product....................................................................................................3
1.11. Edit product....................................................................................................3
1.12. Delete product................................................................................................3
1.13. Manage bill.....................................................................................................3
1.14. Add bill...........................................................................................................4
1.15. Edit bill...........................................................................................................4
1.16. Delete bill.......................................................................................................4
 2. Non-functional requirement.................................................................................4
2.1. Product requirements.......................................................................................4
2.2. Organizational requirements............................................................................5
2.3. External requirements......................................................................................5
Part III. DESIGN SPECIFICATION.........................................................................6
1. Use-case diagram...................................................................................................6
2. Data flow diagram.................................................................................................7
3. Class diagram........................................................................................................8
4. Entity Relationship diagram................................................................................9
5. Relational schema................................................................................................10
6. Database schema.................................................................................................10
7. Data object...........................................................................................................11
8. Data dictionary....................................................................................................13
Part IV. TRIGGER....................................................................................................13
1. Trigger 1..............................................................................................................13
2. Trigger 2..............................................................................................................14
3. Trigger 3..............................................................................................................14
4. Trigger 4..............................................................................................................15
5. Trigger 5..............................................................................................................16
6. Trigger 6..............................................................................................................17
Part V. PROCEDURE...............................................................................................18
1. Procedure 1..........................................................................................................18
2. Procedure 2..........................................................................................................19
3. Procedure 3..........................................................................................................19
 4. Procedure 4..........................................................................................................20
Part VI. FUNCTION..................................................................................................21
1. Function 1............................................................................................................21
2. Function 2............................................................................................................21
3. Function 3............................................................................................................22
4. Function 4............................................................................................................22
Part VII. USER INTERFACES................................................................................23
1. Main form............................................................................................................23
2. Product management form.................................................................................24
3. Bill management form........................................................................................25
4. Customer management form..............................................................................26
5. Employee management form..............................................................................26
Part VIII. SUMMARY...............................................................................................27
1. Difficulty..............................................................................................................27
2. Development........................................................................................................27
3. Conclusion...........................................................................................................27
Part IX. REFERENCES:...........................................................................................28
FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

Part I. INTRODUCTION

1. Abtract
1.1. Problem
Society is developing and people's need to enjoy life is increasing, besides the needs for food, fashion,
transportation, ... the beauty needs are also being special. special interest. So cosmetics is one of the
essential products everywhere and it is for both men and women. Cosmetic stores are increasingly
appearing on a large scale and store management becomes more difficult. And MIN Cosmetic(store)
also has a lot of problems in doing business with traditional methods.

The first problem is product management. Diverse types, brands and suppliers of cosmetics make you
a headache when remembering the name, price, and quantity of each product in the cosmetic shop.
It even leads to deviations in the store's sales management process. The second is about business
reporting. Do you often travel for work or travel, so you cannot be at the store 24/24? You want to
know the specific sales of each day, the transaction history of each type of cosmetic item, the sales of
each employee. More important, we will have a hard time taking care of our customers. Maybe the
store's customer data is too big? How to manage customer information well? How to make customers
loyal to your cosmetic shop? So there are many other problems in the process of store management
whether large or small.

1.2. Solution
The information system was created for the purpose of helping investors to reduce the required
human resources, improve the accuracy in product management and purchase. We can quickly and
efficiently manage the store and make it easier for the manager to do the following:

 Product management.
 Customer management.
 Employee management.
 Sale management.

2. Project purpose
Building Windows-Form application that meets the following requirements:

 Update data into system quickly, safe storage capacity.

 Statistics of revenue per month, per year.
 Statistics of customer needs, products customers are most interested in.
 Product management (Price, Quantity).
 Sale management (Bill, Payment's information, Voucher...).
 Customer management (Customer's information, Payment's history).
 Employee management (Employee's information, Bill created by employees).

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

Part II. REQUIREMENT SPECIFICATION

1. Funtional requirement
Add Pic Here

1.1. Manage employee

 Initial condition: Admin must be properly logged in to the system.
 Normal: Admin can manage all information related to Employee.

1.2. Add employee

 Initial condition: Admin must be properly logged in to the system.
 Normal: When we hire a new employee and he/she join with us, the information of
employee will be entered into the system.

1.3. Edit employee

 Initial condition: Admin must be properly logged in to the system.
 Normal: If have a wrong information, we have to update information.

1.4. Delete employee

 Initial condition: Admin must be properly logged in to the system.
 Normal: If we don’t need to storage the employee or he/she resigned from job
forever.

1.5. Manage customer

 Initial condition: Admin must be properly logged in to the system.
 Normal: Admin can manage all information related to Customer.

1.6. Add customer

 Initial condition: Admin must be properly logged in to the system.
 Normal: When we have a new customer and he/she have bill in our store, the
information of customer will be entered into the system.

1.7. Edit customer

 Initial condition: Admin must be properly logged in to the system.
 Normal: If have a wrong information, we have to update information.

1.8. Delete customer

 Initial condition: Admin must be properly logged in to the system.
 Normal: If we don’t need to storage the customer or he/she has never come back.

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

1.9. Manage product

 Initial condition: Admin must be properly logged in to the system.
 Normal: Admin can manage all information related to Product.

1.10. Add product

 Initial condition: Admin must be properly logged in to the system.
 Normal: When we have a new product, we need to storage product information.

1.11. Edit product

 Initial condition: Admin must be properly logged in to the system.
 Normal: If have a wrong information, we have to update information of product, or it
have the promotion program.

1.12. Delete product

 Initial condition: Admin must be properly logged in to the system.
 Normal: If we don’t need to storage the information of product or we no longer sell
it.

1.13. Manage bill

 Initial condition: Admin must be properly logged in to the system.
 Normal: Admin can manage all information related to Bill.

1.14. Add bill

 Initial condition: Admin must be properly logged in to the system.
 Normal: When we have a new bill, the information of bill will be entered into the
system.

1.15. Edit bill

 Initial condition: Admin must be properly logged in to the system.
 Normal: If have a wrong information, we have to update information, or it can be
change when the customer want to buy more or decrease the number of a certain
product.

1.16. Delete bill

 Initial condition: Admin must be properly logged in to the system.
 Normal: If we don’t need to storage the bill or the customer cancel this bill.

2. Non-functional requirement
2.1. Product requirements

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

Requirement Description

2.2. Organizational requirements

Requirement Description

2.3. External requirements

Requirement Description

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

Part III. DESIGN SPECIFICATION

1. Use-case diagram

2. Data flow diagram

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

3. Class diagram

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

4. Entity Relationship diagram

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

5. Relational schema

6. Database schema

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

7. Data dictionary

Table Description Example

Part IV. TRIGGER

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

Part V. PROCEDURE

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

Part VI. FUNCTION

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

Part VII. SUMMARY

1. Difficulty
2. Development
3. Conclusion

STUDENT: DANG QUOC KHOA

FINAL PROJECT INSTRUCTOR: NGUYEN THI KIM PHUNG

Part VIII. REFERENCES:

[1] “How to call oracle function using C#?”

https://social.msdn.microsoft.com/Forums/en-US/ee5b723c-a2e5-47ce-b96d-c896975c1e34/
how-to-call-oracle-function-using-c?forum=adodotnetdataproviders (accessed Jun. 29, 2021).
[2] “Connecting To Oracle Database Using C#.”
https://www.c-sharpcorner.com/uploadfile/cb92fb/connecting-to-oracle-database-through-c-
sharp/ (accessed Jun. 29, 2021).
[3] “Calling Oracle stored procedures from Microsoft.NET.”
https://www.c-sharpcorner.com/article/calling-oracle-stored-procedures-from-microsoft-net/
(accessed Jun. 29, 2021).

--The end--

STUDENT: DANG QUOC KHOA