Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Definition of system and context and when to use each one #5

Open
mamhend-c opened this issue Jun 18, 2021 · 7 comments
Open

Definition of system and context and when to use each one #5

mamhend-c opened this issue Jun 18, 2021 · 7 comments

Comments

@mamhend-c
Copy link

mamhend-c commented Jun 18, 2021

We need to clarify when to use the system icon or the bounded context icon

@mamhend-c mamhend-c changed the title Definition of system of context w Definition of system of context and when to use each one Jun 18, 2021
@mamhend-c mamhend-c changed the title Definition of system of context and when to use each one Definition of system and context and when to use each one Jun 18, 2021
@yellowbrickc
Copy link
Contributor

Hi @mamhend-c

could you give some more details here?

@philipschm1tt
Copy link

This is a common question about the Domain Message Flow Modeling notation.
You have symbols for both "System" and "Bounded Context".
The two are related, since Bounded Contexts may also be systems/services.
So people are wondering about the difference and why you even need both.
For example, the example diagram with "Website" and "Sales" could only use the Sales Bounded Context – a system that has a website.

@NTCoding
Copy link
Member

NTCoding commented Mar 29, 2022

Hi @philipschm1tt,

In general, I would say purple cloud icon is something that contains business rules or domain logic which your business owns. The system icon is usually a 3rd party system which your business has no control over.

Regarding the UI, I normally use separate icons e.g. a picture of a phone or a computer screen. Most of the time, the mobile app and web UI doesn't belong to any (sub)domain and is something that exposes information and capabilities of multiple (sub)domains.

But logically some people do consider parts of the UI to belong to a particular model and therefore you could show the actor directly interacting with the purple cloud without a system or app in-between..

There aren't many rules with this techniques, as long as you can communicate your intention to the people who will be looking at it, then it's all good.

@philipschm1tt
Copy link

Thanks.
That is pretty much what we figured, too.

Does this answer your question, @mamhend-c?

@alexlawrence
Copy link

@NTCoding Thanks for the explanation. What do you think about adding it to the README? Not as a strict rule but as an option. I had the same thoughts as @mamhend-c when reading it initially.

@NTCoding
Copy link
Member

@alexlawrence it's a good clarification yeah. We should add it to the readme.

I'm hoping to spend some time on this repo addressing some of the comments that have been raised in various discussions. I'm hoping to do this in late July when my book is out of the way. If anyone wants to make any changes before then feel free.

@alexlawrence
Copy link

I'm hoping to do this in late July when my book is out of the way. If anyone wants to make any changes before then feel free.

Sure, if I find some time, I'll go ahead. Currently, I have the same time issue as you it seems 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants