Domain model for team "Analysis"

Acronym

team-analysis-domain-model

Belongs to

Team Analysis

Responsible

mhallweg und FalahSama

History

(v1)   2021-01-08 - created initially

(v2)   2021-01-21 - resolution details added

(v3)   2021-01-22 - moved documentation to wiki

Why is there need for such a decision?

Firstly it’s important to create a matching domain model. Therefore this way we can consider the main objects of the domain and their relationships. With this method, the whole improved understanding for the domain will lead to a better implementation.

Additional sources for better understanding the background

• Ethiktool - Wireframe
• Domain-Driven Design Reference
• Domain Driven Design - Tackling Complexity in the Heart of Business Software
• An introduction to Domain-Driven Design
• Domain Modeling

Viable Options

Best practice at this point is the domain model…

Alternatives not seriously considered

… This is the reason why no other alternatives were considered.

How is this decision evaluated?

Based on the wireframe and the given Excel-file, a first version of the domain model will be created. This version will be improved with several attributes and relationships.

Resolution Details

Further documentation details on the specific wiki page.

Reasons for the resolution

The design-decision for the domain model is needed to work with the whole domain itself.