Changes for page Business case

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Business case
	1	+crashcourse-apigw-exercises-businesscase

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.eMagiz

Content

...	...	@@ -1,7 +1,6 @@
1		-{{container}}
2		-{{container layoutStyle="columns"}}(((
3		-With this exercise, we start our journey into the eMagiz platform. This exercise will explain the business case used throughout all exercises linked to this Crash Course. In the following exercises, we will guide you step by step through the platform so you can learn how to use it.
4		-
	1	+{{container}}{{container layoutStyle="columns"}}(((
	2	+With this exercise, we start our journey into the eMagiz platform. This exercise will explain the business case used throughout all exercises linked to the Crash Course Platform Course. In the following exercises, we will guide you step by step through the platform so you can learn how to use it.
	3	+
5	5	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6	6
7	7	== 1. Prerequisites ==
...	...	@@ -10,18 +10,26 @@
10	10
11	11	== 2. Exercise ==
12	12
13		-To kickstart your journey into the eMagiz platform, we have selected a set of exercises linked to the Crash Course API Gateway course that will guide you through the platform, from an API perspective, in building and validating your first integration. To start things off, we will introduce the business case in this exercise that will be used to model out the correct solution in eMagiz.
	12	+To kickstart your journey into the eMagiz platform, we have selected a set of exercises linked to the Crash Course Platform course that will guide you through the platform in building and validating your first integration. To start things off, we will introduce the business case in this exercise that will be used to model out the correct solution in eMagiz.
14	14
15	15	=== 2.1 Business Case ===
16	16
17	17	**Read and understand the following business case**
18	18
19		-As Dream Inc., we supply custom-made dream events for our customer base. Our customers enter orders (i.e., bookings) into our "state of the art" website. From then on, we need to communicate directly with our backend systems and provide information to the customer who entered the booking. On top of that, we have additional functionality to enhance the experience. This extra functionality allows us to report specific information to the client before the dream events truck shows up at the event location. To make this happen, we need to communicate to our own Order Management System that handles the orders (i.e., bookings) and stores metadata information on what truck is going to which event. The external company that supplies the people for the "dream event" must also retrieve the carrier information to be in time for the "dream event" at the correct location. See below for specifications.
20		-
	18	+As eMagiz Ltd. we want to directly receive information from three external sources (FMS, OMS and Country Validator). We expect to get an immediate response in both success as well as failure cases. See below for specifications per system which provide data to the user eMagiz
	19	+* FMS
	20	+ ** Retrieve Invoice Information
21	21	* OMS
22		- ** Retrieve carrier information. This information is relevant to understand what color the truck is on which the order is placed.
23		- ** Send order. Clients can directly submit orders to eMagiz Ltd. in a digital manner
	22	+ ** Retrieve carrier information
	23	+ ** Retrieve parcel status
	24	+* Country Validator
	25	+ ** Retrieve ISO3 code
24	24
	27	+=== 2.2 Model Capture phase ===
	28	+
	29	+Please translate the above business case to a valid Capture phase.
	30	+
	31	+== 3. Solution ==
25	25
26		-)))((({{toc/}}))){{/container}}
27		-{{/container}}
	33	+
	34	+)))((({{toc/}}))){{/container}}{{/container}}