context-mapper-dsl
context-mapper-dsl copied to clipboard
ContextMapper
ContextMapper DSL: A Domain-specific Language for Context Mapping & Service Decomposition
To me one of the primary points of a use case is the extensions section. I actually prefer to call it exceptions but... That's kind of irrelevant. I'd like to...
> Note: Aggregate names must be unique within the whole CML model. > Error: Multiple aggregates with the name 'Artist' have been declared. As I understand it, in Domain Driven...
Hi, I was able to build and run the eclipse and the vscode integration. The vsix downloads and runs a context-mapper-lsp-6.5.0.jar. I would like to build the language server in...
`mapEvents` in `MDSLModelCreator` does not support operations yet, could be mapped to command types in MDSL flow steps too
get stories via traceability links from BC to SD to tbd; preview: ```java IntegrationScenario defaultScenario = new IntegrationScenario(); defaultScenario.setName(apiName); Story defaultStory = new Story(apiName+"DefaultStory", "ContextClient", "ContextResponsibility", "ContextDomainVisionStatement"); defaultScenario.addStory(defaultStory); specification.addScenario(defaultScenario); ```
Context: Aggregate state changes caused by service/entity operations. While `write [S1-> S2x S3]` and `write [S2,S3-> S4]` work I cannot model something like: ``` write [S1->S2, S1->S3, S2->S4, S3->S4] ```...
... to support documentation-as-code even further. https://plantuml.com/use-case-diagram
It would be nice to feature attribute- and operation-level keywords such as "required", "size", "range", "read-only" in puml output. One possible solution: Use stereotypes or attribute-level notes as described here:...
Current flow steps can be of the types: * event EventXY triggers command CommandXY * command CommandZ emits event EventZ Do we maybe need another type? * command CommandA triggers...
Metadata
Owner
Metadata
ContextMapper DSL: A Domain-specific Language for Context Mapping & Service Decomposition