School of Computing
Semester 1, 2024
COMP3760/6760: Enterprise Systems Integration
Assignment 3 (Group Assignment): System Integration
(20% of the semester)
Dr Yang Zhang
Due 11:55 pm Friday – 18th October 2024
COMP3760/6760 Assignment 3 Semester 1, 2024
Process and Service Support for E-Business Systems
(Source: Agoda website www.agoda.com/en-au).
Background: Agoda online platform
About Agoda
See The World For Less
Agoda is an online travel platform that brings high-value and rewarding travel experiences to people all
over the world through the Agoda app and Agoda website. Our mission is to empower everyone to be a
traveler by offering affordable deals on hotels, flights, activities, and more, with an Agoda booking
experience that is hassle-free from start to finish.
Since the Agoda company was founded in 2005, we’ve made searching and booking travel as easy and
stress-free as it should be. Agoda is now considered one of Asia’s leading travel-tech companies with
millions of registered customers supported by a truly diverse team of more than 6,600 people in 31
markets and Agoda customer service available 24/7.
Visitor Numbers
In accordance with Agoda.com’s obligations under the EU’s Digital Services Act (DSA), we estimate that
the average monthly recipients* of the Agoda.com service in the European Union from 1 February 2023
up to and including 31 July2023, is well below 45 million.
This is only an estimate and is based on the data available to Agoda.com at this time, and the limited
guidance in the DSA. This estimate is required to be published under the DSA and should not be used for
any other purpose. The methodologies used to estimate average monthly recipients as defined in the DSA
require significant judgement and design inputs, are subject to data quality, other factors and limitations,
and inherently are subject to statistical variances and uncertainties. These estimates may be revised
upwards or downwards as Agoda.com refines its approach and in response to the publication of
methodology by the European Commission.
Please refer to the website for metrics we consider relevant to Agoda.com’s business.
* ‘recipient of service’ is defined under the DSA to mean “any natural or legal person who uses an
intermediary service, in particular for the purposes of seeking information and making it accessible”. This
requires counting users to whom information was displayed by the Agoda.com service, even if that user
did not make a transaction.
Agoda Platform-to-Business (P2B) Complaint Handling Annual Report (EEA)
For the period: 1 January 2022 to 31 December 2022. Complaints received in the EEA: 1,514 from
209,944 partners. Complaints received were related to the following areas:
• 45% booking rate/price related.
• 42% payment related.
• 11% system issues/bug related.
• 2% property status/content related.
We resolved 100% of the complaints in 2022, of which:
• 68% of the cases were resolved within 3 days.
• 20% of the cases were resolved within 4-7 days.
• 12% of the cases required 7 days or more for resolution.
From January 2022 to date, no mediation cases have been filed by any partner in the EEA.
From an enterprise system integration perspective, please outline a collaborative business process
for Agoda's e-business operations (such as booking hotels or airline tickets) and fulfill the following
requirements:
Project Brief (4 marks)
Provide a description on:
• the group meeting schedule or plan, each member’s role in the project,
• identify risks and ways to manage risks,
• identify ways to communicate between members,
➢ log recording for each meeting, including discussion and any dialogue between members in
relation to the project.
Note: all group members need to contribute to the project. The description and log need to be submitted together
with the four tasks.
Task 1 Collaborative Business Process and EAI (4 marks)
The objective of this task is:
• To use BPMN notation (Week 2 lecture) to draw a collaborative business process for the Agoda
(booking a hotel or booking an air ticket) in which you need to show partners (such as the company, the
seller and the users, etc.), how they interact, and how information/messages are exchanged. In this case,
the partner systems can be custom management system, booking system, payment system, shipping
system, information system, etc. (The process should be straightforward and not as complex as the one
in Assignment 2.)
• There are different ways to design and implement this collaborative business process. Design and draw
an EAI system that support the User makes the inquiry to different systems and make a decision in
booking hotels or air tickets.
• Explain how User’s inquire is processed in your EAI system. You must state any assumptions your group
deems necessary.
Task 2 Web Service Design (4 marks)
Suppose you are creating the components of online booking as web services, which allows users and sellers to
create applications. You are required to:
1. Identify the two (2) necessary functions of these services. You can make (and state) your assumptions
based on your experience in using online booking system;
2. For each of the above functions (from point 1), identify the input/output messages;
3. Use WSDL interface definition constructs to specify the above identified functions with input/output
messages.
Task 3 XML Schema Design (4 marks)
For the above input/output messages, write their XML Schemas. You need to include the following:
• Two different ways of specifying complex types, one is defined inside the element, the other defines a
complex type first, then (re-)uses it as a complex type of an element;
• Use constraints on the values of a simple typed element, on the occurrence of elements;
• Pick up one xml schema, construct a sample xml document.
• Validate your code with the schema and show the steps with screen shots using the online validator of week
8 practical (see xml validator https://www.corefiling.com/opensource/schemaValidate.htm).
Task 4 Discussion (4 marks, @ 600 words)
“The current system is basically a portal for a collection of documents without proper integration”, from
this description we can image the documents stored there are of different formats with different structures. The
challenges are how to bring all the information together in a uniformed interface for search and query. Use what
you have learned in the unit to discuss the following:
• The possible issues relating to the integration of all the components in this E-Business
System (from different layers/aspects) using examples;
• The possible technologies potentially used to support system integration at various levels/aspects;
• The options and considerations of the technologies along with their advantages and disadvantages
Submission: one submission per group, together with the project description and log.
Zero Tolerance for plagiarism:
You are required to use your own words to provide the descriptions and explanations. All submissions will be
checked for plagiarism. No Chatgpt. No Generative AI. Any cases will be reported to the faculty for
disciplinary action, and the marks of the assignment and the unit will be withheld until the case has been
resolved. See Macquarie University’s code of conduct for the details of the process:
https://students.mq.edu.au/study/getting-started/student-conduct.
Submission
Place your soft copy in your assignment 3 submission folder on iLearn. Please submit a single PDF file containing
your source code. There is no word limit. The document should begin with a table of contents that outlines your
work, and make sure to include the names and student IDs of all group members.
Due 11:55 pm Friday – 18th October 2024 (Hard deadline)
Marking Rubric
Developing
(Borderline Pass-Fail)
Functional
(Pass)
Proficient
(Credit)
Advanced
(Distinction-High
Distinction)
System
Integration
Showing some
understanding of
system integration
Showing
understanding of
system integration, can
apply technologies in
the business case
Good understanding of
system integration
issues, can explain and
use the technologies
proficiently and
appropriately without
any significant
mistakes
Excellent
understanding of
system integration and
can explain and use
the technologies at an
expert level
XML, web
service
Limited
understanding of
XML, web services,
some obvious
mistakes
Competent
understanding of XML
and web services,
some trivial mistakes
still in evidence, but
generally an
understanding of what
is taking place
and why
Some incorporation of
the literature beyond
just competent
understanding of
XML and web
services
An excellent grasp of
XML and web services,
also drawing on the
literature widely to
exemplify in the case of
further examples how
XML and web services
has aided system
integration as well