Now that I am doing concrete implementations of our data model I find it hard to get an overview of the single parts of the datamodel.
The complete data model is a bit overwhelming I think. The forum threads are also difficult to evaluate because of their length and their different opinions (that's the nature of a discussion). Another goal would be to optimize the visibility of the "UML connections" - they are really hidden and we cannot see the history of the connections.
These are the reasons for this proposal.
I suggest that we create final documentations for (every) single aspect of the data model. These documentations should contain all details, explanations and examples for one part of the data model. We could create them in our wiki and could enclose a (mini) UML diagramm with PlantUML (see this example). A single documentation can contain a single class with all attributes, or multiple classes (with a few or even none) to explain their relationship (connections).
These examples come into my mind:
What do you thing about it? And where con you help?
Edit: I created a first documentation page for "Game"
The complete data model is a bit overwhelming I think. The forum threads are also difficult to evaluate because of their length and their different opinions (that's the nature of a discussion). Another goal would be to optimize the visibility of the "UML connections" - they are really hidden and we cannot see the history of the connections.
These are the reasons for this proposal.
I suggest that we create final documentations for (every) single aspect of the data model. These documentations should contain all details, explanations and examples for one part of the data model. We could create them in our wiki and could enclose a (mini) UML diagramm with PlantUML (see this example). A single documentation can contain a single class with all attributes, or multiple classes (with a few or even none) to explain their relationship (connections).
These examples come into my mind:
- single documentations for Game, ReleaseGroup, Release, GameTitle, CreditSet, Company, Person, Region and so on
- relationship between Game and GameTitle
- relationship between ReleaseGroup and Release
- relationship between ReleaseGroup, Release
- relationship between Hardware- and Software-(Sub)Platforms
- relationship between Release and Region
- relationships between Person and PersonalEvent
- relationships between Company and CompanyEvent
What do you thing about it? And where con you help?
Edit: I created a first documentation page for "Game"