Project 2 Introduction Information
SWEN20003 Object-Oriented Software Project 2
Semester 1, 2025
Donkey Kong Project
Release Date: Tuesday, April 15, 2025
Project 2A
Submission Deadline:
Tuesday, 06 May 2025 at 4:00pm AEST
Project 2B
Submission Deadline:
Friday, 23 May 2025 at 4:00pm AEST
Assignment Weight:

20% of Total Subject Score
Project 2A 10%
Project 2B 10%

Introduction
In this project, you will be continuing your work in Project 1 to create a 2D arcade platform
game titled Donkey Kong, using the Java programming language and the Bagel game
engine. The game features Mario as the player’s character, navigating platforms and
ladders, dodging barrels, monkeys and ultimately attempting to reach and defeat Donkey
Kong at the top of the level.
This is an individual project. You are permitted to discuss ideas with others, but the
implementation must be entirely your own. There are two parts to this project, with different
submission dates.
Note about Assumptions
Upon reading the specification, if there are any minor implementation details which are not
explicitly explained, you may make reasonable assumptions/decisions in your
implementation.
In this case you must make sure to document these assumptions/decisions in the code files
as necessary and include a README file which explains these design
assumptions/decisions. This is necessary so teaching staff know what you have done.
In other words, as long as your implementation correctly adheres to the requirements set out
in this document, you can make reasonable decisions/assumptions about what do in other
2025/4/29 21:51 Project 2 Introduction Information: Object Oriented Software Development (SWEN20003_2025_SM1)
https://canvas.lms.unimelb.edu.au/courses/211054/pages/project-2-introduction-information?module_item_id=6602035 1/3
situations not exactly described.
e.g. this may cover edge-cases or specific situations which are not explained in the
specification. As long as your assumption/decisions and implementation does not
contradict the requirements set out in this document, it is allowed.
This specification doesn’t explain every possible situation as it would make the
specification far too long to comprehend otherwise.
Academic Integrity
Work submitted by students for assessment must be their independent work. The University
Policy and Procedures for Academic Misconduct can be found at:
https://academichonesty.unimelb.edu.au/#policy.
(https://academichonesty.unimelb.edu.au/#policy.)
The University of Melbourne’s Student Academic Integrity Policy makes clear that all work
submitted by an individual must be their own.
In this project students are only permitted to use AI tools for the purposes of ideation,
reviewing their code files, or searching for information.
Students are not permitted to use AI tools to write any part of the submitted code files.
More information can be found at: Academic Integrity – Use of Artificial Intelligence
Technologies (https://academicintegrity.unimelb.edu.au/artificial-intelligence-tools-and-
technologies)
Extensions and Special Consideration
The Faculty of Engineering and Information Technology has a new process in place for
handling Extensions and Special Considerations. Carefully review the instructions.
This information is published in CANVAS here
(https://canvas.lms.unimelb.edu.au/courses/211054/pages/feit-extensions-and-special-
consideration) .
Do not send emails to the Subject Coordinator without reviewing this process first.
Project 2A: UML Design
Project 2A requires you to produce a class design demonstrating how you plan to implement
the full game. This must be submitted in the form of a UML class diagram showing all the
classes you plan to implement, relationships (e.g. inheritance and associations) between
them, any enumerated values, and their attributes/methods (both public and private).
The class diagram must follow correct UML notation as shown in the lectures.
You do not need to include constructors, getters/setters methods, dependency, composition
2025/4/29 21:51 Project 2 Introduction Information: Object Oriented Software Development (SWEN20003_2025_SM1)
https://canvas.lms.unimelb.edu.au/courses/211054/pages/project-2-introduction-information?module_item_id=6602035 2/3
or aggregation relationships. Bagel classes can be shown similar to primitive data types.
If you so choose, you may show the relationships between classes on a separate page to
the details (attributes and methods) of the classes in the interest of neatness.
You must submit this as a PDF file only via Canvas.
Project 2B: Implementation
Project 2B requires you to complete the implementation of the game as described in the rest
of this specification. You do not need to strictly follow your class design from Project 2A, as
you will likely find ways to improve the design as you implement it.
You will also need to implement any feedback given from your tutor after you receive your
2A feedback.
Additional information about Project 2B requirements including skeleton code,
resources, and data files will be provided at the end of Week 8. Focus on working on
Project 2A until this time.

2025/4/29 21:51 Project 2 Introduction Information: Object Oriented Software Development (SWEN20003_2025_SM1)
https://canvas.lms.unimelb.edu.au/courses/211054/pages/project-2-introduction-information?module_item_id=6602035 3/3

学霸联盟