UML Issues about kings-n-things-server HOT 8 CLOSED

Why do Rack and Game Piece have owner attributes when they're both pointing to player anyways?
A: by owner it means player, I know thats not correct UML style

Why does Hex Tile have a type attribute, point a Hex Tile type class AND point to a terrain class?
A: Ya we added Terrain in at the end and never removed hex tile type, Hex Tile Type is no longer needed

I think Board Location is a confusing term, maybe Board Container?
A: Sure

Why so many classes with only one attribute? Example Creature points to a terrain class but the terrain class only has a name attribute, wouldn't we just want to give Creature an attribute called Terrain?
A: Terrain is shared by 3 different classes. It makes more sense to encapsulate the terrain in its own class since there will most likely be logic surrounding different terrains which can be shared among the classes.

from kings-n-things-server.

Updated UML any other changes necessary ?

-adding java code for this in my branch

from kings-n-things-server.

Game piece has an id and all the subclasses do as well, the id would just be inherited, no need for each to have one set explicitly.

from kings-n-things-server.

What's a counter?

from kings-n-things-server.

new dia uml version Jpeg here

dia file will be included in the repo

from kings-n-things-server.

Did you mean to have game piece point to player or should it be the other way around?

On Sun, Jan 19, 2014 at 12:55 AM, GTLives [email protected]
wrote:

new dia uml version Jpeg here

dia file will be included in the repo

Reply to this email directly or view it on GitHub:
#7 (comment)

from kings-n-things-server.

We only showed 1 to 1 relationships for now , we didn't include sets. Player does have many pieces but all we showed was that player has piece

from kings-n-things-server.

John, can you post the updated diagram?

from kings-n-things-server.