Pls follow the software used strictly The following requirements are already mentioned in the document attached, but these specific ones require greater attention, I have added my opinions as comments :
A1. Refactor the code by adding some design patterns to enhance maintainability comment : explain how he has implemented it
A2. Organise the code to adhere to the MVC design pattern comment : explain how he has implemented it
A3. Translate code from Swing to Java comment: All the classes that are currently using java swing need to be converted into java fx , this is very important
A4. Create a permanent high score list (using a file to store scores and player names) comment : implemet this and create a button to see the list
A5. Add interesting levels to the game (based either on your own ideas or on the original game) comment : add difficulites to the game, like add a level selector at the start of the game where with each level the ball speed increase or the paddle size decreses.
A6. Add game object pictures (sprites) to the game, for representing ball/paddle/bricks comment ; this was not implemeted in the previous solution
A7. Use build files (Maven or Gradle) comment - only use maven , cause gradle cause too many issues
A8. Come up with your own groundbreaking idea ... surprise us :) comment - add stuff to the game , like background option or a ball colour , background music or anything else that is better idea than this that the expert can implement
Recommendations: We recommend dedicating approximately 40-60 total hours on the coursework. We expect 30-40 hours of work for those who are aiming for a pass (40+) and 60 or more hours of work for those that are aiming for a first (70+). Please keep in mind that the skill level varies quite a bit in a class with over 300 students, and that the exact number of hours depends on your individualskill level.In order to help you, we have less required lectures in the last two weeks of term and some of the lab sessions are dedicated to your coursework.
Deadline: The deadline will be most likely the second week in December. The exact deadline will be posted on Moodle
Assessment: The marks will be split as follows:
- 15% for git use (e.g. push, branch, merge, providing .gitignore)
- 30% for refactoring
- 30% for additions
- 15% for documentation (Readme file + source code documentation)
- 10% for the demonstration video, explaining your refactoring activities and additions
Questions: Questions can be asked either on Teams or in person during the lab. We will try to answer them as quickly as possible.Please read the questions that have been already asked before you post yours, to avoid duplication.
Summary: This coursework is about maintaining and extending a re-implementation of a classic retro game called Breakout. The new implementation has never been completed, but at least it runs, once it is set up properly. More information about the original Breakout game and its history is available on Wikipedia
In addition, you will find many opportunities on the internet to play the original game online.
1. Set up a PRIVATEgit repository on the school's GitLab server and use it actively for version control activities.
2. Do some basic maintenance of the delivered code base (this should include things like providing a meaningful Readme. md file and Javadocs, organising files in a meaningful way into packages, breaking up large classes in a meaningful way to support the idea of single responsibility, improving encapsulation, etc.)
3. Extend the delivered code base by adding:
a. A module-info.java fileÂ
b. A START screen (using JavaFX) with a colour theme choice for the Game screen and a button that allows going to the GAME screen.Â
c. A SCORE pop-up, appearing at the end of each round, showing the scores from each round