Auto saved by Logseq

2025-06-02 17:15:13 +02:00
commit d9ea3d552d
6279 changed files with 711145 additions and 0 deletions
@@ -0,0 +1,68 @@
+file:: [TTC_2023_paper_3_1682076037575_0.pdf](../assets/TTC_2023_paper_3_1682076037575_0.pdf)
+file-path:: ../assets/TTC_2023_paper_3_1682076037575_0.pdf
+
+- These requirements imply a need for a bidirectional transformation (“bx”) which is asymmetric
+  ls-type:: annotation
+  hl-page:: 1
+  hl-color:: purple
+  id:: 6442724f-b3be-4d37-a58b-89edfca76769
+- asymmetric 
+  ls-type:: annotation
+  hl-page:: 1
+  hl-color:: purple
+  id:: 64427261-5ced-46c1-8fc9-3625d87259b8
+- directed 
+  ls-type:: annotation
+  hl-page:: 1
+  hl-color:: purple
+  id:: 64427264-e4f2-413e-9d5b-84424bc77acd
+- automate continuous
+  ls-type:: annotation
+  hl-page:: 1
+  hl-color:: green
+  id:: 64427447-bafd-4aeb-8397-0a53ac38e58d
+- delivery of new software versions, while guaranteeing their correctness and reliability
+  ls-type:: annotation
+  hl-page:: 1
+  hl-color:: green
+  id:: 6442744e-da5b-4317-ad3d-ba90039627f3
+- DevOpsML: towards modeling DevOps processes and platforms
+  ls-type:: annotation
+  hl-page:: 5
+  hl-color:: green
+  id:: 6442747c-1480-4def-88b8-1494fc8202ec
+- infrastructure-as-code tools 
+  ls-type:: annotation
+  hl-page:: 1
+  hl-color:: green
+  id:: 64427791-7afa-40c5-8911-766b9e6bde71
+- container orchestration tools 
+  ls-type:: annotation
+  hl-page:: 1
+  hl-color:: green
+  id:: 6442779b-eaf0-4431-a733-4e8bf45d0fbf
+- It stands to reason that DevOps model-driven approaches would often aim to generate at least some of these configuration files from the high-level descriptions of the intended service compositions.
+  ls-type:: annotation
+  hl-page:: 1
+  hl-color:: purple
+  id:: 644277b8-90e5-4152-a242-505a3bd89fa7
+- customise the generated configuration files to cover the aspects not described by the high-level model. 
+  ls-type:: annotation
+  hl-page:: 1
+  hl-color:: green
+  id:: 644277d2-3431-452b-b66c-b69e15ed4f6f
+- reorganising the system in a more approachable notation with domain-specific validation rules.
+  ls-type:: annotation
+  hl-page:: 1
+  hl-color:: green
+  id:: 64427805-3a2e-4e17-a578-fc0990d1c7df
+- The proposed case is still directed, but it is asymmetrical (the Docker Compose YAML file contains strictly more information than the high-level model, so information loss only happens in one direction).
+  ls-type:: annotation
+  hl-page:: 2
+  hl-color:: green
+  id:: 64427865-96f7-4130-94f0-db40666b1357
+- this could prove to be an interesting application niche.
+  ls-type:: annotation
+  hl-page:: 2
+  hl-color:: green
+  id:: 6442788a-72e5-458e-a773-e3f77b313ed4