Frequently asked questions:

Where can I download the Eclipse Plugin?

Use the following Eclipse Update Site and install the plugin in Eclipse via Help -> Install New Software… (copy past the update site link)

Update Site: https://dl.bintray.com/contextmapper/context-mapping-dsl/updates/

How do I create a new context map?

Just create a file with the file extension cml (Context Mapping Language). Take a look at our example to get an idea how it looks like: https://github.com/ContextMapper/context-mapper-examples

Which DDD Patterns are supported by CML?

Have a look at our CML Reference - Introduction page. There you will find all patterns supported by CML.

Which combinations of Strategic DDD Patterns are allowed?

Have a look at the page Language Semantic Model which introduces the semantic model of our DSL and lists the implemented semantic checkers.

Which transformations can I apply to my CML model?

Currently you can generate MDSL (micro-)service contracts providing assistance regarding how your system can be implemented in an (micro-)service-oriented architecture, Service Cutter input to get suggestions for service cuts or new bounded context, and you can generate UML (PlantUML) diagrams out of your CML. The following pages explain the generators in detail:

How can I refactor my CML model?

The Context Mapper tool provides a set of architectural refactorings which you can apply to your model. Find more information and all available refactorings here.

Where do I find a documentation regarding the tactic DDD syntax to specify a bounded context in detail?

The tactic DDD part of our DSL is based on the Sculptor DSL. However, you can find a short introduction and examples how you can detail your bounded contexts on the pages Aggregate and Tactic DDD Syntax. If you are interested in more details and all features, we refer to the Sculptor documentation.

I have other questions not listed here. How can I contribute?

If you have any questions not answered by our documentation page, we are happy if you create an issue in our documentation repo. Of course, PR’s are always welcome as well.

Your contribution is welcome!