ddd-crew / ddd-crew/context-mapping
Team relationships vs patterns.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.9k
- Forks
- 155
- PR merge metrics
- No merged PRs in 30d
Description
Could someone please explain better why the "Partnership" and "Customer-Supplier" are patterns and not team relationships? It seems like a mistake of categorization.
Even the explanation of these "patterns" begin with teams relationships.
If the aim of the repo is to simplify the understanding, I think it would be greate to either fix the categorization issue or explain why it was made this way.
I think Evanse's book is not a Bible and could tolerate new interpretations, doesn't it?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the repository's current documentation for team relationships, Partnership, and Customer-Supplier patterns. Compare the categorization with the stated explanations, then either revise the categorization or document a clear rationale for keeping it; completion requires one consistent, explained treatment.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100