To gain experience in designing a database using Entity

1804ICT & 7003ICT – Assignment Part 1 Page 1
1804ICT – DATA MANAGEMENT
7003ICT – DATABASE DESIGN
School of Information & Communication Technology
Trimester 2, 2018
Assignment Part 1:
Designing a Database for BigM
Aims
To gain experience in designing a database using Entity Relationship Diagram (ERD),
Normalisation, and Relational Database modelling techniques.
Learning Objectives
In the process of this assessment task you will:
 plan, schedule and execute project tasks with a view to improving your personal
productivity;
 gain awareness of the typical challenges related to the design of practical databases;
 learn that database design is an iterative process; and
 use the ERD, Normalisation techniques, and Relational models to develop elegant
logical models for a database;

Due date:	Week 7, 31 August Friday, 5:00 PM Submit the individual work file, named ‘a1-<Surname_ID>.pdf‘, by the above due date.
Late submission:	Any submission after the due date will receive a deduction of 10% per day. Standard university policy will apply for all late submissions. See the course website/profile for detail.
Marks:	This assignment has a total 100 marks and it is worth 15% out of the total assessment.
Extensions:	An extension will only be considered with supporting documentation from a health professional and if the problem/illness occurred within the week prior to the due date. If an extension is granted the extension will then equal the number of days specified on the doctor’s certificate, with a maximum limit of five (5) working days.
Authorship:	This assignment is an individual assignment and it shall be completed by the individual student only. The final submission must be identifiably the work of the individual. Breaches of this requirement will result in an assignment not being accepted for assessment and may result in the offending student or students being required to present before the Disciplinary Committee.

1804ICT & 7003ICT – Assignment Part 1 Page 2 of 4
Designing a Database for Commonwealth Transport Services
Introduction
The proprietors of BigM have approached you and asked if you 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.
Business Rules

	BigM operates stores in many cities in Australia. Stores are 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. Each store has a number of departments, for example, finance, accounts, sales, customer


service etc. For each department, there is a department ID, department name, phone and
e-mail address.

	Each department has a number of employees. For each 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. BigM also stores postal and residential addresses of their employees. For each address they need to store street address, city, state and postcode. For each employee, his or her job type (for example, accountant, sales, customer service etc.), and annual salary is recorded. Each store is managed by an employee as a store manager and each department is




supervised by an employee. The department supervisor is also the supervisor for all the
staffs within that department.

	Each store may be assigned a supervising store where all training, payroll, server application and help desk are located. Each supervising store 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. BigM sales different products like CDs, cloths, computers etc. For each product it stores product number, product description, brand, toys, product size and price. An inventory of the number of each particular product in each store is kept. BigM keeps track




of the quantity of each product that is on order, as well as the number currently available in
each store.

	Customer may place orders in the store. Customer details are 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.
 A customer may order more than one product at a time, and 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.
BigM understands that they may not have provided you with sufficient information. If you need to
make assumptions about their organisation please ensure that you record them.
1804ICT & 7003ICT – Assignment Part 1 Page 3 of 4
Assessable Tasks
From the BigM’s business requirements specified above, prepare a document according
to the followings:
1. Use the supplied template for your Assignment submission.
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 page numbers.
4. An ERD using Crow’s Foot notation. The diagram should include:
a) all entities, attributes, and relationships (including names) ;
b) primary keys (underlined) and foreign keys (italic) identified;
c) cardinality and modality (optional / mandatory) symbols; and
d) assumptions you have made, e.g., how you arrived at the
cardinality and/or participation for those not mentioned or clear in
the business description, etc.
5. Normalisation of the relations which identifies:
a) dependency diagram for each relation
b) the level of Normalisation achieved for each relation
c) the reasons for any relation that is NOT maintained in 3NF.
6. Relational database schema that translate your ERD and include:
a) relation (table) names,
b) attribute (column ) names and data types (as required by XAMPP or
UwAmp),
c) length of each field & its description (e.g., if it is a primary key, a
foreign key referring to another table or format, etc.)
d) primary and foreign keys identified;
7. A bibliography, containing all resources used to complete the assignment. If
no resources have been used please indicate this appropriately.
1804ICT & 7003ICT – Assignment Part 1 Page 4 of 4
Assessment Criteria and Marking Overview

Tasks	Marks
1. Presentation How clear and well‐presented your submission is.	10
2. ERD Adherence to the standard of the course, assumptions made, inclusion of correct primary and foreign keys, appropriate entities, relationships, and attributes.	50
3. Normalisation Appropriate interpretation of each normal form, arguments for leaving the schema in the normal form you consider optimal.	20
4. Conversion of ERD to relational database schema Schema is a correct translation of the ERD submitted with appropriate tables, columns, primary keys, and foreign keys, field type & format, etc.	20
Total	100

 

The post To gain experience in designing a database using Entity appeared first on My Assignment Tutor.

• • Assignment status: Resolved by our Writing Team
  • Source@PrimeWritersBay.com

GET THIS PAPER COMPLETED FOR YOU FROM THE WRITING EXPERTS  CLICK HERE TO ORDER 100% ORIGINAL PAPERS AT PrimeWritersBay.com

• • • • NO PLAGIARISM