Introduction

Welcome Getting started Create CML Project Examples Usage as Library Frequently Asked Questions

Language Reference (Core)

CML Reference - Introduction Language Semantics Context Map Bounded Context Domain and Subdomain Domain Vision Statement Partnership Shared Kernel Customer/Supplier Conformist Open Host Service Anticorruption Layer Published Language Responsibility Layers Knowledge Level Aggregate Tactic DDD Syntax Application and Process Layer User Requirements Stakeholders Value Registers Imports

Analysis and Design Transformations

Rapid Object-oriented Analysis and Design Story Splitting (PoC) Stakeholder and Value Modelling Transformations

Architectural Refactorings (ARs)

Architectural Refactorings AR-1: Split Aggregate by Entities AR-2: Split Bounded Context by Features AR-3: Split Bounded Context by Owner AR-4: Extract Aggregates by Volatility AR-5: Extract Aggregates by Cohesion AR-6: Merge Aggregates AR-7: Merge Bounded Contexts AR-8: Extract Shared Kernel AR-9: Suspend Partnership AR-10: Change Shared Kernel to Partnership AR-11: Change Partnership to Shared Kernel

Value-Driven Analysis and Design

Value-Driven Analysis and Design (VDAD) Support

Service Cutter

Context Map Suggestions with Service Cutter Service Cutter Configuration File (.servicecutter.yml)

Reverse Engineering

Context Map Discovery

Generators

Generators Overview Context Map Generator PlantUML Generator BPMN Sketch Miner Generator MDSL (Micro-)Service Contracts Generator Service Cutter Generators Generic Generator (Templating)

Tutorials

Model Event Storming Results in Context Mapper Event Sourcing and CQRS Modeling in Context Mapper Generate Microservices From Context Map Using JHipster Systematic Service Decomposition with Context Mapper and Service Cutter Validating the Implementation against the Model (with ArchUnit)

IDE Plugins and Extensions

Visual Studio Code Extension Online IDE (via Gitpod) Eclipse Plugin Feature Support

Conformist

The Conformist pattern describes a relationship between two bounded contexts and is used on a context map in CML.

Syntax

The Conformist pattern can be used as a role for the downstream context in a Upstream/Downstream relationship by using the CF abbreviation. The following example illustrates the syntax:

PolicyManagementContext [D,CF]<-[U,OHS,PL] CustomerManagementContext {
  implementationTechnology = "RESTful HTTP"
}

Semantic Rules

Note that semantic rules (validators) exist for Conformist within CML. This means that not every combination of patterns and concepts is allowed, even if it would be syntactically correct. The following rules apply to a Conformist:

The Conformist pattern is not applicable in a Customer/Supplier relationship.

For a summary of all semantic rules and further justifications, please consult Language Semantics.

Improve this page