uml Create a UML class diagram that includes Game, Board, Position, Piece and Player. A Game should have a Board and Pla

[answerhappygod]

Uml Create A Uml Class Diagram That Includes Game Board Position Piece And Player A Game Should Have A Board And Pla 1 (50.47 KiB) Viewed 39 times

Uml Create A Uml Class Diagram That Includes Game Board Position Piece And Player A Game Should Have A Board And Pla 2 (50.47 KiB) Viewed 39 times

uml Create a UML class diagram that includes Game, Board, Position, Piece and Player. A Game should have a Board and Players. The Position class should be abstract, with PlayablePosition and Unplayable Position inheriting from it. Position should have a pure virtual method canPlay():boolean, with the return value being true for playable positions that are empty. Polymorphism must (and should) be used. There is some latitude on how one could approach the design, but one would want a play() method that loops and Board will want to store its pieces internally. Based on where the program stores information in the resulting design, a save method should exist, as should a static load method. A makeMove method and methods to determine whether a move converts any pieces will be needed. A method to check if there are any valid moves left will be needed. Think about the game problem and rules and include any additional methods, mindful of what should be public and private. Classes should showe Constructors to communicate, at a high level, how the life-cycle of the elements of the game (or their construction) will work. Use UML Notes! It is ok to indicate via UML Note that access/mutator methods are not shown/can be interpreted based on fields. Use UML. Notes to provide clarifications on salient decisions. Generally, if a note would be helpful for someone trying to implement based on this design, then it is probably a good note. A note should not describe implementation details. A note should explain how things in the diagram fit together clearly, filling in details that are not well-communicated through simple box-line diagrams. A UMI diagram may be split into simpler diagrams, identifying stub classes via UML note indicating a detailed version elsewhere. Splitting up a UML diagram can make a complex diagram easier to read. Suppose two classes have a relation in one diagram. In that case, they must have the same relation in another diagram, even if they are stubs.