Changes for page Discovery
Last modified by Danniar Firdausy on 2024/08/20 15:09
From version 40.1
edited by Erik Bakker
on 2024/08/08 15:24
on 2024/08/08 15:24
Change comment:
There is no comment for this version
To version 43.1
edited by Erik Bakker
on 2024/08/08 15:27
on 2024/08/08 15:27
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -23,7 +23,7 @@ 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 -== 4. Capture ==26 +=== 3.1 Capture === 27 27 28 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 ... ... @@ -48,7 +48,7 @@ 48 48 49 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 -== 5. Design ==51 +=== 3.2 Design === 52 52 53 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? ... ... @@ -65,13 +65,13 @@ 65 65 66 66 Several more questions may be relevant. Documentation on development in the design phase can be found in the [[Crash Course Platform>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]. 67 67 68 -== 6. Key takeaways ==68 +== 4. Key takeaways == 69 69 70 70 * Discovery concerns the design of the integration landscape. 71 71 * An establishment of technical requirements is necessary before continuing with discovery in eMagiz. 72 72 * The Capture & Design phases are used to discover the integration landscape in eMagiz. 73 73 74 -== 7. Suggested Additional Readings ==74 +== 5. Suggested Additional Readings == 75 75 76 76 * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] 77 77 ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]