Reference no: EM132536362

ISY1002 Database Management for Business - Australian Institute of Higher Education

Assignment - Database Project, Report and Individual Video Presentation

Learning Outcome 1: Show an understanding of the fundamentals of database design, implementation, management, and maintenance, including consideration of appropriate data security

Learning Outcome 2: Implement a relational database using the Structured Query Language (SQL) Data Definition Language (DDL)

Learning Outcome 3: Demonstrate an ability to query a relational database using Structured Query Language (SQL) and Data Manipulation Language (DML)

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.

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.

a. 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).

b. 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.

c. 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.

d. 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.

e. 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.

f. AMC sales different products like fashion, health, beauty, electronics etc. Each product is characterised by product number, name, brand, description and price.

g. 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.

h. 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.

i. 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.

j. 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.

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:

Part A: Entity Relationship Diagram

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 UM Lnotation.

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).

Part B: Normalisation

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.

Part C: Relational schema and PostgreSQL database

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.

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.

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.

4. Part D: SQL

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.

5. Part E: Individual Personal Report, and 5 minutes video presentation, including presentation slides - Every group member needs to write/make this part individually and add to the documentation/submission

1. Make a 5 minutes individual video presentation, including presentation slides, and Write a page to the AMC proprietors as a personal reflection that describes your experience building the database, and your contribution to your group project. You can discuss any challenges / difficulties that you experienced or solutions that you found. Comment on any limitations and / or strengths of your database design. Comment on whether your database meets all the system requirements as specified in Project Specification. Avoid making excuses or comments that reflect negativity. Include an acknowledgement of all students you have spoken to about the assignment.

2. Students are also required to present your work in the class. The video presentation + Q&A can be around 5 to 10 minutes long.

6. Part F: Report Layout, SQL script and presentation

Deliverables for Parts A, B, C, D and E must be printed as a report with a cover sheet attached. See Administrative Details on page 10 for more details. Your report must include header and footer that include all the group members' name and student number, unit name, assignment name, and page numbers. Your report must be checked for spelling and grammar. Your report must also be formatted so that it is well set out and easy to read.

a) Each group must submit a single zip file on Moodle which contains all the assignment files (single word file with deliverables for parts A - D, separate personal reports for each group member, PostgreSQL script notepad file and individual 5 minutes video presentation, including slides).

b) The SQL that can be used to restore your database should also be uploaded to Moodle. You can create the SQL for your database as follows:

Create a text version of the database. Create PostgreSQL file that contains a list of SQL statements which can be used to restore/recreate the original database.

Attachment:- Database Management for Business.rar