Confused about IDDD's bounded context explanation

In Vaughn Vernon's excellent red book I read that the subdomains live in the problem space while the BC lives in the solution space. I copy that.

I also read that, in an ideal greenfield project, each subdomain in the problem space should be modeled as a BC in the solution space. I'm still following.

I also read that, existing systems you integrate with form a BC on their own. OK, makes sense.

I also read that the organisational structure of your company influences the bounded contexts you define. Different teams should work on different bounded context. I understand.

But then I read that a bounded context is mainly a linguistic boundary. I'm confused...

If bounded contexts are in the solution space, how can it be a linguistic boundary? I understand that your domain can be divided into subdomains based on existing linguistics boundaries. However, bounded contexts seem to be something you define. It's your strategic choice how you divide your code into seperate bounded context.

You might allign it with the subdomains you found in the problem space and in that case, indeed, your BC's match the linguistic boundaries. But you might also allign it according to some o
ther criteria and in that case it's not a linguistic boundary at all.

So if they say "a bounded context is a linguistic boundary", they really mean "a subdomain forms a linguistic boundary and in the ideal case you allign your BC with your subdomain and thus it forms a linguistic boundary as well".

Does this make sense or am I completely missing the point?

Jan

__._,_.___

Your email settings: Individual Email|Traditional

Change settings via the Web (Yahoo! ID required)

Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured

Visit Your Group |
Yahoo! Groups Terms of Use |
Unsubscribe

__,_._,___