[SOLVED] 代写 game scala GAP255 Midterm – Refactor Challenge

GAP255 Midterm – Refactor Challenge
Object-Oriented Programming
Description
Please work alone on this project and don’t share your work with classmates.

Download the project files for this assignment HERE.

Observe the project. It is a playable, but poorly written strategy game. The game specification is as follows:

•Each player has a base, represented by the % character.
•The base can produce units, represented by > or <. The point of the character is toward the base owned by the other player.•Each player starts with 5 resources.•Each player earns one resource per turn. The exception is the player who goes first; they do not receive a resource on their first turn.•At the beginning of each player’s turn, they may move each of their units one time in any direction. They may also choose not to move a unit.•If a unit collides with an enemy unit, that enemy unit takes damage. Units can take 2 hits before dying. If an enemy unit is killed, the friendly unit will move into its place on the board.•If a unit collides with the enemy base, the unit’s owner wins the game.•Units may move on empty spaces (‘.’) but cannot move on walls (‘#’).•At the end of each player’s turn, they may choose to produce a new unit. The left player’s new units appear to the right of their base; the right player’s new units appear to the left of their base. If that spot is occupied, no unit can be produced. Units cost 2 resources.Your primary task is to refactor the program to make use of object-oriented techniques. You can do this in any way you wish, but the priorities for your refactoring should be as follows:•Improve readability. Make it easier to understand the parts of the program by breaking them apart into functions, and grouping those functions into classes.•Maintain high cohesion. Group functions into classes with other related functions. Avoid grouping unrelated functions.
•Maintain loose coupling. Reduce the number of other classes that access each other whenever possible.
•Strive for scalability. Anticipate changes to the game design. Make it easy to add game content or features.DeadlinesPart OneRefactor the project in its current form. Due October 21st at 11:59 PM. Part TwoOn October 22nd you will be given a unique design change. You must implement that design change and submit it by October 28th at 11:59 PM. You may change your architecture as needed for this design change.