Changes for page Discovery

Last modified by Danniar Firdausy on 2024/08/20 15:09

From version 13.1
edited by Carlijn Kokkeler
on 2023/09/06 14:03
Change comment: There is no comment for this version
To version 15.1
edited by Carlijn Kokkeler
on 2023/09/06 14:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -43,6 +43,18 @@
43 43  
44 44  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.
45 45  
46 +== 5. Design ==
47 +
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 +* What should my data model look like?
50 +* What message definitions are needed?
51 +* Which message formats are required?
52 +* How should the message mapping be done?
53 +* What should the architecture (incl. instances, machine sizes, etc.) be like?
54 +* What metadata needs to be stored?
55 +
56 +Several more questions may be relevant. Documentation on how to develop in the Design phase can be found in the [[Crash Courses>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.||target="blank"]].
57 +
46 46  === 3.1 What is a data model ===
47 47  
48 48  A data model is a visual representation of how a system has structured its data. With the help of a data model, you can show the relationships between entities and define the attributes on the entity level. See below for a small example of a data model.