-There will be three java files: Room class, Dungeon class, Main method(tester file)

-Please make sure it compiles

Room Room description: String north: Room east: Room west: Room south: Room < > Room (description: String) + setNorth (north: Room) + setEast (east:Room) + setWest (west:Room) + setSouth(south:Room) + setExits(n: Room, e:Room, w: Room, s:Room) + getNorth(): Room getEast(): Room getwest(): Room + getSouth(): Room + getDescription(): String +getExits(): String toString(): String UML class diagram for Room Dungeon Dungeon balcony: Room bedroom1: Room bedroom2: Room dining: Room kitchen: Room northHall: Room southHall: Room < > Dungeon() +getRoom@(): Room Room Class Rooms are responsible for representing an area in the dungeon. The properties that define a room are its description and its exits. The room description may be stored using a String. For the exits, this room can hold references to other rooms that connect to it. The room constructor only sets up its description leaving its exits initially null. Client code can then update the room's properties with getter and setter methods. It would be convenient to also have a method that can set all 4 exits at once. The room's description shouldn't say its exits; instead have a method (getExits) that creates a String of exits. The toString method should contain the description and the exits. Dungeon Class The dungeon is responsible for setting up all the rooms and establishing the connections between them. The dungeon's properties (i.e. instance variables) are the rooms that it contains. The dungeon constructor should initialize all of the rooms' descriptions and its exits. The only method that our dungeon needs is to provide the starting room. Once we have the starting room we can navigate to any other room from using the rooms themselves.