Assignment 2. Database Implementation and Queries

Transcription

1 Faculty of Science ITECH006/5006 Database Management Systems Assignment 2 Database Implementation and Queries Due Date: Friday Week (See Course Description for further date and time). Objectives: To analyse and comprehend a provided ER diagram and Database Schema To implement a database based on the provided ER diagram and Database Schema To write required SQL statements to query the database Project Specification The management team of BigM now require a partial implementation of the design made in Assignment. In order to keep consistency between the assignments, database specification containing the ER diagram and the schema is provided in this document. You should create your database according to this documentation. Please make sure that your implementation is consistent with this design. This means that your table names (upper case), field names (mixed case, no spaces) and data types have to be according to the specifications provided in this document. The implementation phase includes writing SQL statements to create a database and its tables, populating the tables with data, writing a number of queries to create reports that can be used by the management team. Your database should contain sufficient data in each table (at least, 5 to 0 records in each table; some may require less or more) to demonstrate that your queries work. Specific Design Requirement There are a number of supertypes and subtypes (entities) in the ERD (see below). For example, for the supertype EMPLOYEE there are two subtypes FULLTIME and CASUAL. Also for the supertype PRODUCT there are two subtypes CD and OTHERPRODUCT. While an employee can work only fulltime or casual, a product can only be CD or other product. Thus, the relationship from a supertype to one of its subtype is one to one and there is an optional participation sign on the subtype side. Also, when an employee works as fulltime, he/she cannot work as casual, and vice versa. Similarly, when a product is a CD, it cannot be in an other product, and vice versa. Therefore, a special design requirement has to be observed as follows: An employee working fulltime in EMPLOYEE table can only be entered into FULLTIME table (i.e., trying to insert it into CASUAL table will show an error), An employee working casual in EMPLOYEE table can only be entered into CASUAL table (i.e., trying to insert it into FULLTIME table will show an error), A product designated as CD in PRODUCT table can only be entered into CD table (i.e., trying to insert it into OTHERPRODUCT will show an error), and A product designated as other product in PRODUCT table can only be entered into OTHERPRODUCT table (i.e., trying to insert into CD table will show an error). Page

2 Faculty of Science ITECH006/5006 Database Management Systems Implementation of the Database To implement the database system, you are required to a) provide SQL commands to create the database, its tables, the relationships of the tables b) Create a text file called YourStudentId-Create.sql (format xxxxxxx-create.sql) for example Create.sql that will provide SQL commands to: i. create a database called BigM[YourStudentID] (eg BigM300) ii. create all of the required tables for the database including their primary keys, foreign keys and the relationships of tables. c) Create a text file called YourStudentId-Insert.sql (format xxxxxxx-insert.sql) for example Insert.sql that will provide SQL commands to: i. insert sufficient data into each table you have created to test the queries (at least 5 to 0 records in each table; some table may require less or more). ii. You are required to include your full name as one of the employee and/or customer; but you can provide fake details for your address and contact. d) Create a text file called YourStudentId-Queries.sql (format xxxxxxx-queries.sql - for example Queries.sql) that contains all of the queries to display the following reports:. List of names and complete address of all employees sorted by their salary. Also indicate if the employee works fulltime or casual. 2. The date on which the most recent customer order has been made. The customer name and date of order will suffice. 3. List of all the store names and their addresses, sorted in dictionary order of the store name. 4. A list of all customers that have not placed an order yet. Displaying customer number and name will be sufficient. 5. A list containing the name of employees, which work as accountant. 6. A list containing the total quantity on hand for each product (product no and description) regardless of stores. 7. A list showing each product sold (picked) on or before May 20, 205. Show product number, name and quantity sold, sorted by product number and then quantity sold. 8. A list of CDs (show CD title, release date and price) whose price is less than or equal to the average CD price. 9. Increase each fulltime employee s salary by 7.5% and show the updated salary of all fulltime employees (name and salary). 0. Show all the artist names and CDs in which they appear, sorted by artist first name and then by last name and finally by CD title. Page 2

3 ITECH5006 Students Only. Make a list of all action movie CDs and their price in ascending order of price. Show the CD title and price. 2. A list of supervisors (employee id, name) and all of their subordinates (employee id, name). 3. Show the pay information (employee name, hours paid, amount paid) of all casual employees in the most recent pay date. Note: There are some general requirements when defining your select queries: You are required to adhere to the following output formatting conventions: Any query requiring names of people should be printed as GivenName FamilyName (e.g. John Smith) in a column labelled NAME Any query requiring addresses should be printed as Street, Suburb State Postcode (e.g. 23 Anzac Pde, Maroubra NSW 2038) in a column labelled ADDRESS All monetary values should be printed with a dollar symbol ($), two digits after the decimal point, and with space for 7 digits before the decimal point You must use consistent and legible formatting in laying out your SQL queries. Include (brief) comments for any query or procedure that uses an "unusual" approach. What to submit An electronic copy of your assignment should be submitted through Moodle and should include a copy of your report, completed according to the Federation University Australia Guide for the Presentation of Academic Work (available and the three files described in Implementation of the Database above. Your document should include: A copy of the SITE Assignment Coversheet that includes a copy of the plagiarism statement. A copy of the SQL statements required to: o create the database and tables; o insert sufficient sample data into each table to demonstrate that your queries work. o a report of the results from running the SQL queries by using Copy/paste of their output. A bibliography containing a list of all resources used to complete the assignment. If no resources, apart from the course materials, have been used please indicate this. Assessment Criteria Adhere to the specific design requirement given on Page (check the supplementary document for an example). How clear and well organised your presentation is. On the front page of your report you should include a list of acknowledgements of all people who have assisted you with this assignment including fellow students, along with a statement of completion. Page 3

4 Adherence to our standards. How clear and well organised your presentation is. You should write all the queries in consistent style and use indent format. Data correctness and quality. Please use appropriate data for your examples (e.g. do not use inappropriate person names) Joining of data from multiple tables should be completed using a WHERE statement only. JOINs are not to be used within any of the SQL statements. Use of any JOINs will result in 0 (zero) marks being allocated for each SQL statement that utilizes them. Please refer to the provided marking guide (below) to see the distribution of marks. Take it as a guide, but NOT as an exact distribution of marks. Assignment Resources: The Standard ER Diagram Relational Database Schema A supplementary document (from online) to help you how to implement the specific design requirement involving supertype and subtype entities in the ERD. Hint: you need to decide the order that tables need to be created; and the order of tables in which data need to be inserted into. Page 4

5 Page 5 STORE Str_Name Str_Phone Str_Fax Str_ StoreManagerID SupStore_Num Address_ID STOREDEPARTMENT StrDept_ID StrDept_Phone StrDept_ DeptSupervisorID Dept_ID EMPLOYEE Emp_ID Emp_FName Emp_LName Emp_Phone Emp_DoB Emp_StartDate Emp_TaxFNum StrDept_ID SupvisorID Address_ID_Postal Address_ID_Resident JobTime_ID DEPARTMENT Dept_ID Dept_Name JOBTYPE JobType_ID JobType_Name PAYSLIP Pay_ID Pay_date Pay_num_of_hours Pay_amount_gross Emp_ID ARTIST Artist_ID Artist_FName Artist_Lname Artist_DoB Artist_Website CDARTIST Artist_ID CDArtist_NumTracks CD CD_Title CD_Length CD_NumOfTracks CD_ReleaseDate CD_Price CD_ReorderLevel CD_CategoryID CDType_ID OTHERPRODUCT OthProd_Desc OthProd_Size OthProd_Price OthProd_brand OtherType_ID CATEGORY Category_ID Category_Desc INVENTORY ProductNum Inv_QntyOnHand Inv_QtyOrdered CUSTOMER Cust_Number Cust_Fname Cust_LName Cust_Phone Address_ID CUSTOMERORDER CustOrd_ID CustOrd_Date Cust_Number ORDERLINE CustOrd_ID OrdLn_DateArrived OrdLn_DatePicked OrdLn_Qnty has supervises supervises places managed by supervised by employs has starred by has has contains generates receives maintains is for generates receives is works is a is a PRODUCT ProdType_ID CASUAL FULLTIME Emp_ID Emp_salary_hourly JobType_ID CasualJob_ID Emp_ID Emp_salary_yearly JobType_ID FullTimeJob_ID ADDRESS Address_ID Address_St Address_City Address_State Address_Postcode Add_TypeID ADDRESSTYPE AddType_ID Add_Type has has relates JOBTIME JobTime_ID JobTime_Desc works PRODUCTTYPE ProdType_ID ProdType_Desc has JOBFULLTIME FullTimeJob_ID JOBCASUALTIME CasualJob_ID is is CDTYPE CDType_ID OTHERTYPE OtherType_ID is works is is

6 Notes for the ERD: Primary keys are underlined and foreign keys are made italic (also coloured for easy identification). Supertype and subtype relationships are: EMPLOYEE to FULLTIME and CASUAL and PRODUCT to CD and OTHERPRODUCT. 2. Relational Database Schema Relation Attributes Data type Comment ADDRESSTYPE AddType_ID Primary Key, Expected examples R for residential, P for postal and B for both res. & pos. Add_Type VARCHAR(5) Cust_Number Primary Key, Auto Increase Cust_FName VARCHAR(30) CUSTOMER Cust_LName VARCHAR(30) Cust_Phone CHAR(0) Includes area code Address_ID ADDRESS (Address_ID) Address_ID Primary Key, Auto Increase Address_St VARCHAR(50) e.g., 52 Temple St ADDRESS Address_City VARCHAR(30) e.g., Ballarat Address_State VARCHAR (3) Examples VIC, NSW Address_Postcode CHAR(4) Examples 3350, 200 Add_TypeID ADRESSTYPE(AddType_ID) JOBTYPE JobType_ID Primary Key, Auto Increase JobType_Name VARCHAR(30) e.g., Accountant Page 6

7 Artist_ID Primary Key, Auto Increase ARTIST Artist_FName Artist_LName VARCHAR(30) VARCHAR(30) Artist_DoB DATE Format: YYYY-MM-DD Artist_Website VARCHAR(00) CATEGORY Category_ID VARCHAR(5) Primary Key, example, M for music, AM for action movies Category_Desc VARCHAR(40) e.g., Music, Adult movies DEPARTMENT Dept_ID Primary Key, Auto Increase Dept_Name VARCHAR(40) e.g., Sales, Training, Payroll Primary Key, Auto Increase Str_Name VARCHAR(50) e.g., BigM Ballarat Str_Phone CHAR(0) Includes area code Str_Fax CHAR(0) Includes area code STORE Str_ StoreManagerID VARCHAR(40) EMPLOYEE(Emp_ID) SupStore_Num STORE() Address_ID ADDRESS (Address_ID) StrDept_ID Primary Key, Auto Increase STOREDEPARTMENT StrDept_Phone CHAR(0) Includes area code StrDept_ VARCHAR(40) DeptSupervisorID EMPLOYEE(Emp_ID) Page 7

8 Dept_ID STORE() DEPARTMENT (Dept_ID) JOBTIME PRODUCTTYPE JobTime_ID Primary Key, expected F for fulltime and C for casual JobTime_Desc VARCHAR(0) e.g., fulltime, casual ProdType_ID Primary Key, expected C for CD and O for Other product ProdType_Desc VARCHAR(30) e.g., CD and Other product Emp_ID Primary Key, Auto Increase Emp_FName Emp_LName VARCHAR(30) VARCHAR(30) Emp_Phone CHAR(0) Includes area code Emp_DoB DATE Format: YYYY-MM-DD Emp_StartDate DATE Format: YYYY-MM-DD Emp_TaxFNum CHAR(2) e.g., EMPLOYEE StrDept_ID STOREDEPARTMENT (StrDept_ID) SupvisorID EMPLOYEE(Emp_ID) Address_ID_Postal ADDRESS (Address_ID) Address_ID_Resident ADDRESS (Address_ID) JobTime_ID JOBTIME (JobTime_ID) JOBFULLTIME FullTimeJob_ID Primary Key Page 8

9 JOBCASUALTIME CasualJob_ID Primary Key Emp_ID reference EMPLOYEE(Emp_ID) Emp_salary_yearly DOUBLE(0,2) e.g., 0, FULLTIME JobType_ID JOBTYPE (JobType_ID) FullTimeJob_ID NOT NULL, DEFAULT F, JOBFULLTIME (FullTimeJob_ID) Emp_ID reference EMPLOYEE(Emp_ID) Emp_salary_hourly DOUBLE(0,2) e.g., CASUAL JobType_ID JOBTYPE (JobType_ID) CasualJob_ID NOT NULL, DEFAULT C, JOBCASUALTIME (CasualJob_ID) Pay_ID Primary Key, Auto Increase Pay_date DATE Format: YYYY-MM-DD Pay_num_of_hours DOUBLE(4,2) e.g., PAYSLIP Pay_amount_gross DOUBLE(6,2) e.g., Emp_ID EMPLOYEE(Emp_ID) STORE() CDTYPE CDType_ID Primary Key OTHERTYPE OtherType_ID Primary Key Page 9

10 Primary Key, Auto Increase PRODUCT ProdType_ID PRODUCTTYPE (ProdType_ID) reference CD () CDARTIST Artist_ID Primary Key, Foreign key reference ARTIST (Artist_ID) CDArtist_NumTracks reference PRODUCT () CD_Title VARCHAR(50) CD_Length TIME Format: 'HH:MM:SS' CD_NumOfTracks CD CD_ReleaseDate DATE Format: YYYY-MM-DD CD_Price DOUBLE(4,2) e.g., CD_ReorderLevel VARCHAR(0) CD_CategoryID VARCHAR(5) CATEGORY (Category_ID) CDType_ID NOT NULL, DEFAULT C, CDTYPE (CDType_ID) reference PRODUCT () OTHERPRODUCT OthProd_Desc VARCHAR(50) e.g., Pant for man, skirt for girl OthProd_Size VARCHAR(0) e.g., Large, Medium, etc. OthProd_Price DOUBLE(4,2) e.g., 0.50 Page 0

11 OthProd_brand VARCHAR(20) e.g., Masters, Century OtherType_ID NOT NULL, DEFAULT O, OTHERTYPE (OtherType_ID) ProductNum reference PRODUCT () INVENTORY reference STORE () Inv_QntyOnHand Inv_QtyOrdered CustOrd_ID Primary Key, Auto Increase CustOrd_Date DATE Format: YYYY-MM-DD CUSTOMERORDER Cust_Number CUSTOMER (Cust_Number) STORE () CustOrd_ID reference CUSTOMERORDER (CustOrd_ID) ORDERLINE reference PRODUCT () OrdLn_DateArrived DATE Format: YYYY-MM-DD OrdLn_DatePicked DATE Format: YYYY-MM-DD OrdLn_Qnty End of specification. Page

12 Assignment 2 Marking Overview Documentation /5 Create statements /5 insert statements /5 Queries /45 ITECH5006 Queries /5 Total: ITECH006 /80 ITECH5006 /95 Page 2

13 ITECH5006 Assignment 2 Marking Guide Student name: Student ID: Marker: ITEM Max Mar k Documentation /5 document well laid out and easy to read contains a coversheet or front page contains a table of contents and is set out according to the university guidelines contains all of the required components of the assignment bibliography included in APA format Create statement /5 Create table, Create (all/most/some/no) of the relevant new tables 4 relationship, Database correctly named and created (Includes own name and number) 3 correct Includes all of the PKs and FKs and relationships in the database 2 supertypesubtype No evidence that tables have been created using the GUI Maintains the specific design requirement for supertype and subtype 3 design They work properly 2 Insert statement /5 Insert, correct Successfully inserts data into (all/most/some/no) of the tables Includes own details as one of the customers 2 2 supertypesubtype NO evidence exporting from GUI INSERT file includes primary keys 2 design Maintains the specific design requirement for supertype and subtype 2 They work properly Sufficient data SQL Queries Q Q2 Q3 Q4 Q5 Contains (sufficient/some/no) data to test (all/some/no) of the queries (thoroughly/ only with limited entries/no entries) 5 /45 - appropriate statement formatted as per instructions (e.g., name and 5 address) - correct joins and where clause - appropriate ORDER BY - appropriate statement formatted as per instructions (e.g., name) - correct joins - appropriate statement formatted as per instructions (e.g., address) - correct joins and ORDER BY - appropriate statement formatted as per instructions (e.g., name) - correct subquery - appropriate statement - correct joins and union Q6 - correct statement according to the description (AS [Total: ]) Page 3

14 - correct joins and where clause - Includes required GROUP BY Q7 - correct statement according to the description 5 - Correct use of joins and ORDER BY - Includes required GROUP BY Q8 - appropriate statement 4 - correct use of sub-query Q9 - correct statement formatted as per instructions (e.g., name, $ salary) 5 - correct joins & where clause Q0 - correct statement according to the description 4 - correct joins and ORDER BY ITECH5006 ONLY 5 Q - correct statement formatted as per instructions (e.g., $ price) 4 - correct joins and ORDER BY Q2 - correct statement formatted as per instructions (e.g., name) - correct joins 5 Q3 General Comment: - correct statement and formatting (e.g., $ payment) - correct joins - Includes required sub-query Total ITECH 5006 /95 Total ITECH006 /80 Weight /20% 6 Page 4