Skip to Content

Changes for page Discovery

Last modified by Danniar Firdausy on 2024/08/20 15:09
From version 30.1
edited by Carlijn Kokkeler
on 2024/08/08 11:23
Change comment: There is no comment for this version
To version 34.1
edited by Erik Bakker
on 2024/08/08 15:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -16,16 +16,16 @@
16 16  == 3. Technical requirements ==
17 17  
18 18  Before entering the Capture phase, several technical requirements need to be considered.
19 -* First of all, it needs to be discussed who will provide data and who will consume data.
19 +* First, it needs to be discussed who will provide data and who will consume it.
20 20  * Secondly, the exact definition of the data elements that will be exchanged has to be obtained.
21 -* Thirdly, the size of the data packets needs to be established, as well as the frequency of the packets.
22 -* Lastly, it has to be considered what constraints with respect to connectivity have to be in place.
21 +* Thirdly, the size and frequency of the data packets need to be established.
22 +* Lastly, constraints concerning connectivity have to be considered.
23 23  
24 24  A more elaborate description of the technical requirements can be found in [[this>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-intro-technrequirements||target="blank"]] microlearning.
25 25  
26 26  == 4. Capture ==
27 27  
28 -In the Capture phase, the involved systems and integrations are drawn into a canvas. The technical requirements as described in the previous section should be stored in this phase as well. We recommend filling out all documentation available in this phase, because this documentation can help to ensure smooth development by means of providing the context and other supporting information to the involved team members/stakeholders, so they can make better decisions when developing or maintaining the integration in the subsequent phases.
28 +The systems and integrations are drawn into a canvas in the capture phase. The technical requirements, as described in the previous section, should also be stored in this phase. We recommend filling out all documentation available in this phase because it can help ensure smooth development by providing context and other supporting information to the involved team members/stakeholders so they can make better decisions when developing or maintaining the integration in the subsequent phases.
29 29  
30 30  When you want to create your systems, you need to ask yourself the following questions:
31 31  * What systems are relevant in our business case?
... ... @@ -38,7 +38,7 @@
38 38  * Does this system have similarities with existing systems?
39 39  * How should this system interact with existing systems?
40 40  
41 -Some more documentation may be relevant, and can be filled out easily while configuring a system. More information on how to configure a system can be found in [[this>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-system||target="blank"]] microlearning.
41 +Some more relevant documentation may be quickly filled out while configuring a system. More information on configuring a system can be found in [[this>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-system||target="blank"]] microlearning.
42 42  
43 43  When you want to create an integration, you need to ask yourself the following questions:
44 44  * What is the purpose of this integration?
... ... @@ -46,24 +46,24 @@
46 46  * What should this integration be called?
47 47  * Which integration pattern belongs to this integration?
48 48  
49 -Some more documentation may be relevant, and can be filled out easily while configuring an integration. More information on how to configure a [[message type>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-message-type||target="blank"]] or [[integration>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-integration||target="blank"]] can be found in the corresponding mircolearnings.
49 +Some more documentation may be relevant and easily filled out while configuring an integration. More information on configuring a [[message type>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-message-type||target="blank"]] or [[integration>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-integration||target="blank"]] can be found in the corresponding microlearning.
50 50  
51 51  == 5. Design ==
52 52  
53 -After the Capture phase, you can proceed to the Design phase. In the Design phase, the system message definitions are created, and the transformation mappings are drawn. A message definition is a visual representation of how the elements are related to each other, whether they are mandatory and the data types they have that can be used in the message mapping. The client infrastructure is also determined in the Design phase, and several cloud components are specified. When you start working in the design phase, you should ask yourself the following questions:
53 +After the Capture phase, you can proceed to the Design phase. The system message definitions are created in the Design phase, and the transformation mappings are drawn. A message definition is a visual representation of how the elements are related to each other, whether they are mandatory, and the data types they have that can be used in the message mapping. The client infrastructure is also determined in the Design phase, and several cloud components are specified. When you start working in the design phase, you should ask yourself the following questions:
54 54  * What should my data model look like?
55 55  * What message definitions are needed?
56 56  * Which message formats are required?
57 57  * How should the message mapping be done?
58 -* What should the architecture (incl. instances, machine sizes, etc.) be like?
58 +* What should the architecture (incl. instances, machine sizes, and more) be like?
59 59  * What metadata needs to be stored?
60 60  
61 61  In case you would like to expand your existing integration landscape, you need to ask yourself several questions as well:
62 62  * How does my addition to the data model fit into the current data model?
63 -* Which entities in the current data model have overlap with the entities I wish to add?
63 +* Which entities in the current data model overlap with those I wish to add?
64 64  * Are there any overlapping system messages if I add this system message?
65 65  
66 -Several more questions may be relevant. Documentation on how to develop in the Design phase can be found in the [[Platform Crash Courses>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.||target="blank"]].
66 +Several more questions may be relevant. Documentation on development in the design phase can be found in the [[Platform Crash Courses>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform||target="blank"]].
67 67  
68 68  == 6. Key takeaways ==
69 69  
... ... @@ -72,11 +72,24 @@
72 72  * The Capture & Design phases are used to discover the integration landscape in eMagiz.
73 73  
74 74  == 7. Suggested Additional Readings ==
75 +
76 +[[this>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-system||target="blank"]]
77 + [[message type>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-message-type||target="blank"]]
78 +[[integration>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-capture-configure-a-integration||target="blank"]]
75 75  * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
76 76  ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
77 -*** [[Technical requirements before starting in eMagiz (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-intro-technrequirements||target="blank"]]
78 -* [[Integration Lifecycle Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-intro-the-five-phases-of-emagiz||target="blank"]]
79 -* [[Platform Crash Courses>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.||target="blank"]]
81 +*** [[Integration Lifecycle Management (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-intro-the-five-phases-of-emagiz||target="blank"]]
82 +*** [[Technical Requirements (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-intro-technrequirements||target="blank"]]
83 +*** [[Message Type (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-intro-technrequirements||target="blank"]]
84 +*** [Configure An Integration (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-intro-technrequirements||target="blank"]]
85 +*** [[What Is A Message Definition (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-what-is-a-message-definition||target="blank"]]
86 +*** [Importing A Message Definition (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-import-message-definition||target="blank"]]
87 +*** [Understanding Design Architecture - Basic (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-understanding-design-architecture-basic||target="blank"]]
88 +** [[Crash Course Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.WebHome||target="blank"]]
89 +*** [Understanding Design Architecture - Basic (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-what-is-cdm||target="blank"]]
90 +* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
91 +** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.WebHome||target="blank"]]
92 +*** [Understanding Design Architecture (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.intermediate-solution-architecture-understanding-design-architecture||target="blank"]]
80 80  
81 81  
82 82  )))((({{toc/}}))){{/container}}{{/container}}