Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    So, in an ideal world, there would be a 1-to-1 relationship between subdomains and bounded contexts? (Understanding, obviously, that what is ideal and what is true differ). Commented May 5, 2014 at 20:59
  • 2
    Not necessarily: the key thing is that a BC overlapping many subdomains is a bad smell. Well... it's not bounded. In DDD terms a model should be perfectly fit to its purpose, and different subdomains have different purposes (and probably even different bosses with different goals). But within the same subdomain, different BC may exists for different reasons. Web and mobile app might be the case, or different models for planning or execution. Commented May 5, 2014 at 21:53
  • But the key thing is to understand that there are two problem families: 1) reading the existing context (where you can only accept and categorise the existing models and collaborations), 2) designing the right software given the existing constraints, thus imposing context boundaries between small, purpose oriented models. In the second scenario you won't intentionally overlap subdomain borders. ...in general, looking for perfect software in an non-perfect organisation might be hard stuff. But solving those inconsistencies might be worth the effort. Commented May 5, 2014 at 22:03