Chain Reaction Simple Game

Develop a game in Java that closely resembles this game: [login to view URL] Try to copy the game’s look and behaviour closely e.g. balls moving with different speed, semi-transparent explosions, chain-based score multiplier etc. You should have a secret menu that lets the user select one of the 12 levels without having to play through the previous levels. This is necessary for testing and demonstration purposes. The following list shows how many balls the user must explode in order to proceed to the next level and how many balls will appear on the screen in total: Level 1: 1 of 5 Level 2: 2 of 10 Level 3: 4 of 15 Level 4: 6 of 20 Level 5: 10 of 25 Level 6: 15 of 30 Level 7: 18 of 35 Level 8: 22 of 40 Level 9: 30 of 45 Level 10: 37 of 50 Level 11: 48 of 55 Level 12: 54 of 60 Note how scoring works in this game. How many point an explosion is worth depends on the length of the chain. So for example if the user clicks and the initial explosion causes balls 1, 2 and 3 to explode, each explosion will be worth only 100 points and the user will get 300 point in total. However if the initial explosion causes ball 1 to explode, ball 1 explosion causes ball 2 to explode and ball 2 explosion causes ball 3 to explode, the user will get 100, 800, 2700 points respectively. That’s 3600 points in total, 12 times more than in the first scenario! You can find the formula used to calculate a score for each subsequent link by playing the game, writing down a big enough sample and asking WolframAlpha to analyze the sequence. The design of “welcome”, “level failed”, “level completed”, “next level” and “game over” screens is entirely up to you, as long as they effectively perform their function. Sound effects are very welcome but are not necessary. Additional features such as highscores list, particle effects etc. are also welcome. Your project must be accompanied by JUnit tests. Submission Details: You are required to both electronically submit and to hand in a hard-copy of your assignment on the due date. The details of each are below. Hand in to the lecturer on or before the due date the following:  a hard copy listing of your source code, well structured and commented,  a hard copy of your design document that documents each class with a textual description of each class including an explanation of all variables and methods used.