diff --git a/_cmls/systematic-service-decomposition-tutorial-1.cml b/_cmls/systematic-service-decomposition-tutorial-1.cml
new file mode 100644
index 0000000..664b43d
--- /dev/null
+++ b/_cmls/systematic-service-decomposition-tutorial-1.cml
@@ -0,0 +1,48 @@
+BoundedContext CargoTracking {
+ Aggregate Cargo {
+ owner CargoPlaner
+
+ Entity Cargo {
+ aggregateRoot
+ - TrackingId trackingId
+ - Location origin
+ - RouteSpecification routeSpecification
+ - Itinerary itinerary
+ - Delivery delivery
+ }
+ /* shortened Aggregate here */
+ }
+ Aggregate Location {
+ owner Administrators
+
+ Entity Location {
+ aggregateRoot
+ - UnLocode unLocode
+ String name
+ }
+ /* shortened Aggregate here */
+ }
+ Aggregate Handling {
+ owner CargoTracker
+
+ DomainEvent HandlingEvent {
+ - HandlingEventType handlingEventType
+ - Voyage voyage
+ - Location location
+ Date completionTime
+ Date registrationTime
+ - Cargo cargo
+ }
+ /* shortened Aggregate here */
+ }
+ Aggregate Voyage {
+ owner VoyageManager
+
+ Entity Voyage {
+ aggregateRoot
+ - VoyageNumber voyageNumber
+ - Schedule schedule
+ }
+ /* shortened Aggregate here */
+ }
+}
diff --git a/_cmls/systematic-service-decomposition-tutorial-1.html b/_cmls/systematic-service-decomposition-tutorial-1.html
new file mode 100644
index 0000000..2e655e8
--- /dev/null
+++ b/_cmls/systematic-service-decomposition-tutorial-1.html
@@ -0,0 +1,49 @@
+BoundedContext CargoTracking {
+ Aggregate Cargo {
+ owner CargoPlaner
+
+ Entity Cargo {
+ aggregateRoot
+ - TrackingId trackingId
+ - Location origin
+ - RouteSpecification routeSpecification
+ - Itinerary itinerary
+ - Delivery delivery
+ }
+ /* shortened Aggregate here */
+ }
+ Aggregate Location {
+ owner Administrators
+
+ Entity Location {
+ aggregateRoot
+ - UnLocode unLocode
+ String name
+ }
+ /* shortened Aggregate here */
+ }
+ Aggregate Handling {
+ owner CargoTracker
+
+ DomainEvent HandlingEvent {
+ - HandlingEventType handlingEventType
+ - Voyage voyage
+ - Location location
+ Date completionTime
+ Date registrationTime
+ - Cargo cargo
+ }
+ /* shortened Aggregate here */
+ }
+ Aggregate Voyage {
+ owner VoyageManager
+
+ Entity Voyage {
+ aggregateRoot
+ - VoyageNumber voyageNumber
+ - Schedule schedule
+ }
+ /* shortened Aggregate here */
+ }
+}
+UseCase ViewTracking {
+ reads "Cargo.trackingId", "HandlingEvent.type", "HandlingEvent.location", "HandlingEvent.completionTime", "Delivery.transportStatus", "Delivery.estimatedArrivalTime", "Delivery.misdirected", "Voyage.voyageNumber", "RouteSpecification.destination"
+}
+
+UseCase ViewCargos {
+ reads "Cargo.trackingId", "RouteSpecification.destination", "RouteSpecification.arrivalDeadline", "Delivery.routingStatus", "Itinerary.itineraryNumber"
+}
+
+UseCase BookCargo {
+ reads "Location.unLocode"
+ writes "Cargo.trackingId", "RouteSpecification.origin", "RouteSpecification.arrivalDeadline", "RouteSpecification.destination"
+}
+
+UseCase ChangeCargoDestination {
+ reads "Cargo.trackingId", "RouteSpecification.destination"
+ writes "RouteSpecification.destination"
+}
+
+/* we shortened this listing to save space (find all use cases in the original CML file) */
+BoundedContext CargoTracking {
+ Aggregate Cargo {
+ owner CargoPlaner
+
+ /* removed content here to save space */
+ }
+ Aggregate Location {
+ owner Administrators
+
+ /* removed content here to save space */
+ }
+ Aggregate Handling {
+ owner CargoTracker
+
+ /* removed content here to save space */
+ }
+ Aggregate Voyage {
+ owner VoyageManager
+
+ /* removed content here to save space */
+ }
+}
+
+/* team definitions: */
+BoundedContext CargoPlaner { type TEAM }
+BoundedContext CargoTracker { type TEAM }
+BoundedContext VoyageManager { type TEAM }
+BoundedContext Administrators { type TEAM }
+
-
Note: The Service Cutter generators are not yet supported in our new Visual Studio Code extension. We continuously work on the extension and will support them soon! To use this generators you have to use the Eclipse plugin for now. You can find a feature support table for Eclipse and VS Code
here.
-
-Note that the Context Mapper menu entry is also available within the context menu uf the CML editor
-(right-click anywhere in the editor).
-
-
### Generate SCL File
The second input file for Service Cutter deals with additional *User representations*. Service Cutter takes them in JSON format, but there is some manual work required to create these file. Hence, we implemented another DSL which makes this step much easier. These files have the file extension `*.scl*` (for *Service Cutter Language*).
-A SCL file can be generated out of a CML file. Again, a right-click to the CML-file will open the **Context Mapper** context menu. You can initialize your SCL file with the action **Service Cutter: Initialize User Representations File (Exemplary)**:
+An SCL file can be generated out of a CML file. Again, a right-click in the CML editor will allow you to call the action **Generate Service Cutter User Representations (SCL)**:
-**Note:** The generated SCL file is a template that intends to help you by setting the structure expected by Service Cutter. The following generated parts are only examples, and
-will have to be adjusted:
+The SCL grammar allows you to describe all [user representations supported by Service Cutter](https://github.com/ServiceCutter/ServiceCutter/wiki/User-Representations):
+
+ * Entity Relationship Model (ERM)
+ * Use Cases
+ * Shared Owner Groups
+ * Aggregates
+ * Entities
+ * Predefined Services
+ * Separated Security Zones
+ * Security Access Groups
+ * Compatibilities
+
+Most of the user representations we derive from the CML model automatically. The ERM is derived from the Entities and their references in CML. The Use Cases and Shared Owner Groups can be modeled in CML as well (have a look at our [service decomposition tutorial](/docs/systematic-service-decomposition/)). We further derive the Aggregates and Entities for Service Cutter from the corresponding counterparts in CML. In addition, we derive Predefined Services from already existing Bounded Contexts of your CML model. The remaining user representations have to be described manually, in case they are relevant for your application.
+
+However, the generated SCL file already contains most of the representations:
- * **[Use Cases](https://github.com/ServiceCutter/ServiceCutter/wiki/Use-Cases)**
- * **All [Compatibilities](https://github.com/ServiceCutter/ServiceCutter/wiki/Compatibilities)**
- * **[Security Access Groups](https://github.com/ServiceCutter/ServiceCutter/wiki/Security-access-groups)**
- * **[Separated Security Zone](https://github.com/ServiceCutter/ServiceCutter/wiki/Separated-security-zones)**
- * **[Shared Owner Group](https://github.com/ServiceCutter/ServiceCutter/wiki/Shared-owner-groups)**
+
-The following elements are actually derived from the CML model and do not have to be changed:
+**Note:** The automatically derived user representations are overwritten if you call the generator again.
- * **[Aggregates](https://github.com/ServiceCutter/ServiceCutter/wiki/Aggregates)** (derived from your Aggregates in the CML file)
- * **[PredefinedService](https://github.com/ServiceCutter/ServiceCutter/wiki/Predefined-services)** (derived from your bounded contexts in the CML file)
+#### Examplary SCL File
+In case you want to add more user representations that are missing in the automatically generated ones, you can generate an exemplary SCL file that illustrates the syntax for all possible representations. Just call the **Generate Service Cutter User Representation Example File (SCL)** action to generate an example:
+
+
+
+**Note:** This generated SCL file is only exemplary and intended to help you setting up the structure in the actual SCL file generated in the step above.
### Generate User Representations JSON File
-Once you have prepared your SCL file, you can generate the corresponding JSON file with the action **Service Cutter: Generate User Representations File (JSON)** in the context menu:
+Once you have prepared your SCL file, you can generate the corresponding JSON file with the action **Generate Service Cutter User Representation JSON File** in the context menu:
@@ -67,3 +71,8 @@ Have fun with cutting your services :)
*Note:* Service Cutter has not been updated in a while, and only intended to demonstrate the possibilities of criteria-based graph clustering in the context of service decomposition (and establish a method and a first catalog of criteria). So do not expect mature, production-ready cuts to be suggested, but view them as a discussion and design workshop input. Further research is required to harden the approach; such research is ongoing (evidence: [40+ citations of the Service Cutter paper presented at ESOCC 2016](https://www.researchgate.net/publication/307873263_Service_Cutter_A_Systematic_Approach_to_Service_Decomposition)).
+
+## Further Links
+Note that you can also generate new service cuts in Context Mapper directly without using Service Cutter! We integrated the Service Cutter library into Context Mapper so that our users are able to generate new service decompositions out of CML models easily.
+
+ * Have a look at our [Systematic Service Decomposition with Context Mapper and Service Cutter](/docs/systematic-service-decomposition/) tutorial.
diff --git a/_docs/ide-plugins-and-extensions/ide-support.md b/_docs/ide-plugins-and-extensions/ide-support.md
index 4ce2b4a..90b2e76 100644
--- a/_docs/ide-plugins-and-extensions/ide-support.md
+++ b/_docs/ide-plugins-and-extensions/ide-support.md
@@ -3,41 +3,45 @@ title: Feature Support
permalink: /docs/ide/
---
-We currently offer Context Mapper for Visual Studio Code and Eclipse:
+We currently offer Context Mapper for [Visual Studio Code](https://code.visualstudio.com/), in the Online IDE [Gitpod](https://www.gitpod.io/), and [Eclipse](https://www.eclipse.org/):
* [Context Mapper for VS Code](https://marketplace.visualstudio.com/items?itemName=contextmapper.context-mapper-vscode-extension) (Marketplace)
+ * [Context Mapper Online (Gitpod)](/docs/online-ide/)
* [Context Mapper for Eclipse](https://marketplace.eclipse.org/content/context-mapper) (Marketplace)
Note: We have only recently published the VS Code extension and it does not support all the features yet. In case you need all the features, you have to work with Eclipse for now. We work on the VS code extension and hope to support all the features soon!
+Note: The Online IDE is based on our VS Code extension and supports the same features.
+
+
## Supported Features per IDE
The following table illustrates which features are already implemented in VS Code. Both IDEs shall support all features in the future.
-| Feature | Supported in Eclipse Plugin | Supported in VS Code Extension |
-|--------------------------------------------------------------|-----------------------------|--------------------------------|
-| Editor: Syntax Highlighting | yes | yes |
-| Editor: Auto-completion | yes | yes |
-| Editor: Hover texts with pattern descriptions | yes | no |
-| Editor: Semantic validators | yes | yes |
-| Graphical Context Map generator | yes | yes |
-| PlantUML generator | yes | yes |
-| MDSL generator | yes | yes |
-| Generic text file generator | yes | yes |
-| Service Cutter input file generators | yes | no |
-| New service cut generator | yes | no |
-| OOAD transformation: Derive Subdomain from user requirements | yes | yes |
-| OOAD transformation: Derive Bounded Context from Subdomains | yes | yes |
-| OOAD transformation: Derive frontend and backend systems | yes | no |
-| OOAD transformation: Split system context into subsystems | yes | no |
-| AR: "Split Aggregate by Entities" | yes | yes |
-| AR: "Split Bounded Context by Use Cases" | yes | yes |
-| AR: "Split Bounded Context by Owner" | yes | yes |
-| AR: "Extract Aggregates by Volatility" | yes | no |
-| AR: "Extract Aggregates by Cohesion" | yes | no |
-| AR: "Merge Aggregates" | yes | no |
-| AR: "Merge Bounded Contexts" | yes | no |
-| AR: "Extract Shared Kernel" | yes | no |
-| AR: "Suspend Partnership" | yes | no |
-| AR: "Change Shared Kernel to Partnership" | yes | no |
-| AR: "Change Partnership to Shared Kernel" | yes | no |
+| Feature | Supported in Eclipse Plugin | Supported in VS Code Extension (and online) |
+|--------------------------------------------------------------|-----------------------------|---------------------------------------------|
+| Editor: Syntax Highlighting | yes | yes |
+| Editor: Auto-completion | yes | yes |
+| Editor: Hover texts with pattern descriptions | yes | no |
+| Editor: Semantic validators | yes | yes |
+| Graphical Context Map generator | yes | yes |
+| PlantUML generator | yes | yes |
+| MDSL generator | yes | yes |
+| Generic text file generator | yes | yes |
+| Service Cutter input file generators | yes | yes |
+| New service cut generator | yes | yes |
+| OOAD transformation: Derive Subdomain from user requirements | yes | yes |
+| OOAD transformation: Derive Bounded Context from Subdomains | yes | yes |
+| OOAD transformation: Derive frontend and backend systems | yes | no |
+| OOAD transformation: Split system context into subsystems | yes | no |
+| AR: "Split Aggregate by Entities" | yes | yes |
+| AR: "Split Bounded Context by Use Cases" | yes | yes |
+| AR: "Split Bounded Context by Owner" | yes | yes |
+| AR: "Extract Aggregates by Volatility" | yes | no |
+| AR: "Extract Aggregates by Cohesion" | yes | no |
+| AR: "Merge Aggregates" | yes | no |
+| AR: "Merge Bounded Contexts" | yes | no |
+| AR: "Extract Shared Kernel" | yes | no |
+| AR: "Suspend Partnership" | yes | no |
+| AR: "Change Shared Kernel to Partnership" | yes | no |
+| AR: "Change Partnership to Shared Kernel" | yes | no |
diff --git a/_docs/service-cutter/context-map-suggestions.md b/_docs/service-cutter/context-map-suggestions.md
index 9711e72..2cd2bbd 100644
--- a/_docs/service-cutter/context-map-suggestions.md
+++ b/_docs/service-cutter/context-map-suggestions.md
@@ -8,10 +8,6 @@ to 14 prioritized [coupling criteria](https://github.com/ServiceCutter/ServiceCu
graph clustering algorithms to identify possible *service cuts*, which are returned as output. The approach was proposed by
[this paper](https://link.springer.com/chapter/10.1007/978-3-319-44482-6_12).
-
-
Note: This feature is not yet supported in our new Visual Studio Code extension. We continuously work on the extension and will support it soon! To use this feature you have to use the Eclipse plugin for now. You can find a feature support table for Eclipse and VS Code
here.
-
BoundedContext CargoTracking {
+ Aggregate Cargo {
+ owner CargoPlaner
+
+ Entity Cargo {
+ aggregateRoot
+ - TrackingId trackingId
+ - Location origin
+ - RouteSpecification routeSpecification
+ - Itinerary itinerary
+ - Delivery delivery
+ }
+ /* shortened Aggregate here */
+ }
+ Aggregate Location {
+ owner Administrators
+
+ Entity Location {
+ aggregateRoot
+ - UnLocode unLocode
+ String name
+ }
+ /* shortened Aggregate here */
+ }
+ Aggregate Handling {
+ owner CargoTracker
+
+ DomainEvent HandlingEvent {
+ - HandlingEventType handlingEventType
+ - Voyage voyage
+ - Location location
+ Date completionTime
+ Date registrationTime
+ - Cargo cargo
+ }
+ /* shortened Aggregate here */
+ }
+ Aggregate Voyage {
+ owner VoyageManager
+
+ Entity Voyage {
+ aggregateRoot
+ - VoyageNumber voyageNumber
+ - Schedule schedule
+ }
+ /* shortened Aggregate here */
+ }
+}
+UseCase ViewTracking {
+ reads "Cargo.trackingId", "HandlingEvent.type", "HandlingEvent.location", "HandlingEvent.completionTime", "Delivery.transportStatus", "Delivery.estimatedArrivalTime", "Delivery.misdirected", "Voyage.voyageNumber", "RouteSpecification.destination"
+}
+
+UseCase ViewCargos {
+ reads "Cargo.trackingId", "RouteSpecification.destination", "RouteSpecification.arrivalDeadline", "Delivery.routingStatus", "Itinerary.itineraryNumber"
+}
+
+UseCase BookCargo {
+ reads "Location.unLocode"
+ writes "Cargo.trackingId", "RouteSpecification.origin", "RouteSpecification.arrivalDeadline", "RouteSpecification.destination"
+}
+
+UseCase ChangeCargoDestination {
+ reads "Cargo.trackingId", "RouteSpecification.destination"
+ writes "RouteSpecification.destination"
+}
+
+/* we shortened this listing to save space (find all use cases in the original CML file) */
+BoundedContext CargoTracking {
+ Aggregate Cargo {
+ owner CargoPlaner
+
+ /* removed content here to save space */
+ }
+ Aggregate Location {
+ owner Administrators
+
+ /* removed content here to save space */
+ }
+ Aggregate Handling {
+ owner CargoTracker
+
+ /* removed content here to save space */
+ }
+ Aggregate Voyage {
+ owner VoyageManager
+
+ /* removed content here to save space */
+ }
+}
+
+/* team definitions: */
+BoundedContext CargoPlaner { type TEAM }
+BoundedContext CargoTracker { type TEAM }
+BoundedContext VoyageManager { type TEAM }
+BoundedContext Administrators { type TEAM }
+ ](/img/service-cutter-input-generation-1.png){kind=link}
](/img/service-cutter-input-generation-2.png){kind=link}
](/img/service-cutter-input-generation-2-1.png){kind=link}
](/img/service-cutter-input-generation-2-2.png){kind=link}
](/img/service-cutter-input-generation-3.png){kind=link}
](/img/service-cutter-insurance-example.png){kind=link}
](/img/service-cut-generator-config-file.png){kind=link}
](/img/service-cut-generator-dialog.png){kind=link}
](/img/service-cut-generator-ddd-sample-result.png){kind=link}