1 | P a g e Unit ISY1002/ISY103 Database Management for Business Assessment Type Group Assignment – Database Project, Report and Presentation Assessment Number 3 Assessment Weighting 25% Total Marks...

1 answer below »
please see the files i uploaded


1 | P a g e Unit ISY1002/ISY103 Database Management for Business Assessment Type Group Assignment – Database Project, Report and Presentation Assessment Number 3 Assessment Weighting 25% 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 11 – refer Moodle for date and time 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. 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 crow’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 (10 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 MySQL database (35 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. (10 Marks) http://www.gliffy.com/ 4 | P a g e 2. Using MySQL, 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. (20 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 tables’ name, fields’ 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 MySQL 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 MySQL Command Prompt window; choose Mark and then press the [Enter] key 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’, ‘GeorGe’ etc. in street should be returned by your query too. (2 marks) 5. List all the orders having at least two different products ordered. (2 marks) 6. List customer number, name and address of all the customers who has not placed any order. (2 minutes) 7. Retrieve first name, last name and employee number of all the employees along with department name and store name where they work. (3 marks) 8. For each store, display store name and number of employees works in account
Answered Same DayMay 10, 2021ISY103

Answer To: 1 | P a g e Unit ISY1002/ISY103 Database Management for Business Assessment Type Group Assignment –...

Shikha answered on May 31 2021
162 Votes
Student Name
Student ID        6
Database Implementation Report
(Australian Manufacturing Company (AMC))
Submitted By
Course
Professor
Date
Table of Contents
1.    Introduction    3
1.1.    Project Objective    3
1.2.    DBMS Selection    4
1.3.    Business Rules    4
2.    PART A: ERD Diagram    5
3.    PART B: Normalized Schema    6
4.    PART C: Relational Schema    7
5.    Database Schema    9
5.1.    Table Design    9
6.    Referential Integrity Constraint    14
6.1.    Data Insertion    16
7.    SQL Statements    20
8.    PART E: Group Report    24
9.    References    25
1. Introduction
Database as the name shows is the organized or systematic accumulation of information from which information can be retrieved and reviewed as and when required. It goes about as a repository or a storage facility of information and is continuously required by all the significant associations for having appropriate data and furthermore to monitor various operations occurring in it. It gives a back end supp
ort and encourages the best possible working of the progressive associations. Database can have various tables present inside it which are the group of rows and columns that are accessible to store the information. The information can be recovered from a single table or the multiple tables relying upon the user or the association's prerequisite. Database Management System gives us the best approach to deal with our data in an organized and efficient manner with the goal that it tends to be utilized adequately. It gives a powerful interface between the system and the user. (Gouhar, 2017).
According to given scenario, Australian Manufacturing Company (AMC) requires a database framework to deal with their stores, staff, items, providers, benefactors as well as orders. As a database administrator, my job is to develop and implement database system for AMC.
1.1. Project Objective
The main objective of implementing database in AMC is to automate all the processes in the organization by implementing centralized database system. Also, it will help to minimize the response time taken for querying the data from database. All the data will be managed and organized in an efficient way. The system will help the organization to easily retrieve the data according to particular criteria which will help to reduce the time taken to fetch the record.
1.2. DBMS Selection
There are many database engines available to store the data like Oracle, MySQL, SQL, Server but I will use MySQL for organizing the data. MySQL is a quick, reliable, powerful and open source database framework that embeds many features. Organization and security are successful and are effectively setup. MySQL would be recommend for AMC where preparing information to and from the database wasn't so huge. The unique storage engine architecture enables database experts to configure the MySQL database server explicitly for specific applications, with the final product being astonishing execution results. Regardless of whether the planned application is a fast value-based transactional framework or a high-volume site that administrations a billion queries per day, MySQL can meet the most requesting expectations for any framework. With high speed load utilities, distinctive memory caches, full content files, and other execution improving components, MySQL offers all the correct ammunition for the database system. MySQL offers outstanding security includes that guarantee supreme information insurance. As far as database confirmation, MySQL gives incredible systems to guaranteeing just authorized users can have access to the database server, with the capacity to block unauthorized users. (DBQuest, Inc., 2012).
1.3. Business Rules
The following business rules should be considered while implementing database system for AMC:
· The database must store all the data related to its stores, customers, employees, products, orders, and suppliers.
· There are two types of employees – Full time and part time and both employee’s salary details must be saved into the system.
· Pay slips will be generated for both employees on the basis of no of hours worked in a week.
· For a full time, it must store annual salary whereas for part time employees, it must store hourly rate of each employee.
· The database must be centralized as it must consist of data like which store has which product with what inventory.
· All the orders generated will be saved in the orders tables whereas orderdetails will consist of products ordered within each order.
2. PART A: ERD Diagram
3. PART B: Normalized Schema
In order to normalize above schema, entities must be in 1NF, 2NF and 3NF. We are taking the example of three entities – Customer, Order, Orderdetails.
1. Customer CustomerNo, FName, LName, Address, ContactNo, Email
Here, we have taken CustomerNo as primary key as we can't take FName, LName, Address, Email, ContactNo as primary key because all these attributes can be repetitive. So, in order to uniquely identify a customer, we should have unique CustomerNo as no two customers can have unique CustomerNo. Also, in above given functional dependency, no two customers can have repetitive ID. Therefore, this is in 1NF.
As we know that CustomerNo is primary key and can be only candidate key in above functional dependency as all other attributes of customer entity can be repetitive. Hence, the above relationship is single valued candidate key which shows that above FD is in 2NF.
Also, FName, LName can't be unique and cannot be used to find other attributes. We can say that the above entity has no transitive dependency which implies that above entity is in 3NF.
2. Order OrderNo, CustomerNo, OrderDate, StoreNo
Here, we have taken OrderNo as unique primary key as an order can only be identified by unique orderno. A customer can order many times on different dates from different stores. Therefore, CustomerNo, Orderdate and StoreNo can’t be unique. Therefore, above entity is in 1NF. Also, OrderNo can only be candidate key as all other attributes can be repetitive. Therefore, it is in 2NF. Now above entity is in 1NF, 2NF therefore, it is in 3NF.
3. OrderDetails ID, OrderNo, ProductNo, Qty
Here, we have taken ID as unique primary key as an order can have many products orders. Therefore, we have taken ID as primary key. Therefore, OrderNo, ProductNo and Qty can’t be unique. Therefore, above entity is in 1NF. Also, ID can only be candidate key as all other attributes can be repetitive. Therefore, it is in 2NF. Now above entity is in 1NF, 2NF therefore, it is in 3NF.
Hence, I have tried to take all above entities in 3NF with some primary key defined.
4. PART C: Relational Schema
    Entity
    Field Name
    Data Type
    Length
    Key Constraint
    Store
    StoreNo
    INT
    AUTO INCREMENT
    Primary Key, NOT NULL
    
    Name
    VARCHAR
    50
    
    
    Phone
    VARCHAR
    15
    
    
    Email
    VARCHAR
    50
    
    
    Address
    VARCHAR
    50
    
    Employee
    EmployeeNo
    INT
    AUTO INCREMENT
    Primary Key, NOT NULL
    
    FName
    VARCHAR
    30
    
    
    LName
    VARCHAR
    30
    
    
    Address
    VARCHAR
    50
    
    
    Mobile
    VARCHAR
    15
    
    
    Email
    VARCHAR
    50
    
    
    TFN
    VARCHAR
    15
    
    
    Salary
    FLOAT
    8,2
    
    
    JoiningDate
    DATE
    
    
    
    EmployeeType
    VARCHAR
    20
    Check (Full Time/ Part Time)
    
    JobProfile
    VARCHAR
    50
    
    
    StoreNo
    INT
    
    Foreign Key
    Department
    DepartmentNo
    INT
    AUTO INCREMENT
    Primary Key, NOT NULL
    
    Title
    VARCHAR
    10
    
    
    StoreNo
    INT
    
    Foreign Key
    
    Phone
    VARCHAR
    15
    
    
    Email
    VARCHAR
    50
    
    
    Supervisor
    INT
    
    Foreign Key
    PaySlips
    SlipNo
    INT
    AUTO INCREMENT
    Primary Key, NOT NULL
    
    EmployeeNo
    INT
    
    Foreign Key
    
    Week
    VARCHAR
    10
    
    
    Year
    VARCHAR
    5
    
    
    NoOfHours
    INT
    
    
    
    GrossPay
    Float
    (8,2)
    
    
    StoreNo
    INT
    
    Foreign Key
    Supplier
    SupplierNo
    INT
    AUTO INCREMENT
    Primary Key, NOT NULL
    
    Name
    VARCHAR
    50
    
    
    Address
    VARCHAR
    50
    
    
    ContactNo
    VARCHAR
    15
    
    
    Email
    VARCHAR
    50
    
    Product
    ProductNo
    INT
    AUTO INCREMENT
    Primary Key, NOT NULL
    
    Name
    VARCHAR
    50
    
    
    Brand
    VARCHAR
    50
    
    
    Description
    VARCHAR
    100
    
    
    SupplierNo
    INT
    
    Foreign Key
    
    Storeno
    INT
    
    Foreign Key
    Customer
    CustomerNo
    INT
    AUTO INCREMENT
    Primary Key, NOT NULL
    
    Fname
    VARCHAR
    50
    
    
    LName
    VARCHAR
    50
    
    
    Mobile
    VARCHAR
    15
    
    
    Address
    VARCHAR
    50
    
    
    Storeno
    INT
    
    Foreign Key
    Orders
    OrderNo
    INT
    AUTO INCREMENT
    Primary Key, NOT NULL
    
    CustomerNo
    INT
    
    Foreign Key
    
    OrderDate
    Date
    
    
    
    StoreNo
    INT
    
    Foreign Key
    OrderDetails
    ID
    INT
    AUTO INCREMENT
    Primary Key, NOT NULL
    
    OrderNo
    INT
    
    Foreign Key
    
    ProductNo
    INT
    
    Foreign Key
    
    QtyOrdered
    INT
    
    
5. Database Schema
5.1. Table Design
1. Store
mysql> Desc Store;
+---------+-------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+---------+-------------+------+-----+---------+----------------+
| StoreNo | int(11) | NO | PRI | NULL | auto_increment |
| Name | varchar(50) | YES | | NULL | |
| Phone | varchar(15) | YES | | NULL | |
| Email | varchar(50) | YES | | NULL | |
| Address | varchar(50) | YES | | NULL | ...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here