University of Wollongong

School of Computing and Information Technology

CSCI927/427 Service-Oriented Software Engineering
Spring 2022

Group Project (40 marks)

TASKS
Your tasks are to:
1. Form and structure your group, allocating roles and responsibilities to your members. This
must be finalized by the end of Week 2.
2. Organize weekly group meetings. Each group must have at least one meeting per week.
3. Complete the design and development of the project described below using service-
oriented software engineering.
4. Make sure your group makes progress on the project every week. Note that this is the
scope of a 10-week project. If your group doesn’t make progress every week and delays
project work to the last weeks or days, there is a very high risk of project failures.
5. Attend your group meetings, respond promptly to your team communication, actively
participate in discussions, and contribute significantly to your group’s work. Each team
member’s contribution will be recorded and rated in the group’s member contribution
report. If you have little contribution to your group project, your individual mark will be
significantly lower than your group’s mark (or even 0 mark if you have almost no
contribution).
6. Produce a report detailing the group's work.

SUBMISSION
1. Verbal Progress Report: in Week 4 Tutorial
2. Verbal Progress Report: in Week 8 Lecture + Tutorial
3. Final deliverables (softcopy to Moodle) (36 marks): 11:00am Tuesday 18th October 2022
• Final report
• Executable system + source code
4. Project presentation and demonstration (4 marks): Week 12 Lecture + Tutorial
5. True weekly meeting reports from Week 3 to Week 12 (submit to Moodle every week
from Week 3, at least one meeting report per week). Weekly meeting reports should
cover at least the following:
 • Member contribution report up to that week (see details below for what should be
included in the member contribution)
• True (the meeting must occur) group meeting records: agendas and meeting
minutes which include at least the following: meeting date, attendance, progress
reports of each week, review and tracking, discussion summaries, and action
plans/items.

GUIDELINES

1. Verbal progress report – (5 minutes per group for Week 4 and 10 minutes for Week 8)
• One member from each group presents the progress of their group by sharing their
screen and slides.
• Week 4 report should cover at least the following:
i. Introducing their group members and roles
ii. Preliminary findings of all the tasks.
iii. Work plans in the form of a Work Breakdown Structure (e.g. tasks, sub-
tasks, who perform what, outcomes, etc.)
iv. Meeting plans, e.g. how many meetings per week, date/time and location of
meetings.
• Week 8 report should cover at least the following:
i. Reporting work completed and work in progress
ii. Presenting plans for the remaining of the project.
iii. Member contribution up to Week 8.

2. The final report should cover at least the following:

A. Service identification and specification
i. Identify at least 5 service providers. For each service provider, identify at least
3 services.
ii. Specify those services using the Business Service Representation Language.
B. Enterprise Architecture (EA) Design using TOGAF/ArchiMate
i. Your EA design needs to cover at least 3 phases in TOGAF: Business
Architecture, Information Systems Architecture and Technology Architecture,
and the three layers in ArchiMate: Business Layer, Application Layer, and
Technology Layer.
C. Business Process Design and Analysis
i. Develop at least 5 realistic process models in BPMN for the services provided
through this platform. You need to demonstrate the use of a wide range of
BPMN elements discussed in the subject. You need to provide the sources from
 which you developed the process model – these might involve documents you
found on the web, procedure manuals and so on. There must be clear evidence
that your BPMN process model encodes process descriptions contained in these
textual resources.
ii. Use the semantic effect annotation technique for business process models
based on the ProcessSEER technology discussed in the subject to annotate
this model. Effect annotations must be written in both English and first-order
logic. You need to provide both the immediate effects of tasks/activities
and the cumulative effect scenarios obtained at various points in the process.
You need to present the annotations both as text annotations on your BPMN
models and on separate pages of text to process model (in the latter case,
use a numbering or indexing scheme to correlate annotations to various points
in the process model).
D. Service Design and Analysis using SoaML
i. Your design should cover at least service architectures, service interfaces,
service contracts (including their behaviour), and service compositions.
E. Microservices design and implementation
i. Select at least 3 services from your platform, and design and implement them
using the microservices approach.
ii. Clearly demonstrate your design and implementation in the report.
F. Service/process analytics
i. Select at least 3 business processes (in Part C) from your platform and execute
them to generate event logs. For process execution, you can write your own
simulation or use an existing process execution engine.
ii. Use appropriate process mining tools to perform process mining and analytics
on these event logs.
iii. Clearly demonstrate how all of the above tasks were performed in details and
their outcomes.

G. Member contribution for the whole project (with each member’s signature)

Member contribution report (each deliverable, including the weekly meeting report, must be
accompanied with a member contribution report):
• On the cover page of your group’s report, you need to provide rating for the contribution of
each team member and a detailed explanation of what the team member did for the project
to justify the rating.
• Everyone in the team should write a statement “I agree with my group member contribution
report and ratings” and insert their signature next to the statement. Do NOT insert the
signature of your group member without their consent/agreement.
• The individual contribution of each team member is assessed by all the other members.
• The rating scale can be a specific percentage number (e.g. 40%, 60%, 80%, etc.).
 Alternatively, it can be rated into one of the three scales: “contributed”, “very little”, and
“almost no contribution”. For a team member who has “contributed”, he/she will receive 100%
of the group mark; for a team member who contributed “very little”, he/she will receive 50% of
the team mark; for students who made “almost no contribution”, he/she will receive 0 marks for
the entire group project. Your tutor/lecturer may make adjustment to this marking criterion
based on practical situations. The maximum mark that a group member can get is their group’s
mark.

PLEASE READ THIS CAREFULLY: All work should be completed independently by your group.
Plagiarism may result in a FAIL grade and are subject to the University Academic Misconduct
Procedures. If any part (including sentences, figures/diagrams, tables, definitions, descriptions, and so
on) in your work are copied from other people's work (including both published and unpublished papers,
reports, Web articles, etc.), or if any idea is from other people, such work or people must be
acknowledged explicitly. You should avoid “copy and paste” sentences from other people’s work to
your work. In a rare case, where you must do so, you should use quotation marks to quote the copied
sentences and make a citation next to the quoted text.
 Project - Description
Important Notes:
• This Project Description provides only the high-level goals of this project. Based on these,
the team must elicit more detailed and specific requirements. Time will be allocated in the
lectures and tutorials for answering questions regarding the project.
• You need to form a group of 6 people ASAP by the end of Week 2 and register your group
via a link on Moodle, and start working on the project.

Pandemica (a hypothetical name) is a single platform, which provides services specifically during
pandemic such as contact tracing, vaccine rollout, vaccine certification, QR code check-in,
quarantines, PCR testing, registering for a positive rapid antigen test result, financial assistances
and so on. Your team is asked to design this platform and implement a small part of it using a
service-oriented software engineering approach.

This platform will offer services on behalf of different service providers. Each service provider
may offer a different collection of services at various levels of maturity and capability. Users can
interact with the platform through different touchpoints such as face to face, phone, mobile app,
web app, etc. However, the services should be delivered in a coherent manner, providing users
with a consistent experience.
 CSCI927/427 Service-Oriented Software Architecture
Final Project Deliverable and Product Demonstration (Worth 40%)
Group:
Out
Component Marks Comments
of
Project Presentation and Demonstration 4

Final Deliverables

Overall quality of the final deliverables (e.g. 4

presentation, consistencies, sophistication of
solutions, etc.)

Service identification and specification 5

Enterprise architecture design

Business process design and analysis 5

Service design and analysis 5

Microservices design and implementation 5

Service analytics
5

Overall project management (e.g. observed

2
progress, meeting records, etc.)

Total 40