Domain model for team "Impact"
- Acronym
- team-impact-domain-model
- Belongs to
- Team Impact
- Responsible
- hbuhl und tzaika
- History
- (v1) 2021-01-08 - created initially
- (v2) 2021-01-27 - moved a documentation to wiki
- (v3) 2021-01-28 - removed reasons for the resolution
- (v4) 2021-02-09 - updated the status
Why is there need for such a decision?
Before implementation start, some basic research on the domain should be done. We should identify main objects of the domain. In addition, the relationships between these objects are also very important.
Additional sources for better understanding the background
Domain model a system of abstractions that describes selected aspects of a domain and can be used to solve problems related to that domain. [Ev15]
Draw from the model the terminology used in the design and the basic assignment of responsibilities. The code becomes an expression of the model, so a change to the code may be a change to the model. Its effect must ripple through the rest of the project’s activities accordingly. [Ev15]
Links
Viable Options
- conceptual data model (germ.: Fachliches Datenmodell)
- logical data model (germ.: Logisches Datenmodell)
Resolution Details
For this decision, the domain model was created in two steps:
-
First, with the help of the existing wireframes and the Excel file, the main objects of the domain and their relationships were identified. These were the basics for creating a conceptual data model.
-
Then more details like attributes and association directions were added. In addition, it was determined which objects represent an entity. These were the basics for creating a logical data model