1. Page 1 of 4CRICOS Provider No. 00103D Assignment 1
Specification
Faculty of Science
ITECH1006/5006
Database Management Systems
Assignment 1
Development of an ER Diagram and Database Implementation
Weight 20%
Aim:
To give you practical experience in using Entity-Relationship
and Relational Database modelling
techniques.
Due Date:
Monday of Week 7 (see Course Description for further dates
and times).
Project Specification
The proprietors of BigM have approached you and asked if you

2. could design a database to help them
manage their business. The management has commissioned you
(in your capacity as a Database
Management System consultant) to analyse, design and develop
an appropriate conceptual data model
and relational database schema, based on the following
information gathered about the current
business activities.
referenced by store number. BigM
also keeps store name, phone, fax, email for each store. Each
store has a postal address
containing street address, city, state and postcode.
finance, accounts, sales, customer
service etc. For each department, there is a department ID,
department name, phone and e-mail
address.
employee, BigM keeps a record of their
employee ID, first name, last name, phone, date of birth, start
date of his/her work and tax file
number.
employees. For each address they
need to store street address, city, state and postcode.
a casual staff, his or her job type
(for example, accountant, sales, customer service etc.), and
hourly rate is recorded. For a

3. fulltime staff, his or her job type and annual salary is recorded.
each department is supervised
by an employee. The department supervisor is also the
supervisor for all the staffs within that
department.
training, payroll, server application
and help desk are located.
tore generates pay slips for all staffs (in
this store and other stores being
supervised) on a fortnightly basis. For each pay slip, the store
records a pay ID, supervising
store ID, employee ID, pay date, number of hours and the gross
payment.
sales different products like CDs, cloths, computers
etc. For each CD it keeps a record of
CD number, title, length, number of tracks, release date,
category description, price and reorder
level.
st in
the CD. They would like to include first
name, last name and date of birth and website address, if they
have one. If possible, BigM also
wants to store number of tracks where a particular artist appears
in a given CD.
ucts it stores product number,
product description, brand, product size
and price.

4. store is kept. BigM keeps track of
Page 2 of 4CRICOS Provider No. 00103D Assignment 1
Specification
the quantity of each product that is on order, as well as the
number currently available in each
store.
always taken at each order. A
customer is referenced by a customer number, customer first &
last names, phone number and
postal address, if available. For each address they need to store
street address, city, state and
postcode.
they may order multiple copies of
the same product. BigM also records the date a product arrives
and the date when it is picked up
by the customer. Note that these dates may be different for each
product.
sufficient information. If you need to
make assumptions about their organisation please ensure that
you record them.
Assignment Submission

5. You should produce a single pdf file, created using Word,
containing all of the requirements as
specified within this document. Your lecturer will provide
details of how the file is to be submitted
within lectures.
The design document should contain:
1. A completed copy of the SITE Assignment Coversheet.
2. An appropriate title page that includes an acknowledgement
of all students you have
spoken to about the assignment.
3. A table of contents and automatically generated page
numbers.
4. An entity relation (E-R) diagram that models the problem
which includes:
a. all entities, relationships (including names) and attributes;
b. primary (underlined) and foreign (italic) keys identified;
c. cardinality and participation (optional / mandatory) symbols;
and
d. assumptions you have made, e.g. how you arrived at the
cardinality/participation
for those not mentioned or clear in the business description, etc.
The E-R should be completed using the standards of this course
(crow’s feet).
5. Normalisation of relations which identifies:
a. dependency diagram for each relation
b. the level of Normalisation achieved for each relation;

6. c. the reasons for any relation that is maintained NOT in 3NF.
6. Relational data structures that translate your E-R diagram
which includes:
d. relation (table) names,
e. attribute (column ) names and field types (as required by
WAMP),
f. primary and foreign keys identified;
The data structures should be shown using the standards of this
course.
7. A bibliography, in APA format, containing all resources
used to complete the assignment.
If no resources have been used please indicate this
appropriately.
Your assignment should be completed according to the
University of Ballarat General Guide
for the Presentation of Academic Work. This is available online
at the following web address:
http://www.ballarat.edu.au/generalguide
Assessment Criteria
1. How clear and well-presented your submission is.
2. E-R diagram: adherence to our standard, assumptions made,

7. inclusion of correct primary
Page 3 of 4CRICOS Provider No. 00103D Assignment 1
Specification
and foreign keys, appropriate entities, relationships, and
attributes.
3. Normalisation: appropriate interpretation of each normal
form, arguments for leaving the
schema in the normal form you consider optimal.
4. Conversion of E-R diagram to relational schema: schema is a
correct translation of the E-R
submitted with appropriate tables, columns, and primary keys.
Assignment 1 – Marking Overview
ER Diagram / 50
Relational Structure /10
Normalization /20
Relational Schema /15

8. Documentation /5
Total
/100
/20%
Faculty of Science
ITECH1006/5006
Database Management Systems
Assignment 1 – Marking Specification
Student Name: Student Number: Tutor:
Requirements Allocated
Mark
Given
Mark
Total
ER Diagram
Entities
essential entities

9. and foreign keys identified
Relationships
make sense
names, cardinalities and participation
Notation
and inconsistently used
14
7
7
7
15
‐7
/50
Relational Structure
Translation from ER to Relational Data Structure
entities and relationships transferred
of correct notation
names and attributes sensible
4

10. 4
2
/10
Normalization
diagram for each relation
All entities in 3NF; if not then reason provided and is reasonabl
e
assumptions provided
15
3
2
/20
Relational Schema
all tables and attributes
Primary keys and foreign keys identified (including the table an
d key
that the key related to) and clearly presented
of fields included eg dates
notation used

11. 5
4
4
2
/15
Documentation
according to UB guide
des SITE coversheet, title page including list of
acknowledgements, table of contents, page numbers
included in APA format
2
1
2
/5
Total /100
Weight /20%
Comments / Feedback:

12. ITECH1006-5006_Sem1_2015_A1_SpecITECH1006-
5006_Sem1_2015_Assign1_Marking