T1 2020 ISY1002 ISY103 DBM Group Project Outline.pdf Unit ISY1002/ISY103 Database Management for Business Assessment Type Group Assignment Database Project, Report and Individual Video Presentation...

1 answer below »
have you got the file



T1 2020 ISY1002 ISY103 DBM Group Project Outline.pdf Unit ISY1002/ISY103 Database Management for Business Assessment Type Group Assignment Database Project, Report and Individual Video Presentation Assessment Number 3 Assessment Weighting 40% Total Marks 100 Alignment with Unit and Course Unit Learning Outcome ULO2: Show an understanding of the fundamentals of database design, implementation, management, and maintenance, including consideration of appropriate data security ULO3: Implement a relational database using the Structured Query Language (SQL) Data Definition Language (DDL) ULO4: Demonstrate an ability to query a relational database using Structured Query Language (SQL) and Data Manipulation Language (DML) Graduate Attributes Assessed GA1:Communication GA2: Collaboration GA4: Critical Thinking & Problem Solving GA5: Flexibility Due Date/Time End of Week 8 10 & 11 refer Moodle for date and time. 1 | P a g e 2 | P a g e Aim: To give you practical experience in database modelling, normalization and writing SQL statements to query a relational database Assignment Summary: The project specification details provided in this document and you must use only given specifications to come up with your solution. Make appropriate assumptions where ever required. Please make sure that your group must meet your lecturer/tutor at least twice to update the progress of your assignment. Students require to submit 5 minutes individual video presentation, incuding slides to Moodle. Background Information for Sample Database Project: Australian Manufacturing Company (AMC) requires a database system to manage their stores, employees, products, suppliers, patrons and orders. The following information has been gathered about current business activities of AMC. AMC has many stores in different cities across Australia. Each store has unique store number and other details like name, contact details (phone number, email address and fax number) and location details (postal address composed of street number, suburb, state and postcode). There are many departments within each store, for example, HR, accounts, finance and sales etc. each department is uniquely identified by department number. AMC also records department title, phone number and email address. Each store has a number of employees. Each department is supervised by a department supervisor and each store is managed by a store manager who both are employees of AMC. Each department has a single supervisor only i.e. the department supervisor is also the supervisor for all the employees work within that department. Each employee is referenced by unique employee number, name (first and last names), address, mobile number, email, TFN, salary and joining date. An employee s salary is recorded differently as per his or her employment type. Employees can be employed as fulltime or casual basis. For a fulltime staff, annual salary is recorded and hourly rate for a casual staff. Each store creates payslips for all employees work in that store on a weekly basis. As a minimum payslip number, no of hours worked, employee detail, store detail and gross pay are recorded. AMC sales different products like fashion, health, beauty, electronics etc. Each product is characterised by product number, name, brand, description and price. Each product can be supplied by one or more supplier and each supplier can supply one or many products. AMC also keeps appropriate details of their suppliers. Each store maintains an inventory of their products available for sale. The quantity of each product available in store and the quantity ordered are kept. AMC patron visits the store and shops in the store. Each customer is characterised by customer number, name (first and last names), mobile number and address. A patron may place orders. An order contains one or many products at a time. A store keeps track of order number, order date, product(s) ordered and quantity ordered for each product. 3 | P a g e The proprietors of AMC have appointed your group as Database System Consultant to analyse, design and develop conceptual data model and physical database. They want a software/online application in future to be built on the database you design so that the operation of the AMC is greatly improved. Your created models must accommodate the provided requirements. It is understandable that the provided information may not sufficient to create model that centralise all the data appropriately. You are free to make assumptions about their business activities if require. Make sure you record your assumptions. System Requirements: The system is a prototype system and as such is not a full production version. You will be required to enter a representative sample data into your tables in order to test the design and operation of your database. Project Specification: 1. Part A: Entity Relationship Diagram (20 marks) 1. Your first task is to study the Case study requirements and gather as much knowledge to list all the main Entities and attributes. 2. Create an Entity Relationship Diagram (ERD) to help you decide on the relationships. Your entity relation diagram that models your database design should: i. Include all entities, relationships (including names) and attributes. ii. Identify primary and foreign keys. iii. Include cardinality/ multiplicity and show using cro s feet or UML notation. iv. Include participation (optional / mandatory) symbols if applicable. The ERD should be created as part of a Microsoft Word document. Hand-drawn diagrams will not be accepted. It is recommended that you complete your ERD using Draw.io, Visio or try www.gliffy.com (Search for ERD gliffy to get started). 2. Part B: Normalisation (5 marks) 1. Normalise all entities and relationships in optimal normal form. Provide the normalised schema and discuss the level of normalisation achieved for each relation. You goal should be normalise all entities in 3NF. Provide the reasons for any relation that is not maintained in 3NF. 3. Part C: Relational schema and PostgreSQL database (20 marks) 1. Create relational schema that matches ERD and normalised schemas you created in Part A and B. The schema should include suitable data validation, integrity and referential integrity constraints, for example, types and length of attributes, primary and foreign keys etc. Make sure you follow standards, naming conventions and notation. (5 Marks) 4 | P a g e 2. Using PostgreSQL, you are required to develop a demonstration prototype system (database) that stores data for AMC stores, employees, products, suppliers, patrons and orders. Create a new database called AMCDB. Create tables according to your relational schema created in step 1. (10 Marks) Follow a standard naming convention for table names and also field names. Avoid using spaces and any special characters in table and field names. Use underscore_case or use camelCase to separate parts of a name. You are required to be consistent in tabl name, fiel name, data types, field size and key constraints with relational schema created in step 2. 3. Add at least three records into each table. (5 Marks) 4. Part D: SQL (24 marks) Use the AMCDB database that you created in PostgreSQL to design and execute SQL queries that answer the following questions. Number your answers to each question clearly. The answer to each question must be tabulated as shown in the example below and include the SQL statement and also the output that is produced when you execute the statement in your database. The output includes the records that are listed and also the message that appears when you run the SQL statement. For example: Question 1: SQL: SELECT lName, position FROM Staff WHERE salary > 20000; Output: +-------+----------+ | lName | position | +-------+----------+ | Brand | Manager | | White | Manager | +-------+----------+ 2 rows in set (0.03 sec) Do not use screen captures to display the SQL statement or the output. You should right-click on the PostgreSQL Command Prompt window; choose SQL statement and Output, to Copy and then Paste into your Word document that includes the answers to all questions. Format and indent the clauses in your SQL statements for better readability and understanding as shown in the example above. Statements must be syntactically and semantically correct. Format both the SQL and also the Output in Courier New 10 or 11 point. 5 | P a g e 1. List the full name of Patrons, phone number and address in the descending order of customer number. The full name is comprised of first and last name joined with single space. Use the alias Customer full name for the composed column heading. (2 marks) 2. List all the products having price less than $100. (2 marks) 3. List the product number, product title, quantity ordered, unit price and total amount per product (unit price * quantity ordered) for order having order number 1005. (3 marks) 4. List name, full address and fax number of stores that has the word George anywhere in the street component of address. Your query should consider the case sensitivity of the street as well i.e. the stores with words George , GEORGE , george , Geo etc. in street should be returned by your query too. (2 marks) 5. List all the
Answered Same DayMay 06, 2021ISY103

Answer To: T1 2020 ISY1002 ISY103 DBM Group Project Outline.pdf Unit ISY1002/ISY103 Database Management for...

Deepti answered on May 10 2021
155 Votes
Australian Manufacturing company database
Contents
Introduction    2
Part A: Entity Relationship Diagram (Draw.io)    3
Part B: Normalized Schema    4
Part C: Relational Schema    5
Database Schema    9
Describe Statements    9
Select Statements    11
Foreign Key Constraints    13
Part D: SQL Queries    14
Part E: Report    18
References    18
Introduction
The target Company AMC is a manufacturing company with stores located in various cities in Australia. They require an efficient central
ized system to manage their chain stores. Subsequently, they need to manage information about their patrons, employees, products, orders and suppliers. The owners of the company intend to improve the AMC operations with the help of an online software application. In order to fulfil this purpose, they require analysis, designing and development of conceptual model of the proposed system and its physical database. This report covers all the aspects of the conceptual data model and physical database of AMC. The assumptions that were made during the analysis of the system are
· A supervisor is an employee and can supervise single department. It is assumed that a store manager may supervise a department witin the same store where he/she is employed. The Employee table can be normalized to 3rd NF over department ID.
· Employment types Full and Casual shall determine the salary and hourly rate of an employee. For a full time employee, hourly rate remains null and for a casual employee, salary remains null.
Part A: Entity Relationship Diagram (Draw.io)
AMC ERD
Part B: Normalized Schema
The table Customers holds information about each customer of AMC. It is in 3rd Normal Form since the functional dependencies are managed and transitive dependencies do not exist in this table. The table Stores contains information about AMC stores. It is in 3rd NF as the functional dependencies are managed by splitting the composite attribute into separate attributes and transitive dependencies do not exist. Products table contains detail about each product of AMC. It is in 3rd NF by separating the product information of an order, supplier of that product and store information at which it is sold separately into three other tables to manage data redundancy.
Part C: Relational Schema
Customers
    Name
    Data Type
    Length
    Key Constraints
    Cust_ID
    Int
    11
    Primary Key NOT NULL
    C_FirstName
    Varchar
    25
    
    C_LastName
    Varchar
    25
    
    C_Mobile
    Varchar
    10
    NOT NULL
    C_Address
    Varchar
    75
    
Orders- The table contains order information and who placed the order. It is in 3rd NF.
    Name
    Data Type
    Length
    Key Constraints
    O_ID
    Int
    11
    Primary Key NOT NULL
    O_Date
    Date
    8
    
    Cust_ID
    Int
    11
    NOT NULL
    Foreign Key Cust_ID references Primary key of table Customer
Stores- The table is in 2nd NF. The attributes email and phone number are unique at each store along with their ID.
    Name
    Data Type
    Length
    Key Constraints
    S_ID
    Int
    11
    Primary Key NOT NULL
    S_Name
    Varchar
    25
    
    S_Phone
    Varchar
    10
    NOT NULL
    S_Fax
    Varchar
    10
    
    S_Email
    Varchar
    25
    
    S_Street
    Varchar
    25
    
    S_Suburb
    Varchar
    25
    
    S_State
    Varchar
    25
    
    S_PostCode
    Varchar
    6
    NOT NULL
Department- The table contains details about department and the store where that department exists. It is not in 3rd NF since phone and email are unique attributes. Data redundancy is managed through table Store_Dept.
    Name
    Data Type
    Length
    Key Constraints
    Dept_ID
    Int
    11
    Primary Key, NOT NULL
    Title
    Varchar
    13
    Unique, NOT NULL
    Dept_Phone
    Varchar
    15
    
    Dept_Email
    Varchar
    30
    
    S_ID
    Int
    11
    NOT NULL
Store_Dept- Contains each unique combination of the store with its department number in order to manage data redundancy among Stores and Departments
    Name
    Data Type
    Length
    Key Constraints
    Dept_ID
    Int
    11
    Foreign Key referencing PK of Department
    S_ID
    Int
    11
    Foreign Key referencing PK of Store
Employee- Table contains details about each employee working at AMC.
    Name
    Data Type
    Length
    Key Constraints
    Emp_ID
    Int
    11
    Primary Key NOT NULL
    E_FName
    Varchar
    25
    
    E_LName
    Varchar
    25
    
    Address
    Varchar
    100
    
    E_Mobile
    Varchar
    10
    NOT NULL
    E_Email
    Varchar
    35
    
    E_TFN
    Varchar
    25
    NOT NULL
    E_Type
    Varchar
    6
    NOT NULL
    Salary
    Float
    4 bytes
    
    Hourly_Rate
    Float
    4 bytes
    
    JoiningDate
    Date
    8
    NOT NULL
    ManagerStatus
    Varchar
    1
    NOT NULL
    S_ID
    Int
    11
    Foreign Key NOT NULL referencing PK of Store
    Dept_ID
    Int
    11
    Foreign Key NOT NULL referencing PK of Department
Products-
    Name
    Data Type
    Length
    Key Constraints
    P_ID
    Int
    11
    Primary Key NOT...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here