From c3a02804d3d21f57ec297dda8946c353017fc439 Mon Sep 17 00:00:00 2001
From: "Prof. Dr. Volker Coors" <volker.coors@hft-stuttgart.de>
Date: Sun, 19 Jul 2020 09:34:32 +0000
Subject: [PATCH] Update 01 Background_and_Definitions.adoc
---
.../01 Background_and_Definitions.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/D01 Integration of INSEL Models and SimStadt/01 Background_and_Definitions.adoc b/D01 Integration of INSEL Models and SimStadt/01 Background_and_Definitions.adoc
index b53ed2d..407a2f2 100644
--- a/D01 Integration of INSEL Models and SimStadt/01 Background_and_Definitions.adoc
+++ b/D01 Integration of INSEL Models and SimStadt/01 Background_and_Definitions.adoc
@@ -13,9 +13,9 @@ The definition of the scope of a WFS is up to the user. Some predefined WFSs as
In general, a workflow step in SimStadt consists of a functional part F, connector to workflow communication part C and a human computer interaction part HCI.
-
-
-Figure 1: the three components of a SimStadt Workflow Step
+[#img_WFS,reftext='{figure-caption} {counter:figure-num}']
+.The three components of a SimStadt Workflow Step
+image::img/WFS.png[align="center"]
The functional part of the Workflow step encapsulates the purpose of a particular workflow step. For example, the calculation of the volume of a building happens here. The functional part has to be independend of the communication between workflow steps as well as the HCI part. Why? Because a workflow step has to have the same functionality in the SimStadt desktop application and as Web Services. In addition, the workflow can be executed as a batch process and as an interactive system.
--
GitLab