Domain model for team "Requirements"

Acronym

team-requirements-domain-model

Belongs to

Team Requirements

Responsible

jalue

History

(v1)   2021-01-08 - created initially

(v2)   2021-01-16 - need for decision

(v3)   2021-01-20 - complete Draft

(v4)   2021-01-28 - updated Domain Model

Why is there need for such a decision?

A domain model can help to focus on the things needed. By choosing the right boundaries the developers can design the software product as wished by the business. Core features are easier to identify and necessities required can be identified. This helps to develop a MVP. Focussing on the specific Domain of Requirements in this case should support the development process.

Additional sources for better understanding the background

• Wireframe
• Domain Driven Design

Viable Options

There is only one option to be considered.

Alternatives not seriously considered

Alternatives have not been considered

How is this decision evaluated?

To check the decision. The created Domain Model needs to be evaluated against the existing wireframe.

Resolution Details

Resolution Details can be found on the Wiki Page.

Reasons for the resolution

After evaluating what is needed to work within the domain, a domain model for the domain has been designed.