Changes for page Discovery

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -15,11 +15,46 @@
15	15
16	16	== 3. Technical requirements ==
17	17
18		-Before entering the Capture phase, several technical requirements need to be considered. First of all, it needs to be discussed who will provide data and who will consume data. Secondly, the exact definition of the data elements that will be exchanged has to be obtained. Thirdly, the size of the data packets needs to be established, as well as the frequency of the packets. Lastly, it has to be considered what constraints with respect to connectivity have to be in place.
	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.
	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.
19	19
20		-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"]] (https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Microlearnings/Crash%20Course/Crash%20Course%20Platform/crashcourse-platform-intro-technrequirements) microlearning.
	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.
21	21
	26	+== 4. Capture ==
22	22
	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	+
	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	+
23	23	=== 3.1 What is a data model ===
24	24
25	25	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.