Category: Writing

Assignment 1 – Book Romance
Overview
This is an individual assignment in which you are required to develop a dynamic web application as
described below.
Important: This assignment specification is generated just for you. Do not distribute this specification.
Timelines and Expectations
Percentage value of task: 20%
Due: Refer to Course Description
Learning Outcomes Assessed
The following course learning outcomes are assessed by completing this assessment:
K3. Detect opportunities for increasing security and privacy of web applications
S1. Develop client/server web applications using client-side and server-side code
S2. Connect to and manipulate a database management system programmatically using server-side
code
A1. Design, develop, test, and debug client/server web applications to provided specifications
Assessment Details
For this assignment, you will create a web-based online dating system, vaguely similar to “Plenty of Fish” or
“Ok Cupid”.
Your platform is dedicated to matching up people with a shared interest in a certain topic – for your
assignment the topic is Book Romance, a place for book enthusiasts to meet.
Users can create accounts, indicate a set of books that they like, and find people to message who like
similar books.
You must implement this platform using PHP and MySQL or MariaDB, with some JavaScript for validation.
Database Structure
The web application uses a relational database. The database has the following structure:
User ( id, name, email, password, profile, photo_url )
Book ( id, title )
Likes (user_id, book_id)
Message (from_user_id, to_user_id, datetime, text)
Attachments:
3075025_1_ITECH3108-Assignment-1.pdf

Overview
The purpose of this task is to develop student’s skills in designing and implementing a relational
database for a given case study.
Timelines and Expectations
Percentage Value of Task: 20% (75 marks)
Due: Week 7 – Friday, May 3, 2019 at 4pm (16:00)
Minimum time expectation: Preparation for this task will take approximately 20 hours
Learning Outcomes Assessed
The following course learning outcomes are assessed by completing this assessment:
K4. Design a relational database for a provided scenario utilising tools and techniques including
ER diagrams, relation models and normalisation.
K5. Describe relational algebra and its relationship to Structured Query Language (SQL).
A1. Design and implement a relational database using a database management system.
Assessment Details
Background
You have been commissioned by Julie from ABC Event Organisers to design a database to assist them with managing
their booking, customer and supplier information. At this stage you have only been commissioned to provide the design
of the database.
ABC would like to store information regarding their customers. Customers may either be individual or corporate
customers. For individual customers they would like to store the contact name, address details (including their location,
postal and delivery address details), email address and phone numbers (mobile, home, work). For their corporate
customers they would like to store the business name, a contact name, address details (including their location, postal
and delivery address details), email address, website URL, and phone numbers (mobile, work).
ABC has a number of different suppliers who provide them with the products that they require to organise events. For
each supplier they would like to store their business name, contact name, address details (including their location,
postal and delivery address details), and phone numbers (mobile, work).
Each supplier may provide a number of different products. For example a supplier may provide furniture such as chairs,
tables, or other items such as table clothes, cutlery and crockery. Suppliers may only provide one product or many
different products. ABC would like to be able to search their database to obtain a list of suppliers who supply particular
products, however, they do not need to know how many of each particular product the supplier stocks.
In the database ABC would also like to store information about their staff. Staff may be employed full-time, part-time or
on a casual basis. ABC need to store contact information for the staff (address and phone), along with their TFN. They
ITECH 2004 DATA MODELLING
CRICOS Provider No. 00103D ITECH 2004 Assignment 1 Sem2 2019 Page 2 of 3
would also like to know what certifications the employees have. For example: “Responsible Serving of Alcohol”, “Food
Handling”, or any relevant police checks such as “Working with Children”. Each employee may hold a number of
different skills and certifications. Some staff are supervisors of other staff members and this also needs to be stored.
For each event ABC would like to store details such as where the event is to be held, the customer who they are
organising the event for, the date and time of the event, the type of event and how many people will be at the event.
ABC specialises in organising weddings, christenings, birthday parties and work functions. For each event they need to
store information about the supplies that they require (eg tables, chairs, cutlery), the supplier that they will be using for
the different products (they can use more than one), and how many of each product they require. ABC would also like
to store details of the staff that have been assigned to each event. Each event will have one staff member who takes
on the role of event manager.
Requirements
This assignment should be presented in a report format, including the following items:
• An ER Diagram with all entity names, attribute names, primary and foreign keys, relationships,
cardinality and participation indicated. All many to many relationships should be resolved.
• A discussion of normalisation, the normal form that each entity is in, how normalisation was
achieved, and why that is optimal. All entities to be in 3NF, unless there is strong justification
for leaving in 2NF.
• A list of relationships with all table names, attributes, primary and foreign keys indicated as
per the conventions given in the lecture slides (i.e. entity/table names in capitals, attributes as
proper nouns, primary key underlined and foreign keys in italics).
• A database schema indicating the type and purpose of all attributes.
Attachments:
3072348_1_itech-2004-ass-1-er-model-2019-05.pdf