Skip to Content

Changes for page Discovery

Last modified by Danniar Firdausy on 2024/08/20 15:09
From version 21.1
edited by Carlijn Kokkeler
on 2023/09/08 14:03
Change comment: There is no comment for this version
To version 18.1
edited by Carlijn Kokkeler
on 2023/09/07 09:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this fundamental, we will explain the concept of discovery within eMagiz. This concerns the discovery of an integration landscape, which is mainly achieved in the Capture & Design phases from eMagiz. The phases from eMagiz correspond with phases from Integration Lifecycle Management. More information about these phases can be found in [[this>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-intro-the-five-phases-of-emagiz||target="blank"]] microlearning. Discovery of the integration landscape is very important and should be handled by experienced staff.
2 +In this fundamental, we will explain the concept of discovery within eMagiz. This concerns the discovery of an integration landscape, which is mainly achieved in the Capture & Design phases from eMagiz. The phases from eMagiz correspond with phases from Integration Lifecycle Management. More about the Integration Lifecycle Management phases used in eMagiz can be found in [[this>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-intro-the-five-phases-of-emagiz||target="blank"]] microlearning. Discovery of the integration landscape is very important and should be handled by experienced staff.
3 3  
4 4  Should you have any questions, please get in touch with academy@emagiz.com.
5 5  
... ... @@ -25,7 +25,7 @@
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 +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. It is recommended to fill out all documentation available in this phase, to ensure smooth development throughout the next 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?
... ... @@ -45,7 +45,7 @@
45 45  
46 46  == 5. Design ==
47 47  
48 -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 Capture phase, and several cloud components are specified. When you start working in the design phase, you should ask yourself the following questions:
48 +After the Capture phase, you will move to the Design phase. In the Design phase, the system message definitions are created, and the transformation mappings are drawn. The client infrastructure is determined in this phase, and several cloud components are specified. When you start working in the design phase, you should ask yourself the following questions:
49 49  * What should my data model look like?
50 50  * What message definitions are needed?
51 51  * Which message formats are required?