Skip to content

Document basePackage on Bounded Contexts #106

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.

Sign up for GitHub

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

Draft
stefan-ka wants to merge 1 commit into
base: feature/aggregate-invariants
Choose a base branch
from
Draft

Document basePackage on Bounded Contexts #106

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions _docs/language-reference/bounded-context.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ BoundedContext CustomerManagementContext implements CustomerManagementDomain {
type = FEATURE
domainVisionStatement = "The customer management context is responsible for ..."
implementationTechnology = "Java, JEE Application"
basePackage = org.insurance.customermanagement
responsibilities = "Customers", "Addresses"
nonResponsibilities = "Policies", "Debt collection"
knowledgeLevel = CONCRETE
Expand Down Expand Up @@ -96,6 +97,19 @@ With the _domainVisionStatement_ keyword you can describe the vision statement o
### Implementation Technology
The _implementationTechnology_ attribute allows you to add information about how the corresponding bounded context is implemented. Note that this attribute does not correspond to any DDD pattern.

### Base Package
With the _basePackage_ attribute you can declare where the bounded context lives in the code, as a package name (dot-separated identifiers, without quotes):

```cml
BoundedContext TicketSales implements FareSales {
basePackage = com.transit.ticketsales
}
```

This information connects the model with the code. Tools that verify the code against the model (such as architecture tests) or generate artifacts from the model can use it instead of relying on naming conventions. Like _implementationTechnology_, this attribute does not correspond to any DDD pattern.

Modules inside a bounded context can still define their own _basePackage_.

### Responsibility Layers
With the _responsibilities_ keyword you are allowed to specify the responsibilities of the bounded context, according to the DDD Responsibility Layers pattern. See [responsibility layers](/docs/responsibility-layers/).

Expand Down
Loading