Skip to Content

Changes for page Discovery

Last modified by Danniar Firdausy on 2024/08/20 15:09
From version 12.1
edited by Carlijn Kokkeler
on 2023/09/06 13:59
Change comment: There is no comment for this version
To version 13.1
edited by Carlijn Kokkeler
on 2023/09/06 14:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,7 +23,26 @@
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 26  
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 +
30 +When you want to create your systems, you need to ask yourself the following questions:
31 +* What systems are relevant in our business case?
32 +* What is the purpose of each system?
33 +* What should each system be called?
34 +* What should be the default integration pattern for each system?
35 +
36 +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.
37 +
38 +When you want to create an integration, you need to ask yourself the following questions:
39 +* What is the purpose of this integration?
40 +* What should be the direction of this integration?
41 +* What should this integration be called?
42 +* Which integration pattern belongs to this integration?
43 +
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 +
27 27  === 3.1 What is a data model ===
28 28  
29 29  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.