Part 1 of README
This commit is contained in:
commit
7c0ebf944c
69
README.md
Normal file
69
README.md
Normal file
@ -0,0 +1,69 @@
|
||||
# Exam 1 - Queen Anne Curiosity Shop
|
||||
|
||||
## Instructions
|
||||
- Answer Questions A through G found on pages 187-189 in Chapter 3 for the Queen Anne Curiosity Shop.
|
||||
- Answer Questions A through G found on pages 209-210 in Chapter 4 for the Queen Anne Curiosity Shop.
|
||||
- Answer Questions A and B found on page 262 in Chapter 5 for the Writer's Patrol Case.
|
||||
- Answer Questions A through E found on page 265 in Chapter 5 for the Queen Anne Curiosity Shop.
|
||||
- Answer Questions A through E found on page 321 in Chapter 6 for the Queen Anne Curiosity Shop.
|
||||
- Deliver a single sql file, along with a document that contains all the content from the sql file.
|
||||
- Do not include the result table unless specifically directed to.
|
||||
- Include at least one line of white space between answers.
|
||||
|
||||
## Questions A-G in Chapter 3
|
||||
|
||||
### Data
|
||||
|
||||

|
||||

|
||||
|
||||
### Questions
|
||||
A.) Using these data, state assumptions about functional dependencies among the columns of data. Justify your assumptions on the basis of these sample data and also on the basis of what you know about retail sales.
|
||||
|
||||
B.) Given your assumptions in part A, comment on the appropriateness of the following designs:
|
||||
1. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem, Price, Tax, Total)
|
||||
2. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem, Price, Tax, Total)
|
||||
3. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem, Price, Tax, Total)
|
||||
4. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem, Price, Tax, Total)
|
||||
5. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem, Price, Tax, Total)
|
||||
6. CUSTOMER (LastName, FirstName, Phone, EmailAddress)
|
||||
and
|
||||
SALE (InvoiceDate, InvoiceItem, Price, Tax, Total)
|
||||
7. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate)
|
||||
and
|
||||
SALE (InvoiceDate, InvoiceItem, Price, Tax, Total)
|
||||
8. CUSTOMER (LastName, FirstName, Phone, EmailAddress, InvoiceDate, InvoiceItem)
|
||||
and
|
||||
SALE (InvoiceDate, InvoiceItem, Price, Tax, Total)
|
||||
|
||||
C.) Modify what you consider to be the best design in part B to include surrogate ID columns called CustomerID and SaleID. How does this improve the design?
|
||||
|
||||
D.) Modify the design in part C by breaking SALE into two relations named SALE and SALE_ITEM. Modify columns and add columns as you think necessary. How does this improve the design?
|
||||
|
||||
E.) Given your assumptions, comment on the appropriateness of the following designs:
|
||||
1. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor, Phone)
|
||||
2. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor, Phone)
|
||||
3. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor, Phone)
|
||||
4. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor, Phone)
|
||||
5. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate)
|
||||
and
|
||||
VENDOR (Vendor, Phone)
|
||||
6. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor)
|
||||
and
|
||||
VENDOR (Vendor, Phone)
|
||||
7. PURCHASE (PurchaseItem, PurchasePrice, PurchaseDate, Vendor)
|
||||
and
|
||||
VENDOR (Vendor, Phone)
|
||||
|
||||
F.) Modify what you consider to be the best design in part E to include surrogate ID columns called PurchaseID and VendorID. How does this improve the design?
|
||||
|
||||
G.) The relations in your design from part D and part F are not connected. Modify the database design so that sales data and purchase data are related.
|
||||
|
||||
|
||||
## Questions A-G in Chapter 4
|
||||
|
||||
## Questions A and B in Chapter 5
|
||||
|
||||
## Questions A-E in Chapter 5
|
||||
|
||||
## Questions A-E in Chapter 6
|
||||
BIN
images/QACS-Ch3-img1.png
Normal file
BIN
images/QACS-Ch3-img1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 114 KiB |
BIN
images/QACS-Ch3-img2.png
Normal file
BIN
images/QACS-Ch3-img2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 147 KiB |
Loading…
x
Reference in New Issue
Block a user