程序代写案例-INFS2608 T1

欢迎使用51辅导,51作业君孵化低价透明的学长辅导平台,服务保持优质,平均费用压低50%以上! 51fudao.top
1 | P a g e

UNSW Business School
School of Information Systems and
Technology Management



INFS2608 T1 2022 r>Group Assignment Specifications
GoGet Proof of Concept Project


2 | P a g e

Table of Contents

1. Assignment Description ................................................................................ 4
2. Key Dates ..................................................................................................... 4
3. Summary of Submissions .............................................................................. 5
4. Formation of Groups and Contract agreement .............................................. 6
4.1 Formation of Groups ........................................................................................................ 6
4.2 Contract Agreement ........................................................................................................ 6
4.3 Tips based on Previous Experience .................................................................................. 6
5. Private Group Channel (in Microsoft Teams) ................................................. 7
5.1 Microsoft Planner ............................................................................................................ 7
6. Case study .................................................................................................... 8
6.1 Introduction ..................................................................................................................... 8
6.2 Information related to GoGet .......................................................................................... 9
6.3 Proof of Concept Project .................................................................................................. 9
6.4 Requirements for the GoGet System ............................................................................... 9
6.3.1 Section A Entity Relationship Model and Relational Database (Oracle) .............................. 11
6.3.2 Section B Star Schema and Data Warehouse (Oracle) ......................................................... 12
6.3.3 Section C Business Intelligence (Microsoft PowerBI)........................................................... 13
6.3.4 QnA Support for the Assignment ......................................................................................... 13
7. Tasks and Deliverables ................................................................................ 14
7.1 Part A ERM and DW Model Feedback ........................................................................... 14
7.2 Part B PowerPoint Slides ........................................................................................... 14
7.3 Part B Pre-recorded Video Presentation ....................................................................... 15
8. Group Assignment Part A Feedback Submission .......................................... 17
8.1 Tool and Notation for Model ......................................................................................... 18
8.2 Format and Deliverables ................................................................................................ 18
9. Group Assignment Part B Presentation Submission ..................................... 19
9.1 Group Assignment Part B Requirements ....................................................................... 21
9.2 Assignment Part B / Format and Deliverables ............................................................... 21
10. Rubrics ....................................................................................................... 23
11. Self and Peer Assessments .......................................................................... 24
12. General Rules ............................................................................................. 26
11.1 Proper Academic Conduct .......................................................................................... 26
3 | P a g e

11.2 Assignment Submission ............................................................................................... 26
11.3 Professional Group Work ............................................................................................. 26
13. References ................................................................................................. 28

4 | P a g e

1. Assignment Description
The aim of the assignment is for you to learn how transaction data can be
transformed to data to be used for data analytics (or business analytics). This group
assignment is designed for you to work in a team solving complex data-related
problem using Database Life Cycle (DBLC).
Based on a given case study, in this case GoGet an Australian sharing service, you
will apply the basic principles of database design for relational database and data
warehousing, which is part of the Big Data infrastructure. You should investigate
and use emerging trends and tools in database design. You will then create a
relational database and data warehouse in Oracle.
You will also evaluate and discuss data management and big data analytics
strategies. Microsoft Power BI is used as a data visualisation tool for Business
Intelligence.
In your presentation, your team will first demonstrate how transaction data is
created and saved in a relational database. Secondly, you will present how data is
then transformed and populated into a data warehouse. Finally, you will show how
the data in the data warehouse is used for data analytics.


2. Key Dates
Item Time
Project group formation By the end of Week 2 Lab
Project group contract (see separate
group contract document)
Due Date: Week 3, Friday, 4 March
2022, 4pm (Sydney Time)

Group Assignment Part A Feedback
Submission

via Moodle
Due Date: Week 5, Friday, 18 March
2022, 4pm (Sydney Time)

Group Assignment Part B Presentation
Submission
via Moodle
Due Date: Week 8, Friday, 8 April 2022,
4pm (Sydney Time)

Self and Peer Assessments via Moodle (UNSW Review)
Due Date: Week 9, Monday, 11 April
2022, 4pm (Sydney Time)


5 | P a g e

3. Summary of Submissions
There are two submissions:

(a) Group Assignment Part A Feedback:
• Due on: Week 5, Friday, 18 March 2022, 4pm (Sydney Time)
• No mark is allocated for this but your team’s action on the feedback given
on this submission will be assessed in Part B.
• The purpose of the first submission is to obtain in progress feedback from
the teaching team related to the group assignment.
• See Section 8 Group Assignment Part A Feedback Submission.

(b) Group Assignment Part B Presentation:
• Due on: Week 8, Friday, 8 April 2022, 4pm (Sydney Time)
• It is worth 30% of the course mark.
• Submission requirements:
o Coversheet
o PowerPoint slides
o Pre-recorded video PowerPoint presentation
o Oracle Zip file, and
o Self and peer assessment.
• See Section 9 Group Assignment Part B Presentation Submission.






6 | P a g e

4. Formation of Groups and Contract agreement
4.1 Formation of Groups
• You will sign up to a group in your class.
• All group members must come from the same class.
• You will form a group of four (three or five is only allowed if there is an uneven
number of students in the class, and can only be approved by the tutor)
• A group leader should be elected. The group leader is responsible for taking
the minutes in a meeting, submit assignments, update the planner, and
driving the team to complete the assignment on time.

4.2 Contract Agreement
• To ensure all the group members participate and contribute evenly to the
assignment, there will be a contract agreement to be negotiated and signed
by all the group members.
• A template of the contract agreement can be downloaded from Moodle.
• The contract agreement is an agreement between all the group members.
Thus, all the group members have to agree up front what tasks are to be
delivered and when the tasks are to be delivered.
• This contract agreement can be re-examined if one group member has
withdrawn from the course, or an unexpected event happened to one of the
group members. Please let the tutor know if the contract agreement has
changed.
• The group contract agreement to be signed by all group members and to be
submitted by the group leader on Moodle.

4.3 Tips based on Previous Experience
• Make every effort to learn Oracle, including outside the lab!
• Keep backup copies of all your work!
• Hold group meetings at least once, better twice, per week!
• Define roles and responsibilities within the team; especially you will need a
group leader (group coordinator for handling submissions, scheduling
meetings, etc.).


7 | P a g e

5. Private Group Channel (in Microsoft Teams)
• A private group channel will be created in Microsoft Teams by the teaching
team after the group formation at the end of Week 2.
• The name of your private group channel is same as your group ID.
• Only your group members and the teaching team will have access to your
private group channel. That is, no member from outside the group can
access to your private group channel.
• All conversations and files saved in the private group channel remain in the
channel.
• The purpose of the private group channel is 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.
• All the posts, files, meeting times and other group activities will be saved in
the channel.
• Another important factor of using the private group channel in Microsoft
Teams is it is transparent 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 planning of tasks.
• The whole team can access the planner so there will be no excuse such as, “I don’t
know what’s going on”.
• Notifications can be used as a reminder task to be completed.
• Microsoft Planner should be maintained by the group leader. 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)


8 | P a g e

6. Case study

6.1 Introduction
GoGet is a car sharing start-up company formed in 2003. You probably have seen
GoGet CarShare vehicles around Sydney. We had a research relationship. A case
study for GoGet was published by Tan et al (2017).
The business of GoGet has expanded since it first started in 2003. Instead of just
focusing on B2C (Business to Customer), it is now in B2B (Business to Business)
environment. As shown in Figure 1, it also provides car sharing services for students
(GoStudent). Today, GoGet has provided car sharing services to the business as well.
Thus, it starts to compete with the car hire companies such as Hertz car rentals and
Avis.


Figure 1 GoGet Business (Tan et al., 2017, p.269)

Your team (= assignment group) has been hired as a group of technical consultants
by GoGet to redevelop their database and data warehouse. Moreover, they want
you to develop a business intelligence platform to produce some basic reports. The
first stage of the project is to demonstrate as a proof of concept that the
introduction of a data warehouse will help to improve the speed and accuracy of
producing reports. As this is a proof of concept project, we do not expect you to
produce a fully functional database for GoGet.



9 | P a g e

6.2 Information related to GoGet
You can find information and a case study related to GoGet from the following links.
• GoGet Website:
➢ GoGet - Australia's Leading Car Share Network
• An article on GoGet Case Study by Tan et al. (2017) [Note: due to the license
agreement, you can only download the article at the UNSW campus]:
➢ "How GoGet CarShare's Product-Service System is Facilitating Collaborat"
by Felix Ter Chian Tan, Michael Cahalane et al. (aisnet.org) [Note: there is
a presentation PowerPoint slides you can also download].
You can also find plenty of other information related to GoGet on the Internet,
which you can use in the group assignment.

6.3 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 and not the full system. The purpose is to show viability of the
proposal of the system. It also helps stakeholders of the project to visualise what
the system can deliver or sometimes we call it a “stakeholder buy-in”.
In this project, you do not expect to develop a full system. The purpose of this Proof
of Concept Project is to evaluate the feasible of using data warehouse for reporting.
You introduce the concept of using data warehouse to provide data for creating
reports in using the business intelligence tools.
You just have to demonstrate:
(a) how a transaction data is captured in a relational database,
(b) how the data is then transferred to a data warehouse, and
(c) how the reports are generated using the data warehouse.

6.4 Requirements for the GoGet System
Instead of us giving you the requirements for the GoGet System, you can gather
most of the requirements from interpreting the GoGet website. The website has
plenty of information related to the car sharing. You can create a reasonable
GoGet’s business model from the website. For example, to work out the revenue
of GoGet, you can simply examine the pricing model on the website. There are five
pricing plans (see Figure 2), and you can make a reasonable assumption that a
customer has to select one of the plans (see Join GoGet Car Share - Compare Plans
and Membership) to hire a vehicle. Based on a plan, you can work out the revenue
generated.
10 | P a g e


Figure 2 GoGet Five Pricing Plans
There is some information not on the website such as the cost of a vehicle which is
part of the business model of GoGet. You can exclude them as you already enough
information for the project. However, if you want to include information not on the
website in your project, you can do it as long as you can make a reasonable
assumption. For example, you cannot say all vehicles worth $20,000 but you can
say vehicle A worth $25,000 and vehicle B worth $55,000, and so on.
There are three sections of the project shown in Figure 3 you need to address:
(a) Section A Entity Relationship Model and Relational Database (Oracle)
(b) Section B Star Schema and Data Warehouse (Oracle)
(c) Section C Business Intelligence (Microsoft PowerBI)

Figure 3 Three Sections Required in Proof in Concept Project
11 | P a g e

We will now go through the three sections.
6.3.1 Section A Entity Relationship Model and Relational Database (Oracle)
(a) Looking at the GoGet website, you can make a reasonable business model.
(b) You do not expect to address the whole business model. In this Proof of
Concept project, you have to decide which part of the model you want to
demonstrate. This will be the scope of your project. Do not define the scope
to be too large as you might find it too overwhelming to complete.
(c) You have to create an Entity-Relationship model (ERM) based on your scope
defined in (b).
[This ERM is to be submitted for feedback as part of Part A submission – see
the requirements in 8. Group Assignment Part A Feedback Submission.]
(d) A schema is generated from the ERM.
(e) The model must be normalised to 3NF or BCNF.
(f) The number of tables to be generated is based on the number of members
in your group. As a rule of thumb, you have to create at least four tables per
group member. For example, a four-member group will have to create at
least sixteen tables, but you can create more tables as required.
(g) If you do not have enough tables in your relational database, then you might
find it difficult to create enough attributes for the fact table and dimensions
in the data warehouse (in Section B).
(h) You have a choice of using one of these tools to create your ERM:
(1) Oracle SQL Developer/Data Modeler or
(2) draw.io (used in INFS1603).
(i) As for the notation, you have a choice of using:
(1) Barker (default notation used in Oracle SQL Data Modeler) or
(2) Chen (learned in INFS1603) or
(3) Crow Foot (used in the textbook).
(j) The selection of a tool and a notation in (h) and (i) will not impact on how
you will be marked. Also, see 8. Group Assignment Part A Feedback
Submission for more information related the selection of tool and notation.
[Note: The advantage of using Oracle SQL Data Modeler/Developer is the
ERM and tables are automatically generated by the software.]
(k) Implement a relational database in Oracle based on your relational
database schema. Populate the tables of the database with at least ten
sample records in each table. Create data with proper names, description,
and values such as prices from the GoGet’s Website. For example, do not
have a name called “ABC” or “XYZ”. Ensure that you have adequate data to
run and test queries and showcase the database.
12 | P a g e

(l) From the website, it is difficult to say if GoGet uses GPS to track the
movement of the vehicle. If they do, they might use Hadoop or something
similar. If that is the case, it will be outside the scope of the project. You do
not have to worry about Hadoop.
(m) Most of GoGet vehicles park in “pods”. Pod is a destination parking spot
provided by council or developer partners (see Basic GoGet Rules | GoGet
Help Center). Therefore, for this project, you can assume a vehicle is parked
on a pod or near a pod, and you can find the vehicle’s location easily.
(n) You do not need to write any computer programs or use Oracle Apex for
data entries. You use Oracle SQL statements defined in Data Manipulation
Language (DML) to insert, update, or delete data records.

6.3.2 Section B Star Schema and Data Warehouse (Oracle)
(a) A star schema is to be created based on the ERM.
(b) You have to show how a fact table and dimension tables in a star schema
are created from tables in the relational database or ERM in Section A. A
star schema should be de-normalised. You can go one step further to create
a snowflake schema or even a galaxy schema as your data warehouse model.
Any of the three schemas is fine for this project.
[Either a star or a snowflake or a galaxy schema is to be submitted for
feedback as part of Part A submission – see the requirements in 8. Group
Assignment Part A Feedback Submission.]
(c) You have to create a new calendar dimension table and populate the table
with data.
(d) Apart from adding a calendar dimension table, if you have any other
dimension tables or even a fact table not based on ERM, you have to explain
why you need to create such table.
(e) Once the schema is created, you can create the tables and at least one
materialized view in Oracle. Data warehouse is made up of tables (classified
as fact and dimension) and materialized view.
(f) You must populate the tables with data from the relational database using
Oracle SQL statements defined in Data Manipulation Language (DML).
(g) The schema (star, snowflake, or galaxy) and data warehouse must be
associated with the ERM and relational database.
(h) You do not need to worry about the storage parameters for the data
warehouse.




13 | P a g e

6.3.3 Section C Business Intelligence (Microsoft PowerBI)
(a) You will create a Microsoft PowerBI using the tables from the data
warehouse created in Section B.
(b) You might want to create one or two tables and one or two graphs. The
tables and graphs in PowerBI just have to be simple and not complex.
(c) As part of the proof of concept, you have to demonstrate:
(1) some transaction data created in the relational database (in Section
A),
(2) the data are then added or updated to a fact table in the data
warehouse (in Section B), and
(3) the data is retrieved using a materialized view from the data
warehouse and displays in a graph (or a table).

6.3.4 QnA Support for the Assignment
(a) A general channel will be set up in Microsoft Teams for Questions and
Answers (QnA). All questions related to the group assignment should be
posted in the channel.
(b) All announcements from the teaching team related to the assignment will
be posted in this channel.
(c) Before posting your questions, please check in the channel that your
question has not been answered.
(d) Please do not send your lecturer and tutors an email with your questions
because if you have a question, then someone might have the same
question as well. If you send us an email, we will ask you to post your
question.





14 | P a g e

7. Tasks and Deliverables

7.1 Part A ERM and DW Model Feedback
(1) Create an Entity-Relationship model (ERM) based on your defined scope and
normalised to 3NF or BCNF. The defined scope and assumptions have to be
reasonable.
(2) Create one of the three types of schemas, namely star, snowflake or galaxy,
as data warehouse model.
For more information, please see 8. Section Group Assignment Part A Feedback
Submission.

7.2 Part B PowerPoint Slides
(1) PowerPoint Structure:

First slide ▪ This slide should have your group number and names, with
individual pictures if you like.
Main slides ▪ A maximum number of slides is 5 main PowerPoint (PP) slides
per group member.
For example, for a 4-member group, you have a maximum
of 20 main PP slides. However, you can present less
than 20 main PP slides.
Appendix slide(s) ▪ Apart from the main PP slides, you can have appendix slide(s)
– the slide after main slides is treated as Appendix. You can
include SQL code, diagram, charts, your analysis, or extra
findings, which are not used in the presentation. A maximum
of 12 extra slides can be included.
Reference slide(s) Include any references used in the assignment

(a) You add notes in the speaker notes or notes page section of the PP slide,
at least for the Main slides. The number of words in the speaker notes or
Notes Page should not be more than 300 words per slide. However, you
do not have to present in exact wording as on the speaker notes.
(b) You also have to state in the speaker notes or notes page which group
member(s) wrote the notes and which group member presents in the pre-
recorded video. This does not count towards the 300 words limit. For
example,
(i) This slide wrote by: Vincent Pang and Silvia Lin
(ii) This slide presented by: Silvia Lin

(c) On the top of each slide, you show the name or initials, and/or a picture
of the presenter. You can also do the same for the Appendices slides.
15 | P a g e

(2) Define the scope for the proof for concept project based on GoGet website.
You might need to list any assumptions for the project.
(3) Submit a revised ERM. Describe the changes to the model briefly (changes
may or may not arise from the feedback on Part A and the experience in the
implementation process).
(4) Provide a revised schema for data warehouse model. Describe the changes
to the model briefly (changes may or may not arise from the feedback on
Part A and the experience in the implementation process).
(5) Use the Oracle skills you gained from the labs, lab exercises and textbook to
implement a relational database in Oracle based on your ERM, i.e., the
relational database schema. Populate the tables of the database with at
least ten sample records in each table.
(6) Use the Oracle skills you gained from the labs, lab exercises and textbook to
implement a data warehouse in Oracle based on your schema, i.e., star,
snowflake, or galaxy. Populate the tables from the relational database in (5)
and create a calendar dimension table.
(7) Use the Microsoft PowerBI skills you gained from the labs, lab exercises and
textbook to create a few data visualisation tables or graphs in Microsoft
PowerBI. You must draw the data directly from data warehouse in Oracle
into Microsoft PowerBI.
(8) The distribution of work on Oracle and PowerBI should be done evenly. You
are expected to learn Oracle and PowerBI as part of your technical skills
development. Try to avoid having two group members to do all the technical
components and the remaining group members spend their time on the
PowerPoint slides. This will defeat the purpose of learning both technical
and soft skills.
(9) In addition to what you have done in (1) to (8), you also need to provide a
discussion of any noteworthy features you have created, a description of
possible improvements and a discussion of limitations (problems,
constraints, and future work) of the project if any. Two to three slides should
be sufficient to cover all the discussions.
For more information, please see 9. Section Group Assignment Part B Presentation
Submission.

7.3 Part B Pre-recorded Video Presentation
1. Time Limit: As a guide, time for presentation is 4 minutes per group member.
For example, for a 4-member group, you have a maximum of 16 minutes to
present. However, you can present less than 16 minutes.
2. All group members are expected to present. If an individual does not
contribute to presentation without a good reason, then his/her mark might
be adjusted accordingly.
16 | P a g e

3. Presentation time: each group member should try to present their allocated
4 minutes. The group leader should try to distribute the slides and
presentation time evenly. If a group member writes most of the notes for
the PowerPoint slides, then that group member can have less presentation
time to even out the contribution. However, the group leader has to alert
us (the teaching team) at the beginning of the presentation such as during
the introduction that this group member has done most of work on the
slides and the rests will have more presentation times.
4. The video must be saved in MP4 video format.
5. The group will be awarded a group mark as a baseline mark. This baseline
mark may or may not be adjusted for the individual group members (based
on peer review).
6. There is also an individual presentation component. This is based on how an
individual presents his/her part. If a group member does not have a camera
on, then the person can only be judged on the voice. If a group member’s
time of presentation is reduced for a good reason, the mark will be adjusted
accordingly. [Tip: try not to read the notes without any expression.]

For more information, please see 9. Section Group Assignment Part B Presentation
Submission.



17 | P a g e

8. Group Assignment Part A Feedback Submission
Title: Group Assignment Part A Feedback
Weighting: 0% (No mark)
Due date: Week 5, Friday, 18 March 2022, 4pm (Sydney Time)
Assignment type: Report
Length: Not more than 5 pages.
A template file (Word Document) can be downloaded
from Moodle.
Submission requirements:
(a) Coversheet: Submit a signed UNSW coversheet.
Failure to include signatures from all group
members on the coversheet might not receive
feedback.
(b) A report (a report template is provided and can be
downloaded from Moodle)

Submission Box: Moodle > Assignments > Group Assignment Part A
Feedback submission

Late Submission: Late feedback might be given for late submission

Feedback: You will receive your feedback within one week of the
due date.

Purpose:
In the Part A of the group assignment, the requirements are to design two
models:
(1) You design an entity relationship (ER) model based on the case study.
The model must be normalised.
(2) You then design a data warehouse (DW) model based on the ER model
you have designed in (a). Both models must be associated with one
another.


18 | P a g e

8.1 Tool and Notation for Model
To create these models, you have a choice of one of these tools:
(1) Oracle SQL Developer/Data Modeler, or
(2) draw.io.

As for the notation, you have a choice of using:
(3) Barker (default notation used in Oracle SQL Data Modeler) or
(4) Chen (learned in INFS1603) or
(5) Crow Foot (used in the textbook).

Selection of tool(s) and notation:
(6) If you were to use the Oracle SQL Developer/Data Modeler to create the
models, then by default, you will use Barker notation. The bright side of
using the Data Modeler is attributes, tables, keys, and other parameters
will all be created automatically.
(7) If you were to use either Chen or Crow Foot notation, you still need to use
Oracle SQL Developer to create the tables.
(8) You can create attributes, tables, keys, and other parameters first in
Oracle SQL Developer, and then reverse engineer back to an ERM. Please
note that there are some limitations such as sub-types might not be
generated in the reverse engineering process (if that is the case, you have
to state the sub-types).

8.2 Format and Deliverables
(a) You download a report template from Moodle.
(b) For Part A assignment for feedback, you have to create two models
using one of the suggested tools.
(c) The two models are then transferred to a report.
(d) You might want to include some brief notes related to the two models
in the report.
(e) You do not need to have a workable database, i.e., you do not need to
create all the tables and populate the database with data.
Note: No mark is allocated for this but your team’s action on the feedback given
on this submission will be assessed in Part B.



19 | P a g e

9. Group Assignment Part B Presentation Submission
Title: Group Assignment Part B Presentation
Weighting: 30%
Due date: Week 8, Friday, 8 April 2022, 4pm (Sydney Time)
Assignment type: Pre-recorded Video Presentation
Length: PowerPoint Presentation based on 4 min per group
member
Group work:
(a) Group task assessed on both the outcome and the group
processes
(b) Marks will be given to all members equally depending on
the outcome and/or group processes
Submission requirements:
(a) Coversheet
(b) Oracle Zip file
(c) PowerPoint slides (Please do not submit in pdf file format)
(d) Pre-recorded Video PowerPoint Presentation
(e) Self and peer assignment (Individuals)
Note: You do not need to submit a written report.
Submission Box:
Moodle > Assignments > 1. Group Assignment Part B
(excluding video) Submission Box

(a) Coversheet,
(b) PowerPoint slides, and
(c) Oracle Zip file.

Moodle > Assignments > 2. Assignment Part B Pre-
recorded PowerPoint Presentation Video Presentation
Submission Box
[Note: This is a BoxMedia collection submission box]

(d) Pre-recorded Video PowerPoint Presentation

Moodle > Assignments > 3. Self and Peer Assignment
(UNSW Review)

(e) Self and peer assessments (Individuals) (Due on 11
April 2022, 4pm)
20 | P a g e

Late Submission: Penalties apply for late submission as indicated in the
course outline

Grades and Feedback: You will receive your grade and feedback within two
weeks of the due date.







21 | P a g e

9.1 Group Assignment Part B Requirements
For this assignment, you need to design and implement a database according to the
scenario and requirements. You are to design a ERM and a data warehouse model
in Part A of the assignment. You then using these models to implement to a
relational database and data warehouse respectively using Oracle SQL in Part B of
the assignment. The completed assignment in Part B will also be presented in an
oral (video) presentation.
Your assignment is evaluated based on rubrics (see Section 9), self and peer
assessment (see Section 10) and submission rules as indicated as part of the
deliverables (such as file naming).

9.2 Assignment Part B / Format and Deliverables
1. UNSW Coversheet. Submit your assignment with a signed coversheet of all
group members. Failure to include the UNSW coversheet with signatures will
lead to 5% penalty, and no marks will be released until the coversheet is
received.

2. PowerPoint slides are created based on your group activities as previously
discussed.
First slide This slide should have your group number and names, with
individual pictures if you like.
Main slides ▪ A maximum time of presentation is 4 minutes
per group member.
▪ A maximum number of slides is 5 main
PowerPoint (PP) slides per group member.
For example, for a 4-member group, you
have a maximum of 16 minutes to
present and a maximum of 20 main PP
slides. However, you can present less
than 16 minutes and have less than 20
main PP slides.
Appendix slide(s) Apart from the main PP slides, you can have
appendix slide(s) – the slide after main slides is
treated as Appendix. You can include SQL code,
diagram, charts, your analysis, or extra findings,
which are not used in the presentation. A
maximum of 12 extra slides can be included.
Reference slide(s) Include any references used in the assignment

o Note: the marker will not give any additional marks for slides in the
appendix.
22 | P a g e

3. Pre-recorded video presentation is created based on the PowerPoint slides.
The video must be saved in MP4 video format. All group members must
present. If an individual does not contribute to video presentation without a
good reason, then his or her mark might be adjusted accordingly. It will be
assessed as a group as well as an individual for the presentation.
➢ Support for Oral Presentations | UNSW Current Students
➢ Present in PowerPoint Using PowerPoint | UNSW Current Students

4. Oracle ZIP File. The ZIP file should contain all code of your system (Oracle
implementation) of the project. Include a snapshot of the relational schema
and script file(s) to create tables including constraints / scripts file(s) to insert
rows/records into tables (note: you must arrange a logical order of inserting
records into the tables to avoid violating the table constraints). An “SQL dump”
will typically be sufficient to fulfil these requirements. Generally, make sure
that we are able to re-create your implementation based on your digital
submission alone. Provide the SQL queries and their results in a digital format.

5. File naming: the files should be named as:
a. Coversheet: CourseCode-GroupID-Assignment-B.docx
b. PowerPoint: CourseCode-GroupID-Assignment-B.pptx
c. Pre-recorded Video: CourseCode-GroupID-Assignment-B.mp4 and
d. Oracle Files: CourseCode-GroupID-Assignment-B.ZIP.

6. Your group will be assigned a GroupID. Failure to use the correct file naming
will lead to a 5% penalty. The group names are NOT 01, 02, etc. The Group
names include your tutorial session code. Please refer to Moodle to get your
complete/correct group names.

7. Only one submission per group. The Team Leader (or a delegated person) is
to complete the submission. Fail to comply will lead to a 5% penalty.

8. The clarity and readability of your diagrams are very important. You can
divide your diagram over more than one slide if needed.

9. References. References and citations should follow either the UNSW
(Harvard) or the APA citation style standard.

23 | P a g e

10. Rubrics
M
A
R
K
IN
G
C
R
IT
ER
IA
H
IG
H
D
IS
T
IN
C
TI
O
N
(
H
D
)
85
-1
0
0
D
IS
T
IN
C
TI
O
N
(
D
)
75
-8
4
C
R
ED
IT
(
C
R
)
65
-7
4
P
A
SS
(
P
)
50
-6
4
FA
IL
(
FL
)
B
EL
O
W
5
0
P
LO
R
e
q
u
ir
e
m
e
n
t
A
n
al
ys
is
(
1
5
%
)
R
e
le
va
n
t
st
a
ke
h
o
ld
e
rs
a
n
d
c
o
n
te
xt
u
al
f
ac
to
rs
a
re
c
le
ar
ly

e
st
ab
lis
h
e
d
a
n
d
c
o
n
si
d
e
re
d
.
M
o
re
o
ve
r,
t
h
e
s
co
p
e
,
o
b
je
ct
iv
e
s,
a
n
d
a
p
p
ro
p
ri
at
e
d
is
cu
ss
io
n
r
e
fl
e
ct
a
h
ig
h
ly

so
p
h
is
ti
ca
te
d
a
n
al
ys
is
o
f
th
e
s
ce
n
ar
io
a
n
d
s
tr
o
n
g
e
vi
d
e
n
ce

o
f
in
d
e
p
e
n
d
e
n
t
re
se
ar
ch
.
R
e
le
va
n
t
st
a
ke
h
o
ld
e
rs
a
n
d
c
o
n
te
xt
u
al
f
ac
to
rs
a
re

ap
p
ro
p
ri
at
e
ly
c
o
n
si
d
e
re
d
.
M
o
re
o
ve
r,
t
h
e
s
co
p
e
a
n
d

o
b
je
ct
iv
e
s'
is
su
e
s
ar
e
t
h
o
u
gh
tf
u
lly
d
is
cu
ss
e
d
a
n
d
w
e
ll
ju
st
if
ie
d
.
So
m
e
e
vi
d
e
n
ce
o
f
in
d
e
p
e
n
d
e
n
t
re
se
ar
ch
, b
ac
ke
d

u
p
b
y
d
e
ta
ile
d
a
n
al
ys
is
.
R
e
le
va
n
t
st
a
ke
h
o
ld
e
rs
a
re
c
le
ar
ly
id
e
n
ti
fi
e
d
, a
n
d

co
n
te
xt
u
al
f
ac
to
rs
c
o
n
si
d
e
re
d
.
M
o
re
o
ve
r,
t
h
e

sc
o
p
e
a
n
d
o
b
je
ct
iv
e
s'
is
su
e
s
ar
e
r
e
as
o
n
ab
ly

d
is
cu
ss
e
d
.
A
d
e
q
u
at
e
c
o
n
si
d
e
ra
ti
o
n
o
f
st
ak
e
h
o
ld
e
rs
a
n
d

co
n
te
xt
u
al
f
ac
to
rs
is
p
ro
vi
d
e
d
w
it
h
a
r
e
as
o
n
ab
le

at
te
m
p
t
to
c
o
n
si
d
e
r
th
e
p
ro
je
ct
s
co
p
e
a
n
d

o
b
je
ct
iv
e
s,
w
h
ile
t
h
e
d
is
cu
ss
io
n
o
f
sc
o
p
e
a
n
d

o
b
je
ct
iv
e
s
is
u
n
d
e
rd
e
ve
lo
p
e
d
.
C
o
n
si
d
e
ra
ti
o
n
s
o
f
st
ak
e
h
o
ld
e
rs
a
n
d
c
o
n
te
xt
u
al

fa
ct
o
rs
a
re
m
is
si
n
g
o
r
m
ar
gi
n
al
, o
r
th
e
s
co
p
e

an
d
o
b
je
ct
iv
e
s
o
f
th
e
p
ro
je
ct
a
re
m
is
si
n
g
o
r
in
si
gn
if
ic
an
t.
P
LO
1
:
B
u
si
n
e
ss

kn
o
w
le
d
ge
P
LO
2
:
P
ro
b
le
m

so
lv
in
g
ER
D
a
n
d
D
W
D
e
si
gn

(4
0
%
)
Th
e
E
R
m
o
d
e
lli
n
g
an
d
S
ta
r
Sc
h
e
m
a
te
ch
n
iq
u
e
s
ar
e
c
o
rr
e
ct
ly

d
e
m
o
n
st
ra
te
d
a
n
d
is
f
u
lly
a
lig
n
e
d
w
it
h
t
h
e
c
as
e
s
ce
n
ar
io

(e
sp
.
n
o
e
n
ti
ty
is
m
is
si
n
g
o
r
is
s
ig
n
if
ic
an
tl
y
m
is
sp
e
ci
fi
e
d
).
A
ll
P
K
s,
F
K
s,
r
e
la
ti
o
n
sh
ip
, c
o
n
n
e
ct
iv
it
ie
s
an
d
c
ar
d
in
al
it
ie
s
ar
e

ac
cu
ra
te
ly
id
e
n
ti
fi
e
d
a
n
d
n
o
te
d
in
t
h
e
E
R
a
n
d
D
W
m
o
d
e
ls
.
A
ss
u
m
p
ti
o
n
s
(e
.g
.,
s
u
p
p
o
rt
y
o
u
r
n
o
ta
ti
o
n
s
o
f
ca
rd
in
al
it
y
an
d

co
n
n
e
ct
iv
it
y)
a
re
c
le
ar
ly
g
iv
e
n
a
n
d
ju
st
if
ie
d
.
B
o
th
m
o
d
e
ls
a
re
c
o
rr
e
ct
a
n
d
c
o
m
p
le
te
ly
r
e
fl
e
ct
t
h
e

as
si
gn
m
e
n
t
sc
e
n
ar
io
a
n
d
t
h
e
E
R
m
o
d
e
l.
T
h
e
E
R
m
o
d
e
l i
s
ac
cu
ra
te
ly
/e
xc
e
p
ti
o
n
al
ly
v
is
u
al
ly
s
tr
u
ct
u
re
d
(
e
as
y
to
r
e
ad

an
d
c
o
m
p
re
h
e
n
d
)
an
d
n
o
rm
al
is
e
d
.
Th
e
s
ta
r
sc
h
e
m
a
in
t
h
e

D
W
m
o
d
e
l i
s
vi
su
al
ly
s
tr
u
ct
u
re
d
(
e
as
y
to
r
e
ad
a
n
d

co
m
p
re
h
e
n
d
).
R
e
ad
ab
ili
ty
:
Th
e
t
w
o
m
o
d
e
ls
a
re
v
e
ry
w
e
ll
d
e
p
ic
te
d
a
n
d
e
as
y
to
r
e
ad
(
cl
e
ar
f
o
n
ts
, c
o
lo
u
rs
, e
tc
.
ar
e
u
se
d
f
o
r
re
ad
ab
ili
ty
).
Th
e
E
R
m
o
d
e
lli
n
g
an
d
S
ta
r
Sc
h
e
m
a
te
ch
n
iq
u
e
s
ar
e
c
o
rr
e
ct
ly

d
e
m
o
n
st
ra
te
d
a
n
d
a
re
a
lig
n
e
d
w
it
h
t
h
e
c
as
e
s
ce
n
ar
io
(
n
o

m
o
re
t
h
an
o
n
e
r
e
la
ti
o
n
o
r
en
ti
ty
is
m
is
si
n
g
o
r
is
s
ig
n
if
ic
an
tl
y
m
is
sp
e
ci
fi
e
d
).
P
K
s,
F
K
s,
r
e
la
ti
o
n
sh
ip
, c
o
n
n
e
ct
iv
it
ie
s
an
d

ca
rd
in
al
it
ie
s
ar
e
a
cc
u
ra
te
ly
id
e
n
ti
fi
e
d
a
n
d
n
o
te
d
w
it
h
e
q
u
al

to
o
r
le
ss
t
h
an
t
h
re
e
m
in
o
r
er
ro
rs
/m
is
ta
ke
s
(e
.g
, m
is
si
n
g
tw
o
a
tt
ri
b
u
te
s
in
o
n
e
o
f
th
e
t
a
b
le
s)
.
A
ss
u
m
p
ti
o
n
s
(e
.g
.,
s
u
p
p
o
rt
y
o
u
r
n
o
ta
ti
o
n
s
o
f
ca
rd
in
al
it
y
an
d

co
n
n
e
ct
iv
it
y)
a
re
c
le
ar
ly
p
ro
vi
d
e
d
.
B
o
th
m
o
d
e
ls
a
re
c
o
rr
e
ct
a
n
d
m
o
st
ly
r
e
fl
e
ct
t
h
e
a
ss
ig
n
m
e
n
t
sc
e
n
ar
io
a
n
d
t
h
e
E
R
m
o
d
e
l.
B
o
th
E
R
a
n
d
D
W
m
o
d
e
ls
(
n
o

m
o
re
t
h
an
o
n
e
t
a
b
le
is
m
is
si
n
g
o
r
n
o
t
m
at
ch
in
g
th
e
E
R

m
o
d
e
l o
r
o
n
e
d
im
e
n
si
o
n
is
m
is
si
n
g)
.
Th
e
E
R
m
o
d
e
l i
s
cl
e
ar
ly

vi
su
al
ly
s
tr
u
ct
u
re
d
(
e
as
y
to
r
e
ad
a
n
d
c
o
m
p
re
h
e
n
d
)
an
d

n
o
rm
al
is
e
d
.
R
e
ad
ab
ili
ty
:
Th
e
m
o
d
e
l i
s
ve
ry
w
e
ll
d
e
p
ic
te
d
a
n
d
e
as
y
to

re
ad
(
cl
e
ar
f
o
n
ts
, c
o
lo
u
rs
, e
tc
.
ar
e
u
se
d
f
o
r
re
ad
ab
ili
ty
).
Th
e
E
R
m
o
d
e
lli
n
g
an
d
S
ta
r
Sc
h
e
m
a
te
ch
n
iq
u
e
s
ar
e
d
e
m
o
n
st
ra
te
d
a
n
d
r
e
as
o
n
ab
ly
a
lig
n
e
d
w
it
h

th
e
c
as
e
s
ce
n
ar
io
w
it
h
m
is
si
n
g/
m
is
sp
e
ci
fi
e
d

e
n
ti
ti
e
s
o
r
re
la
ti
o
n
s.
P
K
s,
F
K
s,
r
e
la
ti
o
n
sh
ip
,
co
n
n
e
ct
iv
it
ie
s
an
d
c
ar
d
in
al
it
ie
s
ar
e
id
e
n
ti
fi
e
d

an
d
n
o
te
d
, w
it
h
m
o
re
t
h
an
t
h
re
e
m
in
o
r
e
rr
o
rs
/m
is
ta
ke
s/
in
co
n
si
st
e
n
ci
e
s.
A
ss
u
m
p
ti
o
n
s
(e
.g
.,
s
u
p
p
o
rt
y
o
u
r
n
o
ta
ti
o
n
s
o
f
ca
rd
in
al
it
y
an
d
c
o
n
n
e
ct
iv
it
y)
a
re
p
ro
vi
d
e
d
.
B
o
th
m
o
d
e
ls
a
re
g
e
n
e
ra
lly
c
o
rr
e
ct
a
n
d
r
e
fl
e
ct

th
e
a
ss
ig
n
m
e
n
t
sc
e
n
ar
io
.
B
o
th
E
R
a
n
d
D
W

m
o
d
e
ls
a
re
m
o
st
ly
v
is
u
al
ly
s
tr
u
ct
u
re
d
.
R
e
ad
ab
ili
ty
:
Th
e
m
o
d
e
l i
s
ve
ry
w
e
ll
d
e
p
ic
te
d
a
n
d

e
as
y
to
r
e
ad
(
cl
e
ar
f
o
n
ts
, c
o
lo
u
rs
, e
tc
.
ar
e
u
se
d

fo
r
re
ad
ab
ili
ty
).
Th
e
E
R
m
o
d
e
lli
n
g
an
d
S
ta
r
Sc
h
e
m
a
te
ch
n
iq
u
e
s
ar
e
m
ai
n
ly
d
e
m
o
n
st
ra
te
d
w
it
h
s
o
m
e
a
lig
n
m
e
n
t
b
e
tw
e
e
n
E
R
D
a
n
d
S
ta
r
Sc
h
e
m
a.
T
h
e
m
o
d
e
ls
a
re

al
ig
n
e
d
w
it
h
t
h
e
c
as
e
s
ce
n
ar
io
w
it
h
t
h
re
e
o
r
m
o
re
m
is
si
n
g/
m
is
sp
e
ci
fi
e
d
e
n
ti
ti
e
s
o
r
re
la
ti
o
n
s.
Th
e
r
e
la
ti
o
n
al
m
o
d
e
l a
n
d
S
ta
r
Sc
h
e
m
a
ex
e
cu
ti
o
n

ar
e
a
d
e
q
u
at
e
.
R
e
ad
ab
ili
ty
:
Th
e
m
o
d
e
l c
an
b
e
r
e
ad
(
fo
n
ts
,
co
lo
u
rs
, e
tc
.
ar
e
r
e
as
o
n
ab
le
s
e
le
ct
e
d
f
o
r
re
ad
ab
ili
ty
).
Ev
id
e
n
ce
o
f
sy
st
e
m
at
ic
al
ly
w
ro
n
g
m
o
d
e
lli
n
g
te
ch
n
iq
u
e
:
th
e
E
R
D
d
ia
gr
am
a
n
d
s
ta
r
sc
h
e
m
a
ar
e

m
is
si
n
g
o
r
co
m
p
le
te
ly
in
ap
p
ro
p
ri
at
e
f
o
r
th
e
c
as
e

sc
e
n
ar
io
.
Th
e
r
e
la
ti
o
n
al
m
o
d
e
l a
n
d
S
ta
r
Sc
h
e
m
a
ex
e
cu
ti
o
n

ar
e
p
o
o
rl
y
d
o
n
e
.
R
e
ad
ab
ili
ty
:
Th
e
m
o
d
e
l c
an
h
ar
d
ly
b
e
r
e
ad

(f
o
n
ts
, c
o
lo
u
rs
, e
tc
.
ar
e
n
o
t
w
e
ll
se
le
ct
e
d
f
o
r
re
ad
ab
ili
ty
).
P
LO
1
:
B
u
si
n
e
ss

kn
o
w
le
d
ge
P
LO
2
:
P
ro
b
le
m

so
lv
in
g
ER
D
a
n
d
D
W

Im
p
le
m
e
n
ta
ti
o
n

(S
Q
L
St
a
te
m
e
n
ts
)
(1
0
%
)
Th
e
S
Q
L
st
at
e
m
e
n
ts
f
o
r
ER
D
a
n
d
S
ta
r
Sc
h
e
m
a
ar
e
c
le
ar
ly

st
at
e
d
a
n
d
e
as
ily
f
o
llo
w
e
d
lo
gi
ca
lly
w
it
h
c
o
n
st
ru
ct
iv
e

co
m
m
e
n
ts
.
A
ll
ta
b
le
s,
P
K
s,
F
K
s,
r
e
la
ti
o
n
sh
ip
, c
o
n
n
e
ct
iv
it
ie
s
an
d

ca
rd
in
al
it
ie
s
ar
e
c
o
rr
e
ct
ly
id
e
n
ti
fi
e
d
a
n
d
n
o
te
d
.
D
at
a
d
e
fi
n
it
io
n
a
n
d
d
at
a
in
se
rt
io
n
t
o
im
p
le
m
e
n
t
th
e
D
B
a
re

fu
lly
p
ro
vi
d
e
d
.
Th
e
S
Q
L
st
at
e
m
e
n
ts
f
o
r
ER
D
a
n
d
S
ta
r
Sc
h
e
m
a
ar
e
c
le
ar
ly

st
at
e
d
a
n
d
e
as
ily
f
o
llo
w
e
d
b
y
so
m
e
c
o
m
m
e
n
ts
.
A
ll
ta
b
le
s,
P
K
s,
F
K
s,
r
e
la
ti
o
n
sh
ip
, c
o
n
n
e
ct
iv
it
ie
s
an
d

ca
rd
in
al
it
ie
s
ar
e
c
o
rr
e
ct
ly
id
e
n
ti
fi
e
d
a
n
d
n
o
te
d
w
it
h
m
in
o
r
e
rr
o
rs
.
D
at
a
d
e
fi
n
it
io
n
a
n
d
d
at
a
in
se
rt
io
n
t
o
im
p
le
m
e
n
t
th
e
D
B
a
re

fu
lly
p
ro
vi
d
e
d
.
Th
e
S
Q
L
st
at
e
m
e
n
ts
f
o
r
ER
D
a
n
d
S
ta
r
Sc
h
e
m
a
ca
n
b
e
f
o
llo
w
e
d
w
it
h
s
o
m
e
c
o
m
m
e
n
ts
.
M
o
st
o
f
th
e
t
a
b
le
s,
P
K
s,
F
K
s,
r
e
la
ti
o
n
sh
ip
,
co
n
n
e
ct
iv
it
ie
s
an
d
c
ar
d
in
al
it
ie
s
ar
e
c
o
rr
e
ct
ly

id
e
n
ti
fi
e
d
b
u
t
w
it
h
s
o
m
e
m
in
o
r
er
ro
rs
.
D
at
a
d
e
fi
n
it
io
n
a
n
d
d
at
a
in
se
rt
io
n
t
o
im
p
le
m
e
n
t
th
e
D
B
a
re
p
ar
ti
al
ly
p
ro
vi
d
e
d
.
Th
e
S
Q
L
st
at
e
m
e
n
ts
f
o
r
ER
D
a
n
d
S
ta
r
Sc
h
e
m
a
ar
e
d
if
fi
cu
lt
t
o
f
o
llo
w
w
it
h
n
o
o
r
m
in
im
al

co
m
m
e
n
ts
.
So
m
e
o
f
th
e
t
a
b
le
s,
P
K
s,
F
K
s,
r
e
la
ti
o
n
sh
ip
,
co
n
n
e
ct
iv
it
ie
s
an
d
c
ar
d
in
al
it
ie
s
ar
e
m
is
si
n
g
o
r
in
co
rr
e
ct
ly
id
e
n
ti
fi
e
d
.
D
at
a
d
e
fi
n
it
io
n
a
n
d
d
at
a
in
se
rt
io
n
t
o
im
p
le
m
e
n
t
th
e
D
B
a
re
p
ar
ti
al
ly
p
ro
vi
d
e
d
.
Th
e
S
Q
L
st
at
e
m
e
n
ts
f
o
r
ER
D
a
n
d
S
ta
r
Sc
h
e
m
a
ar
e
d
if
fi
cu
lt
t
o
f
o
llo
w
w
it
h
n
o
o
r
m
in
im
al

co
m
m
e
n
ts
.
M
o
st
o
f
th
e
t
a
b
le
s,
P
K
s,
F
K
s,
r
e
la
ti
o
n
sh
ip
,
co
n
n
e
ct
iv
it
ie
s
an
d
c
ar
d
in
al
it
ie
s
ar
e
m
is
si
n
g
o
r
in
co
rr
e
ct
ly
id
e
n
ti
fi
e
d
.
D
at
a
d
e
fi
n
it
io
n
a
n
d
d
at
a
in
se
rt
io
n
t
o
im
p
le
m
e
n
t
th
e
D
B
a
re
p
ar
ti
al
ly
p
ro
vi
d
e
d
o
r
m
is
si
n
g.
P
LO
2
:
P
ro
b
le
m

so
lv
in
g
P
LO
3
:
B
u
si
n
e
ss

co
m
m
u
n
ic
at
io
n
P
o
w
e
r
B
I
(V
is
u
al
is
a
ti
o
n
)
[1
5
%
]
A
v
e
ry
w
e
ll
th
o
u
gh
t
o
u
t
o
f
h
o
w
d
at
a
a
re
im
p
o
rt
e
d
a
n
d
u
se
d

in
P
o
w
e
rB
I.
Ex
ce
lle
n
t
w
it
h
t
h
e
u
se
o
f
ch
ar
ts
f
o
r
st
o
ry
t
e
lli
n
g
(i
.e
.,
e
xp
la
in

in
si
gh
ts
o
f
d
at
a
u
se
d
o
n
t
h
e
c
h
ar
ts
).
A
w
e
ll
th
o
u
gh
t
o
u
t
o
f
h
o
w
d
at
a
a
re
im
p
o
rt
e
d
a
n
d
u
se
d
in

P
o
w
e
rB
I.
V
e
ry
g
o
o
d
w
it
h
t
h
e
u
se
o
f
ch
ar
ts
f
o
r
st
o
ry
t
e
lli
n
g
(i
.e
.,

e
xp
la
in
in
si
gh
ts
o
f
d
at
a
u
se
d
o
n
t
h
e
c
h
ar
ts
).
So
m
e
t
h
o
u
gh
t
w
e
n
t
in
to
o
n
h
o
w
d
at
a
im
p
o
rt
e
d

an
d
u
se
d
in
P
o
w
e
rB
I.
G
o
o
d
w
it
h
t
h
e
u
se
o
f
ch
ar
ts
f
o
r
st
o
ry
t
e
lli
n
g
(i
.e
.,
e
xp
la
in
in
si
gh
ts
o
f
d
at
a
u
se
d
o
n
t
h
e
c
h
ar
ts
).
M
in
im
u
m
t
h
o
u
gh
t
w
e
n
t
in
to
o
n
h
o
w
d
at
a
a
re

im
p
o
rt
e
d
a
n
d
u
se
d
in
P
o
w
e
rB
I.
C
h
ar
ts
a
re
u
se
d
b
u
t
n
o
t
a
ss
o
ci
at
e
d
w
it
h
s
to
ry

te
lli
n
g
(i
.e
.,
e
xp
la
in
in
si
gh
ts
o
f
d
at
a
u
se
d
o
n
t
h
e

ch
ar
ts
).
N
o
t
m
u
ch
t
h
o
u
gh
t
w
e
n
t
in
to
o
n
h
o
w
d
at
a
a
re

im
p
o
rt
e
d
a
n
d
u
se
d
in
P
o
w
e
rB
I.
C
h
ar
ts
a
re
c
re
at
e
d
b
u
t
n
o
t
a
ss
o
ci
at
e
d
in
t
h
e

st
o
ry
t
e
lli
n
g
(i
.e
.,
e
xp
la
in
in
si
gh
ts
o
f
d
at
a
u
se
d

o
n
t
h
e
c
h
ar
ts
).
P
LO
2
:
P
ro
b
le
m

So
lv
in
g
P
LO
3
:
B
u
si
n
e
ss

co
m
m
u
n
ic
at
io
n
D
e
m
o
n
st
ra
te
t
h
e

fl
o
w
o
f
d
at
a
(
1
0
%
)
A
n
e
xc
e
lle
n
t
d
e
m
o
n
st
ra
ti
o
n
o
f
d
at
a
in
p
u
t
in
to
a
r
e
la
ti
o
n
al

d
at
a
b
as
e
, u
p
lo
ad
t
o
d
at
a
w
ar
e
h
o
u
se
a
n
d
d
o
w
n
lo
ad
t
o

P
o
w
e
rB
I.
Ex
ce
lle
n
t
e
xp
la
n
at
io
n
a
n
d
e
xp
e
ri
e
n
ce
a
re
g
iv
e
n
t
o
t
h
e
f
lo
w

o
f
d
at
a
f
ro
m
in
p
u
t
th
ro
u
gh
t
o
o
u
tp
u
t.
A
v
e
ry
g
o
o
d
d
e
m
o
n
st
ra
ti
o
n
o
f
d
at
a
in
p
u
t
in
to
a
r
e
la
ti
o
n
al

d
at
a
b
as
e
, u
p
lo
ad
t
o
d
at
a
w
ar
e
h
o
u
se
a
n
d
d
o
w
n
lo
ad
t
o

P
o
w
e
rB
I.
V
e
ry
g
o
o
d
e
xp
la
n
at
io
n
a
n
d
e
xp
e
ri
e
n
ce
a
re
g
iv
e
n
t
o
t
h
e
f
lo
w

o
f
d
at
a
f
ro
m
in
p
u
t
th
ro
u
gh
t
o
o
u
tp
u
t.
A
g
o
o
d
d
e
m
o
n
st
ra
ti
o
n
o
f
d
at
a
in
p
u
t
in
to
a

re
la
ti
o
n
al
d
at
a
b
as
e
, u
p
lo
ad
t
o
d
at
a
w
ar
e
h
o
u
se

an
d
d
o
w
n
lo
ad
t
o
P
o
w
e
rB
I.
G
o
o
d
e
xp
la
n
at
io
n
a
n
d
e
xp
e
ri
e
n
ce
a
re
g
iv
e
n
t
o

th
e
f
lo
w
o
f
d
at
a
f
ro
m
in
p
u
t
th
ro
u
gh
t
o
o
u
tp
u
t.
A
li
m
it
e
d
d
e
m
o
n
st
ra
ti
o
n
o
f
d
at
a
in
p
u
t
in
to
a

re
la
ti
o
n
al
d
at
a
b
as
e
, u
p
lo
ad
t
o
d
at
a
w
ar
e
h
o
u
se

an
d
d
o
w
n
lo
ad
t
o
P
o
w
e
rB
I.
Li
m
it
e
d
e
xp
la
n
at
io
n
a
n
d
e
xp
e
ri
e
n
ce
a
re
g
iv
e
n
t
o

th
e
f
lo
w
o
f
d
at
a
f
ro
m
in
p
u
t
th
ro
u
gh
t
o
o
u
tp
u
t.
V
e
ry
li
m
it
e
d
d
e
m
o
n
st
ra
ti
o
n
o
f
d
at
a
in
p
u
t
in
to
a

re
la
ti
o
n
al
d
at
a
b
as
e
, u
p
lo
ad
t
o
d
at
a
w
ar
e
h
o
u
se

an
d
d
o
w
n
lo
ad
t
o
P
o
w
e
rB
I.
V
e
ry
li
m
it
e
d
e
xp
la
n
at
io
n
a
n
d
e
xp
e
ri
e
n
ce
a
re

gi
ve
n
t
o
t
h
e
f
lo
w
o
f
d
at
a
f
ro
m
in
p
u
t
th
ro
u
gh
t
o

o
u
tp
u
t.
P
LO
3
:
B
u
si
n
e
ss

co
m
m
u
n
ic
at
io
n
P
LO
4
:
Te
am
w
o
rk
C
o
m
m
u
n
ic
at
io
n

(1
0
%
)
Sp
o
ke
n
la
n
gu
ag
e
is
c
le
ar
, c
o
n
ci
se
a
n
d
c
o
m
p
e
lli
n
g,
d
e
liv
e
re
d

in
a
n
e
n
ga
gi
n
g
st
yl
e
a
n
d
e
ff
e
ct
iv
e
ly
c
o
n
ve
yi
n
g
th
e
k
e
y
m
e
ss
a
ge
s.
Sp
o
ke
n
la
n
gu
ag
e
is
c
le
ar
a
n
d
c
o
n
ci
se
, a
n
d
u
se
s
ef
fe
ct
iv
e

to
n
e
, p
ac
in
g
an
d
e
m
p
h
as
is
t
o
c
la
ri
fy
t
h
e
k
e
y
m
e
ss
a
ge
s.
Sp
o
ke
n
la
n
gu
ag
e
is
c
le
ar
ly
p
ro
je
ct
e
d
a
n
d
e
as
ily

u
n
d
e
rs
to
o
d
b
y
lis
te
n
e
r
an
d
w
o
rd
c
h
o
ic
e
s
ar
e

ge
n
e
ra
lly
a
p
p
ro
p
ri
at
e
.
Sp
o
ke
n
la
n
gu
ag
e
is
g
e
n
e
ra
lly
c
le
ar
b
u
t
o
cc
as
io
n
al
ly
f
e
at
u
re
s
p
o
o
r/
u
n
cl
e
ar
w
o
rd

ch
o
ic
e
s,
la
ck
o
f
vo
ic
e
p
ro
je
ct
io
n
a
n
d
/o
r
va
ri
at
io
n
in
t
o
n
e
.
Sp
o
ke
n
la
n
gu
ag
e
is
u
n
cl
e
ar
a
n
d
s
ig
n
if
ic
an
tl
y
co
m
p
ro
m
is
e
s
th
e
e
ff
e
ct
iv
e
n
e
ss
o
f
co
m
m
u
n
ic
at
io
n
, m
ak
in
g
th
e
c
e
n
tr
al
m
e
ss
a
ge
s
d
if
fi
cu
lt
t
o
u
n
d
e
rs
ta
n
d
.
P
LO
3
:
B
u
si
n
e
ss

co
m
m
u
n
ic
at
io
n
P
LO
4
:
Te
am
w
o
rk
N
o
te
:
Fe
e
d
b
ac
k
fr
o
m
P
ar
t
A
w
ill
b
e
m
ar
ke
d
a
s
p
ar
t
o
f
th
e
ab
o
ve
m
ar
ki
n
g
cr
it
er
ia
.
24 | P a g e

11. Self and Peer Assessments
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 UNSW Review website. Most of the
times, the contributions are evenly distributed as shown below:



The self and peer review assessment will allow you to rate your group members’
contribution.
❑ Rate your group members and your own contribution to the group assignment on a
scale out of 5:
▪ 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 uploading of files will all be
date time stamp.
▪ Please note that simply doing the final proof-reading or making a cup of tea does
not count as equal contribution.
25 | P a g e

❑ Unequal contribution
▪ However, occasionally, you might have a “free rider” (i.e., student who does not
do any work but has his or her name on the front cover) or people who just 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. LiC will then examine the communication between the
members including posts, date time stamp of the posts, meeting minutes, files and
so on in Microsoft Teams.
▪ In the case that a dispute emerges, the group needs to discuss with the LiC at the
earliest possible time.
▪ Claims of unequal contributions, especially if contradicting the evaluation of
others, will need to be substantiated with evidence (e.g., upload of files and posts
in the private channel in Teams).
▪ The LiC will make a final judgement in the case that a dispute emerges.


26 | P a g e

12. General Rules

11.1 Proper Academic Conduct
All assignments must 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 may have negative
consequences for your studies at UNSW. The Academic Integrity at UNSW can
be found on Academic Integrity & Plagiarism | UNSW Current Students. For group
assignments: If your group suspects that a group member’s work contains
plagiarism then you should raise this with the group member concerned and
have the problem rectified. If the problem is not rectified, notify the LIC who
will call in a group meeting.
11.2 Assignment Submission
Assignments are to be submitted via Moodle on or before the day of the deadline.
Late submissions of assignments are to be avoided, disrupt the course timelines
and are a sign of poor time management. The late submission of assignments
carries a penalty of 5% of the awarded marks for that assignment per day of
lateness, including weekends and public holidays. Assignments submitted late or
did not follow the submission instructions will miss marked components that are in
their nature dependent on timely submission, especially peer review.
An extension of time to complete an assignment may be granted by submitting a
Special Consideration in the case of illness or misadventure. For group assignments:
groups are expected to plan ahead and to be able to balance out a missing
member without an extension.
Even if an extension is granted, parts of the marks that are dependent on a timely
submission and timely progression of the course (esp. marks for participation in the
peer review process) cannot be achieved at all. The general UNSW guidelines for
special considerations are available online.

11.3 Professional Group Work
The membership of groups is at your discretion. It is your responsibility to join
a group, otherwise we will assign you to a group. If you do not join a group,
you are still expected to complete the assignment in full and no allowance in
marking standards is made for the fact that the assignment becomes a solo effort
in this case.
Groups must plan, schedule, and conduct activities in due time. Groups must
meet on a regular basis (at least twice per week) while the assignment is being
undertaken and keep records (diaries, meeting minutes) of such meetings. The
groups must ensure that all members are involved in the completion of the
assignment. The work is to be divided equally among the group members.
27 | P a g e

All group members are expected to behave professionally and work diligently.
Group members should contribute in a useful and constructive way to the
teamwork. Deadlines should be kept, and work should be delivered at a
professional standard. If problems emerge in your group, then these problems
should in the first instance openly be discussed in the group (different members
might have different views) and resolutions should be agreed on. If internal
arrangements repeatedly fail to remedy the situation, then you should bring the
issues to the attention of the LIC.
The LIC may call a meeting of the group in which each group member will be
asked to describe in detail his or her input into the assignment and provide
supporting documentation of this effort (e.g., posts and upload of files in private
channel in Teams). If group members are found to be making inadequate effort
or delivering poor quality, then they will be counselled to improve their effort.
If sufficient improvement is not made despite group efforts and LIC
interventions, then the mark of under-performing group member(s) may be
moderated to reflect the relative lower input into the assignment. Note that
the inability to resolve internal group conflicts without involving the LIC does
not reflect well on the group’s project management and teamwork skills.

28 | P a g e

13. References

Tan F., Cahalane M., Tan B., and Englert J. (2017), “How GoGet CarShare's Product-Service
System is Facilitating Collaborative Consumption”, MIS Quarterly Executive, Vol. 16
No. 4 (Available at: https://aisel.aisnet.org/misqe/vol16/iss4/5)

欢迎咨询51作业君
51作业君

Email:51zuoyejun

@gmail.com

添加客服微信: Fudaojun0228