Databases
StackOverflow2013
Postsdbo
POObject Oriented Design for a Chess game
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POObject Oriented Design for a Chess game
    primarykey
    data
    text
    <p>I am trying to get a feel of how to design and think in an Object Oriented manner and want to get some feedback from the community on this topic. The following is an example of a chess game that I wish to design in an OO manner. This is a very broad design and my focus at this stage is just to identify who is responsible for what messages and how the objects interact each other to simulate the game. Please point out if there are elements of bad design (high coupling, bad cohesion etc.) and how to improve on them. </p> <p>The Chess game has the following classes</p> <ul> <li>Board</li> <li>Player</li> <li>Piece</li> <li>Square</li> <li>ChessGame</li> </ul> <p>The Board is made up of squares and so Board can be made responsible for creating and managing Square objects. Each piece also is on a square so each piece also has a reference to the square it is on. (Does this make sense?). Each piece then is responsible to move itself from one square to another. Player class holds references to all pieces he owns and is also responsible for their creation (Should player create Pieces?) . Player has a method takeTurn which in turn calls a method movePiece which belongs to the piece Class which changes the location of the piece from its current location to another location. Now I am confused on what exactly the Board class must be responsible for. I assumed it was needed to determine the current state of the game and know when the game is over. But when a piece changes it's location how should the board get updated? should it maintain a seperate array of squares on which pieces exist and that gets updates as pieces move? </p> <p>Also, ChessGame intially creates the Board and player objects who in turn create squares and pieces respectively and start the simulation. Briefly, this might be what the code in ChessGame may look like</p> <pre><code>Player p1 =new Player(); Player p2 = new Player(); Board b = new Board(); while(b.isGameOver()) { p1.takeTurn(); // calls movePiece on the Piece object p2.takeTurn(); } </code></pre> <p>I am unclear on how the state of the board will get updated. Should piece have a reference to board? Where should be the responsibility lie? Who holds what references? Please help me with your inputs and point out problems in this design. I am deliberately not focusing on any algorithms or further details of game play as I am only interested in the design aspect. I hope this community can provide valuable insights. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USSid
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POObject Oriented Design for a Chess game
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POObject Oriented Design for a Chess game
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POObject Oriented Design for a Chess game
      1. USprolink007
      1. VTFavorite
    1. CONitpicky comment: p2 shouldn't call `takeTurn()` if p1's move ends the game. Less nitpicky comment: I find it more natural to call the players `white` and `black`.
      singulars
      1. POObject Oriented Design for a Chess game
      1. USKristopher Johnson
    2. COAgreed. But like I said, I am more interested in the design aspects and what Objects should be responsible for what actions and who holds what references.
      singulars
      1. POObject Oriented Design for a Chess game
      1. USSid
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload