Ancestors

Written by Nick Tune on 2024-08-23 at 18:47

Our conceptual understanding of a business domain plays a fundamental role in how we architect our software systems.

For example, when we have specialised versions of a general concept - do we treat the variability as an attribute or specialized entities?

See the attached image: if we consider a dealership to be one single entity with different shapes of profile, we might lean more towards a profiles subdomain.

1/2

[#]softwareArchitecutre #ddDesign #domainDrivenDesign

=> View attached media

=> More informations about this toot | More toots from nick_tune@hachyderm.io

Toot

Written by Nick Tune on 2024-08-23 at 18:48

But if the profiles are significantly different in shape and behaviour, we might start using words like "international dealership" to communicate more effectively.

And this might lead us towards subdomains aligned to each type of dealership.

Modelling variability is often interesting and nuanced. Looking at the domain from multiple perspectives and working closely with domain experts is crucial.

But don't expect domain experts to give you the answer - you are a modeler as well.

2/2

=> More informations about this toot | More toots from nick_tune@hachyderm.io

Descendants