UNSW Business School

School of Information Systems and
Technology Management
-
INFS1603
Introduction to Business Databases
Term 2 2024
Event Booking System
Part B
2 | P a g e
Table of Contents
1. Overview ......................................................................................................................................... 3
2. IMPORTANT NOTE on File-Sharing Websites – Please read ........................................................... 3
3. Key Dates ......................................................................................................................................... 3
4. Aim of the Assignment (Parts A and B) ........................................................................................... 4
5. Private Group Channel (in Microsoft Teams) .................................................................................. 5
5.1 Microsoft Planner .................................................................................................................. 5
6. Case Study – Event Booking System................................................................................................ 6
6.1 Background ............................................................................................................................ 6
6.2 Your Role ............................................................................................................................... 7
6.3 Requirements ........................................................................................................................ 8
6.4 Entity ...................................................................................................................................... 9
7. Tasks and Deliverables .................................................................................................................. 10
7.1 Proof of Concept Project ..................................................................................................... 10
7.2 Report B: Tasks .................................................................................................................... 10
7.3 Format and Deliverables ..................................................................................................... 14
8. General Rules ................................................................................................................................ 15
8.1 Proper Academic Conduct ................................................................................................... 15
8.2 Usage of AI Tools ................................................................................................................. 15
8.3 Assignment Submission ....................................................................................................... 16
9. Marking Rubrics ............................................................................................................................ 17
10. Self and Peer Assessments ............................................................................................................ 19
11. FAQ ................................................................................................................................................ 21
3 | P a g e
1. Overview
For this project, you will be assessed on:
(1) Two written reports (Part A and Part B)
(2) Implement a database system using Oracle in Part B
(3) Pitch presentation in Part B
• The Individual Assessment (Part A) is worth 20% of the marks of the course.
• The Team Assignment (Part B) is worth 25% of the mark of the course. Part B is to
be undertaken in groups of four (or three to fit) students, all of which must be from
the same tutorial/lab. Further information on Part B will be published after Week 05.
Assessment Part B is the focus of this document.
2. IMPORTANT NOTE on File-Sharing Websites – Please
read
There are some file-sharing websites that specialise in buying and selling academic
work to and from university students.
You should be aware that you would be committing plagiarism if you download a
piece of work from these websites and present it as your own, wholly or partially.
For more information about Academic Integrity and Plagiarism, please click here.
If you upload your original work to these websites, and another student
downloads and presents it as their own either wholly or partially, you might be
found guilty of collusion — even years after graduation.
3. Key Dates
What? When?
Part A Released Week 2.
Assignment Part A Due:
Submission of assignment
written report
Microsoft WORD file submission via Moodle on or before
Friday, 21 June 2024, 11:59 am AEDT (Week 4)
Part B Group Formation Groups of 4 (or 3 to fit), Week 4 tutorial/lab
Assignment Part B Due:
Submission of assignment
written report
Word and ZIP file submission via Moodle on or before
Monday, 29 July 2024, 11:59 am AEST (Week 10)
Pitch presentation file Microsoft POWERPOINT file submission via Moodle on or
before Monday 29 July 2024, 11:59 am AEST (Week 10)
Pitch presentation Week 10 tutorial/lab (presentation in class followed by Q&A)
These file-sharing websites may also accept purchase of course materials,
such as copies of lecture slides and tutorial handouts. By law, the copyright on
course materials (including this assignment brief), developed by UNSW staff
in the course of their employment, belongs to UNSW. It constitutes copyright
infringement, if not plagiarism, to trade these materials.
4 | P a g e
4. Aim of the Assignment (Parts A and B)
This course project (individual assignment + team assignment) addresses all the Learning
Outcomes of the course. By completing each requirement of this assignment, you will
demonstrate your mastery of the principles and practice of Business Databases:
▪ CLO1: Create and apply conceptual and relational database modelling methods.
▪ CLO2: Design, implement and evaluate database systems.
▪ CLO3: Access and manipulate a relational database using Structured Query
Language.
▪ CLO4: Collaborate with peers to solve problems and achieve outcomes.
▪ CLO5: Discuss database ethical issues and elaborate on the privacy and security
implications of Big Data and business analytics.
The assignment aims to design an Entity Relationship (ER) diagram for an Event Booking
System.
5 | P a g e
5. Private Group Channel (in Microsoft Teams)
• The teaching team will create a private group channel in Microsoft Teams.
• The name of your private group channel is the same as your group ID.
• Only your group members and the teaching team can access your private
group channel. No member from outside the group can access your private
group channel.
• All conversations and files saved in the private group channel remain in the
channel.
• The private group channel aims to work as an environment for you to meet,
chat, leave messages, and upload/download files. Moreover, the teaching
team can communicate directly with the group in this channel.
• The channel must contain all the posts, files, meeting times, and other group
activities. This is marked as part of PLO3 (Business Communication) and
PLO4 (Teamwork) (see course outline).
• Note: myBCom Points are awarded for PLO3.
• Another important factor in using the private group channel in Microsoft
Teams is transparency to all the group members and the teaching team.
When there is a dispute between the group members, the LiC will only
examine evidence such as posts, meeting activities and uploaded files in the
private group channel (see 10. Self and Peer Assessments). The LiC will not
examine other communication channels such as WhatsApp, Facebook, and
WeChat.

5.1 Microsoft Planner
• Microsoft Planner can be used to improve task planning.
• The whole team can access the planner, so there will be no excuses like “I don’t
know what’s going on!”
• Notifications can be used as reminders of tasks to be completed.
• The group leader should maintain Microsoft Planner. All other group members
should also assist in managing the tasks in the Planner.
• Training Videos: Create a plan with Planner in Teams (microsoft.com)
6 | P a g e
6. Case Study – Event Booking System
This fictitious case scenario uses Taylor Swift’s concerts as an example to help you
understand the problems and issues identified with the ticketing system.
6.1 Background
Many of Taylor Swift's fans were dissatisfied with the ticketing system's purchase process
during the recent concerts. There are issues and problems with the concert ticket allocation
and distribution. Some of the issues and problems identified are listed below. I did some
online research. I also asked AI tools for assistance. Microsoft Copilot AI (on Bing), as
shown below, probably gave the best summary of these issues and problems identified with
the current ticketing system:

References:
1. Taylor Swift: Ticketek accounts hacked as ‘thousands’ of Australian fans fear for tickets before Eras
tour | Taylor Swift | The Guardian
2. Taylor Swift Australia Eras Tour: 800,000 people waiting on Ticketek website to buy Taylor Swift Tickets
| How to buy Taylor Swift Tickets (9news.com.au)
3. Amy Evans says she faced discrimination trying to get a ticket to Taylor Swift's Australian concert - ABC
News
7 | P a g e
4. Desperate for Taylor Swift tickets? Here are cybersecurity tips to stay safe from scams
(theconversation.com)
5. Taylor Swift tickets Australia: Elaborate Taylor Swift ticket scam could cause stadium chaos and
heartbreak (9news.com.au)
In addition, considering the amount the fans had to pay for the tickets, they were also
charged for handling and service fees on top of the tickets they purchased.
6.2 Your Role
So, she has asked an IT company to create a new event booking system for her concerts
during her next tour to Australia. This IT company has hired you to model and create a
database, and other teams will create the websites and write all the computer programs for a
new system.
Many system components must be addressed in a large and complex project. Although
many issues were identified, you only have to design and create a database model as listed
above. That will be your part in this large project. For your role,
(a) You do not need to write computer programs to capture the data or address
purchasing ticketing processes. Other project teams will do these.
(b) You do not have to worry about the interaction between the computer programs and
the database. You can assume that the other project teams will take care of it.
(c) You can assume that you have agreed with the other project teams before designing
the database model.
(d) You do not have to worry about how the data is captured, such as whether it is on a
mobile app or a desktop.
8 | P a g e
6.3 Requirements
You need to create a database for a ticketing booking system. For ticketing information, you
can use the 2024 tour as a guide: Taylor Swift | The Eras Tour tickets. Here are some of the
requirements you might want to consider:
• Every customer must create an account and include a valid Australian state driving
licence or an identity card (such as a photo card) (for example, Proof of identity |
NSW Government). If a customer does not have a valid driving licence or an identity
photo card, then the customer cannot purchase tickets. Please note that issuing
driving licences is based on states in Australia. You can assume that 2-factor
authentication will be used. Furthermore, you can assume this will address the bot,
fraud, and identity issues.
• You can assume the other project team will create other computer programs and
devices to address identified disability issues. You have to ensure you capture that
the customer has a disability.
• Every concert has pre-defined seating. For example, MCG has allocated seats:
TS_MCG_Map2.jpg (1000×694).
• A customer can purchase once with a limited number of tickets. However, you do not
have to worry about this constraint. You can assume the computer program will
check the limit when the customer enters the details. The other project team will
handle the computer programs.
• Encryption is outside the scope of the assignment. Theoretically, some data might
need to be encrypted, but you do not need to encrypt any data to reduce
complications.
9 | P a g e
6.4 Entity
There are lots of entities in this case study. Some examples of entities you might want to
consider in your database model:
Entity Description
Customers Customer information
Events Details of concert events – place, dates, etc.
Event Venue Seating The seatings of the venue of an event.
Ticket Booking Tickets are booked and paid for by the customers.
Merchandise Merchandise for the events/tour
VIP Packages A package might Include tickets, events, merchandise, and
even accommodation.
Note: For simplicity, if you have wanted to include hotel and ticket packages as a VIP
package, you can assume that the accommodation will be booked accordingly when the
package is purchased. It is outside the scope of your project to address third-party systems.
There are two important key points to remember:
• Not everything in a business process has to be captured in a database.
• The database design does not always follow the order of the business process.
For example, a customer might move around on the website to view the information, but the
data for moving around is not captured in the database.
10 | P a g e
7. Tasks and Deliverables
Your task is to develop a database for the Event Booking System as a proof-of-concept
project. You have to write a report and perform a presentation to discuss what you have
done in the proof-of-concept project.
7.1 Proof of Concept Project
A proof of concept project is common in a business environment (see Proof of concept -
Wikipedia), instead of committing a large sum of money to build or upgrade a system. The
proof of concept project is to demonstrate how a system works but in a cut-down version. In
other words, you demonstrate only a portion of the system, not the full one. The purpose is
to show the viability of the system proposal. It also helps project stakeholders visualise
what the system can deliver, or sometimes we call it a “stakeholder buy-in”.
You do not expect to develop an entire database in this project. One purpose of this proof-
of-concept project is to evaluate the feasibility of using the data for reporting.
7.2 Report B: Tasks
Note: This assignment is to be conducted and submitted as a group.
1. Your group needs to develop an updated version of the scenario's entity-
relationship (ER) model by incorporating the best elements from individual members’
ERDs and feedback from Part A, when available. The ERD should have identified
entities, relationships, keys, constraints, cardinalities, and connectivities. You can
include additional relevant entities and attributes. Use Crow Foot’s notation to draw
the ER model based on what you have identified. Clearly label entities, relationships,
cardinalities, and connectivities in your model. The clarity and readability of your
diagrams are critical.
2. The minimum number of entities depends on the number of group members:
i. A group of two has at least six (6) entities,
ii. A group of three has at least nine (9) entities and
iii. A group of four has at least twelve (12) entities.

11 | P a g e
3. To ensure the “weight” of the entities is fairly even distributed between the group
members within the group and between the groups, here are some of the rules for
counting the number of entities:
a. Each entity must have at least four attributes in addition to the primary
keys. The quality of the inclusion of the attributes will be assessed.
b. You must have at least one supertype and its associated subtypes.
c. All subtype entities belonging to one supertype entity are counted as two
entities. That is, if you have four subtype entities belonging to one
supertype, then you count the four subtype entities as one entity.
d. A “simple” entity with only two or three attributes will be counted as half-
an-entity. For example, a country entity with only two attributes, namely
country code and country name, will be counted as half-an-entity (i.e., 0.50
Entity).

4. You need to list any assumptions (i.e., in case of missing information) that you have
made when drawing the ER diagram.
5. You create a schema/database based on the ERD in Oracle.
a. Write SQL DDL statements to create the tables of the relational model, which
is based on your ERD.
b. Ensure that referential integrity between the tables is enforced.
c. You need to populate the tables with data. As a rule of thumb, an average of
10 rows per table will give you enough data for a report. However, you might
find that some tables will have more than 10 rows per table, whereas others
might have fewer. You have to ensure adequate data to run and test queries
and showcase the database.
d. Ensure your sample data can return the queries as specified in Q6.
e. Do NOT change your group SQL account login password.
f. If more than one person works on a table using the group account, this might
create errors in the database. Please collaborate on who will be, what, and
when within the group!
g. Two script files are expected: one file for SQL statements for creating tables
and inserting rows and a separate file for SQL queries for the reports (see
6.)

6. Develop the below SQL queries for the database. You are required to generate reports
using Oracle SQL. The SQL query scripts must be saved as a separate script file (.SQL
or .TXT file). SQL query scripts inserted as screenshots will NOT be marked. Printouts
of the results of each query (e.g., screenshots) should also be in the report following
each query (not part of the word limit).
The number of reports required is based on the number of members in a group plus the
four general reports. This assessment phase evaluates your technical proficiency and
ability to develop reports that align with business operations. Thus, both your technical
skills and understanding of the business are assessed. Moreover, the query complexity
is considered part of the marking process.

12 | P a g e

There are two parts of the report:
(a) The technical requirements for the four mandatory general reports are shown
below:
1. You need to create one report using a suitable function(s) to calculate the total
number of ticket bookings and the total payment amount made for each
event.
2. You need to create one report using group by and having clauses.
3. You need to create one report using subqueries clauses.
4. You need to create one report  using set operator clauses.
(b) The additional reports depend on the number of group members:
i. A group of two has to do one extra report,
ii. A group of three has to do two extra reports, and
iii. A group of four has to do three extra reports.
Moreover, the extra report(s) must be selected in the following order:
i. You need to create one report using Outer Join (including left and right outer
joins) clause.
ii. You need to create one report using group by, having, and where clauses.
iii. You need to create one report  using subqueries clauses.

For example, a group of three must complete four mandatory reports and two
extra reports for a total of six reports. The two extra reports that will be created
are a report using the outer join clause and a second report using group by,
having, and where clauses.
7. The word limit for this assessment is 2,000 words (excluding cover sheet, table of
contents, summaries/outlines, footnotes, references, endnotes, appendices, SQL
queries, etc. Words in the ER model will not be counted either.)
8. Presentation
(a) As part of the proof of concept, you have to demonstrate the database with
reports:
(b) Your team will present your database system to Taylor Swift’s
management team:
• Microsoft PowerPoint slides must be used, and
• All group members must present in Week 10.
13 | P a g e

(c) The presentation slides should be formatted as:
Introduction
slide
This slide should have your group number and names, with
individual pictures if you like. It does not count towards your
Main slides.
▪ One minute is allocated for introduction and
conclusion
Main slides
▪ A maximum time of presentation is 2 minutes per group
member.
▪ A maximum number of slides is 2 main PowerPoint (PP)
slides per group member.
▪ Do not insert extra slides in between the presenters,
otherwise it will count towards the limit.
▪ You can use animation such as Powtoon (Easily Create
Videos Yourself | Free Video Maker | Powtoon) or any
animation software or even Tik Tok to assist your part
of the presentation. If you were to use animation, you still
have to put the contents to the PowerPoint slides for
completeness. The contents should be similar but do not
necessarily have to be identical.
Professional
and Ethics
Slides
▪ You have to do some research to discuss professional
responsibilities and ethical issues related to
implementing a database in this case scenario.
▪ A maximum number of slides is 2 slides.
Total Number of
Slides
▪ The PowerPoint file could not be more than 200MB in
size.
▪ You must have the correct number of slides.
For example, for a 4-member group, you have a
maximum of 11 minutes (1 minute + (4 members * 2
minutes) + 2 minutes (P & E)) to present. A maximum
of 11 PP slides consists of 8 main PP plus 1
introduction and 2 professional and ethics slides.
However, you can present in less than 11 minutes
for 11 PP slides.
Reference
slide(s)
[optional]
Include any references used in the presentation

• Audience: the management of Taylor Swift (some are non-technical audiences who
are not familiar with databases) and technical specialists (who are familiar with
databases).
• Purpose: To convince the management that you have delivered a proof-of-concept
Project.

Note: The presentation will be assessed in Week 10 Lab/Tutorial under exam
conditions, i.e., students who do not attend the class will not receive the
presentation mark.
14 | P a g e
7.3 Format and Deliverables
For the written report of Part B, you need to consider:
(a) UNSW Coversheet. Submit your assignment with a signed coversheet (typed signatures
or initials are allowed). Failure to include the UNSW coversheet with signatures/initials
will lead to a 5% penalty, and no marks will be released until the coversheet is received.
(b) Table of Contents / Executive Summary. This part of the assignment requires no
executive summary, outline or table of contents.
(c) Format. The style/format of the report can be as you find it appropriate and useful. You
should use headings, sub-headings, bullet points, diagrams, and tables as appropriate.
The report is only in Microsoft Word format.
(d) References. References and citations (if any) should follow the UNSW (Harvard) or the
APA 7th citation style standard.
(e) Turnitin Title and File Naming Convention: Your Turnitin Title should be “GROUPID-
PartB” (e.g., H19A-01-PartB), and your submitted file should be “GROUPID-
PartB”.docx. (e.g., H19A-01-PartB.docx). Failure to use the correct file naming will
automatically lead to a 5% penalty.
(f) Draw your model using a software tool like draw.io or Lucidchart.
(g) Export/save your model in image format (e.g. PNG, JPEG, etc).
(h) Insert your model (picture) in the Word document in Landscape format if necessary. We
will not rotate your model for you if it needs rotation. We should be able to mark your
model on a computer without zooming in or out.
(i) Readability: Ensure your model can be read on A4 paper.
(j) Check your submission. After you submit it, download and check the file.
(k) We will mark what is on Moodle only.
(l) Include Page numbers and subheadings (if necessary).
(m) Colour: If you use colours, ensure they are consistent and that we can read the text
behind the colour.
(n) Text inserted as pictures will NOT be marked. For example, a table cannot be
screenshotted as a picture. Only figures (e.g. diagrams) can be inserted as pictures.
(o) The clarity and readability of your diagrams are very important.
15 | P a g e

8. General Rules
8.1 Proper Academic Conduct
All assignments need to follow UNSW’s guidelines regarding proper academic conduct. The
submission of materials that are non-original or have been submitted elsewhere will be
considered plagiarism. Plagiarism is unacceptable. All instances of plagiarism or other
academic misconduct will be pursued. Plagiarism may lead to you failing this course and
negatively affecting your studies at UNSW. The general UNSW guideline on academic
conduct is available online.
8.2 Usage of AI Tools
As AI applications continue to develop and technology rapidly progresses around us, we
remain committed to our values around academic integrity at UNSW. Your work must be
your own, and where the use of AI tools such as ChatGPT and CoPilot has been permitted
by your course convener, they must be properly credited. Please see that your submissions
must be substantially your own work. For more details about the impact of generative AI
tools, please refer to Generative AI in Learning, Teaching,

The following links are related to the usage of AI tools published by UNSW:
• Preview link to the AI module: https://rise.articulate.com/share/YHi9m-s6NtOcTMY4wSFzuqjUT-
2HfPi_
• Ethical and Responsible Use of Artificial Intelligence at UNSW:
https://www.student.unsw.edu.au/notices/2024/05/ethical-and-responsible-use-artificial-
intelligence-unsw

If you use any AI tool to assist you in your assignment, please acknowledge it in the
Appendix section of your assignment. Words in the Appendix are not counted towards the
total word limit.
Usage of AI Tools
the output in your assessment. Please be honest because TurnItIn can
detect the usage of AI tools.>
Write here…

16 | P a g e
8.3 Assignment Submission
Assignments are to be submitted via Moodle on, or better before, the due date. Late
submission of assignments is undesirable, disrupts the course timelines, is a sign of poor
time management, and will lead to reduced marks. The late submission of assignments
carries a penalty of 5% of the awarded marks for that assignment per day of lateness
(including weekends and holidays).

For example, a 70 mark would be reduced by 3.5 marks per day of lateness. An assessment
will not be accepted after 5 days (120 hours) of the original deadline unless special
consideration has been approved. An assignment is considered late if the requested format,
such as hard copy or electronic copy, has not been submitted on time or where the ‘wrong’
assignment has been submitted.
Students must plan ahead and submit on time. In the case of illness or misadventure,
submitting a Special Consideration may grant an extension to complete Part A of the
assignment. The general UNSW guidelines for special considerations are available online at
https://www.student.unsw.edu.au/special-consideration.

17 | P a g e
9. Marking Rubrics
MARKING CRITERIA HIGH DISTINCTION (HD) 85%-100% DISTINCTION (DN) 75%-84% CREDIT (CR) 65%-74% PASS (PS) 50-64% UNSATISFACTORY (FL) 0-49%
Shows a polished and insightful
approach to the report organisation,
with compelling clarity of expression.
Careful attention to detail with
organisation and written clarity.
Logical organisation, coherent and
mostly written clearly.
Some attempt to organise in a logical
manner, and reasonable clarity of
expression.
Disorganised and incoherent, such as
no linking between
sections/arguments, or there is no
introduction/ conclusion to the report.
Referenced sources, if any, and
formatting are appropriate/accurately in-
text and/or in the reference list
(following Harvard style standards).
Sources are integrated effectively into
the report/argument.
Referenced sources, if any, and
formatting are appropriate/accurately in-
text and/or in the reference list
(following Harvard style standards).
Sources are integrated effectively into
the report/argument with a few minor
errors (e.g., the reference list is not
alphabetised or the word length is
slightly over).
Referenced sources, if any, and
formatting are primarily accurate and in
the reference list but with some errors
(e.g., slight inconsistencies in how
authors are referenced).
Referenced sources, if any, and/or
formatting have systematic errors (e.g.
inconsistency in how authors are
referenced).
Referencing, if any, does not conform
to Harvard style, and/or the report
needs to consistently conform to
formatting requirements (e.g. headings
are missing, page numbers, etc.).
Followed the submission guidelines,
and the UNSW cover sheet has been
signed.
The report is within the word limit.
Followed the submission guidelines
and the UNSW cover sheet has been
signed.
The report is within the word limit.
Followed the submission guidelines
and the UNSW cover sheet has been
signed.
The report is within the word limit.
Followed the submission guidelines
and the UNSW cover sheet has been
signed.
The report is within the word limit.
Did not follow the submission
guidelines OR No cover sheet is
provided with the needed information
OR No table of contents is provided
OR The word limit has not been
adhered to.
The ER modelling technique is
correctly demonstrated AND is fully
aligned with the case scenario
(especially, when no entity is missing or
is significantly misspecified).
All PKs, FKs, relationships,
connectivities and cardinalities are
correctly identified and noted.
The ER modelling technique is
correctly demonstrated AND is aligned
with the case scenario (no more than
two relations or entities are missing or
are significantly misspecified).
PKs, FKs, relationships, connectivities
and cardinalities are mostly correctly
identified and noted with equal to or
less than three minor errors/mistakes.
The ER modelling technique is mainly
correctly demonstrated AND is
reasonably aligned with the case (not
more than three missing/misspecified
entities or relations).
PKs, FKs, relationships, connectivities
and cardinalities are identified and
noted, with more than three minor
errors/mistakes/inconsistencies.
The ER modelling technique is mainly
correctly demonstrated. The model
aligns somewhat with the case (four or
more missing/misspecified entities or
relations).
PKs, FKs, relationships, connectivities
and cardinalities are not clearly
identified, with more than four minor
errors/mistakes/inconsistencies.
Evidence of systematically wrong
modelling technique. OR ER diagram
missing or completely inappropriate for
the case.
Any assumptions are clearly given and
justified.
Any assumptions are clearly provided
and justified.
Any assumptions are clearly given and
justified.
The provided assumptions lack clarity
and are challenging to understand
when it comes to their justification.
The provided assumptions lack clarity
and are challenging to understand
when it comes to their justification.
Crow's Foot Notation has been
accurately implemented with no
significant errors.
Crow's Foot Notation has been
accurately implemented with no
significant errors.
Crow's Foot Notation has been
accurately implemented with some
minor errors.
Crow's Foot Notation has been
implemented with some errors.
Crow's Foot Notation has been
implemented with significant errors.
The model is accurate and
exceptionally visually structured (easy
to read and comprehend) and
normalised to at least 3NF.
The model is technically fully correct
AND mostly reflects the assignment
scenario and the ER model (no more
than 1 table is missing or does not
match the ER model).
The model is mostly technically correct
with some errors AND appropriately
reflects the assignment scenario and
the ER model.
The execution of the model (relational
database schema) is just sufficiently
within the established boundaries.
The model (relational database
schema) is missing, or execution is
marginal (OR the group did not
implement the model/the actual
database at all).
Written
communication:
Organisation, clarity
and grammar (10%)
Entity Relational
Diagram/Model (20%)
18 | P a g e
MARKING CRITERIA HIGH DISTINCTION (HD) 85%-100% DISTINCTION (DN) 75%-84% CREDIT (CR) 65%-74% PASS (PS) 50-64% UNSATISFACTORY (FL) 0-49%
The SQL statements for Relational
Database (Schema) are clearly stated
and easily followed logically with
constructive comments.
The SQL statements for Relational
Database (Schema) are clearly stated
and easily followed with some
comments.
The SQL statements for Relational
Database (Schema) can be followed
with some comments.
The SQL statements for Relational
Databases (Schema) are difficult to
follow with no or minimal comments.
The SQL statements for Relational
Database (Schema) are difficult to
follow, with virtually no comments.
The schema of the relational database
is an exact match to the Entity-
Relationship Diagram (ERD).
The schema of the relational database
is closely matched to the Entity-
Relationship Diagram (ERD).
The relational database schema aligns
with the Entity-Relationship Diagram
(ERD) with minor inconsistencies.
The relational database schema has
some inconsistencies when compared
with the Entity-Relationship Diagram
(ERD).
The relational database schema hardly
match the Entity-Relationship Diagram
(ERD) with many inconsistencies.
All tables, PKs, FKs, constraints, and
relationships are correctly identified.
All tables, PKs, FKs, constraints, and
relationships are correctly identified
with some minor errors.
Most of the tables, PKs, FKs,
constraints, and relationships are
correctly identified but with some minor
errors.
Some of the tables, PKs, FKs,
constraints, and relationships are
correctly identified but with some with
errors.
Most of the tables, PKs, FKs,
constraints, and relationships are
missing or incorrectly identified.
ALL 7 (based on a 4-member group)
SQL queries requested are correct in
terms of syntax, contents and outputs
AND the SQL script file (e.g., data
definition, data insertion) to implement
the DB is fully provided. All queries are
fully clear and clean. The majority of the
SQL queries are complex.
The 5-6 SQL queries requested are
correct in terms of syntax, contents,
and outputs. AND a SQL script file (e.g.,
data definition, data insertion) to
implement the DB is fully provided. All
queries are clear and clean, and most
of them are complex.
The 3-4 SQL queries requested are
correct in terms of syntax, contents,
and outputs. AND an SQL script file
(e.g., data definition, data insertion) to
implement the DB is fully provided. All
queries are clear and clean. Some of
the SQL queries are complex.
The 3 SQL queries requested are
correct in terms of syntax, contents and
outputs, AND an SQL script file (e.g.,
data definition, data insertion) to
implement the DB is provided. Only
one of the SQL queries is complex.
The 2 or fewer SQL queries requested
are correct in terms of syntax, contents,
and outputs (OR SQL queries and their
outputs are missing). SQL queries are
simple.
Teamwork (5%)
Strong evidence of teamwork,
planning, recording, and discussion
among group members in the private
group channel in Teams.
Some evidence of teamwork, planning,
recording, and discussion among group
members in the private group channel
in Teams.
Evidence of teamwork, planning,
recording, and discussion among group
members in the private group channel
in Teams.
Little evidence of tteamwork, planning,
recording, and discussion among group
members in the private group channel
in Teams.
Virtaully no evidence of teamwork,
planning, recording, and discussion
among group members in the private
group channel in Teams.
Communication (25%)
Spoken language is clear, concise,
compelling, delivered engagingly, and
effectively conveys key messages.
Excellent use of posture, gestures, eye
contact, and vocal expressiveness.
Speaker appears confident, maintains
audience attention and presentation is
compelling.
A well-developed and highly effective
professional presentation delivered in
an engaging manner. High level of
understanding of the intended
audience.
Spoken language is clear and concise,
and effective tone, pacing, and
emphasis clarify the key messages.
Good use of posture, gestures, eye
contact, and vocal expressiveness.
Speaker is comfortable and the
presentation is interesting and
engaging.
A well-developed and highly effective
presentation delivered in a
comprehensively professional manner,
with a high level of understanding of
the intended audience.
Spoken language is projected and
easily understood by the listener, and
word choices are generally appropriate.
Some effective use of posture,
gestures, eye contact, and/or vocal
expressiveness assists effective
communication. Some room for
improvement on specific areas of non-
verbal communication and speaker may
have some behaviours which distract
from the message.
Presentation is well structured,
effective, and clearly meets intended
audience needs in terms of verbal and
non-verbal communication.
Spoken language is generally clear but
occasionally features poor/unclear
word choices, lack of voice projection,
and variation in tone.
Reasonable use of posture, gestures
and/or eye contact, and key messages
are communicated clearly but possibly
without expressiveness. Presenter
appears somewhat lacking in
confidence and needs to work on
specific areas of non-verbal
communication to become an engaging
speaker.
Presentation is basic in its
effectiveness with some problems with
verbal and non-verbal communication.
Spoken language is unclear and
significantly compromises
communication effectiveness, making
the central messages difficult to
understand.
Weaknesses in non-verbal
communication and spoken language
(may include problems with
projection/tone) are significant barriers
to effective communication of key
messages and distracting for the
audience.
'Ineffective presentation demonstrating
limited verbal and non- verbal
communication.
SQL statements for
Relational database
(Schema) and SQL
Queries (40%)
19 | P a g e
10. Self and Peer Assessments
In general, equal contribution of group members is expected. At the end of the assignment period,
you will perform a self and peer assessment to evaluate the contribution of all group members
(including yourself) to the group project. The purpose of the self and peer assessment is to critically
reflect on the group work, to prevent “free-riding” and to redistribute marks between group
members in cases where free-riding or unequal contributions occur. Thus, you are strongly
recommended to do self and peer assessments via Moodle, a link is created to the UNSW Review
website. Most of the time, the contributions are evenly distributed as shown below:
The self and peer review assessment will allow you to rate your group members’ contributions.
❑ Rate your group members and your own contribution to the group assignment on a scale out
of 5 (or something similar):
▪ 5 = Significantly above expectations (very strong contribution in terms of quality and
quantity, leadership of the project)
▪ 4 = Slightly above expectation (strong contribution in terms of quantity and quality)
▪ 3 = Meeting expectations (did his/her fair share)
▪ 2 = Slightly below expectations (did some work, but could have been more and/or of
better quality)
▪ 1 = Did not participate at all / free riding or significantly below expectations (did very little
work and/or of poor quality)
❑ Equal contribution is expected.
▪ In your group private channel in Microsoft Teams, you can record all your communication,
such as meetings. All the posts and file uploads will have a date and time stamp.
▪ Please note that simply doing the final proofreading or making a cup of tea does not
count as an equal contribution.
20 | P a g e
❑ Unequal contribution
▪ However, occasionally, you might have a “free rider” (i.e., a student who does not do any
work but has his or her name on the front cover) or people who want to do the minimum,
then you might the contributions as shown below:
▪ Unequal contribution might lead to redistribution of the marks of the group assignment.
▪ Contract agreement will be used as the binding agreement between group members to
check for the plan and tasks.
▪ Conflicting/inconsistent/unfair peer contribution review will lead to the group being
assessed by the LiC. The LiC will then examine the communication between the members,
including posts, dates, timestamps of the posts, meeting minutes, files, and so on, in
Microsoft Teams.
▪ In the case that a dispute emerges, the group needs to discuss it with the LiC at the earliest
possible time.
▪ Claims of unequal contributions, especially if they contradict the evaluation of others, will
need to be substantiated with evidence (e.g., uploading files and posts in the private
channel in Teams).
The LiC will make a final judgement in the case that a dispute emerges.
21 | P a g e
11. FAQ
Q.: Can we get help with assignments in the PASS sessions?
A: As mentioned in the Course Orientation slides, teaching staff and PASS leaders do not
provide direct help with the Assignment. However, you can ask general questions.
Q: With a word limit of 2,000 words, are we expected to provide a comprehensive
description of all the entities, relationships, attributes, and key assumptions in the
diagram? Or are we expected to explain these details as a list?
A: You do not have to describe all the models comprehensively. Focus on the assumptions
that help the marker understand your approach to modelling the case. Moreover, you can
write less than 2,000 words and do not have to reach the word limit.
Q: Is it allowed for the ER diagram to be landscaped in a Word document but the
coversheet to be a portrait?
A: It is highly recommended that you use landscape for the ER model and keep other pages
as portraits.
Q: Can I insert a link in my Word document for my ERD model?
A: No, we will not access or mark links.
Q: Does the assumption text need a separate page?
A: The assumption text must be on a separate page (portrait format).
Q: Should we include the coversheet on the first page of the Word file?
A: Yes, the cover sheet should be the first page of the Word document. Words in the
coversheet are not counted towards the total word limit. Moreover, you have to document
the usage of AI on the second page.
Q: Where do we put the SQL DDL and DML statements?
A: All the SQL DDL (e.g., CREATE) and DML (e.g., SELECT) statements should be saved in
script (.SQL or .TXT) files. Two script files are expected: one file for SQL statements for
creating tables and inserting rows and a separate file for SQL statements for the reports.