HowTo:Design a Customizing - Revision history

CWI at 15:30, 25 September 2025

2025-09-25T15:30:47Z

CWI at 12:17, 18 September 2025

2025-09-18T12:17:14Z

NWE at 08:51, 14 August 2023

2023-08-14T08:51:21Z

NWE at 08:50, 14 August 2023

2023-08-14T08:50:16Z

NWE at 08:26, 14 August 2023

2023-08-14T08:26:32Z

NWE: /* Topology */

2023-08-14T08:24:47Z

‎Topology

NWE: /* Semantics */

2023-08-14T08:23:37Z

‎Semantics

NWE: /* Semantics */

2023-08-14T08:13:48Z

‎Semantics

NWE at 08:00, 14 August 2023

2023-08-14T08:00:53Z

NWE at 07:59, 14 August 2023

2023-08-14T07:59:14Z

← Older revision		Revision as of 15:30, 25 September 2025
Line 194:		Line 194:
	[[Category:How-To\|Design a Customizing]]		[[Category:How-To\|Design a Customizing]]
	[[Category:Resources (internal)\|Design a Customizing]]		[[Category:Resources (internal)\|Design a Customizing]]
−	~~[[Category:Mobile\|Design a Customizing]]~~

← Older revision		Revision as of 12:17, 18 September 2025
Line 194:		Line 194:
	[[Category:How-To\|Design a Customizing]]		[[Category:How-To\|Design a Customizing]]
	[[Category:Resources (internal)\|Design a Customizing]]		[[Category:Resources (internal)\|Design a Customizing]]
		+	[[Category:Mobile\|Design a Customizing]]

@@ Line 52: / Line 52: @@
 = Architecture =
 The architecture is something to consider on a rather abstract level, in the beginning of a project, but also on the level of a single task.
-In the context of a whole project, architecture means defining whether there are multiple {{UBIK}} installations on different sites, what products will be involved and how they are connected topologically and semantically. On task level, the same is interesting, just in greater detail and smaller scope, like zooming in on it.
+In the context of a whole project, architecture means defining whether there are multiple {{UBIK}} installations on different sites, what products and 3rd party systems will be involved and how they are connected topologically and semantically. On task level, the same is interesting, just in greater detail and smaller scope, like zooming in on it.
 === Topology ===

@@ Line 32: / Line 32: @@
 Make sure to maintain the Project Structure Plan for non-trivial tasks. In the rest of this article, best practices for the individual steps are described.
 = Architecture =
@@ Line 45: / Line 62: @@
 ** using which protocol
 ** covering what data
 === Semantics ===
@@ Line 54: / Line 67: @@
 * What is the purpose of a module?
 * What information is exchanged via an interface, what does it do for the use-case?
 === Restrictions ===

@@ Line 35: / Line 35: @@
 = Architecture =
 The architecture is something to consider on a rather abstract level, in the beginning of a project, but also on the level of a single task.
-In the context of a whole project, architecture means defining whether there are multiple {{UBIK}} installations on different sites, what products will be involved and how they are connected topologically and semantically. On task level, the same is interesting, just in greater detail.
+In the context of a whole project, architecture means defining whether there are multiple {{UBIK}} installations on different sites, what products will be involved and how they are connected topologically and semantically. On task level, the same is interesting, just in greater detail and smaller scope, like zooming in on it.
 === Topology ===
@@ Line 46: / Line 46: @@
 ** covering what data
-[[Category:Best Practices (internal)|Design a Customizing]]
-[[Category:How-To|Design a Customizing]]
-[[Category:Resources (internal)|Design a Customizing]]
 === Semantics ===
@@ Line 55: / Line 55: @@
 * What information is exchanged via an interface, what does it do for the use-case?
-[[Category:Best Practices (internal)|Design a Customizing]]
-[[Category:How-To|Design a Customizing]]
-[[Category:Resources (internal)|Design a Customizing]]
 === Restrictions ===

@@ Line 38: / Line 38: @@
 === Topology ===
-In this context, topology addresses the technical architecture. Questions:
+In this context, topology (the science of spatial relations) addresses the technical architecture. Questions:
 * What top-level modules do exist where?
 ** in the network
@@ Line 45: / Line 45: @@
 ** using which protocol
 ** covering what data
 === Semantics ===

@@ Line 35: / Line 35: @@
 = Architecture =
 The architecture is something to consider on a rather abstract level, in the beginning of a project, but also on the level of a single task.
-In the context of a whole project, architecture means defining whether there are multiple {{UBIK}} installations on different sites, what products will be involved and how they are connected topologically and semantically. In this context, topology addresses the technical architecture. Questions:
+In the context of a whole project, architecture means defining whether there are multiple {{UBIK}} installations on different sites, what products will be involved and how they are connected topologically and semantically. On task level, the same is interesting, just in greater detail.
 * What top-level modules do exist where?
 ** in the network
@@ Line 42: / Line 45: @@
 ** using which protocol
 ** covering what data
 Semantics in this context addresses the functional architecture: which task-level modules are taking care of what responsibility, and how they play together. Questions:
 * What is the purpose of a module?
 * What information is exchanged via an interface?
-On task level, the same is interesting, just in greater detail.
+=== Restrictions ===
-−
 We recommend the architecture to satisfy the following restrictions.
-=== Top-Level architecture ===
+==== Top-Level architecture ====
 * Network-distances between the database server and the application server (e.g., web services) should be minimal for performance reasons.
 * One should always plan for a staging strategy with multiple environments for QA.
-=== Task-level architecture ===
+==== Task-level architecture ====
 * Custom code should always be developed in a plugin where possible, with the {{UBIK}} custom code just connecting the plugin code with the {{UBIK}} objects.
 * Custom code should be arranged so heavy-duty processes (involving much data and complex calculations) are performed on powerful machines (and not on the mobile client).