Database of Auto Parts Warehouse Design

Content

1. Description of the application and its users
1.1 User (Predefined and Specified in Section 6):
1.2 Process
1.3 Data Flow of Diagram of Database design
1.4 Scope Define:
1.5 A

2. Conceptual and physical design of your database
2.1 Entity Relationship Diagram
2.2 Relationship E

3. Explanation of transactions that impact the database and their SQL

4. Documentation of all integrity rule
4.1 Primary and Foreign key
4.2 Customer, Staff, Part, Vendor name cannot be null
4.3 Email must be unique
4.4 Price and Quantity should be larger than
4.5 When manager stock new part from vendor, the inventory number (Onhand) in Part table and the quantity in the PartSupportInfo table should be updated correspondently
4.6 When manage stock new part, the part id and vendor id should be on the part list and vendor list
4.7 When updating CarPartInfo table Car ID should be on the list of Car table
4.8 Each Customer can only purchase same part less than 10 within same

5. Documentation of all

6. Documentation of users and their role
6.1 Web Customer
6.2 Customer Represent
6.3 Staff Manager
6.4 Database A

7. Documentation of test result
7.1 Data integrity test
7.2 Functional

8. Disaster recovery plan of AutoParts Warehouse
8.1 Create T_SQL statement for backup and restore
8.2 Backup S

9. Documentation of the data warehouse and its purpose
9.1 Inventory statistic
9.2 Geographic Information
9.3 Data Mining S

Appendix I – SQL Script of all