Database Management for Business

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)